DST issues? For OES2 to OES11 upgrade?

Question

Hi all
I have a client with DST working well on a couple of OES2 sp3 64-bit
servers on vSphere 5.0
Does anyone here have any experience with such upgrades?
I'd be pretty sure that the one upgrade path of just rebinding the NSS
volumes to new servers would be more grief than is worth it. I'd also
like to avoid the server migration option just because of how much data
is involved, not even sure if we have enough extra space to go this
route, plus from our experience with Migrating from NW6.5 to these
boxes in the beginning (OES2 sp1 at the time) did NOT understand DST on
the destination.
Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php?userid=75037
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

Answer 1

Originally Posted by konecnya
Hi all
I have a client with DST working well on a couple of OES2 sp3 64-bit
servers on vSphere 5.0
Does anyone here have any experience with such upgrades?
I'd be pretty sure that the one upgrade path of just rebinding the NSS
volumes to new servers would be more grief than is worth it. I'd also
like to avoid the server migration option just because of how much data
is involved, not even sure if we have enough extra space to go this
route, plus from our experience with Migrating from NW6.5 to these
boxes in the beginning (OES2 sp1 at the time) did NOT understand DST on
the destination.
Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
View Profile: konecnya - Novell Forums
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
We just went through a round of upgrades from OES2 SP3 (physical) with and without DST to OES11/SP1 on VMware
Now, given your particular setup, I'd think you could be fine with moving the disks. In our case, we needed to do ID transfers, and that could still be done. Setup your target OES11 SP1 VM, do your iPrint, DHCP, etc. migrate them (just not the file services). Do the ID transfer. Power off source VM. "move" the NSS disks (I'm ASSUMING the NSS disks are separate VMware virtual hard disks) to the new OES11 box and voila.
The only gotcha that I can think of:
I BELIEVE that if you stored the disks with the virtual machine (default I believe), you have to be VERY VERY careful to NOT "delete from disk" when you remove the OES2 Guest, as I think it'll delete the entire underlying directory which is now where your disks are
In other words, if you SCP or something to the ESXi host and look at the directory/file structure it'll be something like:
\OES2-Guest\bunch of .vmdk files
\OES11-Gust\bunch of .vmdk files
When you "move" the virtual disks from OES2-Guest to OES11-Guest, it's just pointing to the:
\OES2-Guest\nssdisk.vmdk files
You could manually move them around I believe if you want to maintain the proper directory structure.
Personally that would probably be the biggest time saver for you.
Otherwise you COULD migrate the file systems with DST but there's some scenarios/caveats involved with that.
Let me know if you choose the route to actually migrate the DST file systems and I'll explain further.
But, if it were me, and I had them on VMware, I'd just "move" the disks around.