AutoPilot Backups

Backups Section

The backups for deployments are created and viewed from the "Backups" tab for each deployment. This tab is accessed by selecting the deployment and selecting the "Backups" tab.

User -> Organization -> Deployment -> Backups

Backups can be manually created for each deployment. Backups from other deployments will not display on this screen, and backups are not interacted with from this screen.

Creating Backups

From the "Backups" Section of the deployment, input a meaningful backup name under the "Request Backup" section and select "Request."

Types of AutoPilot Backups

Database Data: This backup contains the automatic database dumps that are performed on a daily basis as well as the program data from the database application.

Web Files & Media: This backup contains the site files, logs, and configuration data.

Operating System: This backup is an image of the entire instance disk. This disk image can be used to persist data even if the instance is re-created. For example, if you installed the ionCube loader module. This type of backup is only available from within the deployment it was created.

Accessing 'Web Files & Media Storage' and 'Database Storage' Backups

'Database Storage', and 'Web Files & Media Storage' can be accessed from any deployment. These backups are mounted to the Jump instance and made available via a read-only mount. The files can then be copied from the read-only mount to the jump instance.

Mounting Backups

Backups can be mounted to the Jump node instance by navigating to the adjustment settings for the instance.

User -> Organization -> Deployment -> Adjust -> Jump Host Configuration -> Recovery Mount

From this dropdown, you will select the deployment from which the backup was taken, the type of backup, and finally, the backup to be accessed.

Deployment -> Backup Type -> Backup

Scroll to the bottom of the page and select "Push Update"

Note: Only one backup can be mounted at a time.

Accessing Mounted Backups

Mounted backups are accessed on the Jump node; they are mounted at the path /mnt/recovery-or-data. The mount can be verified with the following command.

$ findmnt /mnt/recovery-ro-data
TARGET SOURCE FSTYPE OPTIONS
/mnt/recovery-ro-data /dev/nvme2n1p1 xfs ro,relatime,nouuid,attr2,inode64,logbufs=8,logbsize=32k,sunit=8,swidth=8,noq

Using 'Operating System' Backups

Operating system backups are disk images of the entire instance operating system, including all the files needed for the instance to boot and operate. They store the current state of the instance, including any software that may have been added to it, like the ionCube loader or NewRelic. This allows new instances to be created that include the changes that have been made previously. The data on these backups is only available by using the backup image as the 'Operating System Image' in the instance configuration.

NOTE: Changing the operating system image on anything but the web tier will create downtime for that service because the nodes will need to be restarted in order to use the new image.

An Operating System backup for an instance can be selected through the instance adjustment tab.

User -> Organization -> Deployment -> Adjust

Select the instance you would like to modify

Select the image to use

Default Image -> Operating System -> Select Image

Scroll down and select "Push Update"

The status message "Modifying Deployment" will appear. Once this message disappears, the deployment has been modified, and the instance is using the selected operating system image.