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 are 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 is reset to the previous backed-up state.

9.After the controller restore is complete, change the value of CTL_RESTORE_INSTALL_MODE 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 of “Restoring a controller from a backup ” (page 95).)

10.It is possible to query the restore status by using the get command at v2.0/restore/ status. Since the restore is not hitless, the REST query will fail until the controller has successfully restarted.

NOTE: To restore a controller team, restore each controller as a standalone controller. See “Distributed (team) backing up and restoring ” (page 97).

NOTE: Attempting to restore a backup taken on any release prior to version 2.3 will not complete.

9.3Distributed (team) backing up and restoring

In a team environment, all team members must successfully complete the backup.

A team backup consists of using the single-system backup process. All controllers in the team must be active, and all of the backups in the team should be done either serially at approximately the same time, or in parallel. To complete a teamed backup, no controller can be in a failed state. (A controller team must have three controllers.) In a team environment, all team members must successfully complete the backup for the backup to be successful.

A team restore consists of using the single-system restore process on each controller in the team. Like backups, a system restore in a team should be done either serially at approximately the same time, or in parallel.

NOTE: When restoring a team, be sure to re-install all of the controllers, before initiating the actual restore on any of the controllers.

Also, if backing up the team controllers was done serially, then the restore of the team controllers should be done in reverse order.

A controller that fails a restore operation is not allowed to rejoin the team, and must be re-added as a new controller.

There are reference scripts to automate the backup and restore of an entire team. See “Scripts” (page 121).

9.4 Backing up and restoring the keystone configuration and database

Backup/Restore for the Keystone configuration and database are separate actions from the controller Backup/Restore. The backup/restore does not backup any keystone related configuration/credentials therefore any changes made to keystone will be lost after the restore.

NOTE: These instructions apply to the default local Keystone instance (Keystone 2012.2) as specified in the HP VAN SDN Controller Installation Guide. If you are using a different Keystone installation, please follow the OpenStack instructions for backup/restore of the Keystone instance specific to your installation. For OpenStack documentation, visit http://docs.openstack.org.

9.3 Distributed (team) backing up and restoring 97