Deployment Infrastructure—Restore Procedure

This procedure assumes that you have followed the Appliance Backup Requirements and that you initially use this procedure as part of a 'try and test'.

  1. Build the Appliance from the Thumb Installation Image (1hrs).

    The box must be re-thumbed with the initial thumb (that is, the earlier MOR level). Use the restored version of appliance.properties for the appliance initial configuration.

  2. Reconnect SAN Volumes (10mins).

    If you had previously configured the Appliance to store its critical artifacts on SAN then you need to reconnect the newly initialized logical volumes to the SAN.

  3. Restore backup files.

    Restore backup files to a temporary location on the appliance.

  4. Upload MORs.

    All required MOR files should be uploaded using VEAM. Menu Operations > Upload MOR as well as those infrastructure upgrades carried out (VEAM > Menu Help > Upgrade Infrastructure), starting from the oldest MOR.

    Note: Failure to upload the MORs result in VEAM showing errors against the restored configuration and the inability to re-create the pre-existing environments.

  5. Restore VEAM configuration.

    This step is critical to restoring the last working environment configuration.

    1. Connect to cmdctl.ventyxinternal, stop veam, stop puppet (use the service stop command).
    2. On cmdctl, delete all content of the following local directory containing the GIT Clone of customer configuration database:

    /appliance/data/conf/git-repos

    Do not delete the directory. Directory contents should be similar to this:

    drwxr-xr-x 3 appliance cloud 4096 Feb 28 13:54 customer-config

    but other directories may be listed.

    1. If logical volume vgdata-lvconf contained valid data after re-attaching the SAN volumes, skip to step 5.
    2. On the appliance, restore the following directory containing the GIT bare customer configuration database from a backup copy:

    /appliance/data/conf/cmrepo

    1. On cmdctl, start puppet. This populates the customer configuration repository with the original restored data and restarts VEAM. Connect to VEAM and verify all environments are listed.
  6. Restore EFS.

    On the appliance, restore the following directiy containing the Enterprise File System (EFS):

    /appliance/data/efs

    It should be noted that the EFS stores application business process specific content. To maintain integrity, the EFS should be backed up when the DB is backed up. Any DB recovery to a point in time different to when the EFS backed up could result in data integrity issues.

7. Recreate Environments

The appliance re-configuration process is concluded at this stage.

  • Connect to VEAM and verify that all environment definitions are restored correctly.
  • Make a small environment change to any of the defined environments and click Submit to effectively recreate the servers.

This process requires some time, based on the number of servers defined at the time of the last backup.

8. Verify EFS

Connect to the existing environments and verify that reports (EFS restore).

The restore procedure is now complete.

Make sure your backups are recoverable before you need them!