You are here: Full server protection > Managing and controlling full server jobs > Viewing full server job details

Viewing full server job details

From the Manage Jobs page, highlight the job and click View Job Details in the toolbar.

Review the following table to understand the detailed information about your job displayed on the View Job Details page.

Job name

The name of the job

Job type

Each job type has a unique job type name. This job is a Full Server Failover job. For a complete list of all job type names, press F1 to view the Double-Take Console online help.

Health

The job is in a healthy state.

The job is in a warning state.

The job is in an error state.

The job is in an unknown state.

Activity

There are many different Activity messages that keep you informed of the job activity. Most of the activity messages are informational and do not require any administrator interaction. If you see error messages, check the rest of the job details.

Connection ID

The incremental counter used to number connections. The number is incremented when a connection is created. It is also incremented by internal actions, such as an auto-disconnect and auto-reconnect. The lowest available number (as connections are created, stopped, deleted, and so on) will always be used. The counter is reset to one each time the Double-Take service is restarted.

Transmit mode

Active—Data is being transmitted to the target.
Paused—Data transmission has been paused.
Scheduled—Data transmission is waiting on schedule criteria.
Stopped—Data is not being transmitted to the target.
Error—There is a transmission error.
Unknown—The console cannot determine the status.

Target data state

OK—The data on the target is in a good state.
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.
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.
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.
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.
Busy—The source is low on memory causing a delay in getting the state of the data on the target.
Not Loaded—Double-Take target functionality is not loaded on the target server. This may be caused by an activation code error.
Unknown—The console cannot determine the status.

Target route

The IP address on the target used for Double-Take transmissions.

Compression

On / Level—Data is compressed at the level specified.
Off—Data is not compressed.

Bandwidth limit

If bandwidth limiting has been set, this statistic identifies the limit. The keyword Unlimited means there is no bandwidth limit set for the job.

Connected since

The date and time indicating when the current job was made. This field is blank, indicating that a TCP/IP socket is not present, when the job is waiting on transmit options or if the transmission has been stopped. This field will maintain the date and time, indicating that a TCP/IP socket is present, when transmission has been paused.

Additional information

Depending on the current state of your job, you may see additional information displayed to keep you informed about the progress and status of your job. If there is no additional information, you will see (None) displayed.

Mirror status

Calculating—The amount of data to be mirrored is being calculated.
In Progress—Data is currently being mirrored.
Waiting—Mirroring is complete, but data is still being written to the target.
Idle—Data is not being mirrored.
Paused—Mirroring has been paused.
Stopped—Mirroring has been stopped.
Removing Orphans—Orphan files on the target are being removed or deleted depending on the configuration.
Verifying—Data is being verified between the source and target.
Restoring—Data is being restored from the target to the source.
Unknown—The console cannot determine the status.

Mirror percent complete

The percentage of the mirror that has been completed

Mirror remaining

The total number of mirror bytes that are remaining to be sent from the source to the target

Mirror skipped

The total number of bytes that have been skipped when performing a difference or checksum mirror. These bytes are skipped because the data is not different on the source and target.

Replication status

Replicating—Data is being replicated to the target.
Ready—There is no data to replicate.
Pending—Replication is pending.
Stopped—Replication has been stopped.
Out of Memory—Replication memory has been exhausted.
Failed—The Double-Take service is not receiving replication operations from the Double-Take driver. Check the Event Viewer for driver related issues.
Unknown—The console cannot determine the status.

Replication queue

The total number of replication bytes in the source queue

Disk queue

The amount of disk space being used to queue data on the source

Bytes sent

The total number of mirror and replication bytes that have been transmitted to the target

Bytes sent compressed

The total number of compressed mirror and replication bytes that have been transmitted to the target. If compression is disabled, this statistic will be the same as Bytes sent.

Target Server Image

When a full server job is created with reverse protection enabled, an image of the target's system state is stored on the source server. This image allows you to reverse your source and target after a failover. To improve performance, the target's system state is not continuously replicated to the source. You should manually update the image of the target's system state by clicking Update if there is a change on the target. For example, if the credentials on the target server are updated, you should update the target server image that is on the source. This reverse protection mirror may cause a performance impact on your source server. This impact is only temporary, and system performance will return to normal when the reverse protection mirror is complete.