Problem excluding with GNUtar
Title: Problem excluding with GNUtar
Hi,
I'm having a problem backing up one of my linux hosts with amanda. I keep getting...
FAILURE AND STRANGE DUMP SUMMARY:
linux1 /dev/hda3 lev 0 FAILED [/bin/tar returned 2]
and...
/-- linux1 /dev/hda3 lev 0 FAILED [/bin/tar returned 2]
sendbackup: start [linux1:/dev/hda3 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./log/messages: file changed as we read it
| Total bytes written: 61583360
? gtar: Error exit delayed from previous errors
sendbackup: error [/bin/tar returned 2]
\
Obviously /var/log/messages is the problem (/dev/hda3 is /var). But I followed the instructions in the man pages to exclude this file - from amanda.conf ...
define dumptype always-full-tax {
global
comment "Full dump of this filesystem always using tar"
program "GNUTAR"
exclude "/var/log/messages"
compress fast
priority high
record no
index yes
dumpcycle 0
}
and from disklist..
linux1 /dev/hda3 always-full-tax 1 le0
I also tried exclude"./log/messages" in the dumptype definition but that didn't work either. Has anyone else had a problem like this.
I'm using amanda2.4.2p2 the server is Solaris 6 and the client is Slackware 7.1.0 with GNU tar 1.13
BMRB International
http://www.bmrb.co.uk +44 (0)20 8566 5000
This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
RE: Problem excluding with GNUtar
Title: RE: Problem excluding with GNUtar
Thanks, (and to everyone else who replied)
If I'm reading this right...
I want to back up each partition seperately so to backup my root / partition I should put /var in an exclude list and then backup var excluding ./log/messages...
yes?
Sorry if that seems like a stupid question but I'd like to be sure.
-Original Message-
From: Doug Silver [mailto:[EMAIL PROTECTED]]
Sent: 18 April 2002 16:44
To: Spicer, Kevin
Cc: '[EMAIL PROTECTED]'
Subject: Re: Problem excluding with GNUtar
Hi Kevin -
Two problems, your gtar is too old and needs to be upgraded. Second is
that if you're using gtar, you're not suppose to use the disk device but
the actual partition in the disklist, e.g.:
linux1 / always-full-tax 1 le0
(assuming hda3 is /)
I use exclude files, which you put on the client. Assuming the partition
is '/', the exclude list would just contain:
./var/log/messages
to exclude entire directories would be like this:
./var/spool/mqueue
Check the online FAQ and/or the online search archives for further
examples.
-Doug
On Thu, 18 Apr 2002, Spicer, Kevin wrote:
> Hi,
>
> I'm having a problem backing up one of my linux hosts with amanda. I keep
> getting...
>
> FAILURE AND STRANGE DUMP SUMMARY:
> linux1 /dev/hda3 lev 0 FAILED [/bin/tar returned 2]
>
[snip]
>
> Obviously /var/log/messages is the problem (/dev/hda3 is /var). But I
> followed the instructions in the man pages to exclude this file - from
> amanda.conf ...
>
> define dumptype always-full-tax {
> global
> comment "Full dump of this filesystem always using tar"
> program "GNUTAR"
> exclude "/var/log/messages"
> compress fast
> priority high
> record no
> index yes
> dumpcycle 0
> }
>
> and from disklist..
>
> linux1 /dev/hda3 always-full-tax 1 le0
>
> I also tried exclude"./log/messages" in the dumptype definition but that
> didn't work either. Has anyone else had a problem like this.
>
> I'm using amanda2.4.2p2 the server is Solaris 6 and the client is Slackware
> 7.1.0 with GNU tar 1.13
BMRB International
http://www.bmrb.co.uk +44 (0)20 8566 5000
This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
RE: Problem excluding with GNUtar
Title: RE: Problem excluding with GNUtar That makes a lot of sense, but presumably you have to use root as the amanda user on the client machine to tar in this way? -Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED]] Sent: 18 April 2002 19:20 To: '[EMAIL PROTECTED]' Subject: Re: Problem excluding with GNUtar On Thu, Apr 18, 2002 at 04:59:15PM +0100, Spicer, Kevin wrote: > Thanks, (and to everyone else who replied) > > If I'm reading this right... > I want to back up each partition seperately so to backup my root / partition > I should put /var in an exclude list and then backup var excluding > ./log/messages... > yes? > Sorry if that seems like a stupid question but I'd like to be sure. No, here is some clarification (hopefully) "partitions", "file systems", "directories", each a term with multiple uses. To avoid confusion, you back up "disk list entries" (DLE's :), ie things you put in your disklist file. These DLE's can be any of the above, but using tar there should be at least one DLE for each file system (partition?) you want to backup. A DLE of "/" does not back up the entire system unless you have only one file system. I installed my laptop Solaris is like this, but no other system. Often the DLEs are the full path to the mount point of a file system. Thus, supposing you have 3 file systems, the root (/), /var, and /opt, you should have a minimum of 3 DLEs. hostname / dumptype hostname /var dumptype hostname /opt dumptype To exclude a single file like /var/log/messages, you could put a line in the dumptype 'exclude "./log/messages". Note that the path should NOT include the part of the path to the start of the DLE. (for more detail, see the excellent article on exclude by A.Hall in your "docs" directory) But note that this will also exclude /opt/log/messages and /log/messages if all three DLEs use the same dumptype entry. For finer control you will have to create separate, nearly identical dumptypes. (not hard as one dumptype can incorporate a common type). This exclude mechanism will only allow the exclusion of a single file. For multiple file exclusions you have to use an 'exclude list filename' directive and specify a file containing the exclusions. Again see A.Hall's article. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
RE: Hard drive as backup media?
Title: RE: Hard drive as backup media? I'm not quite clear what you have in mind, you're presumably not talking about having a cycle of hard drives (are you?) but just keeping a mirror on a different machine. A couple of packages that might interest you... rdiff-backup - makes a mirror on a remote (or local) disk over a secure connection, and keeps it up to date by sending diffs . A nice feature is the ability to roll back files to the state they were in 1,2,3 etc days ago. http://www.stanford.edu/~bescoto/rdiff-backup/ MkCDrec - makes rescue CD's for linux systems (x86) if a fast recovery of a hopelessly broken system is what you're looking for. http://mkcdrec.ota.be/ This is not to say that Amanda doesn't do the business - it rocks! But sometimes you don't want to wait while the tape drive tries to find that important file among 70G of other data! I use a combination of all three methods, theres something reassuring about knowing that theres a nice safe tape of all your data in a big sturdy safe somewhere :) -Original Message- From: Ben Snyder [mailto:[EMAIL PROTECTED]] Sent: 02 May 2002 15:25 To: [EMAIL PROTECTED] Subject: Hard drive as backup media? Hi all I've got a situation where Amanda is already set up and running fine on my network, but I'd like to change my backup media from tapes to hard drives. Has anyone ever tried this? Thanks, -ben BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
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: disk offline - runtar as root
I guess it must be a check thats compiled in? Try recompiling, if I remember (its been a while...) its something like --with-amanda-user=amanda [or whichever user you are using] --with-amanda-group=sys [in your case] Best to check this in the docs though! -Original Message- From: Jonathan Murray [mailto:[EMAIL PROTECTED]] Sent: 06 June 2002 18:25 To: Spicer, Kevin Cc: [EMAIL PROTECTED] Subject: 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: hi
One possibility is to allow anonymous users to post through a web page, but only list members to post via email. If a non-member attempts to post via email they should recieve a polite bounce referring them to the website. -Original Message- From: Dave Sherohman [mailto:[EMAIL PROTECTED]] Sent: 10 September 2002 15:15 To: [EMAIL PROTECTED] Subject: Re: hi There is such a thing as being overly paranoid... On Mon, Sep 09, 2002 at 03:46:37PM -0400, Greg A. Woods wrote: > I beg to differ. List servers should be no more tolerant of accepting > e-mail from known abusers, dial-up/DSL/cable addresses, ITYM "ISP DHCP pools". A static IP address is a static IP address, regardless of whether the device's uplink is via T1, ISDN, DSL, cable, modem, or carrier pigeon. You can't assume that someone's a spammer purely based on their physical connection to the network. > No, I don't think so. All postings to un-moderated lists like this > should be only from validated subscribers. Interested users can > subscribe just long enough to discuss their issues if they don't want to > remain subscribed. And receive how many dozens/hundreds of unrelated messages from the list over the course of a few days while discussing and resolving their issues? Sorry, can't agree with you here. > Bug reports from non-subscribers should go to a separate (hopefully > low-traffic) list that only select developers and other highly > interested parties need to subscribe to, After all, we wouldn't want the list's normal riff-raff to learn anything from non-subscribers' questions or - heaven forbid! - have someone other than "select developers and other highly interested parties" offer help to them. BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business. BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
RE: Quick Multiple Tape Question
> Amanda cannot span one file across more than one tape, and because > of the potentials for a disaster in such things as re-ordering the > tapes on recovery, or any one of the other things that Mr. Murphy > is famous for, it isn't likely that amanda ever will have that > ability programmed in. Thats a shame, I've persisted using amanda as it has all the features I want except for this one. I had hoped that this functionality would appear soon. I always thought that one of the best features of Amanda was its ability to enforce correct tape usage, therefore I can't see why that should be a big issue. This is the one thing that is stopping me consolidating all my unix/linux backups onto amanda. I know you can split one partition into smaller sections using options to tar, but given the way the filesystem changes frequently I'm not happy to trust this (its easier and safer to stick with ufsdump) BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
Amrestore error
Hello,
I'm having a strange problem with amrestore. I get an I/O error in the
middle of a restore and amrestore exits, but st0 device remains busy and
only a reboot can clear it. There is an error on the console as
follows...
st0: Error 70002 (sugg. bt 0x0, driver bt 0x0, host bt 0x7)
... My first thoughts were hardware errors, but I've checked out
everything I can (short of buying a new library!) and everything seems
fine. Perhaps more revealingly I have no issues performing backups with
amanda or extracting data from the tape using dd.
Heres the amidxtaped.debug file (I originally experienced the problem
while using amrecover)
## START amidxtaped.debug [extract]
amidxtaped: time 6.803: Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "-l"
argv[4] = "UnixDaily-FHH545"
argv[5] = "-f"
argv[6] = "72"
argv[7] = "/dev/nst0l"
argv[8] = "^myhost.mydomain.com$"
argv[9] = "^/export/home$"
argv[10] = "20050219"
amrestore: 72: restoring myhost.mydomain.com._export_home.20050219.0
amrestore: read error: Input/output error
amidxtaped: time 38.951: amrestore terminated normally with status: 2
amidxtaped: time 38.951: rewinding tape ...
gzip: stdin: unexpected end of file
### END ##
Running the amrestore command manually (redirecting output to a file)
gives the same errors. The command was...
amrestore -p -h -l UnixDaily-FHH545 -f 72 /dev/nst0l
^myhost.mydomain.com$ ^/export/home$ 20050219 > 1-amrestore-fromtape
The resulting output file is indeed smaller than expected.
Then...
mt -f /dev/nst0l rewind
my -f /dev/nst0l fsf 72
dd if=/dev/nst0l of=2-dd-fromtape bs=4194304 [My tape
block size is 4096k]
...results in the full file being copied from disk with no errors. I
can then extract the dump from the file with amrestore...
amrestore -p -b 4096k -h ./2-dd-fromtape > 3-amrestore-fromdd
Which is fine.
In case it was relevent I also tried (by trial and error) to see if the
truncated version from the original amrestore fell on a tape block
boundary - it did (22 blocks including the header). I found this by
truncating the dd'd image then running amrestore on it.
dd if=2-dd-fromtape of=4-dd-truncated-to-22-blocks bs=4194304 count=22
amrestore -p -b 4096k -h ./4-dd-truncated-to-22-blocks >
5-amrestore-fromddtruncated
The file sizes from the above can be seen below...
-rw-r--r--1 amanda disk 131203072 Feb 20 15:54
1-amrestore-fromtape
-rw-r--r--1 root root 343932928 Feb 20 16:04 2-dd-fromtape
-rw-r--r--1 root root 498728960 Feb 20 16:11
3-amrestore-fromdd
-rw-r--r--1 root root 92274688 Feb 20 16:15
4-dd-truncated-to-22-blocks
-rw-r--r--1 root root 131203072 Feb 20 16:15
5-amrestore-fromddtruncated
All of which seems to point to some problem with the way amrestore
interacts with the tape device. Has anyone seem this before?
For completeness:
Amanda 2.4.4p4
Tao Linux release 1 (Mooch Update 4) [ Rebuild of Red Hat Enterprise 3 ]
Compaq Proliant 1600R
Overland Powerloader with Quantum SDLT320 drive
Adaptec 29160 Scsi card
My tapetype definition...
define tapetype Quantum-SDLT320 {
comment "Quantum SDLT 320 hardware compression off/ blocksize 4m"
length 159080 mbytes
filemark 4096 kbytes
speed 15762 kps
blocksize 4096 kbytes
}
[The reason for the blocksize change was to improve speed, it now
achieves speeds approaching the manufacturers quoted ones]
BMRB International
http://www.bmrb.co.uk
+44 (0)20 8566 5000
_
This message (and any attachment) is intended only for the
recipient and may contain confidential and/or privileged
material. If you have received this in error, please contact the
sender and delete this message immediately. Disclosure, copying
or other action taken in respect of this email or in
reliance on it is prohibited. BMRB International Limited
accepts no liability in relation to any personal emails, or
content of any email which does not directly relate to our
business.
RE: AMLABEL
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett >Paul: That file (st.init/st.conf) doesn't exist on a redhat flavored >linux install. Nor on a debian sarge based install of BDI-4.08, I >just checked that one too If my Tao box is anything to go by [it should be, Tao is a rebuild of RHEL] then you need the mt-st package installed which contains the program stinit and an example config file /usr/share/doc/mt-st-0.7/stinit.def.examples which you need to copy to /etc/stinit.def and edit to meet your requirements. You'll probably also want to put something in your boot time scripts to run stinit (just call /sbin/stinit without any arguments). BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 _ This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
RE: VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]
>Eric Siegerman schrieb: >> On Mon, Feb 07, 2005 at 04:41:17PM -0500, Jon LaBadie wrote: >>>Can on look at the device connectors, or better yet, the external >>> connectors, and tell if a device is LVD or SE? Or does one have >>> to check the HW doc? >> If you're lucky enough that the manufacturer has prited a scsi symbol on it you can compare the symbol to the list here http://scsifaq.paralan.com/scsifaqanswers4.html [scroll to the bottom of the page] BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 _ This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
RE: Amrestore error
>I'm not sure whats happening at the 92 megabyte mark, but I would make >an observation re the block size you are using. To me, that seems >rather large. To do a checksum over a 4 megabyte block might >possibly be running into a math problem because much of that code is >legacy, and probably never expected anybody to use more than 128k, >and I personally haven't explored the range above 32k. Dropping the block size seems to have helped. Following some experimentation I got the problem with a 2048k block, but not a 1024k block. I've reduced my blocksize now to 512k. I'll know for sure once I've backed up and attempted a restore of something big by means of a test. BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 _ This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
