auto-exclude mode ?
When using tar on different partitions, tar prunes the mounting points as we expect to. When we have big disks, we backup different directories defined in the disklist but if some directories are included in some other ones, data in subdirectories are backup twice if we do not build up an ad-hoc exclude list. This kind of exclude list is cumbersome and error prone... With an auto-exclude option, AMANDA could figure this up and exclude the subdirectories from the directories above. Does this make sense ? Any candidate in the audience to hack this up ? :-) Thank you ! -- Ronan KERYELL |\/ Tel:(+33|0) 2.29.00.14.15 Labo Informatique Télécom |/) Fax:(+33|0) 2.29.00.12.82 ENST Bretagne, CS 83818 KGSM:(+33|0) 6.13.14.37.66 F-29238 PLOUZANÉ CEDEX |\ E-mail: [EMAIL PROTECTED] FRANCE | \ http://www.lit.enstb.org/~keryell
Strange Dumps?
I am running Amanda versions 2.4.2p2 on a AIX 5.1 system. I have been getting these strange dump details, and would like To resolve these problems. The following information is provided. FAILED AND STRANGE DUMP DETAILS: /-- thunder /home lev 1 STRANGE sendbackup: start [thunder:/home level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Removing leading `./' from member names | Total bytes written: 16957440 (17MiB, 1.9MiB/s) sendbackup: size 16560 sendbackup: end \ /-- hail /home lev 4 STRANGE sendbackup: start [hail:/home level 4] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Removing leading `./' from member names | Total bytes written: 19957760 (20MiB, 610KiB/s) sendbackup: size 19490 sendbackup: end \ /-- thunder / lev 2 STRANGE sendbackup: start [thunder:/ level 2] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Removing leading `./' from member names | gtar: ./tmp/.s.PGSQL.5432: socket ignored Total bytes written: | 160993280 (154MiB, 5.9MiB/s) sendbackup: size 157220 sendbackup: end \ /-- hail / lev 1 STRANGE sendbackup: start [hail:/ level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Removing leading `./' from member names | gtar: ./dev/log: socket ignored | gtar: ./tmp/.s.PGSQL.5432: socket ignored | gtar: ./tmp/mysql.sock: socket ignored | gtar: ./var/run/fcron.fifo: socket ignored Total bytes written: | 393256960 (376MiB, 2.6MiB/s) sendbackup: size 384040 sendbackup: end Any help is would be greatly appreciated. Kevin D. Alford Sr. Systems Engineer TMC Technologies, Inc. (304)368-1862 Ext. 53
restore from multiple holding disk files
Hi folks, I'm trying to help someone do a restore from a dump that is split into multiple chunks in holding disk files. In this case, flushing to tape first is not an option. I thought amrestore could do it, but then I read the manpage and didn't see a way to do it. The only way that I could think of doing it is to use dd to strip the amanda header off the chunks and then concatenate them together into one, huge file. The filesystem on the holding disk is XFS so the filesize should not be a problem. Is there an easier way to do this? The files are ufsdump being restored to a Solaris machine, but the holding disk files are on a Linux box which does not support ufsrestore. Thanks, --jonathan
Dump Time Run Time ???
I am certain that this is a misunderstanding on my part ;
How can Dump Time be *GREATER THAN* Run Time?
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:17
Run Time (hrs:min) 9:40
Dump Time (hrs:min) 12:12 12:10 0:02
Clearly, this backup did *NOT* take anywhere near twelve (12) hours.
So, what is that Dump Time value?
What do you think?
P.S., Notice the Estimate Time (re: Speed up 400GB backup? thread).
This successful backup is for 65GB, across (17) DLE's, including a
Netware server over ncpfs, and a couple of windoze over samba.
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
Re: Dump Time Run Time ???
Michael D Schleif wrote:
I am certain that this is a misunderstanding on my part ;
How can Dump Time be *GREATER THAN* Run Time?
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:17
Run Time (hrs:min) 9:40
Dump Time (hrs:min) 12:12 12:10 0:02
Clearly, this backup did *NOT* take anywhere near twelve (12) hours.
So, what is that Dump Time value?
What do you think?
Time Management by Women, like Amanda: do many things at once.
If you have 12 machines, each dumping 1 hours 1 minutes, then
the total dump time is 12:12, isn't it?
From my weekly archive run:
Total Full Daily
Estimate Time (hrs:min)0:35
Run Time (hrs:min)13:21
Dump Time (hrs:min) 54:39 54:39 0:00
Output Size (meg) 104032.4 104032.40.0
Original Size (meg)218422.6 218422.60.0
Avg Compressed Size (%)47.6 47.6--
Filesystems Dumped 113113 0
Avg Dump Rate (k/s) 541.5 541.5--
The dumptime is the time needed when Amanda would run all dumps
sequentially. Amanda does things in parallel.
Run Time is the wall-clock time. The Estimate time is the
first part of this Run Time, when doing the estimates.
(Run Time also includes Tape Time, especially taping
the last image is not done in parallel with anything.)
P.S., Notice the Estimate Time (re: Speed up 400GB backup? thread).
This successful backup is for 65GB, across (17) DLE's, including a
Netware server over ncpfs, and a couple of windoze over samba.
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: restore from multiple holding disk files
Paul Bijnens wrote: If split in chunks, just feed the first part; the rest is done automatically (the name of the next part is in the header of each holding chunk). Hmm. That's what I thought, finding subsequent chunks might not be working correctly then for whatever reason, but I'll have to search for the e-mail from the person who was having the problem. --jonathan
Upgrading Amanda
I am looking for the procedures required to upgrade from 2.4.2p2 to 2.4.4p3. Your assistance in this matter is greatly appreciated. Kevin D. Alford Sr. Systems Engineer TMC Technologies, Inc. (304)368-1862 Ext. 53
tape changer status
hi, our backup didn't run the day before because our server crashed on that day. So last night when backup is running, it suppose to stored data in dailyset2, but it stored data in dailyset1 since it din't get run the day before and the file changer.stat say curslot 1 and curloaded 1. So tonight, it will store data in dailyset2, instead of dailyset3, I want to change the curslot to 2 and curloaded to 2, but the file changer.stat say DO NOT EDIT. What can I do so that backup is running in the right order, meaning running dailyset3 today, and dailyset4 tommorow, and soforth? Thanks
Re: Upgrading Amanda
On Friday 23 July 2004 13:19, Kevin D. Alford wrote: I am looking for the procedures required to upgrade from 2.4.2p2 to 2.4.4p3. Your assistance in this matter is greatly appreciated. Kevin D. Alford Sr. Systems Engineer TMC Technologies, Inc. (304)368-1862 Ext. 53 Kevin, can I asume you are running the rpms now? And that you have the -devel tools like gcc onboard? If so, rip them out with an rpm -e amanda*, and build it from scratch, unpacking the tarball as root, and then doing a chown -R amanda:disk amanda-version-number, then copying this script into that diirectory, setting its perms and ownership as above, then using this script (with suitable mods of course) invoked as ./gh.cf. Or you could call a shell to run it also. -- #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda make You will need a user named 'amanda' who is a member of group 'disk', or to modify those statements above to fit your situation. If you don't use a tape changer, remove that line, and of course fix the --with-tape-server= line to reflect the FQDN of the machine that houses the drive. If your current config dir isn't there, make that line match your environment. Once this script has run and made amanda, then become root, enter the dir again, and do a make install. (or one could install it with checkinstall, which makes an rpm out of it, and then installs the rpm) Your current crontab entries and such should remain functional, but you may want to look at the sample amanda.conf in the src tree for new features you may want to use. I hope this helps. -- Cheers, Gene There are 4 boxes to be used in defense of liberty. Soap, ballot, jury, and ammo. Please use in that order, starting now. -Ed Howdershelt, Author Additions to this message made by Gene Heskett are Copyright 2004, Maurice E. Heskett, all rights reserved.
Re: Upgrading Amanda
Kevin D. Alford wrote: I am looking for the procedures required to upgrade from 2.4.2p2 to 2.4.4p3. Your assistance in this matter is greatly appreciated. The versions are compatibel. You may upgrade the server and/or clients in a phased rollout if you like. First choose a less important client, compile and install on that one. A few days later, do the other clients, and then some days later the server. If you have trouble compiling for some strange clients (e.g. lack of a decent compiler) you are not obliged to upgrade that one. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: tape changer status
Nina Pham wrote: hi, our backup didn't run the day before because our server crashed on that day. So last night when backup is running, it suppose to stored data in dailyset2, but it stored data in dailyset1 since it din't get run the day before and the file changer.stat say curslot 1 and curloaded 1. So tonight, it will store data in dailyset2, instead of dailyset3, I want to change the curslot to 2 and curloaded to 2, but the file changer.stat say DO NOT EDIT. What can I do so that backup is running in the right order, meaning running dailyset3 today, and dailyset4 tommorow, and soforth? amtape config slot prev But I don't think that's needed. What does amcheck say? Will it really skip dailyset2? If yes, then you probably have your tapecycle not correct. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: restore from multiple holding disk files
Jonathan Dill wrote: Paul Bijnens wrote: If split in chunks, just feed the first part; the rest is done automatically (the name of the next part is in the header of each holding chunk). Hmm. That's what I thought, finding subsequent chunks might not be working correctly then for whatever reason, but I'll have to search for the e-mail from the person who was having the problem. Yes, the absolute pathname of the nextchunk is found in the header of each holdingdisk file. That is needed, befause amanda can spread chunks over different holdingdisks. But holdingdisk is meant as a temporary staging area not as the ultimate format. The virtual tapes are meant for that. That means indeed that you cannot easily move holdingdisk files around e.g. burn them on CD etc. For easy restoring you need to put them on the exact location as where they were created. Otherwise, you'll have to fall back to little programs with dd bs=32k skip=1 ... etc. -- 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 * ***
ideal amanda.conf configuration
Dear friends, I'm have dificulties for create and manager back-up with amanda server. My problems: I not get ideal configuration for running back-up. My scenary: 1. Back-up server machine running GNU/Linux kerner 2.4 and file system type ext3. Tape device is SONY and model: SDT-2000E, with tapes of the 2GB uncompressed (single slot). 2. Is necessary running back-up 3 every time this week and incluind rotine of the back-up 3 servers. 3. The volum total of the files is approximate 22Gb. Someone have ideas of the create a amanda.conf file? Thank's a lot. Best regards. P.S.: Please, sorry my bad english... []'s -- Sergio A Lima Jr [EMAIL PROTECTED]
