Tapecycle

From The Open Source Backup Wiki (Amanda, MySQL Backup, BackupPC)
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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. This refusal is accomplished through a proper value for tapecycle which depends on runspercycle and runtapes.

The ideal scenario is for the tapecycle to be at least (runspercycle + 1) * runtapes. It is possible to configure Amanda with fewer tapes than runspercycle * runtapes 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 tapecycle configuration parameter is used in the Taperalgo.

The tapecycle configuration parameter, in addition to the usage above, is also used by the chg-disk changer driver to determine the number of virtual slots if a changerfile is not specified. When setting tapecycle to something other than the total number of slots in the virtual changer, create a separate changerfile configuration for chg-disk, and specify LASTSLOT=n, where n is the actual number of virtual slots.

Please see amanda.conf(5) for information on amanda.conf parameters.


Other languages: [[::Tapecycle|English]] {{#ifexist: {{#if: | | {{#if: | :}}Tapecycle}}/Fr |  • {{#if: |français| [[::Tapecycle/Fr|français]]}}|}}

{{#ifexist: {{#if: | | {{#if: | :}}Tapecycle}}/Zh-cn |  • {{#if: |中文(中国大陆)‎| [[::Tapecycle/Zh-cn|中文(中国大陆)‎]]}}|}}