Backup Operation - HP HPE VAN SDN Controller 2.7 Administrator's Manual

timed out before backup was finished. in the
/var/log/sdn/virgo/logs/log.log file.
To configure the backupLockSeconds parameter:
1. Login to the GUI.
2. Click Configurations.
3. From the list of configurations, click
com.hp.sdn.teaming.impl.CassandraProcessManager.
4. Click Modify.
See "Configuration components" (page
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.

Backup operation

A controller backup includes the controller configuration and databases in one *.zip file.
Backups run in the background, and, except for locking the Cassandra database to prevent
writes, do not interrupt system operation.
Whether operating in a team or operating in standalone mode, each controller is backed-up
as a single system.
When the controller is deployed in a VM, standard VM backup/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.
To complete a teamed backup, no controller can be in a failed state. (A controller team must
have three controllers.)
On any controller or controller team, only one operation can run at any given time (backup,
restore, upload, or download). Also, starting a new backup while another backup is being
downloaded creates an error condition and halts the new backup.
Only authenticated users are allowed to create and restore backups. In some cases the
domain name is also required.
NOTE: The default domain name is sdn. The default username is also sdn. The default
password is skyline.
The controller does not save a non-default domain, user name, or pass-word across a backup.
Changing these settings to non-default values and later backing up the controller, resets these
settings to their defaults in the backup file. Later restoring the backup to the controller resets the
domain, user name, and password to their default settings in the controller.
For backup and restore of the Keystone configuration and database, see
the Keystone configuration and database" (page
If uploading a backup fails, then no backup version remains on the system.
Starting a new backup replaces any earlier backup remaining in the controller. If a backup
is being downloaded when a new backup is started, the new backup halts.
Metering time-series data is not encompassed by the controller backup process. There can
be a large amount of data, possibly tens of gigabytes in size, which is keyed to time. Not
only is the time series data impractical to back up because of its size, but upon restoring it
there is a likelihood that some of the restored data will not be usable because it will be older
than the sliding window of time that metrics are retained for on the controller. However, there
38).
140).
"Backing up and restoring
Backing up a controller 135