Restoring a deleted Controller in a production environment

 

If the Controller is deleted accidentally from the Director, there are two possible recovery options.

1. Restore the Versa Director configuration using the most recent backup created before the Controller was deleted.

2. Redeploy a new Controller through Versa Director

 

Option 1: Restore the Director configuration from a backup

Check whether a Versa Director backup is available from before the Controller was deleted.

Log in the Director shell and run the following commands:

cd /var/versa/backups

ls -ltr

 

 

Look for the backup file that was generated before the controller was deleted.

Once the appropriate backup file is identified, the Director configuration can be restored using the following command:

You can go to the Director cli and enter the following command:

request system recovery restore file <filename >

filename is the name of the backup file to restore from /var/versa/backups.

If you have enabled HA in your Director, restore the backup on the primary Director node:

1. Shut down services on the backup Director node:

admin@Primary-VD$ vsh stop

2.Restore the backup on the primary Director node, where filename is the name of the file to restore from /var/versa/backups:

admin@Primary-VD > request system recovery restore file filename

3. When the backup operation completes, check that all the Versa services are up on the primary Director node:

admin@Primary-VD$ vsh status

4. Start the Versa services on the backup Director node.

admin@Primary-VD $ vsh start

5. When the Versa services are up on the backup Director node, the HA sync operation on the backup Director node then syncs its configuration and database with those on the primary Director node.

When you restore from a backup file on the standby Director node, first copy the desired backup file from the standby node's /var/versa/local-backups directory to the /var/versa/backups directory, and then issue the request system recovery restore file command. If you do not first copy the desired file, the restore operation fails, because the /var/versa/backups directory on the standby Director node contains the synchronized copy of the backup file from the primary Director node.

 

Note: Please perform this activity during a planned maintenance window. Also, any configuration changes made after the selected backup was generated will be lost after the restore.

 

Option 2: Redeploy a new Controller through Versa Director

The second option would be to redeploy a new Controller. However, in environments with a large number of branches, this process may require significant effort. Redeploying the Controller changes the local and peer authentication keys used for the IPsec tunnels between the Controller and the branches. In the post-staging template, we would need to select the newly deployed controller. After that, the templates would need to be committed again to resync the branches with the Controller.

 

Please follow the document below for onboarding a new Controller.

https://support.versa-networks.com/kb?id=kb_article_view&sysparm_article=KB0012225