Am 30.10.22 um 16:32 schrieb Exuvo:
Are you not supposed to do all the -Letter options before the
configuration name? Is that maybe why it does not work? I.e: amflush
-o storage=storage1 configurationNameHere
No.
amflush config -o storage=storage1
works fine so far.
My question is: how
Are you not supposed to do all the -Letter options before the configuration
name? Is that maybe why it does not work?
I.e: amflush -o storage=storage1 configurationNameHere
Anton "exuvo" Olsson
ex...@exuvo.se
On 2022-10-24 19:08, Stefan G. Weichinger wrote:
So far my setups with multiple
So far my setups with multiple storages work.
One of the missing features (or I don't know how):
if dumps stay in the holding disk I don't know which storage they would
go to via amflush.
I start
amflush config -o storage=storage1
and then see in amstatus, that all DLEs would go to
Am 23.08.22 um 23:16 schrieb Exuvo:
I use two separate backup configurations. One for weekly backups and one
for yearly archival.
The weekly i start from crontab and the archival one i start manually
with "sudo -u amanda amdump archive".
Each configuration has its own storage definition with
I use two separate backup configurations. One for weekly backups and one for
yearly archival.
The weekly i start from crontab and the archival one i start manually with "sudo -u
amanda amdump archive".
Each configuration has its own storage definition with tape names starting with
R or A (
Am 10.08.22 um 08:52 schrieb Stefan G. Weichinger:
What I try:
storage1 should leave the lev0 backups in the holding disk after writing
to tapes in pool1
storage2 should be allowed to remove them when written to the tapes in
pool2
Does noone else use multiple storage definitions?
I have
(resend with correct ML-email)
Am 09.08.22 um 16:50 schrieb Jose M Calhariz:
On Mon, Aug 08, 2022 at 04:34:11PM +0200, Stefan G. Weichinger wrote:
Am 04.08.22 um 10:08 schrieb Stefan G. Weichinger:
(...)
combined with
flush-threshold-dumped 200 # (or more)
flush-threshold-scheduled
On Mon, Aug 08, 2022 at 04:34:11PM +0200, Stefan G. Weichinger wrote:
> Am 04.08.22 um 10:08 schrieb Stefan G. Weichinger:
> (...)
>
> combined with
>
> flush-threshold-dumped200 # (or more)
> flush-threshold-scheduled 200 # (or more)
> taperflush200
My experience is this
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
Now that I understand a bit better how to use 2 storage-definitions I'd
like to improve a setup at a customer.
Back then I tried to use amvault, but didn't get the concepts right
(reading the old threads I see that I didn't even get the
command-options right ...).
What is set up right
10 matches
Mail list logo
