permanent archives, client notification and subdirs
Hi, I have just got Amanda set up on a server at client machine. Can anyone help me out with a few questions 1) How do I go about creating a permanent archive of tapes? I actually want to dump newly created files to tape each at dump via amanda (i.e no incrementals, always fulldumps). I tried setting the following params, but I'm not sure this if this is right dumpcycle 0 tapecycle 9 # lots of tapes in the tapecycle... 2) I also want to remove the client files from disk automatically after they've been archived. However, I'm just not sure how to determine if a given set of files/filesystem has been archived from a client machine. Any clues on how to do this? 3) Is there a way of dumping subdirectories to disk, rather than just whole filesystems? Thanks in advance, Justin.
Re: Can load but can't eject tapes...
On Wednesday 09 May 2001 21:22, John R. Jackson wrote: I use the chg-scsi software.. i found the OFFLINE_BE.. in chg-zd-mtx, but is that connected in some way with chg-scsi ?? Those are two different changers. You want to put: eject1 in your chg-scsi config file (or change it from zero to one if the line is already there). Have allready tryed that, but it don't work.. But if i use the chg-scsi changer software to change tape, after running mt -f /dev/nst0 offline it CAN change the tape... Any suggenstions... ?? -Lennart -- Lennart Hansen, System Administrator @ DixaNet (UK) Ltd. Email: [EMAIL PROTECTED] Mobile:[+45] 51 39 67 42 Vedbæk Strandvej 341 Phone: [+45] 45 67 67 42 DK-2950 Vedbæk Fax.: [+45] 45 67 67 45 [Enrum Castle] Quitters Never Win, Winners Never Quit, But Those Who Never Win AND Never Quit Are Idiots.
amanda failed
I recieved this mail, what is the meaning of no backup size line?
Why the dump failded???
Thanks
Montse
These dumps were to tape Miercoles.
The next tape Amanda expects to use is: Jueves.
FAILURE AND STRANGE DUMP SUMMARY:
marte /home lev 0 FAILED [no backup size line]
marte /home lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 0:23
Dump Time (hrs:min)0:11 0:11 0:00
Output Size (meg)1610.8 1610.80.0
Original Size (meg) 1610.8 1610.80.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) 2417.6 2417.6--
Tape Time (hrs:min)0:22 0:22 0:00
Tape Size (meg) 3311.5 3311.50.0
Tape Used (%) 20.0 20.00.0
Filesystems Taped 2 2 0
Avg Tp Write Rate (k/s) 2623.1 2623.1--
FAILED AND STRANGE DUMP DETAILS:
/-- marte /home lev 0 FAILED [no backup size line]
sendbackup: start [marte:/home level 0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f... -
sendbackup: info end
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.bbox_server:
socket ignored
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.comext_server:
socket ignored
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.game_server:
socket ignored
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.scred_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/dev/log:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/tmp/.X11-unix/X0:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.peana_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.scard_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.sound_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.sound_udp_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.supv_gameclient:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
bbox_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
comext_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
game_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
scard_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
scred_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.bbox_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.comext_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.ob_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.sc_server:
socket ignored
| gtar: ./test/test2/lotoserver_sc/socks/sock.bbox_server:
socket ignored
| gtar: ./test/test2/lotoserver_sc/socks/sock.comext_server:
socket ignored
| gtar: ./test/test2/lotoserver_sc/socks/sock.sc_server:
socket ignored
? Total bytes written: nan (0B, ?B/s)
sendbackup: error [no backup size line]
\
NOTES:
taper: tape Miercoles kb 3390944 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
--- -- --
marte/home0 N/A1741440 --N/A N/A 10:102853.2
srvlinux /home0 16494721649472 -- 11:222417.611:222417.3
(brought to you by Amanda version 2.4.2)
Hardware Compression Problem
We are currently using a StoreEdge L280 Multichanger tape unit to backup via Amanda v2.4.1p1. When switching on hardware compression on the tape unit, Amanda seems to override this setting switching hardware compression off. Can anyone tell me how to make the tape units hardware compression setting stay on. Best regards, Keith
Re: permanent archives, client notification and subdirs
On Thu, 10 May 2001 at 6:30am, [EMAIL PROTECTED] wrote 1) How do I go about creating a permanent archive of tapes? I actually want to dump newly created files to tape each at dump via amanda (i.e no incrementals, always fulldumps). I tried setting the following params, but I'm not sure this if this is right dumpcycle 0 tapecycle 9 # lots of tapes in the tapecycle... Yep, that'll work. 2) I also want to remove the client files from disk automatically after they've been archived. However, I'm just not sure how to determine if a given set of files/filesystem has been archived from a client machine. Any clues on how to do this? I'm really not sure what you're trying to accomplish here. If you *really* want to delete everything you back up, you could have your backup script run amanda and then, iff amanda exits normally, parse the disklist and 'rm -rf' one directory below each disklist entry. I *STRONGLY* recommend against this. Automated rm is a Bad Idea (TM). Leave the data there, or remove it by hand. 3) Is there a way of dumping subdirectories to disk, rather than just whole filesystems? Use GNUtar rather than dump. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amflush, chunks, cruft warnings
when running amflush on amanda dumps containing chunk files, can the warning messages about cruft files that correspond to chunks be ignored? for example... NOTES: amflush: visual._1.0.1: ignoring cruft file. are these chunks really being taped along with the rest of the dump, despite the warning message? -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
dumps way too big
I got the following message for all of my hosts, except those that it did a level 0 back up of. ns0 / lev 1 FAILED [dumps way too big, must skip incremental dumps] I read the Faq-o-matic on it, which says ...Amanda couldn't back up some disk because it wouldn't fit in the tape(s)... This does not really make sense to me bacause the majority of the systems have 6GB drives, and I have config'd amanda to use the two 35GB DLT drives. The backups that amanda did do total only about 3.5GB. So why is amanda not using the remaining 66.5GB? What are some possibilities of misconfigurations to make this happen? TIA, William Find the best deals on the web at AltaVista Shopping! http://www.shopping.altavista.com
Re: permanent archives, client notification and subdirs
2) I also want to remove the client files from disk automatically after they've been archived. ... I agree with the comments from Joshua Baker-LePain that automatically doing this is probably dangerous. One thought about how to do it (but not any safer) would be to get a catalogue of the dump image from tape after amdump/amflush and then remove the items it said it found. This is especially unsafe when using dump because a catalogue (restore with the 't' option) does not really read the whole image, but if you use GNU tar and it successfully reads the whole image, you can be reasonably certain the data is really there. Depending on what the data is, I'd want to clone the tape (and verify the clone) so I had at least two copies, though. Justin. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Can load but can't eject tapes...
You want to put: eject 1 in your chg-scsi config file ... Have allready tryed that, but it don't work.. What did it do? I'd like to see the chg-scsi*debug file that goes along with this. Just to be clear, are you using the chg-scsi that comes with 2.4.2p2 or did you get the one from 2.5 (or something else)? -Lennart John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda failed
I recieved this mail, what is the meaning of no backup size line? Why the dump failded??? That message means Amanda could not parse the last line of output from tar that says how big the backups were. It reports the line: ? Total bytes written: nan (0B, ?B/s) That's clearly wrong. My guess is your version of GNU tar is broken. What version are you using? If it's 1.13 based, you need at least 1.13.17, or better yet, 1.13.19. If it's 1.12, you need the patch from www.amanda.org (although I don't think it affects this particular problem). FYI, these errors: | gtar: ./desar/desar11/LineaBase/lotoserver/var/socks/sock.bbox_server: socket ignored are fixed in the latest Amanda (2.4.2p2). Montse John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Hardware Compression Problem
We are currently using a StoreEdge L280 Multichanger tape unit to backup via Amanda v2.4.1p1. What OS on your tape server? When switching on hardware compression on the tape unit, Amanda seems to override this setting switching hardware compression off. Amanda does not do that kind of thing. It must be something in the OS or hardware that's changing the setting. One possibility is that you are not using the correct tape device name. On many OS's, the name encodes the density and compression options. You might also look at the E-mail archives for Subject exb210 changer patch. That person had a similar problem with a different device. In general (if it's not a device name problem), I'd probably insert some kind of script call into your Amanda changer code (whatever you're using) to reset the options after a tape is loaded, or something along those lines. Keith John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] P.S. Please turn off send as HTML in your mailer. It's just a waste of bandwidth.
Re: amflush, chunks, cruft warnings
when running amflush on amanda dumps containing chunk files, can the warning messages about cruft files that correspond to chunks be ignored? Yes (as I recall). Or you can upgrade your server to 2.4.2p2 where the problem is fixed :-). are these chunks really being taped along with the rest of the dump, despite the warning message? Again, I think so, but if you're worried, do some cross-checks. The original amdump report told you how big the dump image was, and you can also du -sk the holding disk area. See if the amflush reports the same amount going to tape. The values should all be within a few KBytes. If they are off by your chunksize (or multiples there-of), well, then it's **really** time to upgrade :-). Todd Pfaff John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: dumps way too big
ns0 / lev 1 FAILED [dumps way too big, must skip incremental dumps] ... This does not really make sense to me bacause the majority of the systems have 6GB drives, and I have config'd amanda to use the two 35GB DLT drives. The b ackups that amanda did do total only about 3.5GB. ... What are some possibilities of misconfigurations to make this happen? Things to check: * What is the length value for your tapetype? * What is runtapes set to? * Find the DELAYING DUMPS IF NEEDED line in your amdump.NN file. It shows you how big the dump estimates were (total_size) as well as how much tape Amanda thought it had to work with (tape length). William John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amflush, chunks, cruft warnings
On Thu, 10 May 2001, John R. Jackson wrote: when running amflush on amanda dumps containing chunk files, can the warning messages about cruft files that correspond to chunks be ignored? Yes (as I recall). Or you can upgrade your server to 2.4.2p2 where the problem is fixed :-). are you sure it's fixed? the server i'm running amflush on is running amanda 2.4.2p2. and, yes, i know i'm running the amflush from the 2.4.2p2 installation (ie. 'which amflush' returns the expected path). -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: amflush, chunks, cruft warnings
are you sure it's fixed? ... H. I sure thought it was. Do you have one of those chunks still laying around? What does: dd if=the-chunk-file bs=32k count=1 have to say? Todd Pfaff John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
tar question
I'm using amanda 2.4.1p1 (the version included in Debian potato). Currently, the /home partition on our main user system is too large to back up fully (we have only a small tape drive). Rather than completely leave users out in the cold, I'd like to back up at least their mail, and probably web directories. So: /home/*/[M,m]ail /home/*/public_html I've been trying to do this with exclude lists, but I haven't hit the solution yet. This: [^*/public_html] at least, does not work. On that note, it is annoying that if I have an exclude file, say /etc/amanda/exclude.home, running amanda with that file produces different results than: tar cvf /dev/null /home -X /etc/amanda/exclude.home Why is this? Thanks for any help, -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
Re: Amanda Setup Guide Available
I've just released a fairly large guide to setting up an Amanda server on Linux, installing clients on Linux and Solaris, and restoring files. I hope it proves useful. I'm sure it will. Many thanks for your work and for making it available. -Robert Hoffman John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amflush, chunks, cruft warnings
On Thu, 10 May 2001, John R. Jackson wrote: are you sure it's fixed? ... H. I sure thought it was. Do you have one of those chunks still laying around? no, amflush removed them. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: tar question
... I'd like to back up at least their mail, and probably web directories. ... I've been trying to do this with exclude lists, but I haven't hit the solution yet. ... Wow! I wouldn't have had the guts to try this with exclude lists. They give me (real :-) headaches just trying to do normal things :-). Maybe you could do it with inclusion instead of exclusion? Take a look at: ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper.* During the pre_estimate you could run find to gather a list of what you want to back up, squirrel that away and then pass it to gtar for both the estimate and the real run. FYI, there is also an exclusion test script there: ftp://gandalf.cc.purdue.edu/pub/amanda/gtartest-exclude ... that might make figuring out the exclude list easier if you want to continue down that path. On that note, it is annoying that if I have an exclude file, say /etc/amanda/exclude.home, running amanda with that file produces different results than: tar cvf /dev/null /home -X /etc/amanda/exclude.home Why is this? What's different? I assume different files are listed/backed up? Who does more, Amanda or cvf? Is Amanda a subset of cvf, or are they all mixed up? Was Amanda doing a level 0? Are you sure you used the same tar that Amanda does (look at a /tmp/amanda/amandad*debug file for the tar path Amanda uses on that client). Amanda runs GNU tar in incremental backup mode. Take a look at a /tmp/amanda/sendbackup*debug file on the client to see the extra arguments involved. I would expect the lists to be the same if you do a full dump with Amanda (in which case the listed increment file will be empty) and with cvf, but otherwise all bets are off as it would also depend on what files had been modified. --Ray John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amflush, chunks, cruft warnings
no, amflush removed them. OK. If it happens again (look before you leap :-), try the dd. I've taken a note to try to reproduce this here as well. Todd Pfaff John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: tar question
On Thu, May 10, 2001 at 08:41:24PM -0400, Ray Shaw wrote: I'm using amanda 2.4.1p1 (the version included in Debian potato). Currently, the /home partition on our main user system is too large to back up fully (we have only a small tape drive). Rather than completely leave users out in the cold, I'd like to back up at least their mail, and probably web directories. So: /home/*/[M,m]ail /home/*/public_html I've been trying to do this with exclude lists, but I haven't hit the solution yet. This: [^*/public_html] at least, does not work. On that note, it is annoying that if I have an exclude file, say /etc/amanda/exclude.home, running amanda with that file produces different results than: tar cvf /dev/null /home -X /etc/amanda/exclude.home I don't think amanda tar's /home, I think it cd's to /home and tar's . (current dir). Thus your exclude file should be relative to ., not /home. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Help with Tapeless Configuration
Hello,
I'm new to Amanda and to this list... running Linux 2.4.3 on a Power PC.
While I'm waiting for the tape drive to arrive, I'm trying to build Amanda
to back up to a hard disk instead of tape. I read in the list archives to
get the amanda-242-tapeio CVS branch. Here's what I did to get that:
$cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/amanda login
Pressed enter.
$cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/amanda
checkout -r amanda-242-tapeio amanda
$cd amanda
$./autogen
The installation from there went just fine.
First, when Amanda runs, it reports itself as 2.4.2p1 and not p2. Is the
tapeio branch not in sync with the latest release?
Second, I'm having trouble configuring Amanda for the tapeless operation.
I'm just testing a local dump on the tape server itself. The only
documentation I could find was in amanda(8) about setting tapedev
file:/path/to/directory and creating a data directory in that folder.
I've done that, but what else to I need to set? Running amcheck complains:
file:/var/amandadumps: not an amanda tape
OK, so I read that Amanda tapes all need to be labeled, so I ran amlabel.
After that, it let me run amdump OK. But then I ran amdump again to try
another dump, but Amanda complained cannot overwrite active tape. How are
tapes ejected or rotated in the tapeless configuration? My goal is to
have a 14 day dumpcycle with 1 run per day, and have all of the files kept
under /var/amandadumps.
Here's what I've changed in amanda.conf. Everything else is the default:
tapedev file:/var/amandadumps
tapetype HARD-DISK
define tapetype HARD-DISK {
comment Hard disk instead of tape
length 4000 mbytes # Simulates end of tape on hard disk
filemark 100 kbytes # Is this needed for a hard disk?
speed 1000 kbytes# Local speed of the hard disk? Is this used?
}
define dumptype hard-disk-only {
global
comment Back up to hard disk instead of tape
holdingdisk no
index yes
priority high
}
Here's the disklist:
localhost /home hard-disk-only
One more question... when I tried to do a dump of /etc, I got the following:
? You can't update the dumpdates file when dumping a subdirectory
sendbackup: error [/sbin/dump returned 1]
What am I doing wrong? Thanks in advance for helping me get started.
Regards,
Clinton Hogge
Industrial Images
