Recovering the Snapshot Manager using manually provisioned virtual machine
You can also recover the Snapshot Manager using manually provisioned virtual machines.
Recover the Snapshot Manager manually
- Using your Azure portal, create a disk from the snapshot identified earlier, in the region where you want to create the Snapshot Manager instance.
- Create a new virtual machine with specifications equal to or higher than your previous Snapshot Manager server.
- Install docker on the new server. Docker and other system related requirements can be found in the NetBackup Snapshot Manager Install and Upgrade Guide.
- Attach the newly created volume to this Snapshot Manager server instance.
- Create the /cloudpoint mount directory on this server using the command:# mkdir /cloudpoint
- Login to the newly created Snapshot Manager instance. After identifying the device path of the newly attached volume in Step 1, mount the same to the /cloudpoint directory you just created by using the command: # mount <device-path> /cloudpoint
- Verify that all Snapshot Manager related configuration data are in the directory by using the command:# ls -l /cloudpoint
- Download or copy the Snapshot Manager installer binary to the newly created Snapshot Manager server instance.
- Install the Snapshot Manager using the following command:
flexsnap_configure install --primary <primary_hostname> --token <security_token> --hostnames <hostnames>
- In the case where a static external IP address is not assigned to the newly created instance, the IP address changes after creating a new machine. You need to regenerate the certificates.
To regenerate the Snapshot Manager certificates with the new IP address / hostname, perform the following steps.
Run the certificate regeneration script:
flexsnap_configure renew --hostnames <new-hostname> --token <auth-token>
Restart Snapshot Manager services:
use flexsnap_configure restart