Create Remote Archive Volume

This article explains how to create a remote archive volume.

Backups can be stored online in a local archive volume or on a remote archive volume. If you want to use a remote archive volume and you did not create it during installation, you can create it later using EXAoperation.

Prerequisites

  • The URL to a remote storage service.

  • The user must have read and write access to the remote storage.

  • If DNS hostnames are used, ensure that the cluster has DNS servers configured.

  • All nodes must be able to reach the remote storage.

Configure remote archive volume in EXAoperation

Do the following to configure the remote archive volume:

  1. Log in to EXAoperation.
  2. Go to Services > EXAStorage and click on Add Remote Volume.

  3. Enter the following details:
    • Archive URL: Use the URL of the remote archive destination. For information about the supported protocols and example URLs, see Other protocols with URL examples.
    • User: Enter the name of the user.
    • Password: Enter the password for the user
    • Allowed Users: Select the EXAoperation users that can use the remote archive volume.
    • Read-only Users: Select the EXAoperation users that can read from the remote archive volume.

      Any user that you add as to the Read-only Users list will be limited to read-only access, even if the user is added to the Allowed Users list. If you have only one user in the Allowed Users list, do not add this user to the Read-only Users list.

    • Labels: Add a label to the remote archive volume for easy identification.
    • Options: You can add one or more options (separated by commas) depending on the protocol used. For more information, see Remote archive volume options.
  4. Click on Add to create the volume.

Remote archive volume options

The following options can be set in the Options field when creating a remote archive volume (depending on the protocol). You can enter multiple options separated by commas.

Option Description
cleanvolume Remote backups will be deleted on expiry. See also Backup Essentials.
noverifypeer Do not check the server certificate.
nocompression Write raw (uncompressed) data to the archive volume.
forcessl Use STARTTLS in the FTP connection.
webdav Set this option when using WebDAV for http (unencrypted) URLs.
webhdfs Set this option when connecting using the WebHDFS protocol (Apache Hadoop).
s3 Volume uses the S3 object format. This option is not required if the remote archive is an Amazon S3 bucket.
timeout=seconds Override the default client/server response time. For example: timeout=300
verbose Write more information to the logs. This will be required when troubleshooting problems with backups.

Other protocols with URL examples

The port numbers in this table are examples. Most protocols allow you to set the port.

Protocol URL example
FTP

ftp://<ftpserver>:2021/optional-directory/

FTPS ftps://<ftpserver>:2021/optional-directory/
SMB smb:////<smbserver>:2139/optional-directory/
WebHDFS

http://<hadoop-server>:2080/optional-directory/

https://<hadoop-server>:20443/optional-directory/

S3

http://<bucketname>.s3.amazonaws.com/optional-directory/

https://<bucketname>.s3.amazonaws.com/optional-directory/

For more information, see Create Remote Archive Volume with Amazon S3.
Azure Blob Storage http://storage_container_name.blob.corewindows.net/container_name

https://storage_container_name.blob.corewindows.net/container_name

For more information, see Create Remote Archive Volume with Azure Blob Storage.
Google Cloud Storage

http://<bucketname>.storage.googleapis.com

https://<bucketname>.storage.googleapis.com

For more information, see Create Remote Archive Volume with Google Cloud Storage.