Amanda and STAR
Hello, Can we use star instead of tar with amanda-2.4.4p1 (rehl AS 3 update 4) ? Thanks !
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: Amanda and STAR
On Sunday 20 February 2005 11:51, FM wrote: Hello, Can we use star instead of tar with amanda-2.4.4p1 (rehl AS 3 update 4) ? Thanks ! I don't know if anyone has tried it. I occasionally play guinea pig, but my current test tar is tar-1.15-1, which so far (that knocking sound?, is me, knocking on wood) is working just fine now for about a month. Read the star docs carefully as ISTR someone said using the posix compat mode breaks things for amanda, or that was their interpretation. No personal experience with it though, which means I could be wrong. -- 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.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Amrestore error
On Sunday 20 February 2005 12:13, Spicer, Kevin (MBLEA it) wrote:
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]
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.
OTOH, not having walked thru that code, I could be full of it. But
thats my intuitive feel for this.
BMRB International
http://www.bmrb.co.uk
+44 (0)20 8566 5000
[snip totally irrevelant legalese]
--
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.33% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Calculated estimates?
On Fri, 18 Feb 2005 at 7:49pm, Kirk Strauser wrote I'm using Amanda 2.4.4p4 on a FreeBSD server with FreeBSD, Linux, and Mac OS X clients. I could have sworn I read something about a new option to make Amanda calculate dump size estimates from data about previous runs. Am I on crack, or does that really exist? This would be a wonderful way to eliminate the glacially slow estimate phase on some of my old Alpha servers. It's only in 2.4.5b1, from what I can tell, available on the snapshots page linked from the amanda.org downloads page. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
So long-
-and thanks for all the tape... I've moved on to backups using a single LTO-2 drive instead of this Sony DDS3 auto-loader. As backup needs and approaches have changed (and the engineering dept. will use the changer from now on, most likely), I say 'goodbye' to Amanda for now. Ever since I learned 'Let Amanda do her own thing, and all will be well...' (the 'Zen of Amanda,' I call it), I've been quite pleased with Amanda's performance. So as I leave Amanda for now, I'd just like to say how pleased I've been. Once I got her set up and running, I haven't had to worry about things since, something I haven't really had from any other backup software I've used. Great piece of software here... I will recommend Amanda to folks I run across in the future, and if anyone out there needs help/advice regarding the Sony TSL-S9000L DDS-3 external auto-loader (even had to pop the cover and fiddle with the guts of it fairly recently), feel free to send me e-mail.
Re: Amanda planner failure
Jingchun Chen wrote: Hi, Greetings to everyone! I am new to Amanda, and new to this mailing list. I got a planner failure and empty schedule. Amcheck seems to pass ok That seems to be because planner had nothing to do: the two disklist entries both seems to have some problem: disk /home/home-nz offline on coil? What are those two entries? (E.g. make sure you are using GNUTAR and not dump?) The real reason is in the amanda debug files on the client in /tmp/amanda/sendsize.DATETIME.debug . (except the two non-existing log dirs which I assume shouldn't cause problem). The tape server and backup client are the same machine, and the two disks to be backed up are NFS exported from another machine. We are running Debian, kernel 2.4.28 on Amanda server (hostname coil) and kernel 2.6 on the NFS server. That's not the normal way to proceed. (E.g. nfs-exported filesystems cannot be fully read by root, except if you used special export options.) The normal way is to install amanda-client on that NFS-server itself. Any clue? Thanks. *** amanda logfile DISK planner coil /home/home-am DISK planner coil /home/home-nz START planner date 20050208 INFO planner Adding new disk coil:/home/home-am. INFO planner Adding new disk coil:/home/home-nz. START driver date 20050208 START taper datestamp 20050208 label normal104 tape 0 FAIL planner coil /home/home-nz 20050208 0 [disk /home/home-nz offline on coil?] FAIL planner coil /home/home-am 20050208 0 [disk /home/home-am offline on coil?] FINISH planner date 20050208 WARNING driver WARNING: got empty schedule from planner STATS driver startup time 15.632 INFO taper tape normal104 kb 0 fm 0 [OK] FINISH driver date 20050208 time 15.634 * amcheck output Amanda Tape Server Host Check - amcheck-server: slot 4: date 20050208 label normal104 (active tape) amcheck-server: slot 1: date 20050201 label normal101 (exact label match) NOTE: skipping tape-writable test Tape normal101 label ok NOTE: info dir /var/log/amanda/normal/curinfo/coil: does not exist NOTE: index dir /var/log/amanda/normal/index/coil: does not exist Server check took 8.634 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 8.518 seconds, 0 problems found (brought to you by Amanda 2.4.4p1) -- 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 * ***
configure for amanda server and client coordinations
Please let me setup the scenerio first for 2 unix machines. The amanda server machine(amserver) is running redhat linux 9, the amanda client(amclient) machine is running FC2. In addition to serve the client machine, amserver also backups some files locally. The amserver is already setup to backup itself. I'm installing amanda on amclient now. This is my first time to set up amanda, so it's confusing how the client and server coordinates so that the server will backup itseft and also backup files from amclient. From amclient: I do ./configure --with-user=general --with-group=disk --with-amandahosts --with-configdir=/Backup/Configs --with-config=WeeklySet --with-index-server=amserver --with-tape-server=amserver --prefix=/Backup/usr --with-gnutar-listdir=/Backup/amanda/gnutar-listdir. Did I get it right? From amserver, since amanda is already installed and running, I'm not sure what I should change so that it will backup the file from the client machine. Please help?
Re: Amanda security +Kerberos
On Tue, 8 Feb 2005, Gil Naveh wrote:
Some have suggested to use sftp or ssh - bring those files to the server and
then backing it up locally.
However, by implementing this technique I am over loading the network -
because I have to ssh or sftp all files daily instead of letting Amanda get
only the changes (level 0,1 etc). But is there a way to implement ssh/sftp
with Amanda?
You can avoid overloading the network by not copying all files, but only the
changes, using rsync (over ssh, of course).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
Re: VXA-2 packet-loader issues and AMANDA [Fwd: hard luck with the new autoloader]
Hi all, if the scsi-connector is more then 50-pin's wide you'll have to look in the HW doc to determin that. If its only 50 pin wide, it's definitly a SE device. Christoph 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? I have no idea. Sorry. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The animal that coils in a circle is the serpent; that's why so many cults and myths of the serpent exist, because it's hard to represent the return of the sun by the coiling of a hippopotamus. - Umberto Eco, Foucault's Pendulum
Re: Issue making amanda on Solaris 8
On Wed, Feb 09, 2005 at 12:30:44PM -0800, Steve H wrote: killpgrp.c:90: error: too many arguments to function `getpgrp' One common cause of weird build problems on Solaris is using the wrong tool set. I don't know about this specific error, but it sort of sounds like a mismatch between the variant of getpgrp() that configure detected, and the one that the C compiler subsequently tried to use. To fix it, make sure that /usr/ccs/bin is in your PATH, and that /usr/ucb is *not*. If that doesn't work, try it the other way around :-) Hmmm, looking at the Solaris 8 box on which I'm typing this, it seems I built Amanda with both /usr/ccs/bin and /usr/ucb in my path. But they're in the order stated here; perhaps you have /usr/ucb first. Maybe it's sufficient to make sure that /usr/ccs/bin precedes /usr/ucb. After making any such path change, it's best to make distclean and rerun configure; otherwise, stale feature detections from the previous setup might continue to screw things up. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The animal that coils in a circle is the serpent; that's why so many cults and myths of the serpent exist, because it's hard to represent the return of the sun by the coiling of a hippopotamus. - Umberto Eco, Foucault's Pendulum
Re: Amanda's report
On Wednesday 16 February 2005 09:45, Gil Naveh wrote: After running Amanda's backup, I receive an email with a report about the last backup. The first section of that report is: FAILURE AND STRANGE DUMP SUMMARY: and under this section I get the following message: FAILURE AND STRANGE DUMP SUMMARY: servername/folder/to/backup lev 0 STRANGE You didn't post all the summary, so we can't guess really well. What does STRANGE means? What it usually means here is that some file changed while it was being read, like here, I get squawks about mail files from time to time because kmail is running 24/7, and may do a mail fetch run,or decide to purge old messages while amanda is running. I checked the data that was backed up on the tape and was able to restore it - should I ignore that message or what does Amanda tries to tell me? Dunno, post the rest of summary and we'll take a look. Many thanks, gil -- 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.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Issue making amanda on Solaris 8
That worked great, thanks for the help. Rookie mistake. Steve --- Paul Bijnens [EMAIL PROTECTED] wrote: Steve H wrote: I am having an issue on Solaris 8. After running ./configure with the appropiate options, I run make, which throws this error: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c `test -f killpgrp.c || echo './'`killpgrp.c killpgrp.c: In function `main': killpgrp.c:90: error: too many arguments to function `getpgrp' *** Error code 1 make: Fatal error: Command failed for target `killpgrp.o' Current working directory /usr/local/amanda-2.4.3/client-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Not quite sure how to handle this fatal error. Any help is appreciated. Dirty config.status file (from a different architecture? Do make distclean before running ./configure . -- 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 * *** __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com
Re: A question regarding backing up Window machines
On Wed, Jan 05, 2005 at 03:58:29PM -0800, Joe Rhett wrote: On Mon, Dec 20, 2004 at 04:02:49PM +0100, Paul Bijnens wrote: - You can exclude only one pattern. On Tue, Jan 04, 2005 at 02:42:13PM -0800, Joe Rhett wrote: Um, hello -- can you clue me in on this? I am trying (lazily) to figure out why my excludes are ignored during backups, but work just fine when I run the same tar command by hand. I need to add some debugging code, and just haven't found the time. Have you clued into something I've missed? On Tue, Jan 04, 2005 at 06:17:31PM -0500, Jon LaBadie wrote: could you give us your example exclude (note it is singlular) pattern that fails with amanda dumps but works with smbclient. Also the path to file(s) on the window machine that is excluded properly by smbclient but gets included by amanda. No such animal. I never said smbclient, I said tar. The system is running the amanda client. On Wed, Jan 05, 2005 at 10:06:27PM -0500, Jon LaBadie wrote: Your subject says Window machines. I assumed you were backing up samba shares. That uses smbclient with its tar option. If you had meant the much less commonly used cygwin port of amanda, which does use gnutar, I thought you would have mentioned it. Or maybe there is another possibility I haven't considered. Give me a hand here. I'm sorry, I thought I was on the amanda mailing list, writing about the amanda client. No, I'm not talking about using a program to back up remote shares - I am writing about the actual amanda client. I'm a bit surprised by your negative response, and your assumption of an indirect method of backup over the native client. And whatever -- this issue has been ignored by you guys for years now, why am I bothering? -- Joe Rhett Senior Geek Meer.net
Re: forcing skipped incrementals into holding disk
On Tuesday 15 February 2005 02:44, Jamie Wilkinson wrote: This one time, at band camp, Frank Smith wrote: --On Tuesday, February 15, 2005 17:44:32 +1100 Jamie Wilkinson [EMAIL PROTECTED] wrote: We've got one problem machine that has about 90GB in one DLE, and our tapes are 100GB LTO1s. Of course, once a cycle, the server decides it can only write maybe 5 DLES out of 150+ to the tape, because one of them is 80GB+, and so all the other dumps end up being reported as FAILED [dumps way too big, 1 KB, must skip incremental dumps] which afaict means that amanda doesn't even attempt to back up this DLE because it knows it's not going to fit it on the tape. But I've got a ton of free space in the holding disk. What I want to know is, is there an option to tell the server to do the dumps anyway and hold them, so later I can come along with another tape and flush them? If you have plenty of holdingdisk space, I would think they would go there. Even with the default reserve of 100%, you should still get the incremental. You might have to look in the debug files to see why they were completely skipped. Well, I did check, and there were no incrementals in the holding disk. According to the debug log, the planner fails the dumps right after building the schedule. In general, we only need one LTO1 a day, this particular DLE is a freak statistic well outside the standard deviations of the other DLE sizes, so doing a flush once every cycle is more appealing than allocating two tapes per run. Just because you set runtapes 1 doesn't mean Amanda will use them all. I keep runtapes set to a number higher than what normally gets used per run, and have autoflush set true. That way even if I have a tape error and it all goes to disk, the next run can flush it all and do the backups as well without running out of tape. If you normally only need one tape, then that's what it will normally use, even if you have runtapes set to 2 or 3 or whatever. The higher number just allows it to use additional tape(s) if needed. I was under the impression that Amanda would choose dump levels to fill as much of the tapes as possible. That's incorrect then? If the holding disk is reserved 100% for incrementals, which is the default, no, it won't do any of them. -- 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.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: client version varies from server
On Tue, Feb 08, 2005 at 10:00:39AM -0500, Don Carlton enlightened us: It looks like it might be a firewall issue on the server? Does anyone know what the minimum server rules and client rules would be in iptables/ipchains? I use the following: Server: allow udp 10080 and tcp 10082,10083 from subnet ip_conntrack_amanda Client allow udp 10080 from server ip_conntrack_amanda You can do things withouth ip_conntrack_amanda by compiling with --with-tcpportrange and --with-udp-portrange, then opening those holes, but that is more work :-) Hope that helps, Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpw8H8GnefPL.pgp Description: PGP signature
Re: A question regarding backing up Window machines
On Fri, Jan 28, 2005 at 04:09:57PM -0800, Joe Rhett wrote: On Wed, Jan 05, 2005 at 03:58:29PM -0800, Joe Rhett wrote: On Mon, Dec 20, 2004 at 04:02:49PM +0100, Paul Bijnens wrote: - You can exclude only one pattern. On Tue, Jan 04, 2005 at 02:42:13PM -0800, Joe Rhett wrote: Um, hello -- can you clue me in on this? I am trying (lazily) to figure out why my excludes are ignored during backups, but work just fine when I run the same tar command by hand. I need to add some debugging code, and just haven't found the time. Have you clued into something I've missed? On Tue, Jan 04, 2005 at 06:17:31PM -0500, Jon LaBadie wrote: could you give us your example exclude (note it is singlular) pattern that fails with amanda dumps but works with smbclient. Also the path to file(s) on the window machine that is excluded properly by smbclient but gets included by amanda. No such animal. I never said smbclient, I said tar. The system is running the amanda client. On Wed, Jan 05, 2005 at 10:06:27PM -0500, Jon LaBadie wrote: Your subject says Window machines. I assumed you were backing up samba shares. That uses smbclient with its tar option. If you had meant the much less commonly used cygwin port of amanda, which does use gnutar, I thought you would have mentioned it. Or maybe there is another possibility I haven't considered. Give me a hand here. I'm sorry, I thought I was on the amanda mailing list, writing about the amanda client. No, I'm not talking about using a program to back up remote shares - I am writing about the actual amanda client. I'm a bit surprised by your negative response, and your assumption of an indirect method of backup over the native client. And whatever -- this issue has been ignored by you guys for years now, why am I bothering? Joe, In your first posting on this thread you deleted the OP's comments, starting with Paul B's response to the OP. That led me to believe, since I did not go back to the archive to examine the thread, that you were the OP. I did not realize you were jumping in on another, windows-related thread with a new, somewhat unrelated question (at least as to OS). If you'd like to continue exploring your situation I'd suggest you start a new thread and I'd like to see the same things I asked for earlier. You still could have shown them to us even given my mistaken assumption that you were dealing with a windows client. Namely things like: - disklist - filesystem organization - exclude file or patterns that amanda does not do what you want - tar command that does (including where you execute from) - ??? whatever you think might help BTW what issue has the list been ignoring? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: archiving tapes?!
On Friday 28 January 2005 14:16, Michael Loftis wrote: --On Friday, January 28, 2005 11:22 -0700 Mark Costlow [EMAIL PROTECTED] wrote: The script is fairly generic (I tried not to let it depend on my local environment too much, but there may be some gotchas). I was also lazy about a couple of assumptions (like the fact that my dumps all used gtar). If anyone wants it, let me know. I'd love to have a copy of it...While we're right now using vtapes, we'll be changing methods to a tape library soon, but I want to keep offsite dumps as well...I think this would be easier than doing them 'in' amanda. I know the script isn't exactly meant for that but it's a starting point, and will save me coding time. Thanks! As a suggestion to preserve the indices, it might be possible to use that level 0 name retrieved from the vtape, to reach into the indices directory and recover each of those indice files that go with it, and stuff it out to the media used for the long term storage too. This is something that would be possible if one were doing a seperate, appended to the tape, saving of both the config directory tree, and the indice directory tree as I am now doing with my wrapper scripts such that if I had to do a bare metal recovery to a fresh drive, the first thing I would do is re-install the os in bare bones mode, use dd, tar and gzip to recover the /home/amanda tree, reinstall amanda from that, then untar the config dir file and the indice dir file. At that point, all of amandas amrestore and amrecover stuff should be up and running, makeing an exact restore of the whole machine possible. If one were to select just the current indice file for that backups last level 0, it certainly seems like it could be made to work, how satisfactory remains to be seen. Negative Comments anybody? Here is my concern: Particularly from the standpoint that such a level 0 scenario only, it does have the potential to restore things out of sync if the last level 0 on /home was say 6 days old, and the /usr/local was last nights. That could be interesting on a machine with lots of volatile stuff, like the maildirs? Or a freshly installed program. Personally I think I'd be more interested in this train of thought if a days snapshot was more fully done, by getting the last level 0, and all subsequent higher levels of that DLE at the same time, and combining that into (as seperate files of course) the offsite storage medium chosen. That would no doubt add to its size, but at least it would be a valid 'snapshot' then. For a business doing such a thing for its accounts payable and accounts receivable, I'd think it would be of paramount importance. -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
RE: AIX guru's please
Title: RE: AIX guru's please This is an old email message. I was able to recover my data. Kevin D. Alford -Original Message- From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED] Sent: Wed 2/2/2005 1:35 PM To: Jon LaBadie Subject: Re: AIX guru's please Hopefully there are some other people on the list with AIX 5 experience, mine stops at AIX 4. Yes, backup is the AIX name for dump, it is a block level backup utility rather than file level. One of its features is the ability to backup by file name or by i-node, but most other versions of dump can do the same. No, it is not compatible with other versions of dump (dump usually is OS specific, though I think Linux and Solaris dump formats can sometimes work with each other). You will need to use the restore program on AIX to read the archive. I can send you the backup/restore AIX man pages via e-mail, no point in cluttering the list with them. Also Sprach Jon LaBadie: Kevin Alford started a thread about losing his amanda server crashing, needing to rebuild it, not having indexes and needing to do a restore. The system details pre-crash were Amanda 2.4.2p2 on AIX 5.1 ML6 I see the dump program is IBM ?proprietary? program called 'backup' !! Is that program dump compatible? From my long ago AIX experience I recall that 'restore' is the appropriate recovery program for 'backup'. But what arguments should be used, i.e. what might be needed for ...? I just love AIX! Kevin extracted the dump file, minus the amanda header. He then tried to use gzip -dc on it to create an uncompressed copy. The copy was 3.5x larger, so obviously it had been gzip'ped. However, when Kevin ran the file command on both the original and on the uncompressed files, AIX's file command reported both as being: data or International text Nothing about either being a gzip or a backup file. Kevin sent me the leading part of the gunzipped file and on my Solaris system, the file command reports it is a ufsdump archive. Does AIX even have the ability to work with UFS type file systems? If so, are ufsdump/ufsrestore part of an add-on package? Kevin reports his rebuilt system has neither program. May not matter. Based on the amanda header, I suspect that backup/restore are the appropriate pair of programs, not ufsdump/ufsrestore. Do other AIX amanda installations use backup/restore? If so, what are appropriate options for a restore from an backup format file already on disk. Maybe both for TOC and for extraction. We can worry about from tape later. -- C. Chan c-chan at uchicago.edu GPG Public Key registered at pgp.mit.edu
Re: client version varies from server
On Tuesday 08 February 2005 10:00, Don Carlton wrote: It looks like it might be a firewall issue on the server? Does anyone know what the minimum server rules and client rules would be in iptables/ipchains? Thats all in the FAQ and docs Don. And its pretty straight forward, if iptables is involved, there is even a special kernel/iptables module for 2.6 kernels that has all the amanda rules builtin. Google for that, or if you built your own kernel, a quick 'make xconfig' should show it under the netfilter branch of the tree. Ditto IIRC for users of SELinux. However, I have no experience with useing these as all my machines being backed up are behind the actual firewall, including the firewall box itself. Two nics in that box, with the firewall being between the outside connection and the box itself which uses the 2nd nic for the local net on a different subnet for connection to the rest of the systems here. Paranoid about the firewall, I both back it up with amanda, and rsync its more important dirs locally, which also gets backed up by amanda. This is one of the reasons I'm in favor of a 2 nic firewall, it can very effectively isolate you, while being absolutely transparent as far as the use of the internet from any box inside the firewall is concerned. I've had two penetration attempts that failed at the firewall logged in the last 22 months, way too much NAT for the script kiddies to negotiate. FWIW, both attacks came from a compromised verizon dns server that was one of the two the routers internal PPPoE hands me, the server running IIS of course, I nmapped it just to see what it was running after both attacks. Verizon runs 100% darkside software, and does not officially support linux. They are getting to the point where they'll 'tolerate' it though. The lawyers rule is supreme there, too bad we don't have an annual official Bill Shakespear holiday... [...] -- 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.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL
On Tuesday 08 February 2005 11:24, Jon LaBadie wrote: On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote: Jon LaBadie wrote: With the ultrium it is less important about considering HW or SW compression. But be aware that on Solaris whether HW compression is turned on or not is determined by the device you choose. You will find lots of /dev/rmt/0xyz devices. The xyz determines the properties of the device the driver will set upon opening it. Don't be fooled into assumptions about the various devices. The c device is listed as compressed. But that is the conventional use. There is no certainty that it turns compression on for every device, or that devices without the c are no compression. You will even have a c device for drives that are not capable of HW compression ;-) Only way to tell is check the docs for the drive and settings for the driver. And then I'd check it if I could. Indeed. And check the file st.init, where the letters get their meaning. Paul, I'm unfamiliar with the file st.init. Nor do I find one on my system. Did you mean the st.conf file in /kernel/drv? If the st.conf file, I don't find an entries for any lto's I recognize. One poster said it was builtin to the driver, another said they had to edit the file and add an entry. The drive docs would probably still be needed to interpret the entry. 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. -- 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.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: So long-
On Tuesday 15 February 2005 17:07, Daniel Bentley wrote: -and thanks for all the tape... I've moved on to backups using a single LTO-2 drive instead of this Sony DDS3 auto-loader. As backup needs and approaches have changed (and the engineering dept. will use the changer from now on, most likely), I say 'goodbye' to Amanda for now. Why? Amanda can run that autoloader just fine. No need to goto the dark side. Ever since I learned 'Let Amanda do her own thing, and all will be well...' (the 'Zen of Amanda,' I call it), I've been quite pleased with Amanda's performance. So as I leave Amanda for now, I'd just like to say how pleased I've been. Once I got her set up and running, I haven't had to worry about things since, something I haven't really had from any other backup software I've used. Great piece of software here... I will recommend Amanda to folks I run across in the future, and if anyone out there needs help/advice regarding the Sony TSL-S9000L DDS-3 external auto-loader (even had to pop the cover and fiddle with the guts of it fairly recently), feel free to send me e-mail. -- 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.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
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: AMLABEL
On Sunday 20 February 2005 19:07, Spicer, Kevin (MBLEA it) wrote: -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). Humm, I apparently never did that, Kevin. All I have is the .examples file. Silly Q? Could this be the reason I've blamed amanda for not being able to rewind the tape in a Seagate 4586N changer? And while amanda couldn't rewind it, mt could? Humm, on inspecting that file, I find its quite jurassic, offering no clues for anything newer than whats obviously decade+ old DDS1 drives. And no mention of rewind capabilities for any drive IIRC. So I doubt its connected with my non-rewinding chg-scsi script useage. -- 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.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Backup
Hi All How can I have monthly,quarterly and half yearly backup using Amanda Thanks in Advance -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. 1st Floor,'C'Wing, Fortune2000, Bandra Kurla Complex, Bandra(East), Mumbai 400051. Maharashtra India Tel: +91-22-3987 Fax: +91-22-39878899 Cell : +91-9820367783 E-mail : [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Backup
On Monday 21 Feb 2005 06:05, Kaushal Shriyan wrote: Hi All How can I have monthly,quarterly and half yearly backup using Amanda Hi, Simply make some more amanda.conf and run them monthly, quarterly and half yearly. Thanks in Advance -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1467 624141 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E [EMAIL PROTECTED] Open Source. Open Solutions(tm). http://www.suretecsystems.com/
