ReadyDATA Replicate Seeding
Views - 1550  |  23 people found this helpful KBA-1

NETGEAR - Storage  

ReadyDATA Replicate Seeding

When running Replicate between two ReadyDATAs (whether cloud managed Replicate or locally managed Replicate), the first time that the job runs will mean that all data in the chosen dataset needs to be transferred from the primary ReadyDATA to the secondary ReadyDATA.

Depending on the size of the source dataset and the bandwidth of the network connecting the two ReadyDATAs, then this initial sync may take a long time.

To avoid a long transfer time, you can avail of Replicate seeding. This means doing the following:

  • Export the source dataset to an NFS share on a NAS device (such as a NETGEAR ReadyNAS) which is on the same local network as the source ReadyDATA.
  • Move the NAS to the same local network as the destination ReadyDATA.
  • Import the dataset to the destination ReadyDATA.
  • Create the Replicate job specifying that the job should use the replica of the source dataset that now resides on the destination ReadyDATA as the base for the Replicate job.

Procedure:

Step 1: Connect a NAS to the same network as the source ReadyDATA. On this NAS, create a share and enable NFS on it. Below is an example of an NFS share called ReplicateSeed on a NETGEAR ReadyNAS. However any NAS device that supports NFS would be fine. Note the 2 hosts that are allowed access are the IPs of the source and destination ReadyDATAs:

 

Step 2: On the source ReadyDATA, go to Shares, right click on the datastore to be replicated and click Export to NAS:

 

Step 3: Enter the IP address of the NFS server (in our case the NAS), enter the path to the NFS share and enter the name of the file which will hold the dataset (this can be any arbitrary filename):

 

Step 4: Press Export. If the export begins successfully, then this pop-up appears:

 

Step 5: Wait for the export to complete. A log entry will appear confirming when this is done: Completed to export Share/LUN ('datastore') to NFS server ('172.22.0.51:/data/ReplicateSeed/datastoreseed').

Step 6: Now connect the NAS to the same network as the destination ReadyDATA

Step 7: On the destination ReadyDATA, go to Shares and press the Import from NFS button (marked in red below):

 

Step 8: Enter the IP address of the NFS server (again this is the NAS in this case), enter the path to the NFS share and enter the name of the file containing the dataset (needs to be the same filename specified in step 3). Also enter the name that you would like the dataset to have when it is imported onto the destination ReadyDATA - in our case, this will be Rep_datastore:

 

Step 9: Press Import. If the import begins successfully, then this pop-up appears:

 

Step 10: Wait for the import to complete. A log entry will appear confirming when this is done: Completed to import Share/LUN ('Rep_datastore') from NFS server ('172.22.0.51:/data/ReplicateSeed/datastoreseed')

Step 11: The dataset is now on the destination ReadyDATA and we can use this to seed the Replicate job

Step 12: Next step is to create the Replicate job and instruct the job to resume from the seed that we have planted on the destination ReadyDATA:

  • For cloud based Replicate, when creating the job choose the source dataset. When selecting the destination, drill down into the volume and choose the dataset that you have imported onto the destination ReadyDATA. Then press Next:
  •  

  • Next, choose the snapshot from which the Replicate job will resume. If there is more than one snapshot, then choose the most recent one:
  •  

  • Continue creating the Replicate job as normal. For more info on Replicate jobs not covered here, please refer to the ReadyDATA software manual.
  • Alternatively, if you are using local Replicate, when creating the job choose the source dataset. When selecting the destination, click on the Resume tab and drill down into the volume, choosing the dataset that you have imported onto the destination ReadyDATA. Then press Next:
  • Next, choose the snapshot from which the Replicate job will resume. If there is more than one snapshot, then choose the most recent one:
  •  

  • Continue creating the Replicate job as normal. For more info on Replicate jobs not covered here, please refer to the ReadyDATA software manual.

Step 13: When the Replicate job is created (whether cloud managed or locally managed), the initial sync should now complete quickly. You do not have to wait for all the data to transfer from source to destination since this has already been done through the seeding process. Instead, only the changes to the source dataset (after the point in time when it was exported) will be transferred to the destination ReadyDATA.

 

 
 
 

    Published on: 5/22/2015 3:45:50 PM   |  Last updated: 12/16/2016 4:38:44 PM  
 
 

Share this article

 

Winco (Pacific) Limited      Phone: 2803-0036   Email: support@winco.com.hk