Backup Where

ZMC Backup Where Page   

The Backup Server and Backup Device are bounded during the creation of BackupSet itself. But the actual device configuration will be done on the Backup Where page. I,e, creation of zmc_binding.conf,  selecting location restriction for cloud storage. You will have to provide backup set specific information for each device depending on the type. Sections below provide more information on how to configure the device for the backup set.  

The physical object that stores a backup is referred to in Amanda as amedium. Thus, Amanda organizes all backup data in the following hierarchy (note thatslotsonly apply to a tape changer device):  

 

 

 

Regardless of the device type, the ZMC alsoallows you to define anoptional write-cache mechanism called a staging area or holding disk, which stores the backup image on the server's hard disk. Because backupscan be written in parallel to the holding disk, backups can be completed in much smaller windows than would be possible if writing directly to the device (even if the device is a virtual tape). The staging area can be configured in the Backup Staging 

 

 page. 

 

Backup Where Page Overview  

Advanced Options  

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

Disk backups  

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 locally attached disk or NAS or SAN device. The disk must accessible from the Amanda server. 

 

 

Comments  

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

  

Root Path  

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

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 ZMCwarnings when the backup volume is running out of space.  

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

 

 

Tape Changer 

 

 

Comments  

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

Taperscan  

The order in which tapes should be searched in the tape changer. Amanda has to load a tape to identify correct tape unless the barcode reader is available.  

Auto Label Tapes  

The 'Auto Label Tapes' radio button allows users to specify whether they want to use the facility of automatic labeling of tapes. The default value is set to No, meaning ZMC expects you to use the Backup Media to pre-label the tapes you intended to use for backup.Used tapes cannot be labeled automatically. Amanda will label the tape automatically based on the policy that is specified in the drop-down box. The list of policies are shown below 

 

 

Setting the policy to "Always" is dangerous and is not recommended. If you are using tape changer for multiple backup products including Amanda Enterprise, do not use "Only if Amanda label not found" policy.  

Slot range  

You can specify the list of slots that can be used for the backup set. Only tapes in these slots will be looked to find tapes for backups. The ranges can be specified as "2-5", "9-13".  

Changer Device  

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

Tape Drive Device  

The tape drive that should be used by the backup set. Please note that Amanda will usemtcommand to manage the device. You can specify multiple tape drives for a backup set. This will allow parallel backups to the tape changer. Users have to match the tape device name to drive slot number. If the match is not done correctly, correct tapes may not be loaded and written to. Use Update and verify button to make sure that the match is done correctly. Note that update and verify may take long time to check each tape drives.

Ignore Barcodes (Advanced Option)  

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.  

Identifying the Tape Drive and the DTE associated with it:    

In the Backup Where page, all the persistent names of tape drives associated with a particular changer are displayed. The data transfer element associated to a certain tape drive is also displayed which helps in keeping track of things really easy.

 

Amazon S3 

 

 

Comments  

Enter a descriptive comment, such as operational notes, amazon account owner.  

Archive To Glacier  

Select Archive To Glacier option to archive your backup for glacier. Number of days refers after how many days of backup archive should happen.  

Location Restriction  

The default isU.S. Standard(Closest Amazon U.S. data center). European customers should useEuropean Union(Amazon Ireland data centers) to reduce latency and backup Windows. Other S3 locations can beU.S.-West(Northern California data center),Asia Pacific(Singapore data center) and other S3 locations. The Storage and Data transfer pricing for each S3 location is different. For details on the storage and data transfer charges associated with different locations, see the Amazon S3 web site athttp://aws.amazon.com/s3/ 

Backups stored at  

The S3 bucket where the backup images will be stored, which was generated when the device was configured in the Storagepage.  

Secure Communications (Advanced Options)  

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

Speed Per Thread  

Users can throttle the network bandwidth for each upload and download thread. The speed limits apply only for the backup set. You can control the backup and restore from the cloud device.  

Threads Per Upload/Download  

Users can control the number of threads used to upload (backup) and download (restore) for the backup set.  

 

Google Cloud Storage 

 

 

Comments  

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

Location Restriction  

Backups can be stored in multiple regions of Google Cloud Storage  

Backups stored at  

The bucket where the backup images will be stored. This value cannot be changed.  

Durable Reduced Availability Storage  

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.  

Bandwidth throttle  

You can use all available bandwidth or throttle the upload (backup) or the download (restore) speed. The throttling is done per thread (see below).  

Parallel threads  

Each cloud object is uploaded or downloaded in separate thread. You can specify how many threads you want to use. Using too many threads might slow the system down.  

  

 

OpenStack Cloud 

 

C:\Users\Lavanya.Rajanna\Documents\Screenshots\Open_Stack_Backup_Where.png

 

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.  

Location Restriction  

Multiple regions in an OpenStack Cloud.  

Backups Stored at  

The bucket where the backup images will be stored. This value cannot be changed.  

Secure Communications  

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

Bandwidth Throttle (Speed per Thread)  

You can use all available bandwidth or throttle the upload (backup) or the download (restore) speed. The throttling is done per thread (see below).  

Parallel Threads (Threads Per Upload/ Download)  

Each cloud object is uploaded or downloaded in separate thread. You can specify how many threads you want to use. Using too many threads might slow the system down.  

 

S3 Compatible Storage 

 

C:\Users\Lavanya.Rajanna\Documents\Screenshots\S3_Compatible.png

 

Comments  

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

Location Restriction  

Backups can be stored in multiple regions of Google Cloud Storage  

Backups stored at  

The bucket where the backup images will be stored. This value cannot be changed.  

Durable Reduced Availability Storage  

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.  

Bandwidth throttle  

You can use all available bandwidth or throttle the upload (backup) or the download (restore) speed. The throttling is done per thread (see below).  

Parallel threads  

 

Each cloud object is uploaded or downloaded in separate thread. You can specify how many threads you want to use. Using too many threads might slow the system down. 

 

 

Wasabi Cloud 

 

C:\Users\Lavanya.Rajanna\Documents\Screenshots\Wasabi_Backup_Where.png

 

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.  

Location Restriction  

Multiple regions in a Wasabi Cloud.  

Backups Stored at  

The bucket where the backup images will be stored. This value cannot be changed.  

Secure Communications  

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

Bandwidth Throttle (Speed per Thread)  

You can use all available bandwidth or throttle the upload (backup) or the download (restore) speed. The throttling is done per thread (see below).  

Parallel Threads (Threads Per Upload/ Download)  

Each cloud object is uploaded or downloaded in separate thread. You can specify how many threads you want to use. Using too many threads might slow the system down.