Open topic with navigation

Failing back then restoring files and folders jobs

Failback before restoration can be a simpler process, but it may require additional downtime. The amount of downtime will depend on the amount of data to be restored. Users must be kept off of the source and target during this entire process.

1. Remove the source from the network and fix the issue that caused your source server to fail. Make sure in resolving the problems that you do not bring the source on the network at this time because the target currently has the source's identity because of failover.
2. Schedule a time for the failback and restoration process. Select a time that will have minimal disruption on your users.
3. When you are ready to begin the failback process, prohibit user access to the source and target.
4. On the Manage Jobs page, highlight the job and click Failback.
5. Confirm that you want to failback the selected jobs and click Failback.
6. Once failback is complete, the Activity will indicate Restore Required. At this time, bring the source onto the network. Make sure that end users continue to be prohibited because the updated data from the target needs to be restored back to the source.
7. Stop any applications that may be running on the source. Files must be closed on the source so that updated files from the target will overwrite the files on the source.

8. On the Manage Jobs page, highlight the job and click Restore.

   

9. If you want to skip the restoration, select Do not restore data, and click Continue. Keep in mind that if you skip the restoration process, any data changes that were made on the target during failover will be lost. If you want to restore the changed data from the target back to the source, select Restore data, highlight your source server in the server list, and click Continue to start the restoration.

   During the restoration, only the data is restored back to the source. Shares are not created on the source during the restoration. Shares that were created on the target during failover will need to be created manually on the source.

    

10. When the restoration is complete, the Activity will indicate Restored. If you skipped the restoration, the Activity will indicate Mirror Required. At either of these points, you can stop the job by clicking Stop. Also at this point, you can allow users to access the source again.

11. If you want to enable protection again, click Start.

    Depending on where you are running the console from, you may need to add the target back to the console after failback in order to see your job.

    If you have configured a source post-failback script, you must restart protection in order to launch the script.