You are here: Failback and restoration > Failing back then restoring

Failing back then restoring

Use these instructions to failback first and then restore your data.

Resolve the problem(s) on the source that caused it to fail. If you have to rebuild your source, make sure you use the same identity as the original source configuration.
Because you do not want your users accessing the source or its data until newer data from the target can be restored, deny access to user logins by setting /etc/nologin. See your Linux documentation for details on creating this file.
Stop any applications that may be running on your source. The files must be closed on the source so that updated files from the target will overwrite the files on the source during the restoration.
From the Failover Control Center, select the target that is currently standing in for the failed source.
Select the failed source and click Failback. The user downtime starts now. If you have a pre-failback script configured, it will be started.
When failback is complete, the post-failback script, if configured, will be started. When the script is complete, you will be prompted to determine if you want to continue monitoring the source. Select Continue or Stop to indicate if you want to continue monitoring the source. After you have selected whether or not to continue monitoring the source machine, the source post-failback script, if configured, will be started.

The source must be online and Double-Take Availability must be running to ensure that the source post-failback script can be started. If the source has not completed its boot process, the command to start the script may be lost and the script will not be initiated.
From the Replication Console, select Tools, Restoration Manager.
Identify the Original Source machine. This is your source machine where the data originally resided.
Select the Restore From machine. This is the target machine where the copy of the data is stored.
Replication Set contains the replication set information stored on the target machine (the machine in Restore From). If no replication sets are available, the list will be blank. Select the replication set that corresponds to the data that you need to restore.
Select the Restore To machine. This is your source where the updated data from the target will be sent.
Select the Use Backup Replication Set check box to use the target’s copy of the replication set database for the restoration. If this check box is not marked, you will be accessing the replication set information from the source.
Select the Restore Replication Set check box to restore the target’s copy of the replication set database to the source during the restoration process.
Select the Route on the target. This is the IP address and port on the target that the data will be transmitted through. This allows you to select a different route for Double-Take Availability traffic. For example, you can separate regular network traffic and Double-Take Availability traffic on a machine with multiple IP addresses.
The Restore To Server Path and Restore From Server Path paths will automatically be populated when the replication set is selected. The restore to path is the directory that is the common parent directory for all of the directories in the replication set. If the replication set crosses volumes, then there will be a separate path for each volume. The restore from path is the path on the target server where the replicated files are located.

Restoring across a NAT router requires the ports to be the same as the original connection. If the ports have been modified (manually or reinstalled), you must set the port numbers to the same values as the last valid source/target connection.
Select the restoration conditionals that you want to use.

Overwrite existing data during restore—This option restores all existing files by overwriting them. Any files that do not exist on the source are written also. If this option is disabled, only files that do not exist on the source will be restored.
Only if backup copy's date is more recent—This option restores only those files that are newer on the target than on the source. The entire file is overwritten with this option.

If you are using a database application, do not use the newer option unless you know for certain you need it. With database applications, it is critical that all files, not just some of them that might be newer, get mirrored.
Use Checksum comparison to send minimal blocks of data—Specify if you want the restoration process to use a block checksum comparison to determine which blocks are different. If this option is enabled, only those blocks (not the entire files) that are different will be restored to the source.

If you want to configure orphan files, click the Orphans tab. The same orphan options are available for a restoration connection as a standard connection.
Click Restore to begin the restoration.

After the restoration is complete, the restoration connection will automatically be disconnected and the replication set deleted. At this time, you can start any applications and allow end-users to access the data on the source.