HP VAN SDN Controller Administrator Guide

Restore a Controller from a Backup

Restore Operation

Notes

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 will update 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.

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

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.

2. Before restoring a controller, set CTL_RESTORE_INSTALL_MODE=True in the

~/.sdn_install_options file in the home directory. If this file is not present in the directory,

create it with the CTL_RESTORE_INSTALL_MODE entry. If the file is already present, ensure

that it includes the CTL_RESTORE_INSTALL_MODE entry. This entry directs the installer to

perform the necessary changes to direct the controller to start in recovery/restore mode,

during which OpenFlow activity is suspended for the subject controller.

3. Re-install the failed controller(s), making sure to use the same IP address configuration.

During the re-installation, log messages similar to the following appear in the Audit Log:

root@mak:~/dev/controller/dist# dpkg -i hp-sdn-ctl_1.11_amd64.deb

Selecting previously unselected package hp-sdn-ctl.

(Reading database ... 212350 files and directories currently

installed.)