HP VAN SDN Controller Administrator Guide

where <file-name> is just the name of the file and <path-and-file-name> is

the full path to the file and the filename. This should match the <path-and-

file-name> used for the .zip file during the backup. The filename MUST match

the name you used during the backup.

curl --noproxy <controller_ip> -X POST --fail -ksSfL --url

"https://<controller_ip>:8443/sdn/v2.0/systems/<controller_uid>/backup" -H "X-Auth-

Token:<auth_token>" -H HP-filename:<file-name>.zip.MD5 --data-binary @<path-and-file-

name>.zip.MD5

where <file-name> is just the name of the file and <path-and-file-name> is

the full path to the file and the filename. This should match the <path-and-file-

name> used for the .zip.MD5 file during the backup. The filename MUST match

the name you used during the backup.

b. Initiate the restore:

curl --noproxy <controller_ip> --header "X-Auth-Token:<auth_token>" --fail -ksS --

request POST --url

"https://<controller_ip>:8443/sdn/v2.0/systems/<controller_uid>/action" --data-binary

"restore"

8. For a controller team, wait for HA synchronization to complete to all the controllers

and wait for the team to become connected. The team can take a few minutes to come

back up. Be sure to verify that team status has all controllers as ACTIVE.

curl --noproxy <controller_ip> --header "X-Auth-Token:<auth_token>" --fail -ksSfL --

request GET --url https://<controller_ip>:8443/sdn/v2.0/systems

 If less than a quorum of controllers are restored, then those controllers will be

updated to the latest state of the running team via HA synchronization. (A

quorum is n/2+1 where n is the total number of controllers in a team. In a

three-controller team, a quorum is two controllers.)

 If the entire team is restored, then each controller will be reset to the previous

backed-up state.

9. Once the controller restore is complete, change CTL_RESTORE_INSTALL_MODE equal

to False in the “~/.sdn_install_options” file on each controller so that it does not

impact a future installation. This is because a future installation of the controller may

not involve starting in recovery mode. (This is the opposite of step 2 on page 71.)

You can follow the restore progress in the controller log found at /opt/sdn/backup/restore.log.

The controller log also records any Restore failure due to a REST communication problem.

Note

To restore a controller team, restore each controller as a standalone controller.

See Distributed (Team) Backup and Restore, below.