Re: Multiple storage-definitions, generating archive tapes
"Stefan G. Weichinger" <[email protected]> Mon, 8 Aug 2022 16:34:11 +0200
| Newsgroups | gmane.comp.archivers.amanda.user |
|---|---|
| Message-ID | <[email protected]> |
Am 04.08.22 um 10:08 schrieb Stefan G. Weichinger: > 1) I would have to "split" a physical tape change into 2 logical changers: > > 12 tapes for "daily" runs (= storage 1) > 12 tapes for "full-only" runs (= storage 2) > > (How) would amanda handle that? As there is only one tape drive it would > have to keep everything in the holding disk and write it 2 times > sequentially to each tape(set). I am working on 2 sites using multiple storages. One runs OK already using 2 changers in parallel. The second one only has one tape library. I define one changer using slots 1-4 (storage1) and the 2nd changer with slots 5-8 (storage2). Both changers use the same and only tape drive ... that's why I need sequential processing. I am unsure how to use that correctly. My approach so far (not yet fully tested): # daily cronjob /usr/sbin/amdump config -ostorage=storage1 combined with flush-threshold-dumped 200 # (or more) flush-threshold-scheduled 200 # (or more) taperflush 200 autoflush yes this should keep the holding disk files. Now if I want to write these to storage2: do I run amdump or amflush? (assuming I use "-o storage=storage2") That second storage should be allowed to clear the written DLEs from the holdingdisk.