Backing Up And Restoring; Backing Up And Restoring Best Practices; Backing Up A Controller - HP HPE VAN SDN Controller 2.7 Administrator's Manual

Table of Contents

Advertisement

9 Backing up and restoring

This chapter describes controller backup and restore actions using curl commands. For information
about the REST APIs related to backup and restore, see /restore and /backup in the RSdoc
facility on the controller. Using a Google Chrome browser window on the controller, enter:
https://system_ip_address:8443/api

Backing up and restoring Best Practices

You cannot use RSdoc to download or upload files.
Only one backup, restore, upload, or download operation can be active at any time on a
given controller or controller team. Parallel operations are not supported.
Use standard VM tools (such as Snapshot or Clone) to back up and restore the entire
controller image.
Use standard Linux server-based tools (such as rsync, LVM snapshot, and Amanda/Zmanda)
to back up and restore the controller on bare metal.
If you change the name of any of the following files, the controller backup will not be able to
backup the renamed file. So before the backup you should manually back up the renamed
files. Then after a restore, stop the controller service, copy the renamed files to the appropriate
location and restart the controller.
/opt/sdn/admin/keystore
/opt/sdn/admin/truststore
/opt/sdn/admin/sdnjar_trust.jks

Backing up a controller

A controller backup takes a snapshot of the controller state, and includes the following in a single
file:
Controller databases
License compliance history and metrics log data
In a teaming environment, the teaming configuration
User repository folder (for user-installed applications)
Controller configuration folder
Application data for applications that have implemented backup/restore functionality.
CAUTION:
and truststore files in the /opt/sdn/admin directory. If you have CA signed certificates or you
have added third party applications to the controller, you must back these files up separately and
recover them after restoration.
For backing up and restoring, Hewlett Packard Enterprise recommends that you use off-the-shelf
solutions such as rsync or Amanda. If your applications use the controller's backup and restore
service and you are using Cassandra, then consider the following:
To back up Cassandra, set the backupLockSeconds configurable Cassandra lock timer
parameter to the size of the data being backed up, the default is 10 minutes. Depending on
the size of the backup, Cassandra could be locked for up to 10 minutes.
If the applications that are using Cassandra encounter a lock timed out failure during the
backup, increase the timer. The failure will generate an error message Cassandra lock
134 Backing up and restoring
The controller does not back up the sdnjar_trust.jks file or existing keystore

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents