Backup Destinations | Backup and Recovery

Last updated 1 year ago

A backup destination is a storage location where Storware Backup & Recovery keeps VMs, Containers, Cloud, and applications backup copies. To configure a backup destination, you can use the following storage types:

The backup destination is defined by the backup provider configuration and retention settings. Each policy can be backed up to the selected backup destination. Backup destinations must be assigned to the nodes in the node configuration.

Note: removal of any backup destination leaves data in the backup provider without an option to re-attach it in the future.

Retention

Note: Retention settings are described in chapter Backup SLAs - Policy - Rule

Pre/post access command execution

Prepare your scripts
- the pre-script is invoked before every access to the Backup Destination - common usage - create and mount the remote volume
- the post-script is executed after Node finishes store, restore, and clean-up operations
The following environment variables are set before each execution - you can use them later in your scripts:
- VP_VM_GUID - GUID of the VM in Storware Backup & Recovery
- VP_VM_UUID - UUID of the VM used by the hypervisor or hypervisor manager
- VP_VM_NAME - the name of the VM
- VP_VM_TMP_DIR - path to the folder containing files in the staging
- VP_BD_GUID - GUID of the Backup Destination being accessed
- VP_BD_NAME - the name of the Backup Destination being accessed
- VP_CONTAINER_NAME - standard container name generated by Storware Backup & Recovery that can be used for names of the volumes (format <VM-NAME>__<PART-OF-UUID>, for example Centos 7__8d3ef6f1, may contain special characters)
- VP_EXPORT_PATH - an export path from Node Configuration, can be used as the mount root for backup destination volumes
- VP_TASK_TYPE - the name of the task type, e.g.: STORE/RESTORE/DELETE_VM/OLD_BACKUPS_REMOVAL - to distinguish operation type when scripts are being invoked
Upload your scripts to the node, where the vprotect user is able to access them
Optionally, you may need to add a new file in the /etc/sudoers.d/ directory to enable the vprotect user to execute privileged script (like chown operations in some file system locations): %vprotect ALL=(root) NOPASSWD: /opt/vprotect/scripts/myscripts/privileged.sh
Open the "BACKUP DESTINATIONS" section from the left menu:

Open your Backup Destination (click on the name)
Provide pre/post access command arguments (the first argument is the command executed locally on the node):

Encryption

Last updated 1 year ago

Note: removal of any backup destination leaves data in the backup provider without an option to re-attach it in the future.

Retention

Note: Retention settings are described in chapter Backup SLAs - Policy - Rule

Pre/post access command execution

Prepare your scripts
- the pre-script is invoked before every access to the Backup Destination - common usage - create and mount the remote volume
- the post-script is executed after Node finishes store, restore, and clean-up operations
The following environment variables are set before each execution - you can use them later in your scripts:
- VP_VM_GUID - GUID of the VM in Storware Backup & Recovery
- VP_VM_UUID - UUID of the VM used by the hypervisor or hypervisor manager
- VP_VM_NAME - the name of the VM
- VP_VM_TMP_DIR - path to the folder containing files in the staging
- VP_BD_GUID - GUID of the Backup Destination being accessed
- VP_BD_NAME - the name of the Backup Destination being accessed
- VP_CONTAINER_NAME - standard container name generated by Storware Backup & Recovery that can be used for names of the volumes (format <VM-NAME>__<PART-OF-UUID>, for example Centos 7__8d3ef6f1, may contain special characters)
- VP_EXPORT_PATH - an export path from Node Configuration, can be used as the mount root for backup destination volumes
- VP_TASK_TYPE - the name of the task type, e.g.: STORE/RESTORE/DELETE_VM/OLD_BACKUPS_REMOVAL - to distinguish operation type when scripts are being invoked
Upload your scripts to the node, where the vprotect user is able to access them
Optionally, you may need to add a new file in the /etc/sudoers.d/ directory to enable the vprotect user to execute privileged script (like chown operations in some file system locations): %vprotect ALL=(root) NOPASSWD: /opt/vprotect/scripts/myscripts/privileged.sh
Open the "BACKUP DESTINATIONS" section from the left menu:

Open your Backup Destination (click on the name)
Provide pre/post access command arguments (the first argument is the command executed locally on the node):

Encryption

Backup Destination Name

Encryption supported?

Encrypted by

Encryption key stored in

Encryption key generation method

Encryption Algorithm