Replication Server Migration

• Overview
• How to get here in the StoreGrid Web Console?
• Instructions for Replication Server Migration
• Troubleshooting Tips
• Limitations

Overview

Replication Server Migration is a feature to avoid bandwidth usage and reduce the replication time needed for a full backup over Internet. Using this feature, you can transfer the backup data from the backup server into a local external drive and then physically move the drive to the Replication Server environment to migrate the data into the replication server.

How to get here in the StoreGrid Web Console?
  In the top menu, select: "Server Admin->Group Management" and click on the "Replication Server Migration" icon on the left hand side.

Instructions for Replication Server Migration

Make sure the backup data that you want to migrate to the replication server is complete and the client machines are not backing up.

Disable replication in the Backup Server from the ‘Server Admin > Replication Management > Configure Replication’ page.

1. Connect an external device to the local backup server.

   

2. Copy the clients’ data (<Server_Location>/1 directory) to it. For example, if the backups are stored in a location "C:\LocalStorage", copy the "C:\LocalStorage\1" folder to the external device.

3. Next connect the external drive to the remote Replication Server.

   

4. Copy the data from the external drive to some location in the remote Replication Server, say C:\MigrateData\1. You can leave it in the external drive itself and migrate directly from the external drive but the migration might take a little longer.

5. In the top menu in the remote replication server StoreGrid web console, go to ‘Server Admin->Group Management’ and click on the ‘Replication Server Migration’ icon on the left hand side.

   

6. Enter the location of the 1/ folder (for e.g.: C:\MigrateData\1) and click the ‘Submit Location’ button.

   

7. The list of clients along with their backup server name is shown.

   

   

8. Choose the clients which are to be migrated and select their respective groups. If a client is already replicating under a particular group, then the ‘Migrate to Group’ and the ‘New Location’ fields will not be selectable for that client.

9. If the target group is not listed, choose Default Group as the target group and migrate the client to it. Once the replication runs from the backup server (after doing Replication Server Migration) to the replication server for the migrated clients, the group under which the client is listed in the backup server will be automatically created in the Replication Server and the client will be moved from Default Group to the particular group under which the client is backing up in the Backup Server.

10. After configuring all the necessary details, click the "Migrate" button.

11. The backup data (data in the 1/ folder) will be migrated to the remote replication server.

    

    

12. Enable replication status in the backup server by going to ‘Server Admin > Replication Management > Configure Replication’ page in the backup server.

    

13. To make sure the data has been migrated successfully to the replication server, try scheduling a replication for one of the clients by clicking the ‘Replicate Now’ icon in the ‘Group Management > Group > Client > List of Backup Schedules’ page in the backup server’s web console. It should not replicate anything or just replicate the additional backup data that came into the backup server since replication migration.

Note: You cannot migrate two clients with the same StoreGrid ID existing in two different backup servers into one replication server. The migration of the second client will fail.

Troubleshooting Tips

	No Clients for migration.
Cause 1: Backups are not present in the location "<LocalServerDataLocation>/<Client_Name>/" where 'LocalServerDataLocation' is the location entered in the remote replication server web console "Server Admin -> Group Management -> Replication Server Migration(Icon)" page. 'Client_Name' is the client name of the backups which is to be migrated. Solution : Delete the client data from the remote Replication Server 'LocalServerDataLocation' and recopy the data from the USB device. Cause 2 : Client's data are not copied from a backup server running StoreGrid 2.3 or later. Solution : Replication Server Migration can be done only with StoreGrid 2.3 (or later) backup data.

	Unable to list the Directory. Permission denied.
Cause : StoreGrid does not have the read permission for the location entered in the remote replication server web console "Server Admin -> Group Management -> Replication Server Migration (Icon)" page. Solution : Provide enough permission for the location you have given for the client or choose any other location where StoreGrid has the read and write permissions.

Limitations

1. If a full backup already exists in the Replication Server then the incremental backup data for this full backup cannot be migrated.
2. Similarly, additional full backups along with its incremental backups cannot be migrated. Only additional full backup data without incremental backups can be migrated.
3. You cannot migrate two clients with the same StoreGrid ID existing in two different backup servers into one replication server. The migration of the second client will fail.
4. If StoreGrid is stopped during the Server side "Replication Server Migration" progress, migration cannot continue from the place where it stopped.
5. No Replication Server migration report is available in remote Replication Server.
6. When there is not enough space in the remote replication server, migration will complete taking the necessary space. It does not throw an error or warning.
7. File version migration is not supported.
8. Backup data copied from one Replication Server cannot be migrated to another Replication Server.