Search <book_title>...

Product Documentation

Last Published: 2024-09-29

Product(s): Resiliency Platform (10.4)

Rollback steps in Azure environment

The rollback operation returns the image or any action to the previous state in case the upgrade fails.

Steps for rollback image in Azure environment

Download the Veritas_Resiliency_Platform_Azure_Upgrade_Scripts_<version>.zip from the Veritas Download Center.
Extract the bundle to obtain the rollbackTemplate.json and saved it locally.
Login to Azure portal.
Browse to the section Deploy a custom template option from Azure portal.
Select the option Build your own template in the editor.
Select the Load file option and load the rollbackTemplate.json file.
While clicking the Save button, it display the below template:
Below are the details of the attributes:

Table: Custom deployment template attributes

Attributes	Description
Subscription	Select the Subscription Name/ID where the original version Resiliency Platform virtual appliances are deployed.
Resource Group	This should be the same "Resource group" name that was used by the original Resiliency Platform virtual appliances.
Region	This is purely on customer discretion where they want to use.
Admin Password	This password is used by the Resiliency Platform virtual appliance once the rollback deployment is complete. It can be the same password used by the admin on the original virtual appliance (preferred) or provide a new password.
Appliance Name	This would be the display name for the Resiliency Platform virtual appliance
Appliance Hostname	This would be the FQDN or the exact full name of the Resiliency Platform virtual appliance when it was of the original version. Eg: If the original Resiliency Platform Resiliency Manager name was azure-rm-pr.abc.local with display name as Azure-RM, then in that case, the "Appliance name" field will have the value as "Azure-RM" and the "Appliance hostname" will have the value as "azure-rm-pr.abc.local".
Appliance Role	This can either be "Resiliency Manager" or "Infrastructure Management Server" depending on which type of appliance is planned for rollback.
Old Appliance Version	This would be current_version, for example if the older/original version was 4.0.
Appliance Deployment Type	This would be "Marketplace" if the original Resiliency Platform virtual appliance was deployed via Azure Marketplace itself.
Appliance virtual machine size	Ensure to select Standard_D8s_v3 for RM and Standard_F8s for IMS.
Image Name	This will be the image name that was created as a part of the "Prepare for upgrade" process. Refer to `Apply updates >> Upgrading Resiliency Platform in Azure environment` section in `Product documentation`.
Eth0Nic Name and Eth1Nic Name	Name of the NIC interfaces used by the older/original virtual appliance.
Primary NIC	This would be the "NIC" primarily used for all communications from the virtual appliance. By default, this is eth0 for all Resiliency Platform virtual appliance. (However, ensure to double check and confirm eth0 is the Primary NIC that was used by the older/original virtual appliance.)

8. Once the deployment process is completed, power on the virtual machine and login with the admin user with the password given in the above template.

9. Once successfully logged in, run the command updates > rollback-update.

Note:

If the rollback is done in a multiple Resiliency Manager setup with above steps, the database rebuild might take some time and until then the "Database service" will be in STOPPED state. It may take up to 30 minutes for database rebuild / repair operation depending upon the size of the database. Once the process is completed, verify the database services using manage > services status as ALL.

10. Finally, login to the Resiliency Manager console to confirm all resiliency group details are reflecting as expected.

Step 1: See Step 1: Prepare for upgrade.

Step 2: See Upgrading Resiliency Platform in Azure environment.

Step 3: See Step 3: Start the automatic bootstrap process.

Apply updatesSee About applying updates to Resiliency Platform.