EasyManua.ls Logo

HP HPE VAN SDN Controller 2.7 - Recommended Backup Practices; Restoring a Controller from a Backup; Restore Operation

HP HPE VAN SDN Controller 2.7
231 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
NOTE: The file name must begin with sdn_controller_backup.
Download the Backup.zip File:
curl --noproxy controller_ip
--header "X-Auth-Token:auth_token" --fail -ksSfL --request GET
--url "https://system_ip:8443/sdn/v2.0/backup>path-and-file-name.zip"
Recommended backup practices
Do not run backup while making configuration changes. Instead, run the backup after
completing configuration changes. Otherwise, an inconsistent system state could result with
a subsequent restore.
Always back up all of the controllers in a team after a configuration change. Just backing up
a subset of the controllers is not sufficient.
Back up all of controllers in a team at approximately the same time. (Team backups can be
in sequence or in parallel). Do not allow days to pass in-between backups of different
controllers in the same team.
A completed backup should be downloaded from the controller to another location for
safekeeping. Include the IP address in the backup filename, so you can easily determine
which backup belongs to which controller in a team. Recommended file naming is:
sdn_controller_backup_ip-address.zip
Store the backup files you take off each controller in the team together, so they can easily
be retrieved for a future restore.
NOTE: If any controller in a team fails to complete the backup, start the backup over for all
members of the controller team.
Examples of curl commands in this guide use the --noproxy option, which is appropriate where
execution of curl commands do not need a proxy to access controllers. If your network is set up
such that a proxy is needed to access controllers, use the --proxy option. For details on curl
proxy options, visit http://curl.haxx.se/docs/manpage.html.
Restoring a controller from a backup
Restore operation
NOTE: To restore a controller from a backup, it is necessary to re-install the controller.
During a user-initiated restore operation, the controller GUI is not accessible and the controller
is not fully functional until the restore is complete.
In a controller team environment each active controller is restored as a single system.
If a backed-up controller in a team fails, use single-system restore to restore the controller.
The HA synchronization updates the controller to the latest version.
The controller blocks traffic over OpenFlow ports during a restore operation.
NOTE: The controller ceases to operate during a restore operation.
Restoring a controller from a backup 137

Table of Contents

Related product manuals