Storage

TheStoragepage lets you select and configure target devices for backup. Once configured, a device can be thenboundwhile creating a backup set on the backup set page.  

Storages Page Overview  

Below table shows, the devices associated with different AE Servers. One device can be associated with one or more servers.  

 

   

   

Storage Device Type is the type of the storage device; existing devices can be filtered/sorted based on the type.  

Device Name is the name of the device as specified on the Admin Devices page.  

Associated Server: A Storage device should be associated with a Server. Cloud Storage devices can be associated with more than one server.  

Status shows the status of the Storage device.  

A green checkmark means the device Active on all the servers that are associated with.  

A red dash sign-meaning the device is inactive on all the servers that are associated with it.  

A crescent for partial meaning the storage device inactive on any of the associated servers.  

Actions:  

Edit: You may edit parameters of allowed fields in any of the existing Storage record.  

Clone: You may clone any existing Storage record to create a new one with few unique parameters.  

Delete: You may delete any/all of the existing Storage Device records by selecting multiple records if they haven’t bound with any backup set.  

  

Adding a Storage Device  

When you click on Add Storage (Simple Disk, Legacy, Cloud Storage, or Tape Storage), the options for that device are displayed in the right pane, as shown below.  

 

  

Click on desired storage option and enter the details as shown below and Click Save. Devices already configured are listed in the Storage main page along with buttons that allow you toEdit,Delete,andClonethe device, as shown above in Storage page overview. When there are more items that can be listed on one page, page navigation links at the top of the table allow you to move between pages.  

  

 

  

Advanced Options:  

Each Device has advanced options that are required to be modified only under special circumstances or when the Zmanda Support team requests you to do so. Please see the specific device section about the advanced options available.  

All devices must have aName; a descriptive Commentis optional. Device-specific options are described in the subsections that follow.  

  

Disk Storage Device  

Using hard disk space for a backup provides a number of important benefits:  

·                       The backup window (in other words, the total time to execute backups) can be reduced.  

·                       Files can be conveniently restored directly from the disk, speeding the restore process.  

The disk can be a locally attached disk or NAS or SAN device. The disk must accessible from the Amanda server.  

 

 

  

Device Name  

A unique name for the Device that will be used in the further configuration.  

Root Path  

The directory where the backup images will be stored, specified when the device was configured in the Storages page.  

Comments  

Enter a descriptive comment, such as operational notes.  

  

Legacy / Virtual tape Storage device  

 

  

Device Name  

A unique name for the Device that will be used in the further configuration.  

Comments  

Enter a descriptive comment, such as operational notes.  

Root Path  

The directory where the backup images will be stored, specified when the device was configured in the Storages page.  

Tip: The amount of free space available to hold backup images is an important consideration for fast retrieval of data. To ensure effective restore capabilities, set aside sufficient disk space to hold more than one full Backup Set worth of Data. Just how many full Backup Sets you should keep on disk depends on the data and your sites requirements for quick restores of accidentally deleted data. The more full backup images stored, the longer the retention of accidentally deleted files. Start with enough space to hold three full Backup Set images and adjust this number as experience dictates.  

Tip: Because there is no value in creating a backup of a backup on the same media, Zmanda recommends that the drive that holds the vtapes be excluded from the Backup Set that points to the vtapes.  

Reserved Percent  

Most file systems reserve a certain amount of free space. This value is used for free space calculations to provide ZMC warnings when the backup volume is running out of space.   

Advanced Options for Disk should not be modified unless Zmanda Support Team recommends you to do so.  

  

Tape Changer     

The user can now detect the changer, tape drive and the Data Transfer Element associated with the tape drive easily. This especially helps in identifying a barcode mismatch if it all it occurs.  

Prerequisites: 

 

Mt-st is required to be installed to check the status of the tape drives at the ZMC server. 

 

Identifying the Tape Changer:    

The persistent name of the changer is displayed while creating tape storage. Persistent names cannot be changed which enables the user to know which changer is used while creating tape storage itself. While discovering the Tape changer for the first time, a warning message will be displayed whcih will suggest, Not to use the tape changer if it's associated with an active backup.  

 

 

After creation of the Tape Storage below are details which are visible to the user :

 

 

  

Device Name  

A unique name for the Device that will be used in the further configuration.  

Tape Changer  

This information is provided for information only and cannot be changed. It can be changed in Storages page.  

Comments  

Enter a descriptive comment, such as the physical location of the device or any operational notes  

Bar code Reader  

You can disable barcode if the tape does not have barcode labels. This is not recommended because it is difficult to keep track of Amanda media labels and tape.  Users will have track this on their own if the barcodes are not enabled.  

On Linux servers, the output of lsscsi and mtx output is provided as a guide to fill out the values as shown below. On Solaris servers, mtx command output is provided (lsscsi command is not available on Solaris).  

 

Cloud Storage Devices  

ZMC supports most of the cloud platforms that can be used as Storage devices for backing up the data. Below are is the list.  

 

  

  

  

  Amazon S3   

 

  

Device Name  

A unique name for the Device that will be used in the further configuration.  

Storage Options  

·         Standard  

·         Reduced Redundancy (RRS)  

Comments  

Enter a descriptive comment, such as operational notes, Google account information.  

Cloud Encrypt  

User can opt for AES256 encryption of data that’s being backed up.  

Bucket Names  

Either of DNS or URL Path can be used for Bucket names.  

Secure Communications  

Enable this to perform secure SSL transfers of data to and from Amazon S3 cloud. Zmanda recommends enabling secure communication.  

  

  Google Cloud Platform  

 

 

  

Comments  

Enter a descriptive comment, such as operational notes, Google account information.  

Storage Option:  

·         Nearline  

·         Standard  

·         Durable Reduced Availability  

You can use storage that has less availability. This storage is less expensive. This value cannot be changed after it is set. Changing this value does not migrate data in the cloud.  

Secure Communications  

Enable or Disable secure backup and recovery to and from the cloud.  

  

OpenStack Cloud  

 

 

  

Device Name  

A unique name for the Device that will be used in the further configuration.  

Comments  

Enter a descriptive comment, such as operational notes.  

Project details     

Fill in valid Project ID, Project Name, and User Domain to create an Open Stack Swift Cloud Device.  

Secure Communications  

Enable or Disable secure backup and recovery to and from the cloud.  

Use Untrusted Certificate  

Enable to use the untrusted certificate.  

  

S3 Compatible Cloud  

Any cloud device that is compatible with AWS S3 can be used to create an S3 compatible storage device. Any AWS, Google Cloud and Wasabi accounts can be used for this.  

 

 

  

Device Name  

A unique name for the Device that will be used in the further configuration.  

Comments  

Enter a descriptive comment, such as operational notes.  

Bucket Names  

Either DNS or URL Path can be used for Bucket names.  

Secure Communications  

Enable or Disable secure backup and recovery to and from the cloud.  

 

Azure Cloud

 

  

  

Device Name 

A unique name for the Device, which will be used in the further configuration. 

Account Name 

Name of your Azure account. 

Account Key 

The Secret Key you obtained when signing up for Azure Cloud Storage. 

Storage Options 

  • Hot 

  • Cool 

Comments 

Enter a descriptive comment, such as operational notes, Azure account information. 

 

Advanced Options: 

Cloud Object Size 

Size of objects stored in Azure Cloud. If there is a network transmission failure, the object is re-transmitted. For network connections that are reliable, larger cloud object sizes can be used. 

Bucket Names 

Either of DNS or URL Path can be used for Bucket names. 

Secure Communications 

Enable or Disable secure backup and recovery to and from the cloud. 

Reuse Connections 

 

When a cloud communication failure occurs, Amanda will reuse the existing communication handle instead of recreating a new one. The default is to reuse communication handles. 

 

Wasabi Cloud  

 

 

  

Device Name  

A unique name for the Device that will be used in the further configuration.  

Comments  

Enter a descriptive comment, such as operational notes.  

Bucket Names  

Either DNS or URL Path can be used for Bucket names.  

Secure Communications  

Enable or Disable secure backup and recovery to and from the cloud.