Tapecycle: Difference between revisions
Jump to navigation
Jump to search
Powertoaster (talk | contribs) No edit summary |
Powertoaster (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
The ideal scenario is for the tapecycle to be at least [[runspercycle]]+1. It is possible to configure Amanda with fewer tapes than [[runspercycle]] but this scenario will not allow Amanda to function properly and will create at least the possibility of overwriting data that is still needed for a full restore. | The ideal scenario is for the tapecycle to be at least [[runspercycle]]+1. It is possible to configure Amanda with fewer tapes than [[runspercycle]] but this scenario will not allow Amanda to function properly and will create at least the possibility of overwriting data that is still needed for a full restore. | ||
Please see {{man|5|amanda.conf}} for information on amanda.conf parameters. | |||
Revision as of 23:21, 8 September 2008
The tapecycle parameter defines the number of tapes that are available to Amanda. This value is primarily used to tell Amanda when it can overwrite tapes. In order to maintain the integrity of the backups completed in a dumpcycle Amanda will refuse to overwrite a tape inserted sooner than it should be.
The ideal scenario is for the tapecycle to be at least runspercycle+1. It is possible to configure Amanda with fewer tapes than runspercycle but this scenario will not allow Amanda to function properly and will create at least the possibility of overwriting data that is still needed for a full restore.
Please see amanda.conf(5) for information on amanda.conf parameters.