Amanda-Users

Re: Alternating dump cycles for offsite storage

2005-12-01 15:27:56
Subject: Re: Alternating dump cycles for offsite storage
From: Joshua Baker-LePain <jlb17 AT duke DOT edu>
To: C Shore <alemc.2 AT bmts DOT com>
Date: Thu, 1 Dec 2005 15:15:04 -0500 (EST)
On Wed, 30 Nov 2005 at 8:05pm, C Shore wrote

I'm wondering if amanda can handle having two different configurations
which are used on alternating two week periods.  I know I could set up
DailySet1 and DailySet2 and a crontab that ran DailySet1 for the first
two weeks of the month and DailySet2 for the next two, but I'm not how
well amanda will deal with the two week gap between dumps.

Hrm.  It seems like:

dumpcycle 4 weeks
runspercycle 12
tapecycle 14

e.g., may work, but I've never tried anything of the sort. Note that I set runspercycle 2 less than tapecycle for a little bit of leeway.

The reason I want to do this is that I want to have offsite storage in
which I deposit one tapecyle's worth of tapes, and pull out the other
tapecylce's tapes.  (The dumpcycle would end up being 13 days because
the tapecycle must be greater than the dumpcycle).

And I like more than just 1 tape worth of extra space, just in case. I'm interested in this as well -- if you find a scheme that works well, definitely let the list and/or Wiki know.

tape on a given day.  Actually the dumps seems to be taking about 22
hours which is another problem for this approach.  I'm hoping the time
is reduced when I upgrade and divide out the server's tasks.

amplot can show you where all the time is being spent (in addition, of course, to just reading it in the report). Are your estimates really long? Is there just that much data to move? Are you hitting disk and/or network bottlenecks that you could iron out?

--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

<Prev in Thread] Current Thread [Next in Thread>