This cmdlet attempts to fix job option errors and warnings. For those errors and warnings that Double-Take cannot correct automatically, you will need to modify the job options manually, modify the source or target configuration, or perhaps select a different target. Use the first syntax for existing jobs and the second syntax for new jobs. For this cmdlet, the -ServiceHost should be your target server.

Syntax

Repair-DtJobOptions [-JobId] <Guid> [-JobOptions] <JobOptions> [-Step] <VerificationStep[]> [-ServiceHost] <Server> [<CommonParameters>]

Repair-DtJobOptions [-CreateOptions] <CreateOptions> [-Step] <VerificationStep[]> [-ServiceHost] <Server> [<CommonParameters>]

Repair-DtJobOptions [-Source] <Server> [-JobType] <String> [-JobOptions] <JobOptions> [-Step] <VerificationStep[]> [-OtherServers] <Server[]> [-ServiceHost] <Server> [<CommonParameters>]

Parameters

-JobId<Guid>

Specify the job GUID returned from the New-DtJob cmdlet or the Id within the job information returned from the Get-DtJob cmdlet.

Required?	true
Position?	2
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-CreateOptions<CreateOptions>

Specify the create options available in DoubleTake.Jobs.Contract.CreateOptions. Use the Windows PowerShell New-Object cmdlet to create this object.

Required?	true
Position?	2
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-Source<Server>

Specify the server object returned from the New-DtServer cmdlet.

Required?	true
Position?	2
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-JobType<String>

Specify the type of job from the following list.

ClusterAwareFilesAndFolders—Cluster-aware files and folders job

ClusterAwareSql—Cluster-aware SQL job

Diagnostics—Throughput Diagnostic Utility job

FilesAndFolders—Files and folders job

FullServerFailover—Full server job

LinuxFullServerFailover—Full server job

LinuxMoveServerMigration—Full server migration job

Lvra—Full server to ESX job

MoveDataOnlyMigration—Data migration job

MoveServerMigration—Full server migration job

MoveLvra—Full server to ESX migration

SQL—SQL job

VRA—Full server to ESX or full server to Hyper-V job

VraMove—Full server to ESX migration or full server to Hyper-V migration job

Required?	true
Position?	3
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-JobOptions<JobOptions>

Specify the JobOptions returned from the Get-DtRecommendedJobOptions cmdlet.

Required?	true
Position?	3
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-Step<VerificationStep[]>

Specify the verification steps returned by the Get-DtVerificationStatus cmdlet.

Required?	true
Position?	3
Accept Pipeline Input?	true (ByValue)
Accept Wildcard Characters?	false

-OtherServers<Server[]>

Specify the server object returned from the New-DtServer cmdlet. Specify multiple server objects in an array using the format @($server1, $server2).

Required?	false
Position?	named
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-ServiceHost<Server>

Specify the server object returned from the New-DtServer cmdlet.

Required?	true
Position?	1
Accept Pipeline Input?	true (ByPropertyName)
Accept Wildcard Characters?	false

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_CommonParameters.

Examples

------------------EXAMPLE------------------

A server object is created for the server beta using the domain\administrator and password credentials. It assigns the server object to the variable called DtServerObjectBeta. The job(s) are retrieved from DtServerObjectBeta, but only the job information where the source machine name is equivalent to the name stored in the variable DtServerObjectAlpha is retrieved. That information is then stored in the variable DtJobForAlpha. The job options used by the job are confirmed, and the validation result is stored in DtValidation. The details of the validation are stored in the variable DtStatus. Those items that can automatically be fixed are corrected. If the job options were modified in order to fix an issues, the updated job options are now contained in the variable $DtRepair. The updated job options are then applied to the job. The connections for the server object are then closed.

$DtServerObjectBeta = New-DtServer -Name beta -UserName domain\administrator -Password password

$DtJobForAlpha = Get-DtJob -ServiceHost $DtServerObjectBeta | Where-Object {$_.Statistics.CoreConnectionDetails.SourceMachineName -eq $DtServerObjectAlpha}

$DtValidation = Confirm-DtJobOptions -ServiceHost $DtServerObjectBeta -JobId $DtJobForAlpha.Id -JobOptions $DtJob.Options

$DtStatus = Get-DtVerificationStatus -ServiceHost $DtServerObjectBeta -Token $DtValidation

$DtRepair = Repair-DtJobOptions -ServiceHost $DtTarget -JobId $DtJob.Id -JobOptions $DtJob.Options -Step $DtStatus.Steps

Edit-DtJob -ServiceHost $DtServerObjectBeta -JobId $DtJobForAlpha.Id -JobOptions $DtRepair.Options

Disconnect-DtServer -ServiceHost $DtServerObjectBeta