Prerequisites
Ensure the new backup location has the same ownership as the instance (such as the amp
user on Linux). You should also have separate sub-directories for each instance, so that backups don’t mix. This will be explained further below. This guide uses /media/backups
as an example, your actual location can vary.
For New Instances
- In ADS navigate to
Configuration->Instance Deployment->Deployment Defaults->Default Settings
- Add the following:
- Key -
LocalFileBackupPlugin.Storage.StorePath
- Value -
/media/backups/{{InstanceName}}/
- This will place the backups in their own subfolder based on the instance name.
If using Docker containers add the following for the specified instance in the instances.json
file within the datastore:
- Key -
CustomMountBinds
- Value -
{"/media/backups":"/media/backups"}
- Typically, these will be the same value on both sides, but for more info: The left side is the path on the host, the right side is the path in the container.
For Existing Instances
- Stop the instance
- In ADS File Manager/SFTP edit
LocalFileBackupPlugin.kvp
in the instance’s directory - Change the location for
Storage.StorePath
to the new location/media/backups/{{InstanceName}}/
. This will place the backups in its own subfolder based on the instance name. - Edit
FileManagerPlugin.kvp
in the same directory - Change the
FileManager.AdditionalVirtualDirectories
to{"backups":"/media/backups"}
and Save. (Left side is directory in the instance directory, right side is the actual folder location) - Start the instance in ADS