Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
bertbrand Absent Member.
Absent Member.
1241 views

Phased migration from NW 6.5 to OES2

Am planning on doing a phased migration of a server running NW 6.5 SP7 to OES2 Linux. Current server is running Groupwise 7, Zenworks 7, eDir 8.7.3.9 and also holds the master replica (they have another server in same tree located in another office).

Here's what I am planning to do, but just want to make sure all OK - suggestions welcome:

- Have new Dell server and will create 2 logical partitions - one for SLES system stuff (about 60gb) and the other for NSS (about 1.5tb). RAID5

- Will partition /boot, /, /swap, /opt, etc.

- Install SLES 10, OES (during main install) and place new server in current tree.

- I'd like to migrate certain folders (users, share, etc.) in phases, keeping user rights once moved. As I do this, I would change the login script mapping to point to new server.

- Once regular user data over, migrate Groupwise.

- Install Zen Config Mgr from scratch, as they currently don't use it for much. But they will once installed/set up.

- Install Teaming

- Decommission NW 6.5 server

- I still want users to get same mappings as they currently have. Basically want to switch them to new server without any real disruptions/changes.


Some question/comments:

- Now that SLES 10 SP3 and OES2 SP2 are out, should I just go ahead and use those? Seems easier than upgrading later. Need it to be stable though.

- How critical is time when adding OES to tree? Detailed suggestions during install? (please)

- Regarding moving folders in phases, that OK?

- New server will have 16gb RAM. 2gb swap OK? Or ???

- Once old NW 6.5 server decommissioned, OK for Windows clients to still use NW client?

thanks!
Labels (2)
0 Likes
6 Replies
Brunold Rainer
New Member.

Re: Phased migration from NW 6.5 to OES2

Bert,

Have new Dell server and will create 2 logical partitions - one for SLES system stuff (about 60gb) and the other for NSS (about 1.5tb). RAID5


Perfect ...

Some question/comments:

- Now that SLES 10 SP3 and OES2 SP2 are out, should I just go ahead and use those? Seems easier than upgrading later. Need it to be stable though.


Yes use that because if you get any problems and would need to talk to Novell support they will ask for updating the server to the latest version. Before doing the installation, make sure all other components you need (ZCM, GW) support that version

- How critical is time when adding OES to tree? Detailed suggestions during install? (please)


It's critical as it is on the Netware box. You can either point the OES Linux box to the Netware box as the time server or use the OES Linux server as the time server for the Netware box. Then both will be time synced. During th installation you get a specific screen where you can add the time server. There add the Netware server ip ... Later on you can decide if you want to have the OES Linux box the master time server and switch that.

- Regarding moving folders in phases, that OK?


Yes, it is ...

- New server will have 16gb RAM. 2gb swap OK? Or ???


Yes it is, if you have enough disk space make it 4GB but in general the system should not swap too much as you would get other problems with that and therefor 2 GB should be enough.

- Once old NW 6.5 server decommissioned, OK for Windows clients to still use NW client?


Yep, just make sure you have at least 4.91 SP5 on them

Another side note on the steps about installing, moving the first stuff over and adding more services to it ...

I would install the server and install all applications and do a quick test with them before switching over any user data. If you have user connected to this system and ZCM or whatever make problems during the installation you might have server downtime when you need to reboot or install additional stuff. Therefor install everything and then switch over.

Also take care that before shutting down the Netware box you might need to check a few configurations on the OES Linux box. During the installation it might point for some ldap applications to the Netware box and if that is shutdown you might need to point them to the OES box itslef. LUM might be such a application.

You might also need to move the CA from the Netware box over to the Linux box.

Rainer
0 Likes
bertbrand Absent Member.
Absent Member.

Re: Phased migration from NW 6.5 to OES2

Thanks Rainer

This will be phased in over a few weeks, so I can add ZCM, etc. on the weekends.

Good to know about decommissioning old server and making sure apps work with SLES10-SP3/OE2-SP2.

One more thing - can you recommend sizes for (based on 60GB logical):

swap = 4gb
/ =
/opt =
/var =
/usr =
/srv =
others?

Again, thanks for the prompt reply

Bert

brunold;1895804 wrote:
Bert,



Perfect ...

Some question/comments:



Yes use that because if you get any problems and would need to talk to Novell support they will ask for updating the server to the latest version. Before doing the installation, make sure all other components you need (ZCM, GW) support that version



It's critical as it is on the Netware box. You can either point the OES Linux box to the Netware box as the time server or use the OES Linux server as the time server for the Netware box. Then both will be time synced. During th installation you get a specific screen where you can add the time server. There add the Netware server ip ... Later on you can decide if you want to have the OES Linux box the master time server and switch that.



Yes, it is ...



Yes it is, if you have enough disk space make it 4GB but in general the system should not swap too much as you would get other problems with that and therefor 2 GB should be enough.



Yep, just make sure you have at least 4.91 SP5 on them

Another side note on the steps about installing, moving the first stuff over and adding more services to it ...

I would install the server and install all applications and do a quick test with them before switching over any user data. If you have user connected to this system and ZCM or whatever make problems during the installation you might have server downtime when you need to reboot or install additional stuff. Therefor install everything and then switch over.

Also take care that before shutting down the Netware box you might need to check a few configurations on the OES Linux box. During the installation it might point for some ldap applications to the Netware box and if that is shutdown you might need to point them to the OES box itslef. LUM might be such a application.

You might also need to move the CA from the Netware box over to the Linux box.

Rainer
0 Likes
Brunold Rainer
New Member.

Re: Phased migration from NW 6.5 to OES2

Bert,

here are the sizes of our linux volumes ffrom the oes server:

This three partitions are primary partitions, not part of a logical volume:

/boot = 300mb (first partition on the disk, no lvm)
swap = 4gb (second partition on the disk)
/ = 10gb (third partition on the disk, no lvm)
the rest of the 60gb should be used for a volume group

The next are just logical volumes in that volume group which allows to increase the size afterwards very easy:

/var = 10gb but depends on applications that might need additional space
/tmp = 2gb

For the other three directories it depends if you have applications that place some data there in. In our case (no zcm) they are just part of the / filesystem. Best would be to check the installation documentations for the additional applications to see where they put their data. It is also possible to keep them right for the beginning as part of the / and create another logical volume for them later on when you see that you really need it.

/opt
/usr
/srv

Rainer
0 Likes
bertschj Absent Member.
Absent Member.

Re: Phased migration from NW 6.5 to OES2

Thanks for that

Will it be a problem if / is part of LVM? /boot and swap are not.

I installed it that way this last weekend.


brunold;1897791 wrote:
Bert,

here are the sizes of our linux volumes ffrom the oes server:

This three partitions are primary partitions, not part of a logical volume:

/boot = 300mb (first partition on the disk, no lvm)
swap = 4gb (second partition on the disk)
/ = 10gb (third partition on the disk, no lvm)
the rest of the 60gb should be used for a volume group

The next are just logical volumes in that volume group which allows to increase the size afterwards very easy:

/var = 10gb but depends on applications that might need additional space
/tmp = 2gb

For the other three directories it depends if you have applications that place some data there in. In our case (no zcm) they are just part of the / filesystem. Best would be to check the installation documentations for the additional applications to see where they put their data. It is also possible to keep them right for the beginning as part of the / and create another logical volume for them later on when you see that you really need it.

/opt
/usr
/srv

Rainer
0 Likes
bertschj Absent Member.
Absent Member.

Re: Phased migration from NW 6.5 to OES2

Thanks for that

Will it be a problem if / is part of LVM? /boot and swap are not.

I installed it that way this last weekend.


brunold;1897791 wrote:
Bert,

here are the sizes of our linux volumes ffrom the oes server:

This three partitions are primary partitions, not part of a logical volume:

/boot = 300mb (first partition on the disk, no lvm)
swap = 4gb (second partition on the disk)
/ = 10gb (third partition on the disk, no lvm)
the rest of the 60gb should be used for a volume group

The next are just logical volumes in that volume group which allows to increase the size afterwards very easy:

/var = 10gb but depends on applications that might need additional space
/tmp = 2gb

For the other three directories it depends if you have applications that place some data there in. In our case (no zcm) they are just part of the / filesystem. Best would be to check the installation documentations for the additional applications to see where they put their data. It is also possible to keep them right for the beginning as part of the / and create another logical volume for them later on when you see that you really need it.

/opt
/usr
/srv

Rainer
0 Likes
Brunold Rainer
New Member.

Re: Phased migration from NW 6.5 to OES2

Bert,

Will it be a problem if / is part of LVM? /boot and swap are not.


no, it is also no problem with that. During this year there were many threads in the forums where people used evms on the boot disk and that made sometimes problems when system updates were applied. But havn't heard of such problems when using lvm, therefor you should be on a good path.

Rainer
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.