Replication service view
You can view the replication service details for a Windows server by right-clicking on a server on the Servers page and selecting View Replication Service Details. A separate window will open allowing you to continue working in the Carbonite Replication Console while monitoring the replication service details. You can open multiple Replication service view windows for multiple servers. When the Carbonite Replication Console is closed, all Replication service view windows will automatically close. If you do not want to open separate windows, you can switch between servers that are in your Carbonite Replication Console from within the Replication service view window by using the drop-down list of servers in the toolbar.
The left pane of the Replication service view window is divided into the root and three folders.
- Root—This section shows high-level overview information for the server. See Root items for the items in this Server Properties section.
-
Connections—This section shows any active connections from this server. A connection is the underlying component of a job that controls data movement, like mirroring and replication. The Carbonite Availability and Carbonite Migrate engine controls the connection.
A connection may or may not be associated with a job. If it is not associated with a job, it can be deleted. However, you should be certain it is not associated with a job because deleting a connection that is being used can corrupt its parent job. Use the Delete button in the toolbar to delete a connection.
When you highlight the Connections folder in the left pane, all active connections from this server will be displayed in the right pane. See Connections folder items for details on the data displayed in this view. If you highlight a specific connection under the Connections folder, only the information for that connection will be displayed in the right pane. The connections are identified by the type of job and the connection ID. See Specific connection items for details on the data displayed in this view.
-
Replication sets—This section shows any replication sets on this server. The replication set is the data that your job is protecting.
A replication set may or may not be associated with a connection. If it is not associated with a connection, it can be deleted. Use the Delete button in the toolbar to delete a replication set.
When you highlight the Replication sets folder in the left pane, all replication sets on this server will be displayed in the right pane. See Replication sets folder items for details on the data displayed in this view. If you highlight a specific replication set under the Replication sets folder, only the information for that replication set will be displayed in the right pane. See Specific replication set items for details on the data displayed in this view.
-
Target connection entries—This section is like the Connections section, however it shows any active connections to this server.
You may see target connections that are not associated with a job. These connections will have a Target Data State of Disconnected. For example, this may happen if you delete a stopped job. These disconnected target connections cannot be deleted. They will be reused when a new connection (same job type, same servers) is created.
When you highlight the Target connection entries folder in the left pane, all active connection to this server will be displayed in the right pane. See Target connection entries folder items for details on the data displayed in this view. If you highlight a specific connection under the Target connection entries folder, only the information for that connection will be displayed in the right pane. See Specific target connection items for details on the data displayed in this view.
Root items
Server name
The name of the server
Product version
The Carbonite Availability and Carbonite Migrate version
Operating system
The operating system version and edition
Source module
Indicates if the source module is running on the server
Target module
Indicates if the target module is running on the server
Failover module
Indicates if the failover module is running on the server
Connections folder items
Replication Set
The name of the replication set the connection is using
Connection ID
The incremental counter used to number connections. The number is incremented when a connection is created. The counter is reset if there are no existing jobs and the Double-Take service is restarted.
Target Name
The name of the target the connection is using, including the port number
Target IP
The target IP address and port, as well as the location on the target where the replication set data is being stored. This is sometimes called the transform path.
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—Carbonite Availability and Carbonite Migrate target functionality is not loaded on the target server. This may be caused by a license key error.
- Not Ready—The Linux drivers have not yet completed loading on the target.
- Unknown—The console cannot determine the status.
Target Status
- OK—The target machine is active and online.
- Not Loaded—The target module is not loaded on the target. This may be caused by a license key error.
- Paused—The target machine is paused by user intervention.
- Retrying—The target machine is retrying operations for the connection.
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.
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.
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 Carbonite Availability and Carbonite Migrate driver. Check the Event Viewer for driver related issues.
- Unknown—The console cannot determine the status.
Queued (ops)
The total number of mirror and replication operations that are in the source queue
Sent (bytes)
The total number of mirror and replication bytes that have been transmitted to the target
Sent Compressed (bytes)
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.
Intermediate Queue (bytes)
The total amount of memory being used by the operations buffer queue
Disk Queue (bytes)
The amount of disk space being used to queue data on the source
Queued Replication (bytes)
The total number of replication bytes in the source queue
Sent Replication (bytes)
The total number of replication bytes that have been transmitted to the target
Sent Compressed Replication (bytes)
The total number of compressed replication bytes that have been transmitted to the target. If compression is disabled, this statistic will be the same as sent replication (bytes).
Sent Mirror (bytes)
The total number of mirror bytes that have been transmitted to the target
Sent Compressed Mirror (bytes)
The sent compressed mirror (bytes) statistic is the total number of compressed mirror bytes that have been transmitted to the target. If compression is disabled, this statistic will be the same as sent mirror (bytes).
Skipped Mirror (bytes)
The total number of bytes that have been skipped when performing a difference. These bytes are skipped because the data is not different on the source and target.
Remaining Mirror (bytes)
The total number of mirror bytes that are remaining to be sent from the source to the target.
Queued Replication (ops)
The total number of replication operations in the queue
Connected Since
The source server date and time indicating when the current job was started. 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.
Bandwidth Limit (Kbps)
If bandwidth limiting has been set, this statistic identifies the limit. The keyword Unlimited means there is no bandwidth limit set for the job.
Specific connection items
Replication set
The name of the replication set the connection is using
Connection ID
The incremental counter used to number connections. The number is incremented when a connection is created. The counter is reset if there are no existing jobs and 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—Carbonite Availability and Carbonite Migrate target functionality is not loaded on the target server. This may be caused by a license key error.
- Not Ready—The Linux drivers have not yet completed loading on the target.
- Unknown—The console cannot determine the status.
Target route
The target IP address and port
Compression
- On / Level—Data is compressed at the level specified.
- Off—Data is not compressed.
Bandwidth limit (Kbps)
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 source server date and time indicating when the current job was started. 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.
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 (bytes)
The total number of mirror bytes that are remaining to be sent from the source to the target.
Mirror skipped (bytes)
The total number of bytes that have been skipped when performing a difference. These bytes are skipped because the data is not different on the source and target.
Queued mirror (ops)
The total number of mirror operations in the queue
Sent mirror (bytes)
The total number of mirror bytes that have been transmitted to the target
Sent compressed mirror (bytes)
The sent compressed mirror (bytes) statistic is the total number of compressed mirror bytes that have been transmitted to the target. If compression is disabled, this statistic will be the same as sent mirror (bytes).
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 Carbonite Availability and Carbonite Migrate driver. Check the Event Viewer for driver related issues.
- Unknown—The console cannot determine the status.
Replication queue (bytes)
The total number of replication bytes in the source queue
Sent replication (bytes)
The total number of replication bytes that have been transmitted to the target
Sent compressed replication (bytes)
The total number of compressed replication bytes that have been transmitted to the target. If compression is disabled, this statistic will be the same as sent replication (bytes).
Sent (bytes)
The total number of mirror and replication bytes that have been transmitted to the target
Sent compressed (bytes)
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.
Intermediate queue (bytes)
The total amount of memory being used by the operations buffer queue
Disk queue (bytes)
The amount of disk space being used to queue data on the source
Queued (ops)
The total number of mirror and replication operations that are in the source queue
Source Path
The location of the data on the source that is being protected
Target Path
The location on the target where the source replica data is located
Usage type
All job types use the Normal replication set type.
Contains
The number of files and directories contained in the replication set
Total size
The amount of data contained in the replication set
Last calculated
The date and time the size of the replication set was last calculated
Path
The path including volume, drive, directory, file, and/or wild card
Attributes
The attributes that define the path.
- Inc—The specified path is included in the replication set
- Exc—The specified path is not included in the replication set
- Rec—The rule is automatically applied to the subdirectories of the specified path
Replication sets folder items
Name
The name of the replication set
In Use
Specifies if the replication set is being used by a connection
Last Calculated
The date and time the size of the replication set was last calculated
Size (bytes)
The amount of data contained in the replication set
Files
The number of files contained in the replication set
Directories
The number of directories contained in the replication set
Specific replication set items
Name
The name of the replication set
Usage type
All job types use the Normal replication set type.
In Use
Specifies if the replication set is being used by a connection
Contains
The number of files and directories contained in the replication set
Total size
The amount of data contained in the replication set
Last calculated
The date and time the size of the replication set was last calculated
Path
The path including volume, drive, directory, file, and/or wild card
Attributes
The attributes that define the path.
- Inc—The specified path is included in the replication set
- Exc—The specified path is not included in the replication set
- Rec—The rule is automatically applied to the subdirectories of the specified path
Target connection entries folder items
Source Name
The name of the source the connection is using
Source Address
The source IP address and port the connection is using
Replication Set
The name of the replication set
Connection ID
The incremental counter used to number connections. The number is incremented when a connection is created. The counter is reset if there are no existing jobs and the Double-Take service is restarted.
Target Data State
- Disconnected—The target connection entry is not associated with a connection. This may happen if you delete a stopped job. These disconnected target connections cannot be deleted. They will be reused when a new connection (same job type, same servers) is created.
- 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—Carbonite Availability and Carbonite Migrate target functionality is not loaded on the target server. This may be caused by a license key error.
- Not Ready—The Linux drivers have not yet completed loading on the target.
- Unknown—The console cannot determine the status.
Target Status
- OK—The target machine is active and online.
- Not Loaded—The target module is not loaded on the target. This may be caused by a license key error.
- Paused—The target machine is paused by user intervention.
- Retrying—The target machine is retrying operations for the connection.
Specific target connection items
Source name
The name of the source the connection is using
Source address
The source IP address and port the connection is using
Replication set
The name of the replication set
Connection ID
The incremental counter used to number connections. The number is incremented when a connection is created. The counter is reset if there are no existing jobs and the Double-Take service is restarted.
Target data state
- Disconnected—The target connection entry is not associated with a connection. This may happen if you delete a stopped job. These disconnected target connections cannot be deleted. They will be reused when a new connection (same job type, same servers) is created.
- 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—Carbonite Availability and Carbonite Migrate target functionality is not loaded on the target server. This may be caused by a license key error.
- Not Ready—The Linux drivers have not yet completed loading on the target.
- Unknown—The console cannot determine the status.
Target status
- OK—The target machine is active and online.
- Not Loaded—The target module is not loaded on the target. This may be caused by a license key error.
- Paused—The target machine is paused by user intervention.
- Retrying—The target machine is retrying operations for the connection.
Schedule
Any configured snapshot schedule
Next scheduled snapshot
The date and time of the next scheduled snapshot, if any
Time Taken
The date and time of the listed snapshot
Type
-
Automatic—This snapshot was taken automatically by Carbonite Availability and Carbonite Migrate.
-
Manual—This snapshot was taken manually by a user.
-
Scheduled—This snapshot was taken as part of a periodic snapshot.
-
Deferred—This snapshot was taken as part of a periodic snapshot, although it did not occur at the specified interval because the job between the source and target was not in a good state.
ID
The snapshot ID
Target States
The state of the target at the time of the snapshot