Dear Ryan,
Actually not, and I have finally partially solved the problems by splitting up the disklist to smaller sized folder instead of backing the whole machine with only a "/". While I still got problem in backing up one of the /var/log folder of one of the machine and the folder is just
34.
On Tue, Sep 06, 2005 at 05:42:22PM +0100, Rodrigo Ventura wrote:
>
> That's an interesting configuration. I think I'll adopt something like
> that here. The only problem is that someone (i.e., me) will have to
> change the magazine at the right times. Hum, since each magazine has 6
> slots, can't
Paul Bijnens wrote:
Or is this a "level X without any historical data" (1 KB above)
with a default "comprate 0.50 0.50" which results in getting about
5 MByte compressed size?
Yes, I think that's exactly it.
Are you 100% sure there was no "previous" run at all? e.g. from
some little test
On Tue, Sep 06, 2005 at 05:09:56PM +0100, Rodrigo Ventura wrote:
>
> Another quick question: hitting end-of-tape error does not mean that
> the tape length setting in tapetype is wrong?
>
> I have:
>
> define tapetype HP-DAT-72x6 {
> comment "HP autoloader DAT 72x6"
> # data provided by
That's an interesting configuration. I think I'll adopt something like
that here. The only problem is that someone (i.e., me) will have to
change the magazine at the right times. Hum, since each magazine has 6
slots, can't use one per day, unless I skip a day, maybe sunday. I
also like the swappin
Another quick question: hitting end-of-tape error does not mean that
the tape length setting in tapetype is wrong?
I have:
define tapetype HP-DAT-72x6 {
comment "HP autoloader DAT 72x6"
# data provided by Rodrigo Ventura <[EMAIL PROTECTED]>
length 31255 mbytes
filemark 527 kbytes
Rodrigo Ventura wrote:
W.r.t. splitting dumps, is it safe to change the DLE file anytime? I'm
afraid of confusing amanda by changing the DLE file...
Yes, you can change the disklist at any time. You'll just need to
remember when you are going to restore something, that backups before
the spl
On Tue, Sep 06, 2005 at 04:29:27PM +0100, Rodrigo Ventura wrote:
>
> Thank you all for the valuable tips (might be a good idea to put some
> of those Q&A in a FAQ).
>
> > "Alexander" == Alexander Jolk <[EMAIL PROTECTED]> writes:
> Alexander> Since you seem to have 30GB tapes, splitting up
Hi again
I have run the following :
[EMAIL PROTECTED]:/ # amrecover DailySet1 -s myserver.smtl.co.uk -t
myserver.smtl.co.uk
AMRECOVER Version 2.4.4p2. Contacting server on nemesis.smtl.co.uk ...
220 nemesis AMANDA index server (2.4.4p2) ready.
200 Access OK
Setting restore date to today (2005-09-
Oops, I just read on amanda.conf:
autoflush no #
# if autoflush is set to yes, then amdump will schedule all dump on
# holding disks to be flush to tape during the run.
I misunderstood your mails, sorry, I'll set this to "yes" and wait for
the next normal dump. Tomorrow let's see the results.
C
Thank you all for the valuable tips (might be a good idea to put some
of those Q&A in a FAQ).
> "Alexander" == Alexander Jolk <[EMAIL PROTECTED]> writes:
Alexander> Since you seem to have 30GB tapes, splitting up those
Alexander> dumps above 3GB might be a good idea anyway, of course.
On Tue, Sep 06, 2005 at 03:07:54PM +0100, Chuck Amadi Systems Administrator
wrote:
> Hi I had a monthly and daily script that checked if it was last friday
> of the month.
> Thus it reverts back to daily config after amcheck notes that a monthly
> tape is still in the server thus I have since the
Hi I have looked at running command amrestore DailySet1 info myserver
Thus insert the tape SMTLSet103 as per the amadmin command below,thus
can I run amrestore -c /dev/nst0 myserver SMTLSet1
Thus have I go to rewind the tape first as I dont want to mess things
up.
amadmin DailySet1 info myserve
On Tue, Sep 06, 2005 at 03:55:58PM +0200, Alexander Jolk wrote:
> Jon LaBadie wrote:
> >On Tue, Sep 06, 2005 at 01:53:05PM +0100, Rodrigo Ventura wrote:
> >>NOTES:
> >> planner: omni /home/hm 20050906 0 [dumps too big, 6360061 KB, full dump
> >> delayed]
&g
Charles Sprickman wrote:
Me neither... Is there any way to increase the verbosity of amandad?
inetd config is good (it's a client, so it's only got the single line
for amandad), nothing in the system logs, all of the stuff in the
libexec directory appears to have correct perms (the proper th
Hi I have run
amrecover> history
200- Dump history for config "DailySet1" host "myserver.smtl.co.uk" disk
"/"
201- 2005-09-05 1 /dumps/amanda/20050905/myserver.smtl.co.uk._.1 0
201- 2005-09-02 0 SMTLSet103 1
201- 2005-09-01 0 SMTLSet102 1
201- 2005-08-31 0 SMTLSet101 1
201- 2005-08-30 0 SMTLSet110
Hi I had a monthly and daily script that checked if it was last friday
of the month.
Thus it reverts back to daily config after amcheck notes that a monthly
tape is still in the server thus I have since the first monthly tape was
used to backup I have been using daily tape thus data that We used on
2005/9/6, Jon LaBadie <[EMAIL PROTECTED]>:
> If I recall correctly your monthly backup used a new amanda config.
>
> Did you tell amrecover to use that new config rather than your default?
>
This question spurrs doubt in my mind.
What happens when you have multiple configurations with record=y
dump of omni://new/E$ on tape ISR005 overwritten on this
run.
planner: Incremental of damiao:/ bumped to level 2.
planner: Incremental of omni:/var/spool/imap/user/hm bumped to level 2.
planner: gtisr /usr 20050906 0 [dumps too big, 398656 KB, full dump delayed]
planner: damiao /usr 20050906 0
er/hm on tape ISR005
overwritten on this run.
planner: Last full dump of omni://new/E$ on tape ISR005 overwritten on this
run.
planner: Incremental of damiao:/ bumped to level 2.
planner: Incremental of omni:/var/spool/imap/user/hm bumped to level 2.
planner: gtisr /usr 20050906 0 [dump
Rodrigo Ventura wrote:
1. what's the meaning of "Some dumps may have been left in the holding
disk."? I mean, can I expect them to be dumped on the next amdump? Or
do I have to call amcleanup/amflush (which?) to check them out to
tape?
amflush, not amcleanup.
amflush is for flushing dumps from
Incremental of damiao:/ bumped to level 2.
> planner: Incremental of omni:/var/spool/imap/user/hm bumped to level 2.
> planner: gtisr /usr 20050906 0 [dumps too big, 398656 KB, full dump delayed]
> planner: damiao /usr 20050906 0 [dumps too big, 598668 KB, full dump
> delayed]
>
On Tue, Sep 06, 2005 at 01:28:25PM +0100, Chuck Amadi Systems Administrator
wrote:
> Hi I have just recently included a monthly backup script whereby I was
> advised to amend the parameters of dumptype {
>recored no
>}
> Thus as default was s
Guy Dallaire wrote:
Is 8kb enough for the filemark ? My last amdump reported en error
writing filemark (But it ran fine for the past 2 months)
There's a misunderstanding. The filemark length is just calculated by
amtapetype in order to estimate how much space your drive uses for
writing a fi
On Tue, 6 Sep 2005 at 7:54am, Guy Dallaire wrote
> Saturday night, I got a tape error (I/O error writing filemark). All
> the dumps were sent to the holding disk. I was not there this week
> end to run amflush.
>
> This morning, last night's amdump is still running.
>
> Will it dump the "holde
en on this run.
planner: Last full dump of omni://new/E$ on tape ISR005 overwritten on this
run.
planner: Incremental of damiao:/ bumped to level 2.
planner: Incremental of omni:/var/spool/imap/user/hm bumped to level 2.
planner: gtisr /usr 20050906 0 [dumps too big, 398656 KB, full dump de
Hi I have just recently included a monthly backup script whereby I was
advised to amend the parameters of dumptype {
recored no
}
Thus as default was set to yes I would cause amanda confusion.
Also when I tried a amrecover exercise I am now unab
Saturday night, I got a tape error (I/O error writing filemark). All
the dumps were sent to the holding disk. I was not there this week
end to run amflush.
This morning, last night's amdump is still running.
Will it dump the "holded" file systems in addition to it's regular dumps ?
I have:
define tapetype DLT4000-IIIXT {
comment "DLT4000 with DLTtape IIIXT uncompressed"
length 15000 mbytes
filemark 8 kbytes
speed 1536 kbytes
lbl-templ "/usr/local/etc/amanda/common/DLT.ps"
}
define tapetype DLT4000-IV {
comment "DLT4000 or DLT7000 writing DLT4000 fo
29 matches
Mail list logo
