Home Print  

Server Disaster Recovery

Overview

This feature helps you recover the Backup Server and its data from the Replication Server. If your Backup Server had been replicating to a Replication Server, then, in case of any crash/disaster at your Backup Server, the Backup Server can be rebuilt from the Replication Server. You can either recover the backup data and the Groups/clients configurations OR you could recover only the Group configurations and copy the backup data separately from the Replication Server. After copying the backup data from the replication server, you would need to do a "Seed Backup Migration".

How to get here in the Web Console?
 In the top menu, select: "Server Management -> Replication Management -> Server Disaster Recovery"

Server Disaster Recovery

To provide redundancy for the backup data, the backup server can be configured to replicate all its backup data to a replication server. If the backup server crashes, the backup server can be restored back by retrieving the replicated data from the replication server using the Server Disaster Recovery(SDR) feature.

The following are the steps to reconstruct the backup server after a crash, through the Server Disaster Recovery feature:

  1. Disable the network in the backup server so that the clients don't connect to the backup server during the disaster recovery

  2. Install in the backup server with the same ID as before.

  3. Go to the Server Management -> Replication Management -> Server Disaster Recovery page. This opens the Server Disaster Recovery screen which has the following fields:

    To perform disaster recovery from the replication server :

    1. Select replication server: Select the replication server name from the drop down list.

    2. Select data to recover.

      1. Group & Client configurations and Client data:

        This recovers the Client and group configurations along with the clients' backup data.

      2. Group & Client configurations Only:

        This recovers only the backup server configurations like group details, disk space allotted, MCALs added etc. The backup data is not recovered. This option is helpful when the amount of data is huge and restoring it from the replication server to the backup server over the internet or a WAN may be slow. Instead, the data (the entire 1/ folder in the storage location in the replication server) can be copied into an external drive and then shipped to the backup server location. The data from the external drive can then be attached to the backup server through the server side Seed Backup Migration. This is explained in steps 6, 7 and 8 in the Seed Backup Migration help document.

    3. Next specify if you are restoring the data afresh to the backup server or just continuing from the previous interruption of the recovery process.

    4. Parallel Threads: Number of simultaneous backups that should be recovered from the replication server. By default, it is set to 5.

    To perform disaster recovery from Amazon S3 :

    1. Select replication server: Select the "s3-amazon-webservice" option from the drop down list and enter the following details :

      1. AWS Access Key: The Amazon WebServices Access key to authorize the Server to replicate to S3.

      2. AWS Secret Key: The Amazon WebServices Secret key to authorize the Server to replicate to S3.

      3. Bucket Name: The Bucket name under which all the backup data has to be replicated.

    2. Select data to recover.

      1. Group & Client configurations and Client data:

        This recovers the Client and group configurations along with the clients' backup data.

    3. Next specify "restore afresh" option to restore the data afresh to the backup server.

    4. Parallel Threads: Number of simultaneous backups that should be recovered from the replication server. By default, it is set to 5.

  4. Click on the Recover data from the replication server to start the recovery process.

  5. If the first option recover Group & Client configurations and Client data was selected, then the progress chart will be as shown below:

    After completion of recovery process, click Server Disaster Recovery Reports through the menu Server Management -> Replication Management.

    Clicking the menu gives the details of the data recovered from the Replication server.

    If the second option Group and Client configurations only was selected in step 4b above, then only the backup server details are recovered.




    Once the group & client configurations are recovered from the replication server, you can manually ship the backup data from the Replication Server to the Backup Server and then do Seed Backup Migration in the backup server.

    Once the Backup Server is successfully recovered, you can enable the network in the backup server and resume the backups from the clients.

  6. Enable replication in the restored backup server by going through Server Management -> Replication Management page in the backup server web console.

Troubleshooting Tips

Could not find any configurations to restore in the Replication Server. Show/Hide

Cause : This error would occur if there were no replicated backups available on the Replication Server (for the Backup Server).

Solution : Please try recovering data from the replication server where the backup server was previously replicating.

Limitations
Print  
Technical support-