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.
djbrightman1 Absent Member.
Absent Member.
1357 views

SLE9/OES1SP2 32bit -> SLE10/OES2SP1 64bit - Tranfer ID?

Hi

Just contemplating a server replacement.
OS change would be SLE9/OES1SP2 32bit -> SLE10/OES2SP1 64bit

Ideally we would like to maintain name and edirectory references, etc.
Should the Migration Tool handle this OK? Any possible issues with eDir/keys, etc. given the change in architecture?

Anyone done this and found any gotchas?!?

Thanks

David
Labels (1)
0 Likes
3 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: SLE9/OES1SP2 32bit -> SLE10/OES2SP1 64bit - Tranfer ID?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The migration from OES 1 to OES 2 should be handled by the migration tool
I believe. Does the documentation state otherwise? I have not done this
myself, not. Have backups just in case and if nothing else things can be
restored.

Good luck.





djbrightman wrote:
> Hi
>
> Just contemplating a server replacement.
> OS change would be SLE9/OES1SP2 32bit -> SLE10/OES2SP1 64bit
>
> Ideally we would like to maintain name and edirectory references, etc.
> Should the Migration Tool handle this OK? Any possible issues with
> eDir/keys, etc. given the change in architecture?
>
> Anyone done this and found any gotchas?!?
>
> Thanks
>
> David
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJKOkdKAAoJEF+XTK08PnB5XVUQAMTW2H2mllwmpGFhSleDqlU8
IpWgK+0MDzglzbq3RAnb8/hkw8untTjIJkmykHU0Gdaw13WczJKOq4boQFMSChdP
eunfbkP9tfd2qKPvIQwff2SfMl0FxoqVAyHyvUxwvx3nqHQEXBYp/HWEJPG9toSD
ay9jWoYQKaNIrNURlDVP8AuJU4j1HbNIuUf7AvvwsRGLoWKTj1IecNDR/rpKQG0+
nAf99NoWDpeH0zscNY92VobRTmuGiaTPjBbwJr9cUQRnTeVxspnGlEGWv+zZc4++
coco6fxZQ4YuDPl+IOtnvK260Xq9c9K08BZ7E6g+8frRneYYdkJHKNyyq7DS52Qq
MREJtBojcwbTpGZRcha6HDZqqdQNO6cq0kdLO3O9wiIWfo/vAaW7XVP/NxtE2tHl
wrmSx2bv+Qb3BQ9oUdLqEDm09l7qti7RB1D2CGhcUr4juPbkaH8rdJiSgLASBZ7X
hRjAKvKaEcIFBsinUp/nUh5fviRbwi28yd/m5ZsCu61W66l7sErMOJC1rgNg+tfl
MJXHPK7IeBclhMFeFPmOrI2xNGwddHQQYEV6WgnNHz0AMEJAXKXgZ/gBC48zjJLR
6GDrZbMKu5+8biNVVuxy0qXl8JYsAM/BFsV8yZve1tRLsxY7pTF2KEvxtF2ff9nP
xtp8hdWAtu3Pp0ARKnLt
=cyZP
-----END PGP SIGNATURE-----
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: SLE9/OES1SP2 32bit -> SLE10/OES2SP1 64bit - Tranfer ID?

djbrightman wrote:

>Ideally we would like to maintain name and edirectory references, etc.
>Should the Migration Tool handle this OK? Any possible issues with
>eDir/keys, etc. given the change in architecture?


Like ab already indicated, the GUI migration tool form OES2SP1 will handle
this scenario. A few important recommendations:

1) Thouroughly read the migration tool doclumentation, especially the
chapters dealing with the services you are gonna migrate and the part
about the ID swap:
http://www.novell.com/documentation/oes2/mig_tools_lx/index.html?page=/documentation/oes2/mig_tools_lx/data/bookinfo.html#bookinfo

2) While this is mentioned in the documention, I will mention it here
again because many people oversee it as the procedure is wuite different
from NetWare to NetWare migrations in the past:
- the destination server has to be installed in the production tree in the
same context as the source server using a different name
- during the selection of OES2 services to install, you *must* select the
premigration pattern
- before starting the migration, the destination server *must* have all
services installed that you want to migrate

3) It is essential that both your source and destination servers are fully
patched. That means the source server must be OES1 SP2 with the latest
patches from the channel and the destination must be running OES2 SP1 also
with the latest patches form the patch channel. This is essential because
on the source server, some services like eDirectory, NSS and SMS must be
on the latest versions in order for the migration to work reliably. On the
destination server, it is even more important to have the latest patches
installed because with the initial release of the GUI migration tool in
OES2SP1, there were so many bugs int he tool that it hardly ever worked
currecty. Just a couple of weeks ago, updated versions of the components
used by the migration tool were released on the patch channel and these
include *many* essential bug fixes that make the tool usable.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
djbrightman1 Absent Member.
Absent Member.

Re: SLE9/OES1SP2 32bit -> SLE10/OES2SP1 64bit - Tranfer ID?

Thanks for that. I'm in the process of creating the scenario in our test lab, so shall model there first.
Cheers

David
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.