Monitoring an application workload

If you have not done so already, launch the Double-Take Availability Application Manager by selecting Start, Programs, Double-Take, Availability, Double-Take Availability Application Manager.

To change whether failover monitoring is enabled, click the Enable/Disable Monitoring button at the bottom of the window, or select either Enable Monitoring or Disable Monitoring from the Actions menu.

Protection status state s

The following table describes the possible protection status states.

Protection Status States
Protection Status	Description
Unprotected	No Double-Take connection exists
Warning	Double-Take connection exists, but has issues (such as with target state, mirroring, or replication). For example, if the mirror has been paused outside of the Application Manager or if the target is down. See details for more information.
Protected	Double-Take connection exists and is active
Synchronizing (% complete)	Mirroring is in progress
Unknown	Source server is not selected
Failing over	Failover from the source to the target is in progress
Failed over	Target has assumed source role
Failing back	Failback from the target to the original source is in progress
Restoring (% complete)	Mirroring (target to source) is in progress

The following table describes the possible monitoring status states.

Monitoring Status States
Monitoring Status	Description
Disabled	No Double-Take monitor
Enabled	Double-Take monitor is started
Failover condition met	Source server is down
Failing over	Failover from the source to the target is in progress
Failed over	Target has assumed source role
Failing back	Failback from the target to the original source is in progress

Protection detail state s

The following table identifies the possible mirror status states.

Mirror Status States
Mirror Status	Description
Calculating size	Double-Take is determining the size of the replication set prior to starting the mirror. The mirroring status will update the percentage complete if the replication set size is calculated.
Idle	Data is not being mirrored to the target machine
Mirroring	If the file size of the replication set has not been calculated and the data is being mirrored to the target machine, the Mirror Status will indicate Mirroring
Paused	Mirroring has been paused
Removing orphans	Double-Take is checking for orphan files within the target path location (files that exist on the target but not on the source). These files will be removed
Verifying	Data is being verified
Restoring	Data is being restored from the target to the source
Transmitting	Data is being sent to the target machine
(Unknown)	Mirror status could not be determined

The following table identifies the possible replication status states.

Replication Status States
Replication Status	Description
Calculating size	Double-Take is determining the size of the replication set prior to starting the mirror. The mirroring status will update the percentage complete if the replication set size is calculated.
Idle	Data is not being mirrored to the target machine
Mirroring	If the file size of the replication set has not been calculated and the data is being mirrored to the target machine, the Replication Status will indicate Mirroring
Paused	Mirroring has been paused
Removing orphans	Double-Take is checking for orphan files within the target path location (files that exist on the target but not on the source). These files will be removed
Verifying	Data is being verified
Restoring	Data is being restored from the target to the source
Transmitting	Data is being sent to the target machine
(Unknown)	Replication status could not be determined

The following table identifies the possible transmit modes.

Transmit Mode	Description
Started	The mirror or replication has been started
Paused	The mirror or replication has been paused
Warning (see details)	A warning condition has been encountered

The following table identifies the possible target status states.

Target Status States
Target Status	Description
Online	The target machine is active and online
Mirroring	The target is in the middle of a mirror process. The data will not be in a good state until the mirror is complete.
Mirroring Stopped	The mirroring process has been stopped
Re-mirror required	The data on the target is not in a good state because a remirror is required. This may be caused by an incomplete or stopped mirror or an operation may have been dropped on the target.
Retrying	The target machine is retrying operations for the connection
Paused	The target machine is paused by user intervention
Pausing	The connection is in the process of pausing
Restore Required	The data on the source and target do not match because of a failover condition. Restore the data from the target back to the source. If you want to discard the changes on the target, you can remirror to resynchronize the source and target.
Replicating	Data is being replicated to the target machine
Snapshot reverted	The data on the source and target do not match because a snapshot has been applied on the target. Restore the data from the target back to the source. If you want to discard the changes on the target, you can remirror to resynchronize the source and target.
Target path unblocked	Target path blocking is disabled for the connection
Target path blocked	Target path blocking is enabled for the connection
(Unknown)	Target status could not be determined