Hi,
No worries - I thought maybe my question was obvious to the point of not
being worthy a reply... :)
Paul Bijns did point out to me that the starttime parameter would be the
one to try, so I will do that. Here's what he said:
The dumpers are not spread in order of the disklist. You cannot map
the third letter to the third server.
There is the disklist parameter "starttime":
starttime int
Default: none. Backups will not start until after this time of day.
The
value should be hh*100+mm, e.g. 6:30PM (18:30) would be entered as
1830.
e.g.
Server2 /dir4/backups/backup1 {
comp-user-tar
dumpcycle 0 # force a full backup each time
starttime 0700
}
Server3 /dir5/backups/backup2 {
comp-user-tar
dumpcycle 0
starttime 0705
}
So I've implemented his suggestions and will see what happens on the
next Amanda run.
Thanks!
Johan
-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org] On Behalf Of Jon LaBadie
Sent: 22 July 2008 15:10
To: amanda-users AT amanda DOT org
Subject: Re: dumporder parameter
On Tue, Jul 22, 2008 at 09:37:17AM +0100, Johan Booysen wrote:
> Hi,
>
> I got no reply so apologies if it was a stupid question. I'm now
simply
> using dumporder "Ssss", and Amanda seems to be dumping disklist
entries
> starting from largest to smallest, which will work just fine for me.
> I'm doing level 0 backups each night, and know how long the largest
DLE
> takes, so can reasonably accurately work out when to start the backup
> job.
>
> Anyways - I'll keep an eye on it just to make sure it keeps on doing
> that.
>
John,
I didn't reply because I've never used the feature.
As no one else has, I'll suggest you look at the "starttime"
parameter. If specified in a dumptype the dump of DLEs using
that dumptype will not begin until after the indicated time.
>
> -----Original Message-----
> From: owner-amanda-users AT amanda DOT org
> [mailto:owner-amanda-users AT amanda DOT org] On Behalf Of Johan Booysen
> Sent: 18 July 2008 21:20
> To: amanda-users AT amanda DOT org
> Subject: dumporder parameter
>
> I have a question about the dumporder parameter in amanda.conf.
>
> I want to back up 4 servers. The volumes of data on disk are as
> follows:
>
> Server1
> /dir1 298G
> /dir2 74G
> /dir3 66G
> Server2
> /dir4/backups/backup1 57G
> Server3
> /dir5/backups/backup2 28G
> Server4
> /dir6/backups/backup3 9.5G
>
> My problem is that all the data to back up on Server2, Server3, and
> Server4 isn't necessarily ready to be backed up until around 7am each
> morning (this could possibly be moved to as early as 5am, but not by
> much more than that). Server1 can be backed up at any time I wish
> during the night. The sizes of the data to be backed up are fairly
> static - I don't anticipate massive sudden increases (touch wood). I
> also now have the capacity to force full backups each night. The data
> on Servers 2, 3, and 4 will change completely each night anyway, so I
> know I'll be backing up the amounts as above, even if I used Amanda
the
> classic way of level 0s and level 1s.
>
> How can I configure the dumporder parameter to first back up Server1
(I
> know how long a level 0 of that will take to dump) before doing the
> other servers? Then I can plan more accurately when to actually start
> the backup job.
>
> Something like "SSsS", if I want to back up Server1 first, then
Server2,
> then Server4, and then Server3 (Server3 takes the longest to create
the
> data to back up, so should come last)?
>
> No sooner had I gotten the backup server to work with two tape drives,
> than one tape drive died. Now I have a fancy new tape drive with lots
> of capacity, so I'm trying to consolidate backups that previously were
> done seperately, i.e. previously Servers 2, 3, and 4 weren't part of
the
> Amanda backup routine at all.
>
> I'd appreciate any advice.
>
> Johan
>
>>> End of included message <<<
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
|
