Prepare for disaster recovery

Cyberattacks, natural disasters, power and network outages, and application failures can occur without warning, resulting in damage to systems and data. By having a plan for backup operations and disaster recovery, you can help your organization recover.

Back up and recover installations

With Continuous Delivery, the system is not backed up automatically. Protect your deployment by using the standard backup procedure. The backups can be used to roll back to a previous state or restore your installation to a new disaster recovery system. See Back up and restore Continuous Delivery (CD).

Back up and recover configurations

The backup and recovery process for configurations involves regularly backing up system and application configuration settings. To optimize the process, the backups can be versioned and encrypted.

The installation of Continuous Delivery is essentially a Puppet Bolt project, which you can protect by using a source-control system. Because the files might contain an API key to access Puppet Forge, store the files in a private repository and follow these guidelines:

  • Ensure that only trusted users have access.

  • Use a Puppetfile in the Bolt project to manage the application version via the module.

  • Do not allow untrusted users to create branches in the Bolt project.

  • Consider implementing additional controls such as peer reviews and security gates.

The standard backup procedure also generates copies of the configuration data. See Back up and restore Continuous Delivery (CD).

Back up and recover hosted data

With Continuous Delivery, you can back up and recover hosted data by using the standard backup and recovery procedures: