Revert

Introduction

As a standard project approach, Tranzman also provides ability to rollback/revert in case of unforeseen situations. Revert helps to bring back the original configuration on Origin and Destination.

Consider below queries before deciding with the Revert option -

• Is it a revert or for just postponing the switch over?
• Is the revert, a temporary change in the plan, or a permanent decision to discontinue with the engagement?
• Is any new backups performed on the destination?

There are multiple points in an engagement when the decision to GO/NO-GO should be considered, and at each point the process or requirements of a revert differs. Tranzman tries to provide a solution to cover all typical use cases.

Reverting before Switch-Over

• Reverting before switchover requires no additional steps as there has been NO change to the Origin environment.
• To continue with migration but with a new switchover date, then the Planned switchover date has to be updated and no additional action is required.
• To STOP the Transition and to purge everything that was migrated on Destination, choose the Revert option and follow the steps displayed.

Reverting after Switch-Over

• To revert after switch-over, Tranzman will verify if the origin has been changed or demoted
• To continue to migrate with a new switchover date, then update the Planned switchover date and while doing the revert select the KEEP option
• To STOP the transition and to purge everything that was migrated to Destination, select the Revert option and follow the steps displayed.

Reverting Clients/Media Server

• Use Host Management to revert any clients/media servers to use the ORIGIN master by toggling to REVERT

NOTE: This should only be performed before switch-over or after Revert under Tasks is completed.

• If the master has been switched then select the Make origin master in host properties icon.
• To remove the destination from the list of servers, select the Remove destination from host properties

During migration NBU certificates are not removed as it is only appended so Origin master doesn’t need any new certificate deployment.
If a switch-over completed with origin demoted, it is possible that the certificate was deleted from the master. In this case, it can be updated using nbcertcmd –getCaCertificate and nbcertcmd –getcertificate after reverting the origin as master.