Destination Site Procedure for Windows Remote Seeding to Clustered Data ONTAP

Following are the destination site procedures:

1. At the destination site, use a spare Windows machine as the destination node. The spare machine should have the following characteristics:

   • The operating system of the spare machine and the Windows primary machine should match one another. For example, if the source machine is Windows 2012, the spare machine should be Windows 2012.

   • The spare machine must be defined as a node.

   • The spare machine must have spare volumes that match the volume sizes of the Windows primary.

2. On the spare node, set the following registry keys:

NIB_SEEDING_UPDATE_DISK_SIGNATURE=Y

NIB_EXTEND_AFTER_VOLUME_RESTORE=N

Warning! Changes to registries or environmental variables should be done only by qualified administrators. If done incorrectly, such changes can adversely affect applications or operating systems. Contact Catalogic Software Data Protection Technical Support if you need assistance.

1. For each volume:

   1. Assign to the spare volume the same drive letter as that used on the original client.

      Note. If the volume on the original client did not have a drive letter (for example, if it has a volume mount point), then you do not need to perform this step, but additional steps will need to be run later on.

   2. Using the DPX management console, define an image restore job of the base image backup to the spare volume.

   3. Run the job. Note that the data on the spare partition of the Windows spare client will be overwritten during the Image restore.

   4. Validate that the restored volume serial number and volume size match those of the original client.

   Repeat the above steps until all the volumes that need to be seeded are completed.

2. If the original volume has the same drive letter as the spare node, do the following. Using the DPX management console, define a block backup job against the original node and volumes, with the destination being the NetApp Clustered Data ONTAP node. Do not run the backup job.

   If the original volume is a volume mount point or the original drive letter differs from that of the spare volume, do not perform this step at this time.

3. Make a note of the IP address of the spare node and the IP address of the original client node. Using the DPX management console, delete the spare node in the Configure Enterprise window. Then update the IP address of the original client to the IP address of the spare node. (This will get reversed later in the procedure).

4. If the original volume is a volume mount point or the original drive letter differs from that of the spare volume, do the following. In the DPX management console, define a block backup job by drilling down in the original client node and selecting the original volumes (volume mount point or drive letter).

5. Before restoring the base image backup to the Clustered Data ONTAP storage system, confirm the following:

   • the spare node contains the image backup

   • the qtree name on the spare node is exactly the same as that on the original client

   • the DPX logical node name is the same as the original client

   • the block backup job name is the same as the original client

   • the volume serial number is the same as the original client

6. Run the block backup job defined in Step 4 or Step 6. The base image backup is transferred from the spare volume to the target Clustered Data ONTAP storage. Allow time for this transfer to complete.