Select the Target tab.
- Target Mirror Capacity High Percentage—You can specify the maximum percentage of Windows system memory that can contain mirror data before the target signals the source to pause the sending of mirror operations. The default setting is 20.
- Target Mirror Capacity Low Percentage—You can specify the minimum percentage of Windows system memory that can contain mirror data before the target signals the source to resume the sending of mirror operations. The default setting is 15.
- Retry Delay for Incomplete Operations (seconds)—This option specifies the amount of time, in seconds, before retrying a failed operation on the target. The default setting is 3.
-
Block Target Path(s) on Connection—You can block writing to the data located in the target paths. This keeps the data from being changed outside of Double-Take Availability processing.
Note: If you are going to use failover, any target paths that are blocked will automatically be unblocked during the failover process so that users can modify data on the target after failover. During a restoration, the paths are automatically blocked again. If you failover and failback without performing a restoration, the target paths will remain unblocked. You can manually block or unblock the target paths by right-clicking on a connection.
Do not block your target paths if you are protecting a full-server workload because system state data will not be able to be written to the target.
- Move deleted files to the following location—This option allows you to save files that have been deleted, by moving them to a different location on the target. When a file deletion is replicated to the target, instead of the file being deleted from the target, the file is moved to the specified location. This allows for easy recovery of those files, if needed. If you enable this option, specify where you want to store the deleted files.
-
Remove after the following number of days—If you are moving deleted files, you can specify a length of time, in days, to maintain the moved files. A moved file that is older than the specified number of days will be deleted. Double-Take Availability checks for moved files that should be deleted once daily at 8 PM. Only the date, not the time, of the file is considered when moved files are deleted. For example, if you specify to delete moved files after 30 days, any file that is 31 days old will be deleted. Because the criteria is based on days and not time, a file that will be deleted could have been moved anytime between 12:01 AM and 11:59 PM 31 days ago.
Note: If deleted files are moved for long enough, the potential exists for the target to run out of space. In that case, you can manually delete files from the target move location to free space.
Do not include the Recycler directory in your replication set if you are moving deleted files. If the Recycler directory is included, Double-Take Availability will see an incoming file deletion as a move operation to the Recycle Bin and the file will not be moved as indicated in the Move deleted files setting.
Alternate data streams that are deleted on the source will only be moved if the location you specified is on the same volume as the replica data. If you have selected a different volume, alternate data streams deleted on the source will not be moved on the target.
Encrypted files that are deleted on the source will only be moved on the target if the move location is on the same volume as the replication set target path.
Compressed and sparse files that are deleted on the source will be moved on the target, although the compression and sparse flags will only be retained on the target if the move location is on the same volume as the replication set target path.
Related Topics