Recovering Data and Servers › Recover Lost Data from Replica

Recover Lost Data from Replica

You can restore data from a replica server. Doing so may require login credentials for the machine you select.

To recover all lost data from a Replica

1. On the Manager, from the Scenario pane select the desired scenario and stop it.
2. [For database applications only] stop the database services on the Master host.
3. On the Manager, from the scenario folder select the Replica host:

   Note: If multiple Replica servers participate in the required scenario, select the Replica from which you want to recover data.

   The Restore Data option is enabled.

4. From the Tools menu, select Restore Data, or click the Restore Data button on the Standard toolbar.

   The Recovery Method page of the Restore Data wizard opens.

   Notes:

   • If the Data Rewind property is set to On, another Restore Data dialog will appear. In this case, select the first option - Replace all data on Master with the data on Replica.
   • The Include Registry Keys synchronization checkbox is enabled, only if you activated the Registry Synchronization property before starting the scenario. If the checkbox is enabled, you can select it to include the synchronized Registry Keys in the recovery process.
5. Click Next. The Synchronization Method page opens.
6. Select the appropriate Synchronization Method, based on scenario type. Click Finish.

   Note: If the user credentials you used to log in to the Manager are different than the ones required for working with the Engine on the Replica, a User credentials dialog appears, asking you to enter log on account details for the selected Replica.

   Once you finished initiating the recovery process, Arcserve RHA builds a temporary reverse tree using the selected Replica as the root, and the Master as the terminating node. After the Master recovery process ends, the temporary scenario is deleted, and you receive the following message in the Event pane: Synchronization finished.

7. By default, once a data recovery occurs a Synchronization Report is generated.

   Now, the Replication process can restart on the original scenario.