<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://docs.stoneram.com/index.php?action=history&amp;feed=atom&amp;title=Revert</id>
		<title>Revert - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://docs.stoneram.com/index.php?action=history&amp;feed=atom&amp;title=Revert"/>
		<link rel="alternate" type="text/html" href="http://docs.stoneram.com/index.php?title=Revert&amp;action=history"/>
		<updated>2026-05-24T03:57:10Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.28.0</generator>

	<entry>
		<id>http://docs.stoneram.com/index.php?title=Revert&amp;diff=3055&amp;oldid=prev</id>
		<title>Lakshmi: Created page with &quot;===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...&quot;</title>
		<link rel="alternate" type="text/html" href="http://docs.stoneram.com/index.php?title=Revert&amp;diff=3055&amp;oldid=prev"/>
				<updated>2023-08-07T11:31:23Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;===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...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;===Introduction===&lt;br /&gt;
As a standard project approach, Tranzman also provides ability to rollback/revert in case of unforeseen situations.&lt;br /&gt;
Revert helps to bring back the original configuration on Origin and Destination.&lt;br /&gt;
&lt;br /&gt;
Consider below queries before deciding with the Revert option -&lt;br /&gt;
* Is it a revert or for just postponing the switch over?&lt;br /&gt;
* Is the revert, a temporary change in the plan, or a permanent decision to discontinue with the engagement?&lt;br /&gt;
* Is any new backups performed on the destination?&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
Tranzman tries to provide a solution to cover all typical use cases.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Reverting before Switch-Over===&lt;br /&gt;
* Reverting before switchover requires no additional steps as there has been NO change to the Origin environment.&lt;br /&gt;
* To continue with migration but with a new switchover date, then the &amp;lt;i&amp;gt;Planned switchover date&amp;lt;/i&amp;gt; has to be updated and no additional action is required.&lt;br /&gt;
* To STOP the Transition and to purge everything that was migrated on Destination, choose the Revert option and follow the steps displayed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Reverting after Switch-Over===&lt;br /&gt;
* To revert after switch-over, Tranzman will verify if the origin has been changed or demoted&lt;br /&gt;
* To continue to migrate with a new switchover date, then update the &amp;lt;i&amp;gt;Planned switchover date&amp;lt;/i&amp;gt; and while doing the revert select the &amp;lt;i&amp;gt;KEEP&amp;lt;/i&amp;gt; option&lt;br /&gt;
* To STOP the transition and to purge everything that was migrated to Destination, select the Revert option and follow the steps displayed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Reverting Clients/Media Server===&lt;br /&gt;
* Use Host Management to revert any clients/media servers to use the ORIGIN master by toggling to &amp;lt;i&amp;gt;REVERT&amp;lt;/i&amp;gt;&lt;br /&gt;
NOTE: This should only be performed before switch-over or after &amp;lt;b&amp;gt;Revert&amp;lt;/b&amp;gt; under &amp;lt;b&amp;gt;Tasks&amp;lt;/b&amp;gt; is completed.&lt;br /&gt;
* If the master has been switched then select the &amp;lt;b&amp;gt;Make origin master in host properties&amp;lt;/b&amp;gt; icon.&lt;br /&gt;
* To remove the destination from the list of servers, select the &amp;lt;b&amp;gt;Remove destination from host properties&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
During migration NBU certificates are not removed as it is only appended so Origin master doesn’t need any new certificate deployment. &amp;lt;br&amp;gt;&lt;br /&gt;
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 &amp;lt;i&amp;gt;nbcertcmd –getCaCertificate&amp;lt;/i&amp;gt; and &amp;lt;i&amp;gt;nbcertcmd –getcertificate&amp;lt;/i&amp;gt; after reverting the origin as master.&lt;/div&gt;</summary>
		<author><name>Lakshmi</name></author>	</entry>

	</feed>