- Print
- PDF
Managing Backups of Device Configurations
Legacy orchestrator maintains backup files of the configuration of individual Provider Connectivity Assurance devices such as Provider Connectivity Assurance Sensors and Provider Connectivity Assurance Sensor Control. A configuration backup file contains the configuration of a particular device at a particular point in time. Configuration backups of devices are a safeguard mechanism for your operations groups.
This article explains how backup files are managed.
For the procedure to restore from backup, see "Restoring the Configuration of a Performance Element from Backup".
How Backups are Made, Managed and Restored
Backups are typically made on a daily basis using a configuration job combined with an executor scheduler (in the Commissioning pages).
You can manage backup files (and restore a Provider Connectivity Assurance device's configuration from a backup file) in the Devices ▶ Backup & Restore page.
You can also export a configuration backup to a file in the Backup & Restore page. See "Exporting a Configuration Backup".
Devices ▶ Backup & Restore Page
The following table explains the information displayed in the Devices ▶ Backup & Restore page.
Backup & Restore Dialog
List of Devices (left pane)
Parameter | Description |
---|---|
Device name | The host name of the device. This value is set on the device. Legacy orchestrator obtains the value from the device. |
Label | An identifier for the device that is defined and used in Legacy orchestrator. You can edit this by selecting the device in the Managed Elements list. |
Serial | The serial number of the Provider Connectivity Assurance device. This value is obtained from the device. |
IP | The IP address of the Provider Connectivity Assurance device. |
Backup Files section (right pane)
Parameter | Description |
---|---|
Backup creation time | The date and time when the backup file was created for the configuration file of a particular unit |
Description | The description of the configuration file associated with a particular unit. Maximum of 255 characters. You can modify this field by double-clicking the field and entering a new description. |
Keep | The Keep flag. If set, this backup file is excluded from the purge algorithm |
Auto activate restore | Determines whether the device will be rebooted automatically to activate the restore.
|
Backup Purge Mechanism
In order to avoid an uncontrolled accumulation of backup files in the Legacy orchestrator data store, a purge mechanism ensures that only the most recent backup files are kept.
The purge mechanism takes several factors into consideration:
- The Keep flag in the Backup & Restore page. These checkboxes allow the operator to classify backup files as either:
- Keepers: Backup files that will be excluded from the purge mechanism. They effectively become permanent backup files.
- Non-keepers: files that will be included in the purge mechanism.
- The number of backups made on a given day. The age of the backup file.
Backup File Maintenance Rules
Legacy orchestrator maintains backup files for each device according to these rules:
- Total backup files: A maximum of 14 backup files (seven keeper backup files; seven non-keeper files) can be present in the system for a particular device.
- Rules for non-keeper backup files:
- If several backup files are created on one day, only the latest file for that day will be kept.
- If more than seven non-keeper backups exist, the oldest one will be purged automatically at midnight (server time zone).
Example of how backup files are managed
As of June 8, for a particular device, you have a total of six non-keeper backup files from these dates:
- February 3
- March 4
- March 9
- April 21
- May 15
- June 7
On June 9, you make six backups of this device. At midnight, only the last backup for June 9 will be kept. The other five backups for June 9 are purged. The previous six backups will be kept. You have a total of seven non-keeper backups.
On July 10, you make another backup. At midnight, the file from February 3 is purged to keep the total at seven non-keeper backups.
On July 12, you check the Keep checkbox for the March 4 backup. You do not make any new backups so you have a total of seven backups (one keeper and six non-keepers).
On July 14, you make another backup. At midnight, no backups are purged (the March 4 backup is not purged because you have designated it as a keeper). You have eight backup files for the device (one keeper and seven non-keepers).
Deleting a Configuration Backup File Manually
To delete a configuration backup file for a device
- Select the Devices tab to access the Backup & Restore page.
- Select the device (in the left pane) whose backup file you want to delete. A list of the available configuration backup files is displayed in the right pane.
- Select the configuration backup that you want to delete.
- Click the Delete Backup button. You are prompted to confirm that you want to delete the configuration backup file.
- In the confirmation dialog, click OK to confirm that you want to delete the file.
Exporting a Configuration Backup
To export a configuration backup for a device to file
- Access the Devices ▶ Backup & Restore page.
- In the left pane, select the device whose backup you want to export.
A list of the available configuration backups is displayed in the right pane. - Select the configuration backup that you want to export.
- Click the Export button.
The backup file is downloaded to the location you choose.
To import a configuration backup file for a device
- Access the Devices ▶ Backup & Restore page.
- In the left pane, select the device whose backup you want to import.
- Click the Import from File button to open the Import backup file dialog.
- Click Choose File.
- In the file selector, select the configuration file that you want to import.
- Click Import.
- Click Close to close the dialog.
The imported backup appears in the list of available backups for the device.
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks