Backing up and restoring software

Blue Planet backup behavior follows specific guidelines and support varies at the solution/application level. To understand how Blue Planet backs up solutions or applications, see Solution or application backup details.

To create the backup of your solution:

  1. Create the default.yaml file only if you use bpocore-orchestrate CLI to perform a backup.

    mkdir -p ~/.blueplanet/sites
cat >~/.blueplanet/sites/default.yaml <<EOF
base_url: https://localhost/
verify_certificate: false
auth_scheme: no-auth
auth_params: {}
EOF

  2. Initiate a backup of your solution. This example shows some environment variables for the backup of the orchestration solution. It uses environment variables that define your existing orchestration versions:

    solman "solution_backup bpdr.io.blueplanet.orchestrate:xx.xx.xx-latest PREVIOUS_ORCH_VERSION --label upgrade-to-NEW_ORCH_VERSION" quit

    Replace the above variables with the correct solution packages. Backups do not include configuration from /etc/bp2. You must back up this directory separately.

  3. Record the snapshot name (upgrade-to-NEW_ORCH_VERSION) for later use:

    SNAPSHOT_NAME="<last line of output>"

    If you want to copy the snapshot to another host, the snapshot is located in /bp2/snapshots.

To restore a backup of your solution:

  1. Before you begin, check Nagios and make sure no critical alarms are raised for bpocore and other integral parts of the system. If alarms are raised, resolve them before you continue.

  2. Initiate a restore of your solution. The examples shows some environment variables for the backup of the orchestration solution. It uses environment variables that define your existing orchestration versions:

    solman "solution_restore ${SOLUTION}:${NEW_VERSION} ${SNAPSHOT_NAME}"
    solman "solution_restore ${SOLUTION}:${NEW_VERSION} bpdr.io.blueplanet.orchestrate:xx.xx.xx-latest"

For more details on additional steps to perform after restore, see your upgrade documentation or contact Ciena Customer Service.

Solution or application backup details

The following details describe useful information about how Blue Planet solutions are backed up during a backup procedure.

  • Backup support is at the solution level. For orchestration users, perform your backup of solution-orchestrate. The orchestrate_ui, nfvo, and RA solutions are stateless and do not need to be backed up.

  • Backup support for companion solutions varies by solution. Logging, alarms, geored, and performance management do not require backup or restore, so are not supported.

  • Backup data for supported solutions are stored in a single snapshot file. This is true for both single-host or multi-host configurations.

  • The data in a backup depends on the application, but it generally does not include logs or configuration data. For orchestration, the snapshot is primarily the databases, the asset area git repos, and onboarded SSH keys. No data stored in Kafka is backed up or restored.

  • The snapshot file resides on the host that contains the active Solution Manager. The Solution Manager provides an API to download the snapshot to a location outside of the Blue Planet site.

  • Backups record the current operational state of the site. You must move backup files to an off-site location to provide reliable recovery to a catastrophic hardware failure (CHF). A CHF cluster site failure is when two or more hosts on a three-host high availability (HA) site fail. If you do not archive backup files at another location, the existing backup files may not provide reliable recovery from a catastrophic user error; for example, deletion of a database.

results matching ""

    No results matching ""