Re: Re:
On Tue, 2005-07-19 at 21:01 +0200, Paul Bijnens wrote: > Yes, correct, but you still need ~amanda/.amandahosts instead of > /root/.amandahosts . Or ~backup/.amandahosts on Debian. I'm sure there's a good reason for their doing this... -- Glenn English [EMAIL PROTECTED] GPG ID: D0D7FF20 signature.asc Description: This is a digitally signed message part
Re: amindexd
That's the fix.
Thankyou.
Quoting Matt Hyclak <[EMAIL PROTECTED]>:
> On Tue, Jul 19, 2005 at 11:48:14AM -0600, [EMAIL PROTECTED] enlightened us:
> > I've tried different ownership for amindexd.
> >
> > Here's the xinetd configuration for amindexd.
> >
> > Thanks
> > Rich
> >
> >
> > [EMAIL PROTECTED] xinetd.d]# cat amandaidx
> > # default: off
> > #
> > # description: Part of the Amanda server package
> >
> > service amandaidx
> > {
> > socket_type = stream
> > protocol= tcp
> > wait= no
> > user= amanda
> > group = disk
> > server = /usr/lib/amanda/amindexd
> > disable = yes
> > }
> ^
>
> Doesn't work so good when it's disabled ;-)
>
> Change to no, restart xinetd, and hope you didn't mess up the permissions on
> amindexd. It should be 0755 by amanda:disk.
>
> Matt
>
> --
> Matt Hyclak
> Department of Mathematics
> Department of Social Work
> Ohio University
> (740) 593-1263
>
Re:
[EMAIL PROTECTED] wrote: You see, I had 127.0.0.1 configured for user amanda for amdump. Amrecover HAS to be run as root. Yes, correct, but you still need ~amanda/.amandahosts instead of /root/.amandahosts . -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amrestore from virtual tape
On Tue, Jul 19, 2005 at 12:26:16PM -0400, Jon LaBadie wrote: > > Ah, reading the man page and RTFMing the documentation helps a bit - I > Oh my gosh, now there is an idea, RTM ;)) My point exactly. ;) > > That, of course, would be a viable alternative to extracting the > > archives using amrestore. But how efficient/fast is that for whole disks? > Never timed it, but a WAG is that it would be similar. The actual commands > executing are the same except for the network transfer piece. > One thing to consider is that amrecover would restore to the state as of > a particular date. It would take the virtual tapes and dump files in > the corrrect order. Also, if the date you pick the restoration point > was an incremental, I believe files deleted between the level 0 and the > incremental will also be deleted in your amrecover'ed result. These > things would have to be done by humans with amrestore. Ack. > > The documentation on www.amanda.org seems to focus on amrestore for > > whole disks and advertises amrecover for individual files. > As is appropriate! Your OP questioned the possibility of amrecover > for the purpose, thus my comments. Thanks for your insights. I still need someone to definitely confirm that my way of accessing the vtape files with amrestore is right or give the proper way to do it, though. But what the heck - I can recover back and forth and sideways now using amrecover on any machine I like. ;) -- bye, Michael Against!
Re: amindexd
On Tue, Jul 19, 2005 at 11:48:14AM -0600, [EMAIL PROTECTED] enlightened us:
> I've tried different ownership for amindexd.
>
> Here's the xinetd configuration for amindexd.
>
> Thanks
> Rich
>
>
> [EMAIL PROTECTED] xinetd.d]# cat amandaidx
> # default: off
> #
> # description: Part of the Amanda server package
>
> service amandaidx
> {
> socket_type = stream
> protocol= tcp
> wait= no
> user= amanda
> group = disk
> server = /usr/lib/amanda/amindexd
> disable = yes
> }
^
Doesn't work so good when it's disabled ;-)
Change to no, restart xinetd, and hope you didn't mess up the permissions on
amindexd. It should be 0755 by amanda:disk.
Matt
--
Matt Hyclak
Department of Mathematics
Department of Social Work
Ohio University
(740) 593-1263
Re: amindexd
I've tried different ownership for amindexd.
Here's the xinetd configuration for amindexd.
Thanks
Rich
[EMAIL PROTECTED] xinetd.d]# cat amandaidx
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
server = /usr/lib/amanda/amindexd
disable = yes
}
Quoting Matt Hyclak <[EMAIL PROTECTED]>:
> On Tue, Jul 19, 2005 at 10:48:23AM -0600, [EMAIL PROTECTED] enlightened us:
> > Well.
> > I have checked the docs and faq.
> >
> >
> > I'm running the command as root as specified by the faq
> > http://amanda.sourceforge.net/cgi-bin/fom?_recurse=1&file=5
> >
> >
> > >You see, I had 127.0.0.1 configured for user amanda for amdump. Amrecover
> HAS
> > to be run as root.
> >
> >
> > Also running the command specifying index server and tape server fails in
> the
> > same way as if it were localhost.
> >
> > #amrecover CCC -s fastkernel.chem.utah.edu -t fastkernel.chem.utah.edu
> > AMRECOVER Version 2.4.4p1. Contacting server on fastkernel.chem.utah.edu
> ...
> > amrecover: cannot connect to fastkernel.chem.utah.edu: Connection refused
> > [EMAIL PROTECTED] xinetd.d]# cat /var/lib/amanda/.amandahosts
> > ##127.0.0.1 root
> > fastkernel.chem.utah.edu root
> >
> > Thanks for your help
> > Rich
>
> It looks like amindexd isn't listening. What is your xinetd configuration
> for amanda?
>
> Matt
>
> --
> Matt Hyclak
> Department of Mathematics
> Department of Social Work
> Ohio University
> (740) 593-1263
>
Re: ssh keys only
Gene Heskett wrote: Yes, Vicki. I haven't had to deal with that here, but perhaps someone else has rigged an ssh script to wrap amanda up in? You might consider shooting the co-worker :) Better yet, offload the problem onto the one that caused it by telling him there will be no backups of that server until he cuts a hole in things so amanda can continue to do her job. Point out how valuable the info on the server is & all that rot... The problem is fixed and the employee in question has been forced to work in a VAX environment for a week as punishment. Thanks. Vicki
Re: your mail
On Tue, Jul 19, 2005 at 10:48:23AM -0600, [EMAIL PROTECTED] enlightened us: > Well. > I have checked the docs and faq. > > > I'm running the command as root as specified by the faq > http://amanda.sourceforge.net/cgi-bin/fom?_recurse=1&file=5 > > > >You see, I had 127.0.0.1 configured for user amanda for amdump. Amrecover HAS > to be run as root. > > > Also running the command specifying index server and tape server fails in the > same way as if it were localhost. > > #amrecover CCC -s fastkernel.chem.utah.edu -t fastkernel.chem.utah.edu > AMRECOVER Version 2.4.4p1. Contacting server on fastkernel.chem.utah.edu ... > amrecover: cannot connect to fastkernel.chem.utah.edu: Connection refused > [EMAIL PROTECTED] xinetd.d]# cat /var/lib/amanda/.amandahosts > ##127.0.0.1 root > fastkernel.chem.utah.edu root > > Thanks for your help > Rich It looks like amindexd isn't listening. What is your xinetd configuration for amanda? Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
[no subject]
Well. I have checked the docs and faq. I'm running the command as root as specified by the faq http://amanda.sourceforge.net/cgi-bin/fom?_recurse=1&file=5 >You see, I had 127.0.0.1 configured for user amanda for amdump. Amrecover HAS to be run as root. Also running the command specifying index server and tape server fails in the same way as if it were localhost. #amrecover CCC -s fastkernel.chem.utah.edu -t fastkernel.chem.utah.edu AMRECOVER Version 2.4.4p1. Contacting server on fastkernel.chem.utah.edu ... amrecover: cannot connect to fastkernel.chem.utah.edu: Connection refused [EMAIL PROTECTED] xinetd.d]# cat /var/lib/amanda/.amandahosts ##127.0.0.1 root fastkernel.chem.utah.edu root Thanks for your help Rich
RE: all estimate failed
I had AMANDA installed as an RPM through synaptic, so I'm sure it had all kinds of default options. I tried to just change the dump user wherever I could find it. I noticed that some apps were still running as "amanda" so I uninstalled the RPM and manually compiled instead with the user=backup. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jon LaBadie Sent: Tuesday, July 19, 2005 11:31 AM To: amanda-users@amanda.org Subject: Re: all estimate failed On Tue, Jul 19, 2005 at 11:04:57AM -0400, LaValley, Brian E wrote: > I am all set now. Thanks for all the ideas. It turned out to be one of the > helper programs running as "amanda" instead of "backup" as a username. > "amanda" is a regular user on my systems. I just completed my first AMANDA > backup. > Was that due to a manual install rather than the "make install" done as root with programs built by you from the amanda sources? If the latter, some part of the install procedure needs to be checked. But I suspect that is not the case. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover fails with stream_client_privileged Connection refused
[EMAIL PROTECTED] wrote: Hi. I'd installed amanda a short time ago. Backups are working fine, however now I'm testing the recover and I'm not able to get the server to access itself. I've changed the user in /root/.amandahosts, commented out the localhost entry as well. And played with ownershop of amandaidx. All to no avail. # amrecover CCC AMRECOVER Version 2.4.4p1. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused cat amrecover.20050719094728.debug amrecover: debug 1 pid 2019 ruid 0 euid 0: start at Tue Jul 19 09:47:28 2005 amrecover: stream_client_privileged: connect to 127.0.0.1.10082 failed: Connection refused amrecover: cannot connect to localhost: Connection refused amrecover: pid 2019 finish time Tue Jul 19 09:47:28 2005 Would you please read the FAQ and/or the docs first? www.amanda.org Thanks, Stefan. -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting & implementation http://www.oops.co.at --
Re: amrestore from virtual tape
On Tue, Jul 19, 2005 at 05:53:00PM +0200, Michael Weiser wrote: > On Mon, Jul 18, 2005 at 04:01:25PM -0400, Jon LaBadie wrote: > > > > > The amrestore command is getting the file in uncompressed format > > > > even if it was compressed. If you want to transfer the compressed > > > > form I think you could add the -r option. > > > I think it's -c actually and the manpage is a bit ambiguous on the > > > actual workings it. From the phrasing I'd expect the files to be > > > uncompressed if necessary and then recompressed if requested using -c. > > > That would mean processing the whole archive twice - first uncompressing > > > then recompressing. > > It also says the -r options causes the output to be exactly as on "tape". > > Thus it 'should' avoid the double processing. > > Right. But ;) it goes on to say that this also includes amdump headers. > What good would that do? I wouldn't be able to extract it using the > original archive/dump program, would I? dd if=/dev/stdin of=stdout bs=32k skip=1 > > Ah, but that closes the circle: I wanted to know how to extract stuff > from virtual tapes using amrestore in the first place. Once I know that > I'm quite happy to do amrestore -p | ssh box cat/tar/whatever. > > But you peeked my interest: How do I feed the raw amdump file to > amrecover to extract individual files on the client? Wouldn't it need > the index from the server? I'm confused. ;) > > Ah, reading the man page and RTFMing the documentation helps a bit - I Oh my gosh, now there is an idea, RTM ;)) > That, of course, would be a viable alternative to extracting the > archives using amrestore. But how efficient/fast is that for whole disks? Never timed it, but a WAG is that it would be similar. The actual commands executing are the same except for the network transfer piece. One thing to consider is that amrecover would restore to the state as of a particular date. It would take the virtual tapes and dump files in the corrrect order. Also, if the date you pick the restoration point was an incremental, I believe files deleted between the level 0 and the incremental will also be deleted in your amrecover'ed result. These things would have to be done by humans with amrestore. > The documentation on www.amanda.org seems to focus on amrestore for > whole disks and advertises amrecover for individual files. As is appropriate! Your OP questioned the possibility of amrecover for the purpose, thus my comments. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover fails with stream_client_privileged Connection refused
[EMAIL PROTECTED] wrote: Hi. I'd installed amanda a short time ago. Backups are working fine, however now I'm testing the recover and I'm not able to get the server to access itself. I've changed the user in /root/.amandahosts, commented out the Root??? Shouldn't that be user ~amanda/.amandahosts. localhost entry as well. And played with ownershop of amandaidx. All to no avail. # amrecover CCC AMRECOVER Version 2.4.4p1. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused localhost??? try amrecover -t the.amanda.server -s the.amanda.server Now it's Stefan's turn to point to the FAQ about localhost again. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
amrecover fails with stream_client_privileged Connection refused
Hi. I'd installed amanda a short time ago. Backups are working fine, however now I'm testing the recover and I'm not able to get the server to access itself. I've changed the user in /root/.amandahosts, commented out the localhost entry as well. And played with ownershop of amandaidx. All to no avail. # amrecover CCC AMRECOVER Version 2.4.4p1. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused cat amrecover.20050719094728.debug amrecover: debug 1 pid 2019 ruid 0 euid 0: start at Tue Jul 19 09:47:28 2005 amrecover: stream_client_privileged: connect to 127.0.0.1.10082 failed: Connection refused amrecover: cannot connect to localhost: Connection refused amrecover: pid 2019 finish time Tue Jul 19 09:47:28 2005
Re: amrestore from virtual tape
On Mon, Jul 18, 2005 at 04:01:25PM -0400, Jon LaBadie wrote: > > > The amrestore command is getting the file in uncompressed format > > > even if it was compressed. If you want to transfer the compressed > > > form I think you could add the -r option. > > I think it's -c actually and the manpage is a bit ambiguous on the > > actual workings it. From the phrasing I'd expect the files to be > > uncompressed if necessary and then recompressed if requested using -c. > > That would mean processing the whole archive twice - first uncompressing > > then recompressing. > It also says the -r options causes the output to be exactly as on "tape". > Thus it 'should' avoid the double processing. Right. But ;) it goes on to say that this also includes amdump headers. What good would that do? I wouldn't be able to extract it using the original archive/dump program, would I? Or could I feed it to amrecover as implied below? > > > Using amrecover might be possible. I think when you specify to > > > extract a directory it extracts recursively anything under that > > > directory. So adding "/" or "." to the extract list (I forget the > > > semantics) might make recovery of the entire dump possible using > > > amrecover. > > Problem is: amrecover always restores to a directory on the backup > > server, doesn't it? So I'd have to NFS-mount some directory from the > > actual target machine to have the data go where I need it. If I want to > > restore the whole box anyway I find the archives more flexible. > Someone will correct me if I'm wrong. The backup program may not be > available on the tapehost. The client may have been some other > architecture or OS. I'm pretty certain that amrecover was made to > run on a remote client, transfer the dump using amrestore (and its > "-r" option) on the tapehost, and do the extraction on the client. Ah, but that closes the circle: I wanted to know how to extract stuff from virtual tapes using amrestore in the first place. Once I know that I'm quite happy to do amrestore -p | ssh box cat/tar/whatever. But you peeked my interest: How do I feed the raw amdump file to amrecover to extract individual files on the client? Wouldn't it need the index from the server? I'm confused. ;) Ah, reading the man page and RTFMing the documentation helps a bit - I think I get it now. So I just run amrecover on the box to be restored and it requests the index from the index server, lets me select the files I want and then requests those *over the network* as well, but from the tape host. That, of course, would be a viable alternative to extracting the archives using amrestore. But how efficient/fast is that for whole disks? The documentation on www.amanda.org seems to focus on amrestore for whole disks and advertises amrecover for individual files. -- Michael Sauced it has to be, sauced!
Re: all estimate failed
On Tue, Jul 19, 2005 at 11:04:57AM -0400, LaValley, Brian E wrote: > I am all set now. Thanks for all the ideas. It turned out to be one of the > helper programs running as "amanda" instead of "backup" as a username. > "amanda" is a regular user on my systems. I just completed my first AMANDA > backup. > Was that due to a manual install rather than the "make install" done as root with programs built by you from the amanda sources? If the latter, some part of the install procedure needs to be checked. But I suspect that is not the case. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: all estimate failed
I am all set now. Thanks for all the ideas. It turned out to be one of the
helper programs running as "amanda" instead of "backup" as a username.
"amanda" is a regular user on my systems. I just completed my first AMANDA
backup.
My etimeout was set at 300 seconds, and the amdump would fail immediately,
so I knew that wasn't the issue.
-Original Message-
From: Brian Cuttler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 19, 2005 10:02 AM
To: Gene Heskett; [EMAIL PROTECTED]
Cc: amanda-users@amanda.org
Subject: Re: all estimate failed
Brian,
Gene,
couple of things, 1st, I'm thinking that if there is a jukebox
involved (tape loaded from slot 3) then perhaps a 5 minute delay
to load the tape isn't necessarilly a problem. 2nd, I'm stupid
and should have seen it yesterday - estimate failed, suggest
raising the etimeout value is amanda.conf.
If the partition(s) are large and etimeout is low or the client is
slow for any reasons...
On Tue, Jul 19, 2005 at 08:57:57AM -0400, Gene Heskett wrote:
> On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
> >I do have some things in different places. What files should be in
> >/tmp/amanda?
> >I already had a username of amanda at this location, so my AMANDA
> > username is "backup"
> >Here is my amcheck run:
> >
> >[EMAIL PROTECTED] [27]>amcheck DailySet1
> >Amanda Tape Server Host Check
> >-
> >Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
> > available, that's plenty
> >amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
> >NOTE: skipping tape-writable test
> >Tape DailySet1-A03 label ok
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does
> > not exist
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does
> > not exist
> >Server check took 312.817 seconds
>
> Somethings definitely wrong here, but from this I've no idea what. It
> should not take a tape drive over 5 minutes to locate and load the
> next correct tape. My server check is usually a very small fraction
> of a second, but I'm also using virtual tapes on a 200Gb drive.
>
> >Amanda Backup Client Hosts Check
> >
> >Client check: 1 host checked in 0.025 seconds, 0 problems found
> >
> >(brought to you by Amanda 2.4.4p3)
> >[EMAIL PROTECTED] [28]>
> >
> The client check time is more realistic. Heres a clip from mine:
> Server check took 0.579 seconds
>
> Amanda Backup Client Hosts Check
>
> Client check: 2 hosts checked in 0.523 seconds, 0 problems found
>
> (brought to you by Amanda 2.4.5-20050711)
>
> >
> >-Original Message-
> >From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >Sent: Monday, July 18, 2005 4:45 PM
> >To: LaValley, Brian E
> >Cc: 'amanda-users@amanda.org'
> >Subject: Re: all estimate failed
> >
> >
> >Brian,
> >
> >On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
> >> Yes, amcheck passed.
> >>
> >> /tmp/amanda doesn't exist.
> >> There isn't anything that seems to be related to amanda in the
> >> messages
> >
> >log.
> >
> >> amcheck didn't pass until I setup the xinetd files. Can I assume
> >> they are setup correctly if amcheck is fine?
> >> How can I test the .amandahosts file?
> >
> >If amcheck said you where ok talking to the client then all of those
> >issues should be ok.
> >
> >I take that back, if amcheck said your client was ok you should have
> >had files in /tmp/amanda at that point. Both amcheck and amdump
> > should be causing files to be created on the client. You sure the
> > client passed the check ?
> >
> >
> >The rest of this email may not be relevant.
> >
> >Haven't a lot of experience in, er, xinetd ?, must be linux ?
> >Can comment but can tell you that in IRIX and Solaris if my
> >amanda user on the client wasn't in the correct group I needed
> >to fix the group and/or devices files /dev/dsk/* to allow RW for
> >the amanda user's group.
> >
> >Suspect you have some similar issue there.
> >
> >> -Original Message-
> >> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, July 18, 2005 4:31 PM
> >> To: LaValley, Brian E
> >> Cc: 'amanda-users@amanda.org'
> >> Subject: Re: all estimate failed
> >>
> >>
> >>
> >> Brian,
> >>
> >> You said manual dump, the amcheck succeeded ?
> >>
> >> Did you find any files in the client's /tmp/amanda/ directory ?
> >> Do you see any errors in /var/adm/{messages|SYSLOG} ?
> >> The client's xinetd files are properly configured to activate
> >> the service ? The client's .amandahosts file is properly setup ?
> >>
> >> Even if the client == server this must be done.
> >>
> >> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> >> > I have just decided to give AMANDA a try and am learning as I
> >> > go. I have gotten as far as trying a manual amdump, but it seems
> >> > the estimate is failing and nothing gets backed up. What could
> >> > this be?
> >
Re: ssh keys only
On Tuesday 19 July 2005 10:06, Vicki Stanfield wrote: >Most of our servers are accessible only via ssh with a root key. > Does amanda work in such a setup or does the amanda user have to > have regular login access? One of my coworkers changed one of our > servers to only accept logins via ssh and now amanda doesn't seem > to be able to get there and we get the following message: > >WARNING: /host/: selfcheck request timed out. Host down? > > >I suspect that amanda simply doesn't like not being able to log in. > Is this accurate? > >Vicki Yes, Vicki. I haven't had to deal with that here, but perhaps someone else has rigged an ssh script to wrap amanda up in? You might consider shooting the co-worker :) Better yet, offload the problem onto the one that caused it by telling him there will be no backups of that server until he cuts a hole in things so amanda can continue to do her job. Point out how valuable the info on the server is & all that rot... -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: ssh keys only
Alexander Jolk wrote: > A quick search in > this mailing list's archives will give you a complete solution with > iptables, or else just open TCP and UDP between your amanda server and > the amanda client in question. Or you look up the FAQ on www.amanda.org/docs . -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting & implementation http://www.oops.co.at --
Re: all estimate failed
On Tuesday 19 July 2005 10:02, Brian Cuttler wrote:
>Brian,
>Gene,
>
>couple of things, 1st, I'm thinking that if there is a jukebox
>involved (tape loaded from slot 3) then perhaps a 5 minute delay
>to load the tape isn't necessarilly a problem.
Maybe not a problem, but I recall my robots were generally only a 2 to
3 minute lag, back when I was using them. Seagate 4586n's,
admittedly pretty cheap though.
>2nd, I'm stupid
>and should have seen it yesterday - estimate failed, suggest
>raising the etimeout value is amanda.conf.
I saw that too, and figured somebody would catch it as the message was
fairly old by the time I saw it. And I agree. Maybe its time the
default etimeout was raised from 5 minutes to 10 or 15?
>If the partition(s) are large and etimeout is low or the client is
>slow for any reasons...
>
>On Tue, Jul 19, 2005 at 08:57:57AM -0400, Gene Heskett wrote:
>> On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
>> >I do have some things in different places. What files should be
>> > in /tmp/amanda?
>> >I already had a username of amanda at this location, so my AMANDA
>> > username is "backup"
>> >Here is my amcheck run:
>> >
>> >[EMAIL PROTECTED] [27]>amcheck DailySet1
>> >Amanda Tape Server Host Check
>> >-
>> >Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
>> > available, that's plenty
>> >amcheck-server: slot 3: date Xlabel DailySet1-A03 (new
>> > tape) NOTE: skipping tape-writable test
>> >Tape DailySet1-A03 label ok
>> >WARNING: info file
>> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info:
>> > does not exist
>> >WARNING: info file
>> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info:
>> > does not exist
>> >Server check took 312.817 seconds
>>
>> Somethings definitely wrong here, but from this I've no idea what.
>> It should not take a tape drive over 5 minutes to locate and load
>> the next correct tape. My server check is usually a very small
>> fraction of a second, but I'm also using virtual tapes on a 200Gb
>> drive.
>>
>> >Amanda Backup Client Hosts Check
>> >
>> >Client check: 1 host checked in 0.025 seconds, 0 problems found
>> >
>> >(brought to you by Amanda 2.4.4p3)
>> >[EMAIL PROTECTED] [28]>
>>
>> The client check time is more realistic. Heres a clip from mine:
>> Server check took 0.579 seconds
>>
>> Amanda Backup Client Hosts Check
>>
>> Client check: 2 hosts checked in 0.523 seconds, 0 problems found
>>
>> (brought to you by Amanda 2.4.5-20050711)
>>
>> >-Original Message-
>> >From: Brian Cuttler [mailto:[EMAIL PROTECTED]
>> >Sent: Monday, July 18, 2005 4:45 PM
>> >To: LaValley, Brian E
>> >Cc: 'amanda-users@amanda.org'
>> >Subject: Re: all estimate failed
>> >
>> >
>> >Brian,
>> >
>> >On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
>> >> Yes, amcheck passed.
>> >>
>> >> /tmp/amanda doesn't exist.
>> >> There isn't anything that seems to be related to amanda in the
>> >> messages
>> >
>> >log.
>> >
>> >> amcheck didn't pass until I setup the xinetd files. Can I
>> >> assume they are setup correctly if amcheck is fine?
>> >> How can I test the .amandahosts file?
>> >
>> >If amcheck said you where ok talking to the client then all of
>> > those issues should be ok.
>> >
>> >I take that back, if amcheck said your client was ok you should
>> > have had files in /tmp/amanda at that point. Both amcheck and
>> > amdump should be causing files to be created on the client. You
>> > sure the client passed the check ?
>> >
>> >
>> >The rest of this email may not be relevant.
>> >
>> >Haven't a lot of experience in, er, xinetd ?, must be linux ?
>> >Can comment but can tell you that in IRIX and Solaris if my
>> >amanda user on the client wasn't in the correct group I needed
>> >to fix the group and/or devices files /dev/dsk/* to allow RW for
>> >the amanda user's group.
>> >
>> >Suspect you have some similar issue there.
>> >
>> >> -Original Message-
>> >> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
>> >> Sent: Monday, July 18, 2005 4:31 PM
>> >> To: LaValley, Brian E
>> >> Cc: 'amanda-users@amanda.org'
>> >> Subject: Re: all estimate failed
>> >>
>> >>
>> >>
>> >> Brian,
>> >>
>> >> You said manual dump, the amcheck succeeded ?
>> >>
>> >> Did you find any files in the client's /tmp/amanda/ directory ?
>> >> Do you see any errors in /var/adm/{messages|SYSLOG} ?
>> >> The client's xinetd files are properly configured to activate
>> >> the service ? The client's .amandahosts file is properly setup
>> >> ?
>> >>
>> >> Even if the client == server this must be done.
>> >>
>> >> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E
wrote:
>> >> > I have just decided to give AMANDA a try and am learning as I
>> >> > go. I have gotten as far as trying a manual amdump, but it
>> >> > seems the estimate is failing and nothing gets backed up.
>> >> > What could this be?
>> >> >
>> >>
Re: ssh keys only
Vicki Stanfield wrote: Most of our servers are accessible only via ssh with a root key. Does amanda work in such a setup or does the amanda user have to have regular login access? One of my coworkers changed one of our servers to only accept logins via ssh and now amanda doesn't seem to be able to get there and we get the following message: WARNING: /host/: selfcheck request timed out. Host down? Actually, the amanda user doesn't ever need to log in; all communication between the server and its clients goes over amanda's own protocol. What amanda needs are a few open TCP and UDP ports between client and server, and a simple host-based authentication in the amanda user's homedirectory, in a file .amandahosts. Since I gather your backup worked before, I wonder whether your collegue mightn't have installed a firewall at the same time. A quick search in this mailing list's archives will give you a complete solution with iptables, or else just open TCP and UDP between your amanda server and the amanda client in question. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: ssh keys only
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, 19.07.2005 at 09:06 -0500, Vicki Stanfield wrote: > Most of our servers are accessible only via ssh with a root key. Does > amanda work in such a setup or does the amanda user have to have > regular login access? One of my coworkers changed one of our servers > to only accept logins via ssh and now amanda doesn't seem to be able > to get there and we get the following message: > > WARNING: /host/: selfcheck request timed out. Host down? > > I suspect that amanda simply doesn't like not being able to log in. Is > this accurate? AMANDA clients should have an entry in /etc/inetd.conf (or somewhere under /etc/xinetd.d depending on distro). This means that the client is listening on the amanda port (typically 10080) and will respond to connections appropriately. The trick is to ensure that /etc/amandahosts contains the list of usernames and hosts which are allowed to connect. This doesn't depend on ssh or login sessions at all. Note that /etc/amandahosts is the name of the file under Debian - in general the file is called .amandahosts and appears in the home directory of the amanda user (usually 'backup'). Debian achieves this using symlinks. Dave. - -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Cancer Epidemiology Unit Cancer Research UK / Oxford University PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370 N 51.7518, W 1.2016 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFC3Qo+bpQs/WlN43ARArUIAJ942oV5xS8dCIQeR6TCf+SApH6suACgrIfx VRW3Dty2CpunuxZhyUSAEJQ= =kgAG -END PGP SIGNATURE-
Re: all estimate failed
Brian,
Gene,
couple of things, 1st, I'm thinking that if there is a jukebox
involved (tape loaded from slot 3) then perhaps a 5 minute delay
to load the tape isn't necessarilly a problem. 2nd, I'm stupid
and should have seen it yesterday - estimate failed, suggest
raising the etimeout value is amanda.conf.
If the partition(s) are large and etimeout is low or the client is
slow for any reasons...
On Tue, Jul 19, 2005 at 08:57:57AM -0400, Gene Heskett wrote:
> On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
> >I do have some things in different places. What files should be in
> >/tmp/amanda?
> >I already had a username of amanda at this location, so my AMANDA
> > username is "backup"
> >Here is my amcheck run:
> >
> >[EMAIL PROTECTED] [27]>amcheck DailySet1
> >Amanda Tape Server Host Check
> >-
> >Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
> > available, that's plenty
> >amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
> >NOTE: skipping tape-writable test
> >Tape DailySet1-A03 label ok
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does
> > not exist
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does
> > not exist
> >Server check took 312.817 seconds
>
> Somethings definitely wrong here, but from this I've no idea what. It
> should not take a tape drive over 5 minutes to locate and load the
> next correct tape. My server check is usually a very small fraction
> of a second, but I'm also using virtual tapes on a 200Gb drive.
>
> >Amanda Backup Client Hosts Check
> >
> >Client check: 1 host checked in 0.025 seconds, 0 problems found
> >
> >(brought to you by Amanda 2.4.4p3)
> >[EMAIL PROTECTED] [28]>
> >
> The client check time is more realistic. Heres a clip from mine:
> Server check took 0.579 seconds
>
> Amanda Backup Client Hosts Check
>
> Client check: 2 hosts checked in 0.523 seconds, 0 problems found
>
> (brought to you by Amanda 2.4.5-20050711)
>
> >
> >-Original Message-
> >From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >Sent: Monday, July 18, 2005 4:45 PM
> >To: LaValley, Brian E
> >Cc: 'amanda-users@amanda.org'
> >Subject: Re: all estimate failed
> >
> >
> >Brian,
> >
> >On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
> >> Yes, amcheck passed.
> >>
> >> /tmp/amanda doesn't exist.
> >> There isn't anything that seems to be related to amanda in the
> >> messages
> >
> >log.
> >
> >> amcheck didn't pass until I setup the xinetd files. Can I assume
> >> they are setup correctly if amcheck is fine?
> >> How can I test the .amandahosts file?
> >
> >If amcheck said you where ok talking to the client then all of those
> >issues should be ok.
> >
> >I take that back, if amcheck said your client was ok you should have
> >had files in /tmp/amanda at that point. Both amcheck and amdump
> > should be causing files to be created on the client. You sure the
> > client passed the check ?
> >
> >
> >The rest of this email may not be relevant.
> >
> >Haven't a lot of experience in, er, xinetd ?, must be linux ?
> >Can comment but can tell you that in IRIX and Solaris if my
> >amanda user on the client wasn't in the correct group I needed
> >to fix the group and/or devices files /dev/dsk/* to allow RW for
> >the amanda user's group.
> >
> >Suspect you have some similar issue there.
> >
> >> -Original Message-
> >> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, July 18, 2005 4:31 PM
> >> To: LaValley, Brian E
> >> Cc: 'amanda-users@amanda.org'
> >> Subject: Re: all estimate failed
> >>
> >>
> >>
> >> Brian,
> >>
> >> You said manual dump, the amcheck succeeded ?
> >>
> >> Did you find any files in the client's /tmp/amanda/ directory ?
> >> Do you see any errors in /var/adm/{messages|SYSLOG} ?
> >> The client's xinetd files are properly configured to activate
> >> the service ? The client's .amandahosts file is properly setup ?
> >>
> >> Even if the client == server this must be done.
> >>
> >> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> >> > I have just decided to give AMANDA a try and am learning as I
> >> > go. I have gotten as far as trying a manual amdump, but it seems
> >> > the estimate is failing and nothing gets backed up. What could
> >> > this be?
> >> >
> >> >
> >> > The email report follows, and the amdump log is attached.
> >
> >
> >
> >
> >
> >
> >
> >
> >> > --
> >> >
> >> > These dumps were to tape DailySet1-A02.
> >> > The next tape Amanda expects to use is: a new tape.
> >> > The next new tape already labelled is: DailySet1-A01.
> >> >
> >> > FAILURE AND STRANGE DUMP SUMMARY:
> >> > blavalley- hdc5 lev 0 FAILED
ssh keys only
Most of our servers are accessible only via ssh with a root key. Does amanda work in such a setup or does the amanda user have to have regular login access? One of my coworkers changed one of our servers to only accept logins via ssh and now amanda doesn't seem to be able to get there and we get the following message: WARNING: /host/: selfcheck request timed out. Host down? I suspect that amanda simply doesn't like not being able to log in. Is this accurate? Vicki
Re: all estimate failed
On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
>I do have some things in different places. What files should be in
>/tmp/amanda?
>I already had a username of amanda at this location, so my AMANDA
> username is "backup"
>Here is my amcheck run:
>
>[EMAIL PROTECTED] [27]>amcheck DailySet1
>Amanda Tape Server Host Check
>-
>Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
> available, that's plenty
>amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
>NOTE: skipping tape-writable test
>Tape DailySet1-A03 label ok
>WARNING: info file
>/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does
> not exist
>WARNING: info file
>/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does
> not exist
>Server check took 312.817 seconds
Somethings definitely wrong here, but from this I've no idea what. It
should not take a tape drive over 5 minutes to locate and load the
next correct tape. My server check is usually a very small fraction
of a second, but I'm also using virtual tapes on a 200Gb drive.
>Amanda Backup Client Hosts Check
>
>Client check: 1 host checked in 0.025 seconds, 0 problems found
>
>(brought to you by Amanda 2.4.4p3)
>[EMAIL PROTECTED] [28]>
>
The client check time is more realistic. Heres a clip from mine:
Server check took 0.579 seconds
Amanda Backup Client Hosts Check
Client check: 2 hosts checked in 0.523 seconds, 0 problems found
(brought to you by Amanda 2.4.5-20050711)
>
>-Original Message-
>From: Brian Cuttler [mailto:[EMAIL PROTECTED]
>Sent: Monday, July 18, 2005 4:45 PM
>To: LaValley, Brian E
>Cc: 'amanda-users@amanda.org'
>Subject: Re: all estimate failed
>
>
>Brian,
>
>On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
>> Yes, amcheck passed.
>>
>> /tmp/amanda doesn't exist.
>> There isn't anything that seems to be related to amanda in the
>> messages
>
>log.
>
>> amcheck didn't pass until I setup the xinetd files. Can I assume
>> they are setup correctly if amcheck is fine?
>> How can I test the .amandahosts file?
>
>If amcheck said you where ok talking to the client then all of those
>issues should be ok.
>
>I take that back, if amcheck said your client was ok you should have
>had files in /tmp/amanda at that point. Both amcheck and amdump
> should be causing files to be created on the client. You sure the
> client passed the check ?
>
>
>The rest of this email may not be relevant.
>
>Haven't a lot of experience in, er, xinetd ?, must be linux ?
>Can comment but can tell you that in IRIX and Solaris if my
>amanda user on the client wasn't in the correct group I needed
>to fix the group and/or devices files /dev/dsk/* to allow RW for
>the amanda user's group.
>
>Suspect you have some similar issue there.
>
>> -Original Message-
>> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
>> Sent: Monday, July 18, 2005 4:31 PM
>> To: LaValley, Brian E
>> Cc: 'amanda-users@amanda.org'
>> Subject: Re: all estimate failed
>>
>>
>>
>> Brian,
>>
>> You said manual dump, the amcheck succeeded ?
>>
>> Did you find any files in the client's /tmp/amanda/ directory ?
>> Do you see any errors in /var/adm/{messages|SYSLOG} ?
>> The client's xinetd files are properly configured to activate
>> the service ? The client's .amandahosts file is properly setup ?
>>
>> Even if the client == server this must be done.
>>
>> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
>> > I have just decided to give AMANDA a try and am learning as I
>> > go. I have gotten as far as trying a manual amdump, but it seems
>> > the estimate is failing and nothing gets backed up. What could
>> > this be?
>> >
>> >
>> > The email report follows, and the amdump log is attached.
>
>
>
>
>
>
>
>
>> > --
>> >
>> > These dumps were to tape DailySet1-A02.
>> > The next tape Amanda expects to use is: a new tape.
>> > The next new tape already labelled is: DailySet1-A01.
>> >
>> > FAILURE AND STRANGE DUMP SUMMARY:
>> > blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
>> > blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate failed]
>> >
>> >
>> > STATISTICS:
>> > Total Full Daily
>> >
>> > Estimate Time (hrs:min)0:00
>> > Run Time (hrs:min) 0:03
>> > Dump Time (hrs:min)0:00 0:00 0:00
>> > Output Size (meg) 0.00.00.0
>> > Original Size (meg) 0.00.00.0
>> > Avg Compressed Size (%) -- -- --
>> > Filesystems Dumped0 0 0
>> > Avg Dump Rate (k/s) -- -- --
>> >
>> > Tape Time (hrs:min)0:00 0:00
Re: all estimate failed
LaValley, Brian E wrote: I do have some things in different places. What files should be in /tmp/amanda? I already had a username of amanda at this location, so my AMANDA username is "backup" the command "amadmin XX version" will show you where the debug files are in: ... AMANDA_DBGDIR="/tmp/amanda" ... -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
RE: all estimate failed
I do have some things in different places. What files should be in
/tmp/amanda?
I already had a username of amanda at this location, so my AMANDA username
is "backup"
Here is my amcheck run:
[EMAIL PROTECTED] [27]>amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space available,
that's plenty
amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
NOTE: skipping tape-writable test
Tape DailySet1-A03 label ok
WARNING: info file
/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does not
exist
WARNING: info file
/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does not
exist
Server check took 312.817 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.025 seconds, 0 problems found
(brought to you by Amanda 2.4.4p3)
[EMAIL PROTECTED] [28]>
-Original Message-
From: Brian Cuttler [mailto:[EMAIL PROTECTED]
Sent: Monday, July 18, 2005 4:45 PM
To: LaValley, Brian E
Cc: 'amanda-users@amanda.org'
Subject: Re: all estimate failed
Brian,
On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
> Yes, amcheck passed.
>
> /tmp/amanda doesn't exist.
> There isn't anything that seems to be related to amanda in the messages
log.
> amcheck didn't pass until I setup the xinetd files. Can I assume they are
> setup correctly if amcheck is fine?
> How can I test the .amandahosts file?
If amcheck said you where ok talking to the client then all of those
issues should be ok.
I take that back, if amcheck said your client was ok you should have
had files in /tmp/amanda at that point. Both amcheck and amdump should
be causing files to be created on the client. You sure the client passed
the check ?
The rest of this email may not be relevant.
Haven't a lot of experience in, er, xinetd ?, must be linux ?
Can comment but can tell you that in IRIX and Solaris if my
amanda user on the client wasn't in the correct group I needed
to fix the group and/or devices files /dev/dsk/* to allow RW for
the amanda user's group.
Suspect you have some similar issue there.
> -Original Message-
> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 18, 2005 4:31 PM
> To: LaValley, Brian E
> Cc: 'amanda-users@amanda.org'
> Subject: Re: all estimate failed
>
>
>
> Brian,
>
> You said manual dump, the amcheck succeeded ?
>
> Did you find any files in the client's /tmp/amanda/ directory ?
> Do you see any errors in /var/adm/{messages|SYSLOG} ?
> The client's xinetd files are properly configured to activate
> the service ? The client's .amandahosts file is properly setup ?
>
> Even if the client == server this must be done.
>
> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> > I have just decided to give AMANDA a try and am learning as I go. I have
> > gotten as far as trying a manual amdump, but it seems the estimate is
> > failing and nothing gets backed up. What could this be?
> >
> >
> > The email report follows, and the amdump log is attached.
> >
>
> >
>
> > --
> >
> > These dumps were to tape DailySet1-A02.
> > The next tape Amanda expects to use is: a new tape.
> > The next new tape already labelled is: DailySet1-A01.
> >
> > FAILURE AND STRANGE DUMP SUMMARY:
> > blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
> > blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate failed]
> >
> >
> > STATISTICS:
> > Total Full Daily
> >
> > Estimate Time (hrs:min)0:00
> > Run Time (hrs:min) 0:03
> > Dump Time (hrs:min)0:00 0:00 0:00
> > Output Size (meg) 0.00.00.0
> > Original Size (meg) 0.00.00.0
> > Avg Compressed Size (%) -- -- --
> > Filesystems Dumped0 0 0
> > Avg Dump Rate (k/s) -- -- --
> >
> > Tape Time (hrs:min)0:00 0:00 0:00
> > Tape Size (meg) 0.00.00.0
> > Tape Used (%) 0.00.00.0
> > Filesystems Taped 0 0 0
> > Avg Tp Write Rate (k/s) -- -- --
> >
> > USAGE BY TAPE:
> > Label Time Size %Nb
> > DailySet1-A02 0:00 0.00.0 0
> >
> >
> > NOTES:
> > planner: Adding new disk blavalley-l:hdc1.
> > planner: Adding new disk blavalley-l:hdc5.
> > driver: WARNING: got empty schedule from planner
> > taper: tape DailySet1-A02 kb 0 fm 0 [OK]
> >
> >
> > DUMP SUMMARY:
> > DUMPER STATSTAPER STATS
> > HOSTNAME DISK
Re: file changed as we read it: strange
Stefan G. Weichinger wrote: Guy Dallaire wrote: This morning, amanda (2.4.5) told me that some files changed during the backup. I don't think it actually changed. Why does it mean by "changed" ? The file in question was not being written to during amanda's backup of the server, that I am sure of. I'm suspecting a file "last access time" change. Otherwise, a bug in tar/amanda ? > If files get changed between estimates and dumping, this message is triggered as well ... I don't think so. There is no state saved between estimate and dump. Gnutar compares ctime of the file and just before closing and if that has changed, you get the message "file changed as we read it". Note a ctime change can also result from inode change like chown, or a forced mtime or atime change (e.g. from an --atime-preserve option of another tar; tar resets the atime just after this test, otherwise you'ld get all false alerts). If you read a block of a file, seek back again to the beginning of the block, and write the same block again, the ctime changes too; nevertheless, the contents of the file are still the same. I'm suspecting something else on the system. Don't blame it on bugs in tar when there are people around to blame. You said it was an oracle datafile. Are you 100% sure all the oracle processes stopped, and no process had the file open? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
