View source for FAQ:Should I use a holdingdisk when the final destination of the backup is a virtual tape?

{{FAQ Header}}

[[Holding disk]]s and [[vtape]]s serve a complete different purpose:  holding disk allows different clients to backup simultaneously and the server collects the incomplete images in the holding disk.
When a backup image is complete, the server then adds it to the tape queue.
The taper can choose the best file, depending on the criteria you set in "[[taperalgo]]".
Especially "taperalgo largestfit" is helpful fitting as much as possible on a vtape.  
(e.g. when you want to burn the backups to a DVD later).

* [[Holding disk]]s allow paralellism and [[vtape]]s do not allow it by default (It can be configured to do paralellism).
* [[Holding disk]]s and [[vtape]]s should never be on the same hard disk.
* Use [[Holding disk]]s if it is faster than the [[vtape]]s , eg. [[Holding disk]]s on SSD or [[vtape]]s on USB.

To get parallel dump to vtape, add the following in the storage section:
 taper-parallel-write 10
 max-dle-by-volume 1

In case there are problems with your vtapes (e.g. the external disk with vtapes
is full, or got disconnected), then Amanda can still fall back to degraded mode, 
and dump only incrementals to the holding disk.

= Credit =
Based on text by Stefan G. Weichinger, November - December, 2003, with updates in April, 2005.
Updates in January, 2018 by Jean-Louis Martineau
{{Languages}}