Symptoms:
When failing over a Full Server job, the failover process may not complete. Leaving the job status as, ‘failover failed’.

This answer describes how to reset the job status in order to attempt another failover once the failover issue has been corrected. These steps also apply if the failover monitor has been removed (leaving the failover bottom grayed out) and the server needs to be failed over.

**Using the FCC to failover as in 5.2.x will not work in 5.3.x

Environment:

Actions Taken:

Answer

1. Close the Double-Take Console and stop the Double-Take Management Service on the target.
2. Open job .xml file in notepad. Location: …\Vision Solutions\Double-Take\Service\Data\…
3. Change the job state to “DoubleTake.FullServer.Service.Jobs.States.JobStateStopped”<JobPersistedState>
   <FilesAndFoldersPersistedState xmlns:d3p1=” http://schemas.datacontract.org/2004/07/DoubleTake.Jobs.Contract.FilesAndFolders ” i:nil=”true” />
   <FullServerPersistedState xmlns:d3p1=”DoubleTake.Jobs.Contract.FullServer”>
   <d3p1:BackupConnectionPersistedState i:nil=”true” />
   <d3p1:BackupTargetState i:nil=”true” />
   <d3p1:FailoverOptions i:nil=”true” />
   <d3p1:MonitorPersistedState>
   <Id>ccaa7cc7-02af-4559-aac1-0129810bd838</Id>
   </d3p1:MonitorPersistedState>
   <d3p1:ProtectionConnectionPersistedState>
   <EngineConnectionId>1</EngineConnectionId>
   <Id>354cb4ab-eaca-46dd-a6ed-a74025c9287c</Id>
   <InitialMirrorComplete>true</InitialMirrorComplete>
   <SourceAddress i:nil=”true” />
   <SourceEnginePort>0</SourceEnginePort>
   </d3p1:ProtectionConnectionPersistedState>
   <d3p1:ProtectionTargetState>FailoverMonitoring</d3p1:ProtectionTargetState>
   <d3p1:State>DoubleTake.FullServer.Service.Jobs.States.>JobStateProtecting </d3p1:State>
   <d3p1:SystemVolumeRevertPersistedState i:nil=”true” />
   </FullServerPersistedState>
   </JobPersistedState>
4. Start the Double-Take Management service and Open the Double-Take Management console to failover.