Table of contents
No headersZMC Backup How Page
After you have defined what, where and when for the backup set, you can use the Backup How page to define some of the key internal parameters that control how the backup set will run after it has been activated. In most situations, the default values set for these parameters will work well for most backup sets and therefore need not be changed.
Advanced users intending to modify the default values should study the logs and reports of a few past backup runs in light of the discussion that follows.
The parameters should be specified for each backup set. Select the backup set using the table at the bottom of the page by clicking the table row.
Performance Parameters
Media Utilization
Staging area holding disks are written in parallel. By the time the first completed Sources backup has been written to the media, many more Sources backups may also be ready to be moved. This parameter sets the algorithm that determines the order in which the completed backup images are moved from holding disk to the backup media.
Only completed backup images on the holding disk are considered for moving; the ordering of the images can help in better utilization of backup media.
Options are:
- First: (Default value) First in - first out.
- Firstfit: The first backup image that will fit on the current media volume.
- Largest: The largest backup image first.
- Largestfit: The largest backup image that will fit on the current media volume.
- Smallest: The smallest backup image first.
- Last: Last in - first out.
Backup Order
Whenever two or more parallel streams need simultaneous access to the same media volume, there is a potential conflict: Which stream should be allowed to write first?
Using Backup Order, you can assign priority to each of the parallel backup processes, the number of which is determined by the value of the "Parallel Backups" field above.
The possible option choices and what they mean is indicated below:
- s -> smallest size first
- S -> biggest size first
- t -> smallest time first
- T -> biggest time first
- b -> smallest bandwidth first
- B -> biggest bandwidth first
- Try BTBTBTBTBTBT if holding disks have not been assigned a threshold (see below)
Example 1 :
A string like "sssS" which represents the priority order for four parallel backups indicates that
three dumpers will seek the smallest size hosts
while one dumper will seek the biggest size host to backup.
Example 2 :
A string like 'BbsTt' indicates there are five parallel backup process of which:
One backup process(B) is looking for the Biggest Bandwidth occupying backups.
Another backup process(b) is looking for the smallest Bandwidth occupying backups.
Another backup process(s) is looking for the smallest size backups.
Another backup process(T) is looking for biggest Time occupying backups.
Another backup process(t) is looking for smallest Time occupying backups.
Server Parallel Backups
Sets the number of parallel data backups that are performed from the Amanda clients to the holding disk in a backup run. The default value is 10. How many parallel backups happen to the staging area/holding disk depends on
- CPU and Write speed on the Amanda server
- Network configuration between the Amanda server and Amanda client
Parallel Backup Clients
Sets the number of parallel backups performed from an Amanda client. The default value is 1, which specifies that all Sources on a client is backed up sequentially.
If an Amanda client has sufficient CPU and network resources, multiple Sources on the client could be backed up in parallel.
Ports for Parallel Backups
The port range to use on Amanda server to connect to clients. Amanda will use all the ports in the range that are not bound by another process or not reserved in the /etc/services file. You will have to increase the range (or use different range) if you are increasing the value of Server Parallel Backups.
Time Outs and Notifications
Mail Server Setup
To setup the mail server please go though the detailed documentation in link.
Email address Sets the e-mail address of the Amanda backup administrator. Though this is an optional parameter, it is important to set the Notification parameter to the email address(es) of the Amanda administrator. Amanda backup run notifications will be sent to the email address. The email address can be different from the email address set in the Admin page for a particular user. ZMC also provides content of the notification in the Report Summary page for the backup set. You can enter multiple email addresses separated by comma or white space characters.
The Mail User Agent (MUA) such as Mail should be configured on the Amanda server before any email can be sent. ZMC does not install or configure the MUA. Amanda uses /usr/bin/mail by default to send email notifications. To configure alternate mail program, please see Configuring Alternate Mail Program section.
Notification Type
A notification email will be sent to email ID/s specified in the "Notify Who" field. Multiple recepients can be added to the field.
Type of notification can be customized in the "Notification Type" widget which has following options:
- All notifications - Email recepients will be notified about successful/failure of the backup with a detailed report same as in Management Console.
- Only Errors - Email receipents will be notified only when the backup fails with error details.
- No Notifications - No notification emails will be sent upon selecting this option.
Backup Estimate (per Source/Backup Object)
Limits the amount of time the ZMC will spend on the first phase (Planning phase) of the backup process. The Amanda backup process first estimates the backup size for each Source configured in the backup set. The backup size estimation for all Sources in the backup set is done in parallel.
Specify a time out (in seconds) by which each Amanda client has to respond with a backup size estimate.
If the time out occurs for a particular Sources, that Sources will not be backed up during the backup run. Amanda will perform a full backup for the Sources in the next backup run.
The time out specified should take into account factors such as clients with limited network bandwidth, limited CPU, multiple Sources on one host, and clients with large amounts of data to be backed up.
Some idea of the time being taken to perform size estimates can be had from the Monitor page where details of the current backup run are displayed. A much better idea can be had from the Report Timeline page where Source-wise details are displayed.
If a Sources has timed out, it will be displayed in red. Other Sources are displayed in green.
Verification
ZMC Backup What verifies the configuration of the client/Backup object that is being added or modified. The client verification is controlled by this time out.
The time out may be adjusted for clients with limited network bandwidth.
If the time out expires, the verification of the client fails.
This time out has no impact on the backup process. If the client is properly set up, it will be backed up.
The time out applies to all clients in the backup set.
No Data Sent
Limits the time (in Seconds) that the Amanda server will wait (during the backup data transfer phase) for a client to begin to respond to a backup request.
If data time out occurs for a client, the backup of all directories for the client is not done in the backup run. The directories on the client will be backed up in the next backup run.
The time out may be adjusted for clients with limited network bandwidth.
The time out applies to all clients in the backup set.
Configuring an Alternative Mail Program
By default, Amanda assumes the local mail program found during initial configuration will be used to send notifications. You may wish to override this. For example, if your site uses an SMTP server, you can configure Amanda to use that instead of the program found during initial configuration. Use the mailer directive in the amanda.conf file:
mailer mail_program_path
The mail program must be able to process messages using the syntax:
MAILER -s "subject" user < message_file