Open topic with navigation

Overview

Double-Take includes Windows PowerShell cmdlets that you can use to control most Double-Take features. This guide includes all of the Double-Take cmdlets available and several sample scripts.However, this guide does not explain how to use Windows PowerShell. You should reference your Windows PowerShell documentation and the many web sites devoted to PowerShell to learn how to use and script with Windows PowerShell.

The Double-Take Availability agentless vSphere job does not support PowerShell. You cannot create, control, or manage agentless vSphere jobs with any Double-Take PowerShell cmdlets. Additionally, Double-Take Reporting Service does not support PowerShell. You cannot configure or manage your Double-Take Reporting Service server with any Double-Take PowerShell cmdlets.

Review the following terms and definitions to help you understand the Double-Take PowerShell cmdlets. See the Double-Take Availability User's Guide and the Double-Take Move User's Guide for complete details on how these products work.

• Source—The source is the server that has the data you want to protect. Typically this is a machine on the production network that serves data to clients.
• Target—The target is the server that maintains the replicated copy of the data that is being protected on the source. Typically this is a backup server that may be local or in a remote data center.
• Workload—A workload is a logical definition of the data that is being protected on the source. A workload can be a simple set of paths, for example, C:\Public, or it may be a more complex logical item that maps to multiple paths, for example, protecting a virtual machine means you are protecting multiple, specific virtual machine files.
• Workload Manager—The workload manager is a web service that creates and configures the Double-Take workload.
• Job—A job is a logical unit that includes the source, target, and the workload. The job is what you create and monitor in order to protect your data.
• Job Manager—The job manager is a web service that creates, monitors, and controls the Double-Take job.
• Connection—The engine connection, sometimes just called the connection, is the underlying stream that sends the actual replicated data between the source and target servers. Jobs are higher-level objects that use the lower-level connection to protect data.
• Architecture—Each Double-Take installation has two key services, the Management Service and Engine.
  • Management Service—This service is displayed as Double-Take Management Service in the services list. The service hosts the Job Manager and provides monitoring and control for all job types. By default this service listens on port 6325. This service offers a SOAP-based XML web services interface, implemented using WCF.
  • Engine—This service is displayed as Double-Take in the service list. The service transmits the replicated data between the source and target servers. By default this service listens on port 6320. You do not interact directly with this service.
• Roles—Any Double-Take installation can be a source, target, or both. The existence of a job between two servers and which direction data is being transmitted determines the server’s role.
• Security—Double-Take enforces security by using local groups on each server where Double-Take is installed. There are two levels of security. Double-Take Admin allows full control of Double-Take on a server, and Double-Take Monitor allows read-only access to job information. When you connect to the job manager on a server, you will need to provide the credentials of a user who is a member of one of the local groups on that server.
• Job creation—To create a job, you will first communicate with the source to create a workload. You will then use that workload object and communicate with the target to create the job.
• Monitoring and controlling jobs—To monitor and control jobs, you will communicate with the job manager on the target of the job.