amanda reports are empty all of a sudden
Hello Amanda was working perfectly for over 3 months, but now, all of a sudden the amanda reports I get by mail are empty... What could be the cause of this? Regards Tom Van de Wiele -- Tom Van de Wiele Linux System Administrator Eduline nv/sa Kolonel Bourgstraat 105a 1040 Brussel t: +32 (0)2 730 83 72 e: [EMAIL PROTECTED] w: www.eduline.be -- www.kidcity.be
unsubscribe
Re: Anyone with experience using a Sun Storedge L9 DLT array with Amanda?
Quoting Craig Dewick ([EMAIL PROTECTED]): > > Ok, thanks for this tip. I'm going to try and secure the L9 array since > it's virtually new and a perfect small backup solution. > > How are you using it with Amanda btw? Do you use 'chg-scsi', or are you > controlling it with the 'mtx' utility using 'chg-zd-mtx' or similar? Hi... I have an L9 running on an E220R, using mtx-1.2.11 to control the robotics. (I assume later versions would work too.. I just haven't had reason to upgrade.. :) ) As for the changer script... the two mtx-based changer scripts that come with amanda 2.4.2p2 had some "issues", but that went away when I grabbed a different (better?) script from http://www.killfile.org/~tskirvin/software/mtx-changer/mtx-changer-1.1 Hope this helps... Ted
disk offline - runtar as root
It appears that the client isn't running runtar as root. Does anyone know how to force the client to run runtar as root? Thanks, Jonathan Murray from report: FAILURE AND STRANGE DUMP SUMMARY: borzoi /dev/dsk/dks0d2s7 lev 0 FAILED [disk /dev/dsk/dks0d2s7 offline on borzoi?] borzoi /dev/dsk/dks0d1s0 lev 0 FAILED [disk /dev/dsk/dks0d1s0 offline on borzoi?] on client: calculating for amname '/dev/dsk/dks0d2s7', dirname '/borzoi' sendsize: getting size via gnutar for /dev/dsk/dks0d2s7 level 0 sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" discarded sendsize: spawning /usr/freeware/libexec/runtar in pipeline sendsize: argument list: /usr/freeware/bin/tar --create --file /dev/null --directory /borzoi --one-file-system --listed-incremental /var/amanda/gnutar-lists/borzoi_dev_dsk_dks0d2s7_0.new --sparse --ignore-failed-read --totals . runtar: error [must be invoked by root]
RE: disk offline - runtar as root
cd /usr/local/libexec chown root:amanda runtar chmod 4750 runtar assuming runtar is in usr/local/libexec and that the amanda user is in the amanda group... But... I suspect that you haven't got runtar in the right group (or the amanda user in the right group) as your message suggests runtar is generating the error. When try to invoke runtar on my system (as myself) I get runtar: error [must be invoked by amanda] I don't know whether this check is hardwired in at compile time - in which case you may need to recompile? -Original Message- From: Jonathan Murray [mailto:[EMAIL PROTECTED]] Sent: 06 June 2002 15:25 To: Jonathan Murray Cc: [EMAIL PROTECTED] Subject: disk offline - runtar as root It appears that the client isn't running runtar as root. Does anyone know how to force the client to run runtar as root? Thanks, Jonathan Murray from report: FAILURE AND STRANGE DUMP SUMMARY: borzoi /dev/dsk/dks0d2s7 lev 0 FAILED [disk /dev/dsk/dks0d2s7 offline on borzoi?] borzoi /dev/dsk/dks0d1s0 lev 0 FAILED [disk /dev/dsk/dks0d1s0 offline on borzoi?] on client: calculating for amname '/dev/dsk/dks0d2s7', dirname '/borzoi' sendsize: getting size via gnutar for /dev/dsk/dks0d2s7 level 0 sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" discarded sendsize: spawning /usr/freeware/libexec/runtar in pipeline sendsize: argument list: /usr/freeware/bin/tar --create --file /dev/null --directory /borzoi --one-file-system --listed-incremental /var/amanda/gnutar-lists/borzoi_dev_dsk_dks0d2s7_0.new --sparse --ignore-failed-read --totals . runtar: error [must be invoked by root]
Re: divided backup (breaking up is hard to do?)
No answers back, but I think I've stumbled on the solution and post it
here for the next poor soul who makes the same mistake. Noticed from
another recent post that clients can generate a sendsize.*.debug. Looked
for this on my client that failed to estimate, and found that the
automatically generated 'arguments' line specified the --exclude-from
option and that the estimate failed with message that this option's
argument was a directory. Sure enough, --exclude-from needs the name of a
file that specifies other files for exclusion; what I gave it (via
"exclude list" in my disklist entry) was the top directory of the subtree
to be omitted. I'm pretty sure that the fix is to use "exclude" instead of
"exclude list" (which I had hastily cribbed from one of the examples that
shipped in disklist). I'll make this change for tonight, and will post
again only if it fails and I need more ideas.
The "side question" I posed wrt successful recovery of gnutar'd stuff only
on the original host is still open. I suspect there are clues in the
arrangement of the gnutar-lists, but the answer is not clear to me yet.
Robert L. Becker, Jr.
Col, USAF, MC
Department of Cellular Pathology
Armed Forces Institute of Pathology
Washington, DC 20306-6000
301-319-0300
On Tue, 4 Jun 2002, Robert L. Becker Jr. wrote:
>
> I have a partition on one client that exceeds a tape (as I realized after
> first L0 attempt failed) and is too large for my holding disk. I have
> specified smaller parts (with appropriate 'exclude list') for gnutar to
> handle. Amcheck reports no problem for the client. The L0 attempt for all
> of the partition subparts ran last night. It appeared that one of the
> subparts taped ok. The other two (those with 'exclude' set) were flagged
> as "No Estimate" in the amstatus output during amdump's run, and failed.
> Here are the disklist entries:
>
> # optimas:/reed split up into manageable chunks (wrt holding disk, tape size)
> optimas3.cpt.afip.org /reed/becker/duplicates_pol_thickness/dense comp-user-tar
> optimas3.cpt.afip.org /reed/becker/duplicates_pol_thickness {
> comp-user-tar
> exclude list "dense"
> }
> optimas3.cpt.afip.org /reed {
> comp-user-tar
> exclude list "becker/duplicates_pol_thickness"
> }
>
[...snip...]
> [As a side question, the test recovery worked for putting the data back
> onto optimas3, but it failed when I tried putting the data on another
> host, i.e. the Amanda server, raleigh. Here is the amrecover session
> targeting raleigh:
>
> raleigh 116# /usr/local/amanda/sbin/amrecover Daily
> AMRECOVER Version 2.4.2p2. Contacting server on raleigh ...
> 220 raleigh AMANDA index server (2.4.2p2) ready.
> 200 Access OK
> Setting restore date to today (2002-06-04)
> 200 Working date set to 2002-06-04.
> 200 Config set to Daily.
> 501 No index records for host: raleigh. Invalid?
> Trying raleigh.cpt.afip.org ...
> 200 Dump host set to raleigh.cpt.afip.org.
> $CWD '/tmp/recover_reed' is on disk '/dev/root' mounted at '/'.
> 200 Disk set to /dev/root.
> Invalid directory - /tmp/recover_reed
> amrecover> sethost optimas3
> 501 No index records for host: optimas3. Invalid?
> Trying optimas3.cpt.afip.org ...
> 200 Dump host set to optimas3.cpt.afip.org.
> amrecover> setdisk /reed/becker/duplicates_pol_thickness/dense
> 200 Disk set to /reed/becker/duplicates_pol_thickness/dense.
> amrecover> add m109[5-6]*
> Added dir /m1095p1230 at date 2002-06-04
> Added dir /m1096p1230 at date 2002-06-04
> amrecover> list
> TAPE Daily002 LEVEL 0 DATE 2002-06-04
> /m1096p1230
> /m1095p1230
> amrecover> extract
>
> Extracting files using tape drive /dev/rmt/tps1d4nrsv on host raleigh.
> The following tapes are needed: Daily002
>
> Restoring files into directory /tmp/recover_reed
> Continue? [Y/n]: y
>
> Load tape Daily002 now
> Continue? [Y/n]: y
> :f
> tar: ./m1096p1230: Not found in archive
> tar: ./m1095p1230: Not found in archive
> tar: Error exit delayed from previous errors
> extract_list - child returned non-zero status: 2
> Continue? [Y/n]: amrecover> n
> Invalid command - parse error
> amrecover>
> amrecover> exit
>
> I suspect the problem is due to a mismatch between relative vs absolute
> paths used in the recovery. Whatever the problem, I don't know how to
> untangle it. Can someone point the way? Thanks.
>
amrecover: can't recover some files
Hi, i use amanda 2.4.2p2 (2.4.2p2-4 on Debian woody). When i try to recover a file: amrecover> cd toto/ amrecover> add tata.html amrecover> extract i got: EOF, check amidxtaped.debug file on localhost. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 and i could'nt find the file "amidxtaped.debug". It append at least with one file (not all files :) but if i do: amrecover> add toto amrecover> extract it successfully restore directory "toto" with tata.html inside -- Fabien Seisen [EMAIL PROTECTED] dakol@opn GnuPG ID 1024D/112189D8
Dump configuration on amanda
Hi, I have errors using dump and apparently, it' because I'm doing a dump on an active filesystem. I would like to know if there is a way to configure amanda to execute dump -I ?? Thanks in advance Meryem
ADV: Direct Email Blaster, email addresses extractor,maillist verify, maillist manager ...........
¡¡ Direct Email Blaster The program will send mail at the rate of over 1, 000 e-mails per minute. Legal and Fast sending bulk emails Built in SMTP server Have Return Path Can Check Mail Address Make Error Send Address List( Remove or Send Again) Support multi-threads. Support multi-smtp servers. Manages your opt-in E-Mail Lists Offers an easy-to-use interface! Easy to configure and use Download Now Maillist Verify Maillist Verify is intended for e-mail addresses and mail lists verifying. The main task is to determine which of addresses in the mail list are dead. The program is oriented, basically, on programmers which have their own mail lists to inform their users about new versions of their programs. The program works on the same algorithm as ISP mail systems do. Mail servers addresses for specified address are extracted from DNS. The program tries to connect with found SMTP-servers and simulates the sending of message. It does not come to the message sending ‿/NOBR> EMV disconnect as soon as mail server informs does this address exist or not. EMV can find about 90% of dead addresses ‿/NOBR> some mail systems receive all messages and only then see their addresses and if the address is dead send the message back with remark about it. Download Now Express Email Blaster Express Email Blaster is a very fast, powerful yet simple to use email sender. Utilizing multiple threads/connections and multiple SMTP servers your emails will be sent out fast and easily. There are User Information, Attach Files, Address and Mail Logs four tabbed area for the E-mails details for sending. About 25 SMTP servers come with the demo version, and users may Add and Delete SMTP servers. About 60,000 E-mails will be sent out per hour." Download Now Express Email Address Extractor This program is the most efficient, easy to use email address collector available on the internet! Beijing Express Email Address Extractor (ExpressEAE) is designed to extract e-mail addresses from web-pages on the Internet (using HTTP protocols) .ExpressEAE supports operation through many proxy-server and works very fast, as it is able of loading several pages simultaneously, and requires very few resources. With it, you will be able to use targeted searches to crawl the world wide web, extracting thousands of clean, fresh email addresses. Ably Email address Extractor is unlike other address collecting programs, which limit you to one or two search engines and are unable to do auto searches HUGE address. Most of them collect a high percentage of incomplete, unusable addresses which will cause you serious problems when using them in a mailing. Easier to learn and use than any other email address collector program available. Accesses eight search engines Add your own URLs to the list to be searched Supports operation through a lot of proxy-server and works very fast (HTTP Proxy) Able of loading several pages simultaneously Requires very few resources Timeout feature allows user to limit the amount of time crawling in dead sites and traps. Easy to make Huge address list Pause/continue extraction at any time. Auto connection to the Internet Download Now Express Email Address Downloader ExpressEAD is a 32 bit Windows Program for e-mail marketing. It is intended for easy and convenient search large e-mail address lists from mail servers. The program can be operated on Windows 95/98/ME/2000 and NT. ExpressEAD support multi-threads (up to 1024 connections). ExpressEAD has the ability to reconnect to the mail server if the server has disconnected and continue the searching at the point where it has been interrupted. ExpressEAD has an ergonomic interface that is easy to set up and simple to use. Features: support multi-threads. auto get smtp server address,support multi-smtp servers. auto save E-Mail Lists offers an easy-to-use interface! Download Now Express Maillist Manager This program was designed to be a complement to the Direct Email Blaster and Email Blaster suite of bulk email software programs. Its purpose is to organize your email lists in order to be more effective with your email marketing campaign. Some of its features include: ‿Combine several lists into one file. ‿Split up larger lists to make them more manageable. ‿Remove addresses from file. ‿Manual editing, adding, and deleting of addresses. ‿Ability to auto clean lists, that is, remove any duplicate or unwanted addresses. ‿Maintain all your address lists within the program so you no longer need to keep all your lists saved as separate text files. Download Now ¡¡ if you want to remove your email, please send email to [EMAIL PROTECTED] ¡¡
amrecover reserved port and stream_client.diff patch file
I have compiled amanda 2.4.2p2 with the --with-port-range option and am getting the "amrecover: did not get a reserved port" message. Amanda has been backing up fine as far as I can tell, but I wanted to test the restore capabilities before I actually needed them and found that I have this problem. So I searched the yahoo groups archive for amanda-users and found a patch located at www.amanda.org/patches.html (real location of patch file is http://www.amanda.org/patches/2.4.2p2/stream_client.diff) and tried to apply it, but it appears the patch was generated against a different version of common-src/stream.c than what I have downloaded with the 2.4.2p2 tar file release. Here is what I see when applying the patch: # patch -p0 < stream_client.diff patching file common-src/stream.c Hunk #1 succeeded at 145 (offset 2 lines). Hunk #2 succeeded at 159 with fuzz 1 (offset 3 lines). Hunk #3 succeeded at 180 (offset 3 lines). Hunk #4 succeeded at 198 (offset 3 lines). Hunk #5 succeeded at 213 (offset 3 lines). Hunk #6 succeeded at 263 (offset 3 lines). Hunk #7 succeeded at 275 (offset 3 lines). Hunk #8 FAILED at 285. Hunk #9 succeeded at 307 (offset 5 lines). 1 out of 9 hunks FAILED -- saving rejects to file common-src/stream.c.rej patching file common-src/stream.h patching file recover-src/amrecover.c Hunk #1 succeeded at 513 (offset -11 lines). patching file recover-src/extract_list.c I checked the patch file and see that stream.c was diff'd with version 1.10.2.8: diff -u -r1.10.2.8 --- common-src/stream.c 2001/06/18 22:23:19 1.10.2.8 +++ common-src/stream.c 2001/07.30 19:13:19 My amanda 2.4.2p2 tar ball has the 1.10.2.7 version of common-src/stream.c: $Id: stream.c,v 1.10.2.7 2001/02/28 00:53:15 jrjackson Exp $ Is this why the patch is failing? If so, how do I patch my 1.10.2.7 to be 1.10.2.8 before I apply the stream_client.diff patch? Thanks for any help, Jason Upton [EMAIL PROTECTED]
Re: disk offline - runtar as root
borzoi 63# pwd /usr/freeware/libexec -rwsr-x---1 root sys21876 May 31 17:36 runtar /etc/group: borzoi 6% cat /etc/group sys::0:root,bin,sys,adm,amanda root::0:root daemon::1:root,daemon bin::2:root,bin,daemon adm::3:root,adm,daemon mail::4:root uucp::5:uucp rje::8: lp:*:9: nuucp::10:nuucp user::20:amanda CMWlogin::994: other::995: demos:*:997: guest:*:998: nobody:*:60001: runtar attempt as user amanda: borzoi 8% whoami amanda borzoi 7% ./runtar runtar: error [must be invoked by root] How do did you get runtar: error [must be invoked by amanda] ? thank you, -Jonathan Murray Spicer, Kevin wrote: > cd /usr/local/libexec > chown root:amanda runtar > chmod 4750 runtar > > assuming runtar is in usr/local/libexec and that the amanda user is in the amanda >group... > > But... I suspect that you haven't got runtar in the right group (or the amanda user >in the right group) as your message suggests runtar is generating the error. > When try to invoke runtar on my system (as myself) I get > runtar: error [must be invoked by amanda] > I don't know whether this check is hardwired in at compile time - in which case you >may need to recompile? > > -Original Message- > From: Jonathan Murray [mailto:[EMAIL PROTECTED]] > Sent: 06 June 2002 15:25 > To: Jonathan Murray > Cc: [EMAIL PROTECTED] > Subject: disk offline - runtar as root > > > It appears that the client isn't running runtar as root. Does anyone > know how to force the client to run runtar as root? > > Thanks, > > Jonathan Murray > > from report: > > FAILURE AND STRANGE DUMP SUMMARY: >borzoi /dev/dsk/dks0d2s7 lev 0 FAILED [disk /dev/dsk/dks0d2s7 > offline on borzoi?] >borzoi /dev/dsk/dks0d1s0 lev 0 FAILED [disk /dev/dsk/dks0d1s0 > offline on borzoi?] > > > > on client: > > calculating for amname '/dev/dsk/dks0d2s7', dirname '/borzoi' > sendsize: getting size via gnutar for /dev/dsk/dks0d2s7 level 0 > sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" > discarded > sendsize: spawning /usr/freeware/libexec/runtar in pipeline > sendsize: argument list: /usr/freeware/bin/tar --create --file /dev/null > --directory /borzoi --one-file-system --listed-incremental > /var/amanda/gnutar-lists/borzoi_dev_dsk_dks0d2s7_0.new --sparse > --ignore-failed-read --totals . > runtar: error [must be invoked by root] > > >
Re: amrecover: can't recover some files
I've seen similar error msg (short block, can't read header) on first attempt to recover from tapes just-written and left in my Exabyte 8900 tape drive. Problem disappeared after a) I explicitly rewound the tape and/or (I'm not sure which) b) the tape automatically rewound after the first amrecover error. I assume (since the taping device must be specified non-rewinding) that amrecover hiccuped because it didn't automatically rewind before trying to read, and so started off at EOT. I hope that's the correct explanation... Robert L. Becker, Jr. Col, USAF, MC Department of Cellular Pathology Armed Forces Institute of Pathology Washington, DC 20306-6000 301-319-0300 On Thu, 6 Jun 2002, Fabien SEISEN wrote: > > Hi, > > i use amanda 2.4.2p2 (2.4.2p2-4 on Debian woody). > When i try to recover a file: > > amrecover> cd toto/ > amrecover> add tata.html > amrecover> extract > > i got: > EOF, check amidxtaped.debug file on localhost. > amrecover: short block 0 bytes > UNKNOWN file > amrecover: Can't read file header > extract_list - child returned non-zero status: 1 > > and i could'nt find the file "amidxtaped.debug". > > It append at least with one file (not all files :) > > but if i do: > amrecover> add toto > amrecover> extract > > it successfully restore directory "toto" with tata.html inside > > -- > Fabien Seisen [EMAIL PROTECTED] dakol@opn > GnuPG ID 1024D/112189D8 >
Newbie - amanda.config problems
Newbie question - installing Amanda for the first time. Checked the FAQ's and didn't find an answer to this problem - could be a case of not seeing the forest for the trees. I installed amanda-2.4.2p2 and apparently compiled successfully. After completing the configuration file, amlabel-2.4.2p2 (using suffix) ran successfully and labeled all the tapes. But when I attempt to run amcheck-2.4.2p2, it has a problem with the keyword 'program "GNUTAR"' entry. This is the section of the config file containing the GNUTAR entry: 358 # program - specify the dump system to use. Valid values are "DUMP" and 359 # "GNUTAR". Default: [program "DUMP"]. 360 program "GNUTAR" 361 # record - record the dump in /etc/dumpdates. Default: [record yes] 362 # skip-full - skip the disk when a level 0 is due, to allow full backups 363 # outside Amanda, eg when the machine is in single-user mode. and the error message results from amcheck: possum# amcheck-2.4.2p2 -s Set1 "/usr/local/etc/amanda/Set1/amanda.conf", line 360: configuration keyword expected "/usr/local/etc/amanda/Set1/amanda.conf", line 360: end of line expected "/usr/local/etc/amanda/Set1/amanda.conf", line 361: configuration keyword expected amcheck: could not find config file "/usr/local/etc/amanda/Set1/amanda.conf /tmp/amanda debug file shows this information: amcheck: debug 1 pid 78916 ruid 0 euid 1000 start time Thu Jun 6 10:55:19 2002 amcheck: dgram_bind: socket bound to 0.0.0.0.3095 could not find config file "/usr/local/etc/amanda/Set1/amanda.conf" amcheck: pid 78916 finish time Thu Jun 6 10:55:19 2002 Although the reported error is "can't find", it appears that the program's reading the config file, then erroring out on the keyword entry. I'm not sure what error I've made with the "keyword" but it's obvious there must be one there. I've removed and replaced the entry several times, tried it with and without the quotes, and got the same results. I'd really appreciate somebody steering me in the right direction so I can get Amanda up and running. Jerry Stretch Industry Inet [EMAIL PROTECTED]
Re: Newbie - amanda.config problems
Did you define GNUTAR using --with-gnutar= on the ./configure line or in a suitably placed config.site file? From my /usr/local/amanda/etc/config.site: # GNUTAR--with-gnutar=PROG # Default: look for program named gtar, gnutar or tar # that prints GNU tar when run with --version. GNUTAR=/usr/freeware/bin/tar Robert L. Becker, Jr. Col, USAF, MC Department of Cellular Pathology Armed Forces Institute of Pathology Washington, DC 20306-6000 301-319-0300 On Thu, 6 Jun 2002, Jerry - Industry wrote: > Newbie question - installing Amanda for the first time. > > Checked the FAQ's and didn't find an answer to this problem - could be a > case of not seeing the forest for the trees. > > I installed amanda-2.4.2p2 and apparently compiled successfully. After > completing the configuration file, amlabel-2.4.2p2 (using suffix) ran > successfully and labeled all the tapes. But when I attempt to run > amcheck-2.4.2p2, it has a problem with the keyword 'program "GNUTAR"' entry. > > This is the section of the config file containing the GNUTAR entry: > > 358 # program - specify the dump system to use. Valid values are > "DUMP" and > 359 # "GNUTAR". Default: [program "DUMP"]. > 360 program "GNUTAR" > 361 # record - record the dump in /etc/dumpdates. Default: [record > yes] > 362 # skip-full - skip the disk when a level 0 is due, to allow full > backups > 363 # outside Amanda, eg when the machine is in single-user > mode. > > and the error message results from amcheck: > > possum# amcheck-2.4.2p2 -s Set1 > "/usr/local/etc/amanda/Set1/amanda.conf", line 360: configuration keyword > expected > "/usr/local/etc/amanda/Set1/amanda.conf", line 360: end of line expected > "/usr/local/etc/amanda/Set1/amanda.conf", line 361: configuration keyword > expected > amcheck: could not find config file "/usr/local/etc/amanda/Set1/amanda.conf > > /tmp/amanda debug file shows this information: > > amcheck: debug 1 pid 78916 ruid 0 euid 1000 start time Thu Jun 6 10:55:19 > 2002 > amcheck: dgram_bind: socket bound to 0.0.0.0.3095 > could not find config file "/usr/local/etc/amanda/Set1/amanda.conf" > amcheck: pid 78916 finish time Thu Jun 6 10:55:19 2002 > > Although the reported error is "can't find", it appears that the program's > reading the config file, then erroring out on the keyword entry. I'm not > sure what error I've made with the "keyword" but it's obvious there must be > one there. I've removed and replaced the entry several times, tried it with > and without the quotes, and got the same results. > > I'd really appreciate somebody steering me in the right direction so I can > get Amanda up and running. > > Jerry Stretch > Industry Inet > [EMAIL PROTECTED] > >
unsubscribe
___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
amrestore problems
I recently moved from solaris to linux so I am testing amrestore again. I keep getting the following error: EOF, check amidxtaped.debug file on chena. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 However, amidxtaped shows: amidxtaped: debug 1 pid 32054 ruid 250 euid 250 start time Thu Jun 6 11:24:51 2002 amidxtaped: version 2.4.2p2 > SECURITY USER root bsd security: remote host thames user root local user amanda amandahosts security check passed > 6 amrestore_nargs=6 > -h > -p > /dev/ait2 > thames > ^/export/private$ > 20020606 Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = "amrestore" argv[1] = "-h" argv[2] = "-p" argv[3] = "/dev/ait2" argv[4] = "thames" argv[5] = "^/export/private$" argv[6] = "20020606" amrestore: could not open tape /dev/ait2: Permission denied amidxtaped: amrestore terminated normally with status: 2 Rewinding tape: no tape online amidxtaped: pid 32054 finish time Thu Jun 6 11:24:51 2002 But amanda has read and write permisson to the drive: $ ls -l /dev/nst0 crw-rw1 root disk 9, 128 Aug 30 2001 /dev/nst0 I can read for the tape with dd: $ mt -f /dev/ait2 fsf 1; dd if=/dev/ait2 bs=32k count=1 AMANDA: FILE 20020606 zambezi /boot lev 1 comp N program /bin/gtar To restore, position tape at start of file and run: dd if= bs=32k skip=1 | /bin/gtar -f... - etc, all the way thru the tape. This is not good. No one cares about backups, only restores. So any ideas why amrestore does not work? I am using amanda version 2.4.2p2 -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
unsubscribe
* Linda Potesta * * [EMAIL PROTECTED] # *Phone (734)936-6002 * *Cell (734)323-7745 *
RE: amrestore problems
Maybe /dev/ait2 != /dev/nst0 ? > amrestore: could not open tape /dev/ait2: Permission denied > > $ ls -l /dev/nst0 > > crw-rw1 root disk 9, 128 Aug 30 2001 /dev/nst0 > > I can read for the tape with dd: > > $ mt -f /dev/ait2 fsf 1; dd if=/dev/ait2 bs=32k count=1 > > AMANDA: FILE 20020606 zambezi /boot lev 1 comp N program /bin/gtar > To restore, position tape at start of file and run: > dd if= bs=32k skip=1 | /bin/gtar -f... - > > etc, all the way thru the tape. >
Re: amrecover reserved port and stream_client.diff patch file
FYI... I found the stream.c version I was looking for on sourceforge: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/amanda/amanda/common-src/stream.c I just replaced the 1.10.2.7 version with the 1.10.2.8 version before applying the patch and it seems to be working (at least amrecover runs now). Now I just need to try some restores... Please let me know if this was the incorrect thing to do. Hope it helps someone else searching the archives. Jason Upton [EMAIL PROTECTED] Jason Upton wrote: > I have compiled amanda 2.4.2p2 with the --with-port-range option and > am getting the "amrecover: did not get a reserved port" message. > Amanda has been backing up fine as far as I can tell, but I wanted to > test the restore capabilities before I actually needed them and found > that I have this problem. > > So I searched the yahoo groups archive for amanda-users and found a > patch located at www.amanda.org/patches.html (real location of patch > file is http://www.amanda.org/patches/2.4.2p2/stream_client.diff) and > tried to apply it, but it appears the patch was generated against a > different version of common-src/stream.c than what I have downloaded > with the 2.4.2p2 tar file release. > > Here is what I see when applying the patch: > # patch -p0 < stream_client.diff > patching file common-src/stream.c > Hunk #1 succeeded at 145 (offset 2 lines). > Hunk #2 succeeded at 159 with fuzz 1 (offset 3 lines). > Hunk #3 succeeded at 180 (offset 3 lines). > Hunk #4 succeeded at 198 (offset 3 lines). > Hunk #5 succeeded at 213 (offset 3 lines). > Hunk #6 succeeded at 263 (offset 3 lines). > Hunk #7 succeeded at 275 (offset 3 lines). > Hunk #8 FAILED at 285. > Hunk #9 succeeded at 307 (offset 5 lines). > 1 out of 9 hunks FAILED -- saving rejects to file common-src/stream.c.rej > patching file common-src/stream.h > patching file recover-src/amrecover.c > Hunk #1 succeeded at 513 (offset -11 lines). > patching file recover-src/extract_list.c > > I checked the patch file and see that stream.c was diff'd with version > 1.10.2.8: > diff -u -r1.10.2.8 > --- common-src/stream.c 2001/06/18 22:23:19 1.10.2.8 > +++ common-src/stream.c 2001/07.30 19:13:19 > > My amanda 2.4.2p2 tar ball has the 1.10.2.7 version of > common-src/stream.c: > $Id: stream.c,v 1.10.2.7 2001/02/28 00:53:15 jrjackson Exp $ > > Is this why the patch is failing? If so, how do I patch my 1.10.2.7 > to be 1.10.2.8 before I apply the stream_client.diff patch? > > Thanks for any help, > Jason Upton > [EMAIL PROTECTED] > > >
Amcheck error with smbclient
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having trouble trying to get a windows client backed up. First i have a setup like this. The amanda server is Marvin. The PC to be backup is called Win2k. The machine running smbclient is Aries. Disklist on Marvin:- aries //Win2k's IP/C$comp-user-tar /etc/amandapass on Aries:- //Win2k's IP/C$ username%password Output from running amcheck on Marvin:- Amanda Backup Client Hosts Check - ERROR: aries: [PC SHARE //Win2k's IP/C$ access error: host down or invalid password?] Client check: 1 host checked in 0.837 seconds, 1 problem found Output from amadad.debug on Aries:- amandad: debug 1 pid 32285 ruid 34 euid 34 start time Fri Jun 7 03:51:14 2002 amandad: version 2.4.1p1 amandad: build: VERSION="Amanda-2.4.1p1" amandad:BUILT_DATE="Mon Jun 12 23:14:52 MDT 2000" amandad:BUILT_MACH="Linux rover 2.2.15pre15 #1 Thu Mar 23 02:22:27 MST 2000 i686 unknown" amandad:CC="gcc" amandad: paths: bindir="/usr/sbin" sbindir="/usr/sbin" amandad:libexecdir="/usr/lib/amanda" mandir="/usr/share/man" amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/bin/gzip" amandad:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/var/lib/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="localhost" amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY amandad:USE_AMANDAHOSTS CLIENT_LOGIN="backup" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" got packet: - Amanda 2.4 REQ HANDLE 000-20AD0708 SEQ 1023393074 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR //Win2k's IP/C$ 0 OPTIONS |;bsd-auth;compress-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; - sending ack: - Amanda 2.4 ACK HANDLE 000-20AD0708 SEQ 1023393074 - bsd security: remote host marvin amanda local user backup amandahosts security check passed amandad: running service "/usr/lib/amanda/selfcheck" added interface ip=192.168.1.4 bcast=192.168.1.255 nmask=255.255.255.0 session request to "Win2k's IP" failed (Called name not present) session request to 203 failed (Called name not present) session setup failed: ERRDOS - ERRnoaccess (Access denied.) amandad: sending REP packet: - Amanda 2.4 REP HANDLE 000-20AD0708 SEQ 1023393074 OPTIONS ; running /usr/bin/smbclient Win2k's IP\\C$ -E -U backup -c quit ERROR [PC SHARE //Win2k's IP/C$ access error: host down or invalid password?] OK /usr/lib/amanda/runtar executable OK /bin/tar executable OK /var/lib/amanda/amandates read/writable OK /var/lib/amanda/gnutar-lists/. read/writable OK /usr/bin/smbclient executable OK [/etc/amandapass is readable, but not by all] OK /bin/gzip executable OK /dev/null read/writable OK /tmp has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /var/lib has more than 64 KB available. - amandad: got ack: - I must have missed something or is it my setup is wrong. I don't have smbclient on the Marvin but i do have smbclient on Aries. I tried runing smbclient by hand it works. /usr/bin/smbclient Win2k's IP\\C$ -E -U backup -c quit -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8/8hRInIYkBVpGqURAry+AJ9RUfRu1ZCRVD11w4oF+2cwu8pePwCfale5 ZTZLA0XLSuXSguxrYzKs99s= =8VxJ -END PGP SIGNATURE-
