Contents

1   Introduction

This document describes how to restore the configuration of Atlas for Cloud Execution Environment (CEE).

For more information about the atlas command used for the restore procedure, refer to Atlas Software Management Guide.

1.1   Prerequisites

This section describes the prerequisites which must be fulfilled before Atlas can be restored.

1.1.1   Conditions

Before the restore procedure can be performed, the following conditions must apply:

• The user needs root access to do a restore, using the atlas command.
• A valid backup file must be available in a predefined persistent storage location.

2   Basic Concepts

A restore of CEE Atlas is done by using the atlas command, executed from the Atlas Virtual Machine (VM). The input to restore the Atlas configuration is a previously taken backup, containing key configuration files.

A directory is created for each backup in /var/archives. The directory name consists of the default or a user-given name and the date. An example of a backup directory name is AtlasBackup1471858645. The backup directory consists of several files. Only the following information is stored as Atlas backup:

• A file containing the checksums of the other files, using sha256
• Content of all databases, belonging to the running mysql instance
• Content of the /etc/puppet/hieradata/passwords.yaml file
• Content of the root user directory
• Content of the atlasadm user directory

Note:  

The Atlas backup does not store time zone and Atlas GUI settings information.

An example of a complete set of backup files is shown in Example 1.

atlas_backup.1465911268.sha256.enc
atlas_backup.all-mysql-databases.1465911268.sql.bz2.enc
atlas_backup.etc-puppet-hieradata-passwords.yaml.1465911268.master.tar.gz.enc
atlas_backup.home-atlasadm.1465911268.master.tar.gz.enc
atlas_backup.root.1465911268.master.tar.gz.enc

The user must ensure that the backup file is fetched from an external persistent storage location.

The backup files consists of the default or user given name, content indication, the date, and a file extension. The date of the backup is in s format, where s is the number of seconds elapsed since 1970-01-01 00:00:00 UTC.

3   Downloading Backup Files from Swift

This section describes how backups are downloaded, that is copied, from the AtlasBackups container in Swift.

To download a backup from Swift, do the following:

1. Log on to the Atlas VM.
2. Switch user from atlasadm to root:

   atlasadm@atlas:~$ sudo -i

3. Ensure that the current directory is set to the backup directory:

   root@atlas:~# cd /var/archives/

4. Perform the following steps to verify that the backup files to download are available in Swift:
   1. If the Atlas backup ID is known, continue with Step_c.
   2. If the Atlas backup ID is unknown, search the Atlas backup ID from the list of the available backups in Swift by executing the following command:

      root@atlas:/var/archives# swift list AtlasBackups -d / AtlasBackup1478275297/ AtlasBackup1478620394/

      The command output displays the Atlas backup directories in the following format: <atlas_backup_name><backup_id>

   3. Use the following command to list the files stored for the given backup ID:

      root@atlas:/var/archives/# swift list AtlasBackups | grep <backup_id>

      Where backup_id is the ID of the backup.

      See below an example of the command and the output:

      root@atlas:/var/archives/# swift list AtlasBackups | grep 1465911268

      atlas_backup1465911268/atlas_backup.1465911268-all-mysql-databases.sql.bz2.enc atlas_backup1465911268/atlas_backup.1465911268-etc-puppet-hieradata-passwords.yaml.master.tar.gz.enc atlas_backup1465911268/atlas_backup.1465911268-home-atlasadm.master.tar.gz.enc atlas_backup1465911268/atlas_backup.1465911268-root.master.tar.gz.enc atlas_backup1465911268/atlas_backup.1465911268.sha256.enc

5. Download the backup for a specified ID:

   root@atlas:/var/archives/# swift download AtlasBackups -p <atlas_backup_name><backup_id>

   where atlas_backup_name is the name of the backup and backup_id is the ID of the backup.

   And example of the command is the following:

   root@atlas:/var/archives# swift download AtlasBackups -p atlas_backup1465911268

4   Atlas Restore

The restore feature replaces key configuration files and folders with the content in the backup.

To restore Atlas, do the following:

1. Determine if a local backup file is available, using the following atlas command:

   atlasadm@atlas:~$ sudo atlas backup-list

2. Select the relevant one of the following alternatives:
   1. If a local backup file is available, continue with Step 3.
   2. If no local backup is available, do the following:

      Copy the desired backup from the predefined persistent storage location to the directory /var/archives.

      For information on how to copy the backup using Swift, see Section 3.

3. Do the following:

   atlasadm@atlas:~$ sudo atlas backup-restore --d <backup_id> --p <backup_password>

   Example:

   atlasadm@atlas:~$ sudo atlas backup-restore --d 1465911268 --p <backup_password>

   The following output is received:
   Atlas has been set for restore.
   Please reboot.

   Note:  

   Reboot is mandatory after the execution of the restore command.

   
   
4. Log on to Atlas VM after reboot.
5. Verify that Atlas is operational.

   Note:  

   For an example of one way to verify that Atlas is operational, refer to section Post-Upgrade Activities in Atlas SW Upgrade.