HP VAN SDN Controller Administrator Guide v3

• 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
◦ sdn_controller_backup_<ip-address>.zip.MD5
• Store the backups and associated checksum (MD5) files you take of 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.
8.2 Restore a Controller from a Backup
8.2.1 Restore Operation
NOTE: To restore a controller from a backup, it is necessary to re-install the controller. Otherwise
an Error 404 message appears and the backup will not be restored.
• In a controller team environment each active controller is restored as a single system.
• When the controller is deployed in a VM, standard VM restore tools (such as Snapshot or
Clone) can be used.
• When the controller is deployed on bare metal, standard Linux server-based backup/restore
tools (such as rsync, LVM snapshot, and Amanda/Zmanda) can be used.
• 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.
• When you start a restore, the REST response includes the location of a file where the system
restore progress is logged in a file named restore.log.
NOTE: The controller ceases to operate during a Restore operation.
8.2.2 System Restore Requirements
A system backup can be restored only to a system having the following:
• The same controller version that existed at the time the backup was taken.
• The same network settings (IP address) as were present at the backup.
• The same license ID as was in effect when the controller was installed.
NOTE: If you have modified any environment—specific settings in files such as
/opt/sdn/virgo/options or /etc/init/sdnc.conf, ensure that the appropriate changes are made to
these files after you re-install the controller and before you start the restore. For example, the network
interface that the Virgo service uses (default: eth0) may be eth1 or another setting on some systems.
8.2.3 To Restore a Controller from a Backup
1. Uninstall the controller(s) that will be restored. If this is a rollback to a previous state, uninstall
all controllers.
96 Backup/Restore