Managing and controlling recovery jobs

The details displayed in the bottom pane provide additional information for the job highlighted in the top pane. You can expand or collapse the bottom pane by clicking on the Job Highlights heading.

 

Name

The name of the job

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.
• 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 a license key error.
• Unknown—The console cannot determine the status.

Mirror remaining

The total number of mirror bytes that are remaining to be sent from the source to the target. This value may be zero if you have enabled Mirror only changed files when source reboots on the Server setup properties.

Mirror skipped

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. This value may be zero if you have enabled Mirror only changed files when source reboots on the Server setup properties.

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

Recovery point latency

The length of time replication is behind on the target compared to the source. This is the time period of data that would be lost if a failure were to occur at the current time.

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.

Connected since

The date and time indicating when the current job was started.

Recent activity

Displays the most recent activity for the selected job, along with an icon indicating the success or failure of the last initiated activity. Click the link to see a list of recent activities for the selected job. You can highlight an activity in the list to display additional details about the activity.

Image name

The name of the image on the repository server

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.

 

You can control your job through the toolbar buttons available on the Jobs page. If you select multiple jobs, some of the controls will apply only to the first selected job, while others will apply to all of the selected jobs. For example, View Job Details will only show details for the first selected job, while Stop will stop protection for all of the selected jobs.

If you want to control just one job, you can also right click on that job and access the controls from the pop-up menu.

 

View Job Details

This button leaves the Jobs page and opens the View Job Details page.

Edit Job Properties

This button leaves the Jobs page and opens the EditJob Properties page.

Delete

Stops (if running) and deletes the selected jobs.

Provide Credentials

Changes the login credentials that the job (which is on the target machine) uses to authenticate to the servers in the job. This button opens the Provide Credentials dialog box where you can specify the new account information and which servers you want to update. See Providing server credentials. You will remain on the Jobs page after updating the server credentials. If your servers use the same credentials, make sure you also update the credentials on the Servers page so that the Double-Take Console can authenticate to the servers in the console session. See Managing servers.

View Recent Activity

Displays the recent activity list for the selected job. Highlight an activity in the list to display additional details about the activity.

Start

Starts or resumes the selected jobs.

If you have previously stopped protection, the job will restart mirroring and replication.

If you have previously paused protection, the job will continue mirroring and replication from where it left off, as long as the Double-Take queue was not exhausted during the time the job was paused. If the Double-Take queue was exhausted during the time the job was paused, the job will restart mirroring and replication.

Also if you have previously paused protection, all jobs from the same source to the same IP address on the target will be resumed.

Pause

Pauses the selected jobs. Data will be queued on the source while the job is paused.

All jobs from the same source to the same IP address on the target will be paused.

Stop

Stops the selected jobs. The jobs remain available in the console, but there will be no mirroring or replication data transmitted from the source to the target. Mirroring and replication data will not be queued on the source while the job is stopped, requiring a remirror when the job is restarted. The type of remirror will depend on your job settings.

Take Snapshot

Snapshots are not applicable to DR recovery jobs.

Manage Snapshots

Snapshots are not applicable to DR recovery jobs.

Failover, Cutover, or Recover

Finishes the recovery process. See the final steps of the process for Creating a recovery job.

Failback

Starts the failback process. Failback does not apply to DR jobs.

Restore

Starts the restoration process. Restore does not apply to DR jobs.

Reverse

Reverses protection. Reverse protection does not apply to DR jobs.

Recover Data

Recovers the selected DR job. You will be taken directly to the Choose Source Image to Recover page, which bypasses the first three pages of the recovery workflow (Get Started, Double-Take DR, and Choose Source Repository Server), automatically using the repository server of the selected protection job. See Creating a recovery job for details on recovering a DR job.

Undo Failover or Cutover

Cancels a failover or cutover by undoing it. Undo failover does not apply to DR jobs.

View Job Log

Opens the job log. On the right-click menu, this option is called View Logs, and you have the option of opening the job log, source server log, or target server log.

Other Job Actions

Opens a small menu of other job actions. These job actions will be started immediately, but keep in mind that if you stop and restart your job, the job's configured settings will override any other job actions you may have initiated.

• Mirroring—You can start, stop, pause and resume mirroring for any job that is running.

  When pausing a mirror, Double-Take stops queuing mirror data on the source but maintains a pointer to determine what information still needs to be mirrored to the target. Therefore, when resuming a paused mirror, the process continues where it left off.

  When stopping a mirror, Double-Take stops queuing mirror data on the source and does not maintain a pointer to determine what information still needs to be mirrored to the target. Therefore, when starting a mirror that has been stopped, you will need to decide what type of mirror to perform.

  • Mirror Options—Choose a comparison method and whether to mirror the entire file or only the bytes that differ in each file.

    If you are using a data recovery job and were using a database application on the original source or were protecting a domain controller, do not use the compare file attributes only options unless you know for certain that you need it. With database applications and because domain controllers store their data in a database, it is critical that all files, not just some of the files, are mirrored. In this case, you should compare both the attributes and the data.

     

    • Do not compare files. Send the entire file.—Double-Take will not perform any comparisons between the files on the source and target. All files will be mirrored to the target, sending the entire file. This is equivalent to selecting the mirror all files option prior to Double-Take version 7.1.
    • Compare file attributes. Send the entire file.—Double-Take will compare file attributes and will mirror those files that have different attributes, sending the entire file. This is similar to selecting the mirror different files and the only if source is newer options prior to Double-Take version 7.1. This option is not available for full server recovery jobs.
    • Compare file attributes. Send the attributes and bytes that differ.—Double-Take will compare file attributes and will mirror only the attributes and bytes that are different. This is equivalent to selecting the mirror different files, only if source is newer, and use block checksum options prior to Double-Take version 7.1. This option is not available for full server recovery jobs.
    • Compare file attributes and data. Send the attributes and bytes that differ.—Double-Take will compare file attributes and the file data and will mirror only the attributes and bytes that are different. This is equivalent to selecting the mirror different files and use block checksum options prior to Double-Take version 7.1. If you are using a database application on your source, select this option.

  • Calculate size of protected data before mirroring—Specify if you want Double-Take to determine the mirroring percentage calculation based on the amount of data being protected. If you enable this option, the calculation will begin when mirroring begins. For the initial mirror, the percentage will display after the calculation is complete, adjusting to the amount of the mirror that has completed during the time it took to complete the calculation. Subsequent mirrors will initially use the last calculated size and display an approximate percentage. Once the calculation is complete, the percentage will automatically adjust down or up to indicate the amount that has been completed. Disabling calculation will result in the mirror status not showing the percentage complete or the number of bytes remaining to be mirrored.

    The calculated amount of protected data may be slightly off if your data set contains compressed or sparse files.

     

• Verify—Even if you have scheduled the verification process, you can run it manually any time a mirror is not in progress.

  • Report only—Select this option if you only want to generate a verification report. With this option, no data that is found to be different will be mirrored to the target. Choose how you want the verification to compare the files.

  • Report and mirror files—Select this option if you want to generate a verification report and mirror data that is different to the target. Select the comparison method and type of mirroring you want to use. See the previous mirroring methods described under Mirror Options.

• Set Bandwidth—You can manually override bandwidth limiting settings configured for your job at any time.
  • No bandwidth limit—Double-Take will transmit data using 100% bandwidth availability.
  • Fixed bandwidth limit—Double-Take will transmit data using a limited, fixed bandwidth. Select a Preset bandwidth limit rate from the common bandwidth limit values. The Bandwidth field will automatically update to the bytes per second value for your selected bandwidth. This is the maximum amount of data that will be transmitted per second. If desired, modify the bandwidth using a bytes per second value. The minimum limit should be 3500 bytes per second.
  • Scheduled bandwidth limit—If your job has a configured scheduled bandwidth limit, you can enable that schedule with this option.
• Delete Orphans—Even if you have enabled orphan file removal during your mirror and verification processes, you can manually remove them at any time.

• Target—You can pause the target, which queues any incoming Double-Take data from the source on the target. All active jobs to that target will complete the operations already in progress. Any new operations will be queued on the target until the target is resumed. The data will not be committed until the target is resumed. Pausing the target only pauses Double-Take processing, not the entire server.

  While the target is paused, the Double-Take target cannot queue data indefinitely. If the target queue is filled, data will start to queue on the source. If the source queue is filled, Double-Take will automatically disconnect the connections and attempt to reconnect them.

  If you have multiple jobs to the same target, all jobs from the same source will be paused and resumed.

Filter

Select a filter option from the drop-down list to only display certain jobs. You can display Healthy jobs, Jobs with warnings, or Jobs with errors. To clear the filter, select All jobs. If you have created and populated server groups, then the filter will only apply to the jobs associated with the server or target servers in that server group. See Managing servers.

Search

Allows you to search the source or target server name for items in the list that match the criteria you have entered.

Overflow Chevron

Displays any toolbar buttons that are hidden from view when the window size is reduced.