Backing Up A Controller; Downloading A Backup From The Controller To Another Location - HP HPE VAN SDN Controller 2.7 Administrator's Manual

is one metering file that is backed up and restored. It contains a mapping of metric descriptor
information (such as the ID of the application that created a metric and the metric's primary
tag, secondary tag, and name) to the UID that was assigned to each metric. When a restore
is performed, this file is restored, and any existing metering time-series data is deleted
because it might not match the restored file. The mappings that are restored might, depending
upon time elapsed since the backup was taken, be used to assign the same UID to a metric
created following the restore (and subsequent controller restart) that was assigned to the
metric before the backup was taken. This provides continuity for a metric across the time
spanned between backup and restore because all data for the metric is keyed to the same
UID. Thus, while time-series data from before the restore was not retained during the restore,
UIDs used to key time-series data that was exported to external tools or storage before the
restore will continue to be used for the same metrics.

Backing up a controller

1. 1. Acquire the authentication token for the controller backup:
curl --noproxy controller_ip -X POST --fail -ksSfL
--url "https://controller_ip:8443/sdn/v2.0/auth"
-H "Content-Type: application/json" --data-binary '{"login":
{"domain": "domain","user":
"user","password": "password"}}'
CAUTION:
tokens) used in curl commands might be saved in the command history. For security reasons,
Hewlett Packard Enterprise recommends that you disable command history prior to executing
commands containing credential information.
2. If needed, increase the Cassandra backupLockSeconds configuration using the GUI. See
"Configuration components" (page
3. Acquire the controller uid:
curl --noproxy controller_ip
--header "X-Auth-Token:auth_token" --fail -ksSfL --request GET
--url "https://controller_ip:8443/sdn/v2.0/systems"
4. Set the IP address of the controller using the following curl command:
curl --noproxy controller_ip>
--header "X-Auth-Token:auth_token" --fail -ksSfL --request PUT
"https://controller_ip:8443/sdn/v2.0/systems/controller_uid"
--data-binary '{"system":{"ip":"controller_ip"}}'
5. Perform the actual backup using the following curl command:
curl --noproxy controller_ip
--header "X-Auth-Token:auth_token" --fail -ksS --request POST
--url "https://controller_ip:8443/sdn/v2.0/backup"
6. Get the checksum to verify the backup file has not been corrupted.
curl --noproxy controller_ip --header "X-Auth-Token:auth_token" --fail -ksS --request GET --url
"https://controller_ip:8443/sdn/v2.0/backup/checksum"
7. Check on the status of a backup.
curl --noproxy controller_ip
--header "X-Auth-Token:auth_token" --fail -ksSfL --request GET
--url "https://controller_ip:8443/sdn/v2.0/backup/status"

Downloading a backup from the controller to another location

The backup file should be downloaded to a secure location. Choose the correct name now; you
cannot rename the files later or you will get a file corruption error when you attempt to upload it
for a restore.
136 Backing up and restoring
Credential information (user name, password, domain, and authentication
38).