The Admin Devices page lets you select and configure target devices for backup. Once configured, a device is then bound to the current backup set.
When you click on a device type (Attached storage, Cloud Storage or Tape Storage) and click Add, the options for that device are displayed in the top pane as shown above. Devices already configured are listed in the bottom pane along with buttons that allow you to Edit, Delete, and Use the device as shown below. When there are more items that can be listed one page, page navigation links at the bottom of the table allow you to move between pages.
NDMP Changer Device can be used only with NDMP application. For more information, please see NDMP appliance application agent configuration.
All devices must have a Name; a descriptive Comment is optional. Device-specific options are described in the subsections that follow.
You can select the specific device to edit from the backup devices table. Clicking on List button will list the buckets/containers and objects in case of cloud device. All files (even non-Amanda objects) are listed. Following figure shows an example of Openstack cloud device containers and objects.
Root Path The directory to store backup images, specified as an absolute path.
When using vtapes, you must first decide whether to oversubscribe before you can determine how much disk space to allocate. If oversubscribing, you should still determine by how much you plan to oversubscribe and set up processes on the host system to alert you when oversubscription threatens to prevent backups from occuring.
If you set the number of vtapes in rotation to match the number of vtape slots on the Backup Where page (i.e. normal, recommended configuration), then to avoid oversubscription issues you must allocate disk space equal to the number of vtapes times the size of each vtape. Changes to either of these two parameters require adjusting the amount of disk space allocated for use by ZMC's backup set outside of Amanda, since currently the Amanda does not reserve space before usage.
Reserved Percent Percentage of the file system that should be free. This value depends on the file system in use. All file systems have reserve space. This value is used for ZMC disk space warning messages.
Output Buffer and Maximum Total DLEs need not be adjusted unless Zmanda support team recommends changes in these value for the backup set configuration.
Setting up an Amazon S3 storage device requires that you sign up for an Amazon S3 account and obtain the Access Key ID and Secret Key as described in Setting up an Amazon S3 Account for Use with Amanda. If the S3 account is already set up, you can obtain the Key ID and Secret Key by logging in here (Amazon username and password required), from where you can cut and paste the Key ID/Secret Key.
Storage Option
It can be either standard (Amazon S3 will complete redundancy and more availability) or Reduced Redundancy (Amazon S3 with reduced redundancy and less expensive storage).
Advanced Options
You can disable secure communications to the cloud. This will increase performance at the cost of security. This is recommended only when you are not backing up sensitive data and backing up from Amazon EC2 to Amazon S3.
You can also enable AES 256bit Cloud Encryption provided by Amazon. The backup data is stored at rest in S3 encrypted. The keys are managed by Amazon. Please note that you can enable this option even if you are using Amanda client or server encryption with your private keys.
Other options should be changed only if they are recommended by Zmanda Support team.
ZMC attempts to discover tape changer and tape drive device names automatically. The devices must be readable and writeable by amandabackup user.
Tape Size
Bar Code Reader
All other advanced options should be used when advised by Zmanda Support Team.
You will have to set up Google Account and sign up for Google Cloud Storage. You will have get access and secret keys from Google APIs console under Legacy Access from Google Cloud Storage tab.
Amanda Enterprise talks to Open Stack Swift cloud using Keystone authentication mechanism and without using S3 compatibility layer.
Identity/Auth Service
The IP address and port number used by Keystone authentication service.
Tenant Name
Tenant name or the project name that can be used to isolate resources for a group/project.
Access Key
Name of the user in the tenant or the access key.
Secret Key
Password of the user or the secret key.