NW 6.5 upgrade considerations

[organman]

Hi !
I'm about to upgrade two NW 5.1 SP6 eDir 8.7.0 servers to NW 6.5 SP2.
I have a few questions regarding this upgrade.

Server GRPW has the master replica and certificate server (also runs Groupwise 6.5) and I intend to upgrade this server first, in-place upgrade on the current hardware.

Server SH01 has r/w replica and also runs ZEN 4 but old hardware so I will have to migrate this server to new hardware, I will be using the migration wizard for this.

Would it be best to upgrade server GRPW first and the migrate server SH01 ?

What will happen to eDir after/during the upgrade, GRPW will have eDir 8.7.3 after the upgrade but server SH01 will have ver. 8.7.0 until it's migrated, will this be a problem ?

Server SH01 uses traditional volumes with compression but on the new hardware I will be using NSS volumes without compression, will this be a problem during migration ?

Regards
L-G Nihlman

 

[terry712]

make sure you use the latest migration wizard

on your backup for sh01 make sure you check the crc . pending on backup you can tell this not to backup compressed. there is no probs migrated from trad compressed to nss uncompressed - the migrate copy part is hideously slow though

ds isnt a prob - just get them to same level when all settled

i prefer to do the master first but i think opions are devided on this

the zen 4 - you have to do something with the java - cant remeber what but is easy enough to fix

remember on the in place - patch the firmware of the server - most people never look at firmware

 

[organman]

What about timesync ?

I'm thinking like this:
When I have completed in-place-upgrade of server GRPW (wich also is the time server in the network)and the starts the migration of server SH01 (using migration wizard) I assume that network time will be critical.

I think there will be a problem if the new SH01 server has a time seting that is ahead of server GRPW.

So should I ensure that the clock in the new HW is not ahead of time of server GRPW before I start migration ?

Or will Migration wizard also synchronize time ?

 

[LawnBoy]

Get SH01 close on time (+- 2-3 minutes) and it will be alright. After install configure it as a secondary and it will sync right up.

 

[ITsmyfault]

FWIW
We did the eDir upgrade first so everyone was on the same page. (went 5.1 SP6 to 6.5 Sp1 at the time) just to make sure we had no sync or time issues.

 

[terry712]

the migration stop and tells you about the time

if it's out - it tells you to correct it
with only two servers it's not that big a deal as long as it's not miles out

last thing you want is synthetic

the time will sync as long as it's setup properly just now
i prefer to set one to an external ntp - and then set all others to only go to this source (been bitten before with synthetic)

 

[marvhuffaker]

I've migrated systems straight from 4.11 to 6.5 with numerous systems in the tree and never had a problem with the different versions of NDS. I've also migrated from 5.x to 6.x with hundreds of servers in the tree and never had issues between DS v7.62 and eDir v8.7.3.

Biggest blunders I've seen people make:

- Just dont' forget to pop the CD into your workstation and extend the schema (prepare tree for upgrade) before you actually do the upgrade. That is something a lot of people overlook.

- Get your timesync in check before you do anything. Easy way to get them in sync is make one the SINGLE time source, then make the other the SECONDARY and provide the first one as the source.

- Get DS v7.62 on your servers and make sure they are functional before you try to migrate them.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support

 

[brichr]

I built a few test 6.5 sp2 servers and I seem to be having problems with the server not allowing authentication to its web utilities. iMon, iMan and Remote manager type of pages. I can log into the server no problem with the client, and I get all my drives mapped. But it just so happens that I was installing it specifically for those web tools. Im going to try the beta nw65sp3 patch this week.

Also, I have heard that Novell wont be supporting 6 for very much longer so it you have to upgrade you might as well go ahead and go to 6.5. Other than those login problem the server seems to be awesome.

 

[marvhuffaker]

brichr, That patch probably won't help you. There are ways to make those web utilites work with just your username and password, but i'm guessing if you tried your full nds name you could get in.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support

 

[brichr]

Not so my friend. These tools worked just fine for about one day and then stop working all the sudden. Not a license issue either I have plenty. Also, I am well aware of logging in using the full naming conventions.

Im trying the patch today.

BC
CNE, CCNA

 

[brichr]

The other thing that is funny is that I can login with no problems to Remote Manager from the X server console. I use the exact same credentials as I try from my LAN computers. SO I know the userID/passwords are working.

 

[organman]

Thanx for your input on this question !

I've done a test upgrade in my lab network but I have not yet migrated the other server.
However it's very important to enable LDAP port 636 before starting the in-place-upgrade.

If this is not done, there will be problems with TOMCAT after the upgrade, I had problems with iMonitor.

When using Deploy Manager and running "Prepare for New eDirectory" everything looks OK, but when running the Health Check in Deploy manager I got two warnings.
SSL Transfer and Extend Schema got warnings but I ignored them and continued with the upgrade.

Everything seems to work fine.

/lgnihlman