Backup and restore

Owned by Martin Skorupski
Last updated: Dec 18, 2019
1 min read

This page defines and describes the backup and restore procedures and policies to recover an entire running ONAP with all its components and configurations.



Backup configuration

An environment contains several components, systems and subsystems, and each has its own configuration. The configuration is essential to restore an environment, therefore all configurations should be stored as backup.

The following configurations are of interest:

  • assigned IP addresses and fully qualified domain names

  • Switch configuration of the infrastructure

  • Firewall configuration of the infrastructure

  • OpenStack Configurations

  • Kubernetes Configuration

  • Configuration of ONAP components

    • SO

    • AAI

    • DCAE

    • DMaaP

    • SDNC/SDN-R

    • ...

Question: how do we do this? Scripts? copy of helm charts?

All configuration needs to be in files and the files should be achieved on a daily basis (e.g. 2019-12-18T07:00:00Z-OWL-DEV.tar.gz).

Question: Is there a way to detect that the configuration did not change in the last 24h? - If yes there is no need to store the configuration again just under a different file name.

The file is automatically stored locally at 2 am local time and in addition, could be uploaded a partner lab (e.g. OWL → OSNL; OSNL → OWL)

Max the last seven configuration backups will be stored. 

Backup images

Images of critical infrastructure (switches, firewalls, bare-metal servers) should be stored on a daily bases at 2 am local time.

The images of VMs and docker containers are not stored.