UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Commander
Commander
995 views

A few migration questions

I am needing to move an OES 11SP1 server to new hardware. This server is
used for quite a few things and I am concerned the migration utility
might not be able to move everything. The server is handling:

Novell DNS
SLP DA
traditional DHCP
master replicas for many partitons
NSS volume
CA for the tree
iManager
authentication source for Zen 11.2
NTP time source
rsync

Based on what I am reading in the docs, the DNS server has to be
manually moved using the java console prior to the actual migration. I
cannot find any docs on moving the CA but there's a TID that suggests
doing a backup/restore but it is a little dated. Does the CA get moved
as part of the migration/transferID?

The NTP, SLP, rsync and DHCP stuff will not be an issue.

Does anyone see anything that is going to cause me problems? I moved
iPrint off this server to a VM using consolidation and it did not go
smoothly, I am hoping the TransferID migration is better.

Thanks
Buster Flynn
Sevier County Schools
Labels (1)
0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Hi Buster,

I use TID 3618399 for moving the CA - the first part is relevant, the second part, if you've lost your CA through server crash isn't. As far as I know this is the only way to move a CA.

Partitioning and replication is as simple as adding all the necessary replica's to the new server (read/write) and then promote them to master.

I'll let the guru's comment on the rest.

Best of luck 🙂

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Buster1234;2257253 wrote:
I am needing to move an OES 11SP1 server to new hardware. This server is
used for quite a few things and I am concerned the migration utility
might not be able to move everything. The server is handling:

Novell DNS
SLP DA
traditional DHCP
master replicas for many partitons
NSS volume
CA for the tree
iManager
authentication source for Zen 11.2
NTP time source
rsync

Based on what I am reading in the docs, the DNS server has to be
manually moved using the java console prior to the actual migration. I
cannot find any docs on moving the CA but there's a TID that suggests
doing a backup/restore but it is a little dated. Does the CA get moved
as part of the migration/transferID?

The NTP, SLP, rsync and DHCP stuff will not be an issue.

Does anyone see anything that is going to cause me problems? I moved
iPrint off this server to a VM using consolidation and it did not go
smoothly, I am hoping the TransferID migration is better.

Thanks
Buster Flynn
Sevier County Schools


To answer your question about the CA:

If you use the ID Transfer option for migration, the entire eDir DIB set, including the CA is moved/transferred.
However, it never hurts to make a backup manually

Note:
You do NOT want to manually transfer it to the new server and then do an ID Transfer, as the "new" server will be totally overwritten and that would be bad.

So basically:

Either use ID Transfer
OR
manually move (and NO ID Transfer)

I use ID Transfer quite a lot, and it usually works pretty well. Usually if there's a problem it's with LUM (go figure).
I also use ID Transfer to do paravirtualize to VMware migrations (since my experience with the "unsupported" tools to do such have been only 50/50)

There's no migration utility for SLP (you can see my signature for a link to my OES2 guides which SHOULD have a link somewhere to how i migrated SLP).
DNS is as you pointed out, special.

NTP I don't think gets migrated, but in OES, it's basically "point to this server(s) here", so as long as you use the same IP you're okay.
rsync is manually migrated.

Based upon what you posted above, I'd say ID transfer will basically be your best bet as that'll give you a new server with same name, IP, volumes, etc. and you only need to "manually" migrate/configure:
DNS
SLP
DHCP (yes, even with ID transfer, I THINK you need to adjust DHCP manually or something with the Console). But that's covered in the docs for DHCP/Migration.
rsync

I'd probably shut off the ZCM services while you do the migration.
0 Likes
Micro Focus Contributor
Micro Focus Contributor

For SLP, refer OES11 SP1: Migration Tool Administration Guide @ Novell Documentation
Refer chapter V11 - 31.0 Migrating OpenSLP to OES 11 SP1
Only a few steps which can be handled easily!!

-Ramesh
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

mvramesh;2257734 wrote:
For SLP, refer OES11 SP1: Migration Tool Administration Guide @ Novell Documentation
Refer chapter V11 - 31.0 Migrating OpenSLP to OES 11 SP1
Only a few steps which can be handled easily!!

-Ramesh


Thanks Ramesh. Of course, that only works if you're going OES2/OES11 to OES2/OES11. (which the OP is actually doing)
If you're going from NetWare SLP To OES/OpenSLP it's more involved

Although if it's that simple (OES to OES) why not put that in the miggui?

Just a question.
0 Likes
Micro Focus Contributor
Micro Focus Contributor

kjhurni;2257814 wrote:
Thanks Ramesh. Of course, that only works if you're going OES2/OES11 to OES2/OES11. (which the OP is actually doing)
If you're going from NetWare SLP To OES/OpenSLP it's more involved

Although if it's that simple (OES to OES) why not put that in the miggui?

Just a question.


I will take that request!!
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.