Amdump Only Creates Incremental Dumps in Holding Disk

From The Open Source Backup Wiki (Amanda, MySQL Backup, BackupPC)
Revision as of 23:18, 22 May 2007 by Dustin (talk | contribs) (reformat, use header template)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search



This article is a part of the Troubleshooting collection.

Problem

When Amanda cannot flush dumps to tape, it only creates incremental dumps.

Explanation

Amanda is supposed to be able to redirect the dumps to a specified holding disk in case there is a problem with the tape or drive. This "problem" can be anything from there being no tape in the drive, to the cable became disconnected.

Additionally, in some cases, you just want to fail all dumps to a holding disk in order to flush them all at once in order to save tapes.

Solution

Normally Amanda will only store incrementals on the holding disk, and full dumps will be skipped, as the default is to reserve 100% of the disk for degraded-mode, incremental backups. In order to allow full backups to be dumped to the holding disk, you must reduce the amount of space reserved for incrementals.

For example,

reserve 30

means to save at least 30% of the holding disk space for degraded mode (level 1 and higher) backups. That will allow 70 percent of the space to be used by full backups.

Credits

This text was originally contributed to the AMANDA-FAQ-O-Matic by [email protected].