This section details the procedure you can use to change local volume serial numbers to match each node of the Windows cluster that you want to migrate. The information includes the use of the Volume Manager utility (VolumeManager.exe) to synchronize serial numbers on cluster node local storage.
To download and run the utility:
From the NetIQ Downloads site, search for the PlateSpin Migrate product, then click .
On the Products tab, select PlateSpin Migrate 12.X to go to the product-specific download page, then click .
On the download page, click VolumeManager.exe line or select the comparable download manager link.on the
Download the utility, then copy it to an accessible location on each cluster node.
On the active node of the cluster, open an administrative command prompt, navigate to the location of the downloaded utility, and run the following command:
A listing of the local volumes and their respective serial numbers is displayed. For example:
Volume Listing: -------------------- DriveLetter (*:) VolumeId="System Reserved" SerialNumber: AABB-CCDD DriveLetter (C:) VolumeId=C:\ SerialNumber: 1122-3344
Make note of these serial numbers or keep them displayed for later comparison.
Verify that all local storage serial numbers of the active node match the local storage serial numbers on each of the other nodes in the cluster.
On each cluster node, run the VolumeManager.exe -l command to obtain its volume serial numbers.
(Conditional) If there are any differences in the serial numbers between the active node and this node, take note of the serial number you want to propagate on this node and run the following command to set, and then to verify the serial number:
VolumeManager -s <VolumeId> <serial-number>
Following are two examples of how this command could be used:
VolumeManager -s "System Reserved" AAAA-AAAA
VolumeManager -s C:\ 1111-1111
When you have successfully changed all of the volume serial numbers on a node of the cluster, you need to restart that node.
(Conditional) If the cluster has already been migrated in a PlateSpin environment, we recommend running a full replication on the active node to ensure that any changes are propagated to the database.