Highlighted
tpr520 Absent Member.
Absent Member.
1929 views

Migrate to new platform and hardware

We are planning to migrate from NW 6.5 SP8 physical servers with fiber san storage to OES2 Linux in VI3 environment connected to EQ iscsi storage, and I'm looking for suggestions. My current half baked plan is this-
- create iscsi target on EQ and attach to current Netware servers
- create new volumes on EQ and mount on phys servers
- use VCU to copy content from old nss volumes to new ones
- dismount old volumes and rename new ones with old names
- create pre-migration Netware VMs and migrate to them from phys servers
- Let dust settle
- Create OES Linux VMs and migrate to them from Netware VMs

Also, will run trustee.nlm and make sure I have good backups to tape. Does this sound right, or am I creating a lot of unnecessary work? Thanks.
Labels (2)
Tags (1)
0 Likes
9 Replies
Marcel_Cox Absent Member.
Absent Member.

Re: Migrate to new platform and hardware

I consider your procedure unnecessarily complicated. I don't see the point in migrating your NetWare server from physical to virtual before migrating to Linux. I would simply skip that part.

Realistically speking, I would see the following possible scenarios for migrating your server.

1) Simple migration without any experiements.
Install your OES2 Linux server as virtual server with the new storage. Use the GUI migration tool to migrate from NetWare to Linux.
Advantage: easiest method. No complication due to "exotic" steps in the migration. Also, your source server stays intact. So if anything goes wrong, you can still fall back to your old server
Disadvantage: Data copy can be time consuming

2. Following your idea of migrating the data before migrating the server: Connect the new storage to your existing server. You might use VCU, but if you do, be aware of the following:
- VCU does not handle files >4GB and Macintosh files. If you have any such files, don't use VCU.
- only use the command line version of VCU and let VCU rename your volumes automatically. No hassle that way.
However instead of using VCU, there might even be an easier method. You might be able to mirror your storage between your old and your new SAN at NetWare level. That way, you get an exact copy and no downtime or volume switching at all.
0 Likes
tpr520 Absent Member.
Absent Member.

Re: Migrate to new platform and hardware

Thanks, Marcel. I didn't realize there was a data migration tool for this type of conversion, so I'll take a look at that and probably go that route.
0 Likes
tpr520 Absent Member.
Absent Member.

Re: Migrate to new platform and hardware

Hmmm, so can I mirror the san volumes, break the old side of the mirror, then migrate the servers to the new VMs?
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: Migrate to new platform and hardware

zenking wrote:

>Hmmm, so can I mirror the san volumes, break the old side of the mirror,
>then migrate the servers to the new VMs?


It might work. You have to try whether NetWare allows you to mirror to
this different type of SAN.

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

Re: Migrate to new platform and hardware

OK, I have successfully tested mirroring a clustered nss volume between the old fiber san and the new iscsi san. So to clarify, once I have all the volumes mirrored, I can:
1 - use the migration tool to migrate nw -> oes using the pre-migration pattern
2 - migrate id and all services but skip the nss file migration
3 - after the source servers are down, rescan iscsi luns and mount volumes on new servers

Is step 3 as easy as that, or am I missing something? Been trying to find more examples of this, but there isn't much out there. Thanks for any tips.
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: Migrate to new platform and hardware

It might be prudent to perform the additional step of (re)syhcronizing the
NCP trustees with the NSS trustees.
http://www.novell.com/support/viewContent.do?externalId=3007067

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

Re: Migrate to new platform and hardware

Ah, OK, I think I saw that posted somewhere else (maybe by you?). That is a one time task, then OES Linux will keep up with trustees using LUM, correct? Thanks.
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: Migrate to new platform and hardware

zenking wrote:

>Ah, OK, I think I saw that posted somewhere else (maybe by you?). That
>is a one time task, then OES Linux will keep up with trustees using LUM,
>correct? Thanks.


It is typically a one time task unless manipulations that could alter the
NCP trustee database are performed on the volume. Also, the explanation of
LUM is wrong. This is not really related to LUM, but rather to the NCP
server. In order to also operate on non NSS volumes, the NCP server uses a
trustee database stored in the ._NETWARE directory below the directory the
constitutes the root of the NCP volume. This database is used by the NCP
server to enforce trustee rights. Nommally, a process keeps this database
in sync with the trustees stored in the NSS file system itself. However if
for some reason, this database is not in sync, then the ncp nss resync
option needs to be used to rebuild the database based on the information
that is in the NSS file system itself and that is considered to be
authoritative.

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

Re: Migrate to new platform and hardware

Great, thanks very much for the info.
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.