Recover Eucalyptus Cloud Data

Recovering Your Cloud Data

We recommend that you recover the following data:

• The cloud database: see Restore the Database
• Object storage. For objects in Walrus, the frequency depends on current load. Use your own discretion to determine the restore plan and strategy.
  • Bucket and object metadata are stored in the cloud database. See Restore the Database.
  • In Walrus, the object data in the buckets are stored in /var/lib/eucalyptus/bukkits on all host machines running the Walrus Backend service. Restore this entire directory tree. If the total size of your objects is not too large for a tar file, you can use the tar command. For example:

    tar -xzvf ~/eucalyptus-objects.tgz -C /

  • For information about restoring Riak, see https://github.com/basho/basho_docs/blob/master/content/riak/kv/2.1.4/using/repair-recovery/failure-recovery.md.
• EBS volumes in each cluster (DAS and Overlay)
  • Ensure that the system is quiescent enough that volumes are unlikely to be written while restoring these files.
  • In DAS mode, use LVM to manage and preserve your volumes.
  • In Overlay mode, volumes are stored in /var/lib/eucalyptus/volumes on all host machines running the Storage Controller (SC) service. Restore this entire directory tree, which also contains snapshots in DAS and Overlay modes.
• The configuration file for the Eucalyptus cloud is stored on the CLC: /etc/eucalyptus/eucalyptus.conf.
• Any configuration file for the Eucalyptus cloud stored on any other host (UFS, CC, etc.): /etc/eucalyptus/eucalyptus.conf.
• The cloud security credentials on all hosts (you already restored the CLC keys as part of the database restore). Use the tar command:

  tar -xvf ~/eucalyptus-keydir.tgz -C /

  .
• The CC and NC configuration files, stored on every CC and NC: /etc/eucalyptus/httpd.conf.
• Any Euca2ools (.ini) configuration files, which reside on any Euca2ools host machine. Files in these directories:
  • /etc/euca2ools/euca2ools.ini
  • /etc/euca2ools/conf.d/*.ini
  • ~/.euca/*.ini, for any user's home directory.
  Note: Others besides the root user can have a ~/.euca directory, and any user might have more than one file in that directory. The user "joe" might have /home/joe/.euca with joe_as_viewer.ini and joe_as_admin.ini files.
• Management Console config files you backed up from /etc/eucaconsole should be restored. Typical files:

  -rw------- 1 eucaconsole eucaconsole 1505 Jul 19 20:32 console.crt
  -rwxr-xr-x 1 root        root        4848 Jul 19 18:06 console.ini
  -rw------- 1 eucaconsole eucaconsole 1704 Jul 19 20:32 console.key
  -rwxr-xr-x 1 root        root         116 Jul 19 18:06 memcached
  -rwxr-xr-x 1 root        root        2969 Jul 19 18:06 nginx.conf
  -rw-r----- 1 root        eucaconsole  119 Jul 19 20:32 session-keys.ini

• Ensure you have your instances' private ssh key files stored safely so you can access the instances.
• Eucalyptus and LVM snapshots
  • Ensure that the system is quiescent enough that snapshots are unlikely to be written while restoring these files.
  • Eucalyptus EBS snapshots for DAS and Overlay modes are stored in /var/lib/eucalyptus/volumes on all host machines running the Storage Controller (SC) service. Restore this entire directory tree, which also contains EBS volumes in Overlay mode only.
• SAN technologies vary, so see the restore documentation for your SAN.

Users are responsible for volume restore using EBS snapshots.