Nlv gw8

From CoolSolutionsWiki

Contents

[edit]

summary of mentoring work done (completed Mid July 09)

  1. Assisted customer remotely in the pros/cons of design decisions.
  2. verified correct build checklists, including disk IO performance
  3. Drove the Primary Upgrade process and helped resolve bumps in the road.
  4. Drove the creation of a GW 8 Post Office to pilot users and work through issues before full deployment.
  5. Due to power outage, minor and major PO was running on RELOAD in DR mod. PSE went onsite to help migrate minor PO off RELOAD server onto a GW 8 server...to help with the overloaded RELOAD server, which was having performance issues. Helped resolve post migration "bumps in the road" issues.
    1. bumps in the road
      1. Reload not coping all msg and offiles to destination server!!! used rsync -avu to sync files to destination server
      2. IP MAC address war. Had to aggresively remove sysconfig/network/ifcfg-macADDR file and restart the network service on that server...w/o interupting the large PO.
      3. GW 8 HP1 didn't copy many ofview files. Got from GW 7 PO and pilot po's ofview files
  6. Ran out of "mentoring hours" after going onsite to assist in emergency migrate mid-sized PO off RELOAD to destination server.
  7. We found that moving 2-3 users at a time was problematic, and that bulk moving users (given emergency) worked well.
  8. We SUCCESSFULLY migrated the Primary and mid-sized Post Offices to GW 8 before running out of hours.
[edit]

key goals

  1. support customer in successfully upgrading GW 7.0.3 to GW 8 on Linux
    1. support means coaching/advising and helping make decisions on a plan (plan to be developed by customer and reviewed by support).Also, in the event of a problem related to project help customer resolve the issue.
  2. implement pre-upgrade best practices/recommendations
  3. keep costs down, by being flexible and primarily doing phone/remote control
  4. review from experienced support engineers to avoid known issues and common impact events


[edit]

phase 1 planning/deciding

  1. get approval and cost quote on 16 hours
  2. environment review (quickly) to aid in planning
  3. brainstorm major steps in upgrading/migrating
    1. get management commitment to get a manageable PO (expire/reduce with gw caching AND/or split PO)
    2. what the new system should look like
      1. hardware/software/config
        1. OES?
        2. stand alone? - yes if reload is enabled
        3. SAN - fiber?
        4. restore area server/gwava reload available in the event PO server crash?
  4. build new system and new PO and GW move users to pilot VS copy all DBs and startup on Linux
[edit]

phase 2 building

  1. build server to discussed specs
  2. test IO
[edit]

phase 3 implement/pilot

[edit]

troubleshooting user moves

  1. http://www.novell.com/documentation/gw8/gw8_admin/?page=/documentation/gw8/gw8_admin/data/abps0an.html#aj6re00
  2. http://support.novell.com/techcenter/articles/anz20021101.html


[edit]

TASK LIST

  1. server build checklist!
    1. X NTP
    2. X static IP
    3. X validate disk IO
      1. gws3:/gw # time dd if=gw800.tar of=gw800san2san.tar
      2. 1040420+0 records in
      3. 1040420+0 records out
      4. 532695040 bytes (533 MB) copied, 2.92761 seconds, 182 MB/s
    4. X configure SAN storage
  2. X migrate MTA – split off paired/links to disk so the MTA can go on its own node. Upgrade primary to gw 8.
  3. WIP create GW 8 PO on linux – evaluate/test
    1. NEXT STEPS (July 7, 2009) read up on migrating gw 7 po to gw 8 on linux po
      1. test 5 users this week, then add 30 more users next week. Test gw7 and gw 8 clients. have the pilot eval go as long as you feel or your organization has proved in the past to flush out any significant issues.
      2. Read and understand: upgrading and verifying edir schema
      3. GroupWise migration utility - use it to migrate PO from NW to Linux
      4. OR manual way if fine too, but don't forget to run the stand alone gwcheck against the PO PRIOR TO UPGRADING/MIGRATING: storelowercase
      5. create another domain to serve as the primary Domain w/o any GW agents hanging off of it.
  4. move the 400 users off IF the users move good. IF it goes well...move lots if it doesn't go well, bulk move with reload.
  5. Manual rolling migration from NW to linux. Do one PO at a time.
  6. secure NFS to only the reload server's ip address
[edit]

operations completed

  1. July 6: moved primary MTA to linux
    1. challenges
      1. needed to run the dbcopy -m for migrate to linux
      2. installed fine, but PO could NOT talk to new primary
  2. July 7:created new GW 8 PO
    1. challenges
      1. US02MLS1.VEW missing from GW 8 view directory, found on gw 7 directory and copied to gw 8 po and fixed it.
  3. July 7: started configuring reload, including nfs


http://www.novell.com/communities/node/6771/consultants-corner-upgrading-groupwise-8-part-1-consoleone-schema-sdd

[edit]

helpful commands/opps

  1. netstat -na | grep 1677
  2. rcgrpwise status
  3. rcgrpwise postoffice.domain stop or start
  4. ps aux | grep gwpoa
  5. ps aux | grep gwmta
  6. /opt/novell/groupwise/agents/bin/gwmta --show @ /opt/novell/groupwise/agents/share/city_nlv.mta
  7. rcgrpwise stop gwpo1.city_nlv
Retrieved from "http://wiki.novell.com/index.php/Nlv_gw8"