Re: emailing the correct report.
Gene Heskett wrote: On Tuesday 16 March 2004 16:46, jlm17 wrote: I have a question about the name of the log file generated by amdump. So the format is log.date.number, where number starts at 0. If I run two amdumps in one day, would log.date.0 be the log file for the first amdump to start, or the first amdump to finish? ... Amdump will mail you a report if properly configured, why not use that one? You took the words right out of my mouth :-) But if you want to do something else with the log file, like feeding it to amtoc, then you do need to know which log file is the good one. My cron executes following script each night. It runs amtoc on the right logfile, and ejects from my chg-multi drives with 2 tapes the tapes that were written. (change the pathnames in the script!) ---cut--- #!/bin/sh CONFIG=$1 /opt/local/sbin/amdump $CONFIG LOGF=`ls -t /var/opt/amanda/$CONFIG/log.2* | head -1` /opt/local/sbin/amtoc -a -t $LOGF grep '^START taper .* label ' $LOGF | while read line do /opt/local/sbin/amtape $CONFIG eject /opt/local/sbin/amtape $CONFIG slot prev done ---cut--- -- 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 * ***
excluding while backing up Windows box
I am using Amanda over a SAMBA share to backup the harddrive on a windows
box. The disklist file looks like:
localhost //sun/C$ {
global
exclude file append "./pagefile.sys"
} -1 eth0
I tried placing more 'exclude' statements but got errors - it seems only one
is allowed when using SAMBA. In the final logs I get many errors:
? NT_STATUS_ACCESS_DENIED opening remote file \Documents and Settings\All
Users\Application Data\Microsoft\Dr Watson\user.dmp (\Documents and
Settings\All Users\Application Data\Microsoft\Dr Watson\)
? NT_STATUS_SHARING_VIOLATION opening remote file \Documents and
Settings\bclery\Local Settings\Application
Data\Microsoft\Windows\UsrClass.dat (\Documents and Settings\bclery\Local
Settings\Application Data\Microsoft\Window
Most of these are things I don't care to back up anyway. Is there a way
designate a backup of the whole harddrive ( //sun/C$ ) and exclude a long
list of don't-care subdirectories like:
exclude "\Documents and Settings\bclery\Local Settings\Application
Data\Microsoft\Windows"
exclude "\Documents and Settings\All Users\Application Data\Microsoft\Dr
Watson"
Bill
amdump problem
Hi All, I'm new to amanda, this is my first install. I've created amanda.conf and disklist files by the manuals in /etc/amanda/mydump. Disklist contains the following line: mymachine /var/www always-full When I run # su backup -c "/usr/sbin/amlabel mydump mylabel" everything is OK. Then I run # su backup -c "/usr/sbin/amdump mydump" and I get a mail within a few seconds with this content: *** A TAPE ERROR OCCURRED: [cannot overwrite active tape mylabel]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: a new tape. FAILURE AND STRANGE DUMP SUMMARY: mymachine /var/www lev 0 FAILED [disk /var/www, all estimate failed] . . . NOTES: planner: tapecycle (8) <= runspercycle (49) planner: Adding new disk mymachine:/var/www. driver: WARNING: got empty schedule from planner I'm using debian sarge + amanda 2.4.4p2. What can be the problem? Thanks, Filburt
Re: emailing the correct report.
On Wednesday 17 March 2004 03:24, Paul Bijnens wrote: >Gene Heskett wrote: >> On Tuesday 16 March 2004 16:46, jlm17 wrote: >>>I have a question about the name of the log file generated by >>>amdump. So the format is log.date.number, where number starts at >>> 0. If I run two amdumps in one day, would log.date.0 be the log >>> file for the first amdump to start, or the first amdump to >>> finish? > >... > >> Amdump will mail you a report if properly configured, why not use >> that one? > >You took the words right out of my mouth :-) > >But if you want to do something else with the log file, like feeding >it to amtoc, then you do need to know which log file is the good > one. My cron executes following script each night. It runs amtoc > on the right logfile, and ejects from my chg-multi drives with 2 > tapes the tapes that were written. (change the pathnames in the > script!) > >---cut--- >#!/bin/sh > >CONFIG=$1 > >/opt/local/sbin/amdump $CONFIG >LOGF=`ls -t /var/opt/amanda/$CONFIG/log.2* | head -1` >/opt/local/sbin/amtoc -a -t $LOGF > >grep '^START taper .* label ' $LOGF | >while read line >do > /opt/local/sbin/amtape $CONFIG eject > /opt/local/sbin/amtape $CONFIG slot prev >done >---cut--- What can I say, thats neat. Mine of course cannot eject the used tapes by any method except handling the magazine. -- 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.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: excluding while backing up Windows box
On Wed, 17 Mar 2004 at 7:50am, Bill Clery wrote > Most of these are things I don't care to back up anyway. Is there a way > designate a backup of the whole harddrive ( //sun/C$ ) and exclude a long > list of don't-care subdirectories like: > No. From docs/SAMBA: Smbclient only supports excluding a single file from the command line, not a file of patterns like GNU tar. So "exclude" is supported from a dumptype but not "exclude list". If you need multiple excludes, you may want to try to get amanda working under cygwin on the 'doze box itself. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amdump problem
Filburt wrote: NOTES: planner: tapecycle (8) <= runspercycle (49) At least one error: you cannot have tapecycle less than runspercycle. (you probably have "runpercycle 7 weeks" -- drop the "weeks" unit). In your description you the exact error messages, I guess. Or is your tape indeed labeled "mylabel"? Post exact error messages, then we'll be much better able to guess what's wrong. -- 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: scsi-changer debugging...
Hi Christoph, Joshua et al,... On Sat, 13 Mar 2004 08:36:33 +0100 Christoph Scheeder <[EMAIL PROTECTED]> wrote: > seems like chg-scsi does not know your changer/tape at the moment, > and as a result can't handle the messages it get's back from it. > if you have a little experience with programming, have a > descrition of the sense-codes your changer generates and a little > bit time left, you can take a look at chg-scsi.c/h in the sources > of amanda. There are some tables defining the sensecodes returned Thanks to the both of your for your hints; much appreciated (as always; I've seen way too much friendly helping on this list by now - thanks everyone!). So, situation is as follows: I temporarily switched my configuration to use chg-zd-mtx, yesterday, and it seems to just work. Good, so far. About the chg-scsi - situation: I'll check whether I can find sensecodes for that machine and try to get them into the chg-scsi source as soon as I've got some spare minutes to do that, would be glad to do a (though damn small) contribution to this fine piece of work. Cheers and thanks, Kris -- Kristian Rink -- Programmierung/Systembetreuung planConnect GmbH * Strehlener Str. 12 - 14 * 01069 Dresden 0176 24472771 * [EMAIL PROTECTED]
Windows via samba tips?
Along with several Linux boxes, I have one Windows NT 4 server which I'm using amanda to back up using tar over samba. The DLEs, in case anyone's curious, are simply: peterbilt //server/e$ comp-high-tar peterbilt //server/f$ comp-high-tar (peterbilt is the tapehost, and, yes, some unimaginative soul actually did name the NT box "server" before I got here.) For whatever reason, these two DLEs come up strange pretty regularly, maybe 70-80% of the time, and occasionally fail. I do keep 3 weeks of tape, so I always have at least _a_ backup of each, but it would be nice to reliably get them every night. What can I do to get them to start behaving properly? The failed/strange dump reports tend to be extremely long, but here's one of the shorter ones as an example: /-- peterbilt //server/f$ lev 1 STRANGE sendbackup: start [peterbilt://server/f$ level 1] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | added interface ip=192.168.23.31 bcast=192.168.23.255 nmask=255.255.255.0 | directory \LM600\ ? Expected SMBtrans2 response, got command 0x2d ? ERRDOS - ERRbadfid opening remote file \LM600\C5clax.dll (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\C5dosx.dll (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\C5tpsx.dll (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\CLOCKINI.BAK (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\CW2DOS16.DLL (\LM600\) | directory \LM600\data\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \LM600\data\* | directory \LM600\Doc\ ? Expected SMBtrans2 response, got command 0x04 ? code 0 listing \LM600\Doc\* ? ERRDOS - ERRbadfid opening remote file \LM600\DOWNLOAD.PIF (\LM600\) ? ERRDOS - ERRbadfid opening remote file \LM600\Flash.TPS (\LM600\) | directory \msdownld.tmp\ ? Expected SMBtrans2 response, got command 0x04 ? code 0 listing \msdownld.tmp\* | directory \Project 130 D Line\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \Project 130 D Line\* | directory \RECYCLER\ | directory \TEMP\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \TEMP\* ? ERRSRV - ERRerror opening remote file \test.iso (\) | directory \trudy.000\ | directory \trudy.000\AAL 130D\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \trudy.000\AAL 130D\* ? ERRDOS - ERRbadfile opening remote file \trudy.000\Bearing 130 D.xls (\trudy.000\) ? ERRDOS - ERRbadfile opening remote file \trudy.000\SRE Housing 130 D.xls (\trudy.000\) | directory \vnc_x86_win32\ ? Expected SMBtrans2 response, got command 0x2d ? ERRDOS - ERRbadfile listing \vnc_x86_win32\* ? ERRDOS - ERRbadfile opening remote file \west6.3.zip (\) ? ERRDOS - ERRbadfile opening remote file \Westling053001.zip (\) | directory \Work Instructions\ | directory \Work Instructions\vncviewer\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \Work Instructions\vncviewer\* | directory \Work Instructions\winvnc\ ? Expected SMBtrans2 response, got command 0x2d ? code 0 listing \Work Instructions\winvnc\* | tar: dumped 396 files and directories | Total bytes written: 311787008 sendbackup: size 304480 sendbackup: end \
Re: amdump problem
Hi Bill, > just an idea: make sure there is not bad stuff from previous > tests in the tapelist file. this is in tapelist: 20040317 mylabel reuse amclean says: # su backup -c "/usr/sbin/amcleanup mydump" amcleanup: no unprocessed logfile to clean up. Scanning /var/spool/amanda... it doesn't help... B-(
Firewall and Portrange Settings
I'm using amanda to back up about Linux 10 machines, some through a firewall. I'm looking at making the "holes" I've got punched in the firewall a little smaller and two questions arise: 1) It seems that the --with-tcpportrange and --with-udpportrange options designed to make usage through a firewall easier are strictly compile-time options. Wouldn't these be more appropriate as run-time options, perhaps in amanda.conf? I'm using pre-packaged builds for several different flavors of Linux and I'd rather not have to compile/maintain a bunch of different executables if I can avoid it. 2) Is there some way to get a pre-compiled version of amanda to tell me what portrange settings it was compiled with? I know I can observe the sessions on the wire and figure it out that way, but I'm hoping there is an easier way. Thanks.
RE: amdump problem
Paul wrote: > At least one error: you cannot have tapecycle less than > runspercycle. (you probably have "runpercycle 7 weeks" > -- drop the "weeks" unit). I tried it with 'dumpcycle 1' (it means full dump every day as I read) but the problem is the same. > Or is your tape indeed labeled "mylabel"? No, it's a word in Hungarian (without language specific characters). I just wrote 'mylabel' for you. B-) > Post exact error messages The rest is about some statistics (run time, dump time, output size, etc). There's nothing more about the tape or the label.
Re: amdump problem
--On Wednesday, March 17, 2004 14:51:41 +0100 Filburt <[EMAIL PROTECTED]> wrote: > Hi Bill, > > > just an idea: make sure there is not bad stuff from previous > > tests in the tapelist file. > > this is in tapelist: > > 20040317 mylabel reuse > > amclean says: > ># su backup -c "/usr/sbin/amcleanup mydump" > amcleanup: no unprocessed logfile to clean up. > Scanning /var/spool/amanda... > > it doesn't help... B-( > You do realize that each tape needs a unique label (that matches the labelstr regular expression), and that Amanda won't reuse a tape until after it has used all tapecycle of them? Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Firewall and Portrange Settings
On Wed, 17 Mar 2004 at 10:47am, Barry A. Trent wrote > I'm using amanda to back up about Linux 10 machines, some through a > firewall. I'm looking at making the "holes" I've got punched in the > firewall a little smaller and two questions arise: > > 1) It seems that the --with-tcpportrange and --with-udpportrange > options designed to make usage through a firewall easier are strictly > compile-time options. Wouldn't these be more appropriate as run-time > options, perhaps in amanda.conf? I'm using pre-packaged builds for Yes they would -- patches accepted. :) If you look through the list archives, you'll find that there is agreement that there is a bunch of stuff decided at compile time that shouldn't be, but that it's not really all that easy to fix and there's more pressing development issues. > several different flavors of Linux and I'd rather not have to > compile/maintain a bunch of different executables if I can avoid it. A lot of us find it rather easy to admin amanda this way with scripts to ease compilation. > 2) Is there some way to get a pre-compiled version of amanda to tell > me what portrange settings it was compiled with? I know I can observe > the sessions on the wire and figure it out that way, but I'm hoping > there is an easier way. If you look in /tmp/amanda/amandad*debug, recent versions will tell you the compile time options. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Firewall and Portrange Settings
--On Wednesday, March 17, 2004 10:47:25 -0600 "Barry A. Trent" <[EMAIL PROTECTED]> wrote: > I'm using amanda to back up about Linux 10 machines, some through a > firewall. I'm looking at making the "holes" I've got punched in the > firewall a little smaller and two questions arise: > > 1) It seems that the --with-tcpportrange and --with-udpportrange > options designed to make usage through a firewall easier are strictly > compile-time options. Wouldn't these be more appropriate as run-time > options, perhaps in amanda.conf? I'm using pre-packaged builds for > several different flavors of Linux and I'd rather not have to > compile/maintain a bunch of different executables if I can avoid it. Iptables firewalls on a newer kernel has Amanda support built in, otherwise you either need gaping holes in the firewall or need to compile with the portrange options. I agree that it should be a conf file setting, but its not. > 2) Is there some way to get a pre-compiled version of amanda to tell > me what portrange settings it was compiled with? I know I can observe > the sessions on the wire and figure it out that way, but I'm hoping > there is an easier way. I would bet that all the packaged versions are using the default 'use almost any port' method documented in docs/PORTS.USAGE. Frank > > Thanks. > > -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
amrestore fails
Hi, I get the following error while running amrestore after amdump and amflush are doing their jobs without any errors: I'm running amrecover from the amanda-server machine to avoid possible filters: [EMAIL PROTECTED] amanda]# amrecover -s 192.168.154.21 -t 192.168.154.21 -d /dev/nst0 AMRECOVER Version 2.4.4p2. Contacting server on 192.168.154.21 ... 220 amanda AMANDA index server (2.4.4p2) ready. 200 Access OK Setting restore date to today (2004-03-17) 200 Working date set to 2004-03-17. Scanning /var/tmp... 20040316: found Amanda directory. 200 Config set to DailySet1. 501 Host amanda is not in your disklist. Trying host localhost.localdomain ... 501 Host localhost.localdomain is not in your disklist. Trying host localhost ... 501 Host localhost is not in your disklist. Trying host amanda ... 501 Host amanda is not in your disklist. amrecover> sethost iulian 200 Dump host set to iulian. amrecover> setdisk / 200 Disk set to /. amrecover> cd /var/www/html/usage /var/www/html/usage amrecover> ls 2004-03-17 . 2004-03-17 msfree.png 2004-03-17 webalizer.png amrecover> add msfree.png Added /var/www/html/usage/msfree.png amrecover> extract Extracting files using tape drive /dev/nst0 on host 192.168.154.21. The following tapes are needed: DailySet1-6 Restoring files into directory /tmp/amanda Continue [?/Y/n]? y Extracting files using tape drive /dev/nst0 on host 192.168.154.21. Load tape DailySet1-6 now Continue [?/Y/n/s/t]? y EOF, check amidxtaped..debug file on 192.168.154.21. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n/r]? y amrecover> exit 200 Good bye. My debug file looks like: [EMAIL PROTECTED] amanda]# cat amidxtaped.20040317173814.debug amidxtaped: debug 1 pid 30897 ruid 33 euid 33: start at Wed Mar 17 17:38:14 2004 amidxtaped: version 2.4.4p2 amidxtaped: time 0.000: > SECURITY USER root amidxtaped: time 0.002: bsd security: remote host pluto.d1.net-m.de user root local user amanda amidxtaped: time 0.003: amandahosts security check passed amidxtaped: time 0.003: > CONFIG=DailySet1 amidxtaped: time 0.003: > LABEL=DailySet1-6 amidxtaped: time 0.003: > FSF=1 amidxtaped: time 0.003: > HEADER amidxtaped: time 0.003: > DEVICE=/dev/nst0 amidxtaped: time 0.003: > HOST=^iulian$ amidxtaped: time 0.003: > DISK=^/$ amidxtaped: time 0.003: > DATESTAMP=20040317 amidxtaped: time 0.003: > END amidxtaped: time 0.006: amrestore_nargs=0 amidxtaped: time 0.006: Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = "amrestore" argv[1] = "-p" argv[2] = "-h" argv[3] = "/dev/nst0" argv[4] = "^iulian$" argv[5] = "^/$" argv[6] = "20040317" amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information amidxtaped: time 0.017: amrestore terminated normally with status: 1 amidxtaped: time 0.017: rewinding tape ... amidxtaped: time 2.457: done amidxtaped: time 2.457: pid 30897 finish time Wed Mar 17 17:38:16 2004 So no error. My amrecover debug file says to following: cd_glob (/var/www/html/usage) -> ^/var/www/html/usage$ add_dir_list_item: Adding "2004-03-17" "0" "DailySet1-6" "1" "/var/www/html/usage/." add_dir_list_item: Adding "2004-03-17" "0" "DailySet1-6" "1" "/var/www/html/usage/msfree.png" add_dir_list_item: Adding "2004-03-17" "0" "DailySet1-6" "1" "/var/www/html/usage/webalizer.png" add_glob (msfree.png) -> ^msfree\.png$ add_file: Looking for "msfree\.png[/]*$" add_file: Converted path="msfree\.png[/]*$" to path_on_disk="\/var\/www\/html\/usage/msfree\.png[/]*$" add_file: Pondering ditem->path="/var/www/html/usage/." add_file: Pondering ditem->path="/var/www/html/usage/msfree.png" add_file: (Successful) Added /var/www/html/usage/msfree.png add_file: Pondering ditem->path="/var/www/html/usage/webalizer.png" amrecover: stream_client_privileged: connected to 192.168.154.21.10083 amrecover: stream_client_privileged: our side is 0.0.0.0.923 amrecover: try_socksize: receive buffer size is 65536 amrecover: Can't read file header amrecover: pid 30896 finish time Wed Mar 17 17:38:16 2004 amrecover: pid 30885 finish time Wed Mar 17 17:38:24 2004 The thing is, if I'm running: [EMAIL PROTECTED] amanda]# amrestore /dev/nst0 ^iulian$ ^/$ 20040317 The dumpfile is restored corectly on the amanda-server machine. What should I look for? Thanks for your support. Regards, Iulian Topliceanu
Re: amdump problem
Filburt wrote: this is in tapelist: 20040317 mylabel reuse Is this the exact content of the file: 1 line? You said "tapecycle 8" in a previous mail. Then your tape labelled "mylabel" has indeed been used. Amanda will not overwrite it until "tapecycle" tapes have been given. And they all need to have a different label. -- 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: amrestore fails
Iulian Topliceanu wrote: argv[0] = "amrestore" argv[1] = "-p" argv[2] = "-h" argv[3] = "/dev/nst0" argv[4] = "^iulian$" argv[5] = "^/$" argv[6] = "20040317" amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information Your tape was not rewound. Either, manually rewind the tape and (to speed up) optionally position manually with "mt fsf" to just before the image you need. Or better, add these parameters to amanda.conf: amrecover_do_fsf on amrecover_check_label on (available since 2.4.3 I believe), and then amanda does this for you. The thing is, if I'm running: [EMAIL PROTECTED] amanda]# amrestore /dev/nst0 ^iulian$ ^/$ 20040317 The dumpfile is restored corectly on the amanda-server machine. Probably after you (accidently?) rewound the tape. -- 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 dumpcicle
Hi list, I'm trying to setup amanda to backup 52 weeks with incremental daily and every week a full backup. My amanda.conf shows like: dumpcycle 7 runspercycle 5 tapecycle 55 tapes for sure I'm doing something wrong .. what is it? when I run amadmin to check the due date for each disk I get: Due in 367 days: backupserver:/etc Due in 361 days: backupserver:/var Due in 362 days: backupserver:/home question: how do I modify my amanda.conf to meet my 52 weeks configuration? thx all, sergio --
Re: ideal dumpcicle
--On Friday, March 21, 2003 13:13:06 -0500 Sergio Pereira <[EMAIL PROTECTED]> wrote: > Hi list, > > I'm trying to setup amanda to backup 52 weeks with incremental daily and > every week a full backup. My amanda.conf shows like: > > dumpcycle 7 > runspercycle 5 > tapecycle 55 tapes > > for sure I'm doing something wrong .. what is it? > when I run amadmin to check the due date for each disk I get: > > Due in 367 days: backupserver:/etc > Due in 361 days: backupserver:/var > Due in 362 days: backupserver:/home > > question: how do I modify my amanda.conf to meet my 52 weeks > configuration? To have a years worth of backups, you would need a tapecycle of at least 5 * 52 = 260 tapes. Maybe you need two separate configs, one always-full running weekly with a tapecycle of at least 52 tapes, and one running daily with at least 5 tapes (using your runspercycle). Frank > > thx all, > > sergio > > > -- -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Firewall and Portrange Settings
> Iptables firewalls on a newer kernel has Amanda support built in, > otherwise you either need gaping holes in the firewall or need to > compile with the portrange options. I agree that it should be a > conf file setting, but its not. How new a kernel are we talking about? Is there specific support for Amanda, or are you just referring to the "stateful packet inspection" features of iptables?
Re: Firewall and Portrange Settings
--On Wednesday, March 17, 2004 13:12:19 -0600 "Barry A. Trent" <[EMAIL PROTECTED]> wrote: >> Iptables firewalls on a newer kernel has Amanda support built in, >> otherwise you either need gaping holes in the firewall or need to >> compile with the portrange options. I agree that it should be a >> conf file setting, but its not. > > How new a kernel are we talking about? Is there specific support for > Amanda, or are you just referring to the "stateful packet inspection" > features of iptables? I don't recall when it was added in, perhaps it wasn't until the 2.5 series. Device drivers -> Networking support -> Networking options -> network packet filtering (replaces ipchains) -> IP: netfilter configuration -> Connection tracking -> Amanda backup protocol support CONFIG_IP_NF_AMANDA=y is the actual .config line I believe it considers replies from the clients as 'related established' packets, just like it does with FTP data port connctions. All that said, I haven't actually used it, since I had already started configuring and compiling Amanda with the portrange options, but supposedly it does work. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: ideal dumpcicle
ok. but doesn't amanda get confuse with two configs? sergio On Wed, 2004-03-17 at 13:32, Frank Smith wrote: > --On Friday, March 21, 2003 13:13:06 -0500 Sergio Pereira <[EMAIL PROTECTED]> wrote: > > > Hi list, > > > > I'm trying to setup amanda to backup 52 weeks with incremental daily and > > every week a full backup. My amanda.conf shows like: > > > > dumpcycle 7 > > runspercycle 5 > > tapecycle 55 tapes > > > > for sure I'm doing something wrong .. what is it? > > when I run amadmin to check the due date for each disk I get: > > > > Due in 367 days: backupserver:/etc > > Due in 361 days: backupserver:/var > > Due in 362 days: backupserver:/home > > > > question: how do I modify my amanda.conf to meet my 52 weeks > > configuration? > > To have a years worth of backups, you would need a tapecycle of > at least 5 * 52 = 260 tapes. > > Maybe you need two separate configs, one always-full running weekly > with a tapecycle of at least 52 tapes, and one running daily with > at least 5 tapes (using your runspercycle). > > Frank > > > > > thx all, > > > > sergio > > > > > > -- --
Re: ideal dumpcicle
On Fri, Mar 21, 2003 at 03:42:02PM -0500, Sergio Pereira wrote: > ok. but doesn't amanda get confuse with two configs? Not if one of them (the weekly always-full) has the no-record option set.
Re: ideal dumpcicle
Sergio, No. Call amdump with an argument of the config. Drew On Fri, 2003-03-21 at 15:42, Sergio Pereira wrote: > ok. but doesn't amanda get confuse with two configs? > > sergio > > On Wed, 2004-03-17 at 13:32, Frank Smith wrote: > > --On Friday, March 21, 2003 13:13:06 -0500 Sergio Pereira <[EMAIL PROTECTED]> > > wrote: > > > > > Hi list, > > > > > > I'm trying to setup amanda to backup 52 weeks with incremental daily and > > > every week a full backup. My amanda.conf shows like: > > > > > > dumpcycle 7 > > > runspercycle 5 > > > tapecycle 55 tapes > > > > > > for sure I'm doing something wrong .. what is it? > > > when I run amadmin to check the due date for each disk I get: > > > > > > Due in 367 days: backupserver:/etc > > > Due in 361 days: backupserver:/var > > > Due in 362 days: backupserver:/home > > > > > > question: how do I modify my amanda.conf to meet my 52 weeks > > > configuration? > > > > To have a years worth of backups, you would need a tapecycle of > > at least 5 * 52 = 260 tapes. > > > > Maybe you need two separate configs, one always-full running weekly > > with a tapecycle of at least 52 tapes, and one running daily with > > at least 5 tapes (using your runspercycle). > > > > Frank > > > > > > > > thx all, > > > > > > sergio > > > > > > > > > --
Re: Windows via samba tips?
Hi, Dave, on Mittwoch, 17. März 2004 at 16:51 you wrote to amanda-users: DS> Along with several Linux boxes, I have one Windows NT 4 server which DS> I'm using amanda to back up using tar over samba. [..] DS> The failed/strange dump reports tend to be extremely long, but here's DS> one of the shorter ones as an example: DS> /-- peterbilt //server/f$ lev 1 STRANGE DS> sendbackup: start [peterbilt://server/f$ level 1] DS> sendbackup: info BACKUP=/usr/bin/smbclient DS> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... - DS> sendbackup: info COMPRESS_SUFFIX=.gz DS> sendbackup: info end DS> | added interface ip=192.168.23.31 bcast=192.168.23.255 nmask=255.255.255.0 DS> | directory \LM600\ DS> ? Expected SMBtrans2 response, got command 0x2d DS> ? ERRDOS - ERRbadfid opening remote file \LM600\C5clax.dll (\LM600\) DS> ? ERRDOS - ERRbadfid opening remote file \LM600\C5dosx.dll (\LM600\) This sounds somewhat familiar to me. I have to say first that I don't have the solution, but maybe we can add another piece to the whole picture ... Please let me know, what Samba-release you use. I bet it is > 2.2.x -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
flush full dumps only?
Has anyone tried the approach of only flushing full dumps and leaving incremental dumps on disk? I think that this would have roughly the same effect as doing full dumps out of cycle, but I have not had luck so far with the out-of-cycle approach. I think that it should be fairly easy to script, create a parallel directory tree and temporarily move out the incremental dumps that you don't want to flush, for example. The idea would be to leave all of the incremental dumps available on a huge disk, but keep all of the full dumps on tape, so at most one tape should be required for any restore. Since the full dumps take up the most space, clearing them out should leave more space for a longer history of incrementals. At least that is the idea. --jonathan
Re: excluding while backing up Windows box
JBL> On Wed, 17 Mar 2004 at 7:50am, Bill Clery wrote >> Most of these are things I don't care to back up anyway. Is there a way >> designate a backup of the whole harddrive ( //sun/C$ ) and exclude a long >> list of don't-care subdirectories like: Then Joshua wrote: JBL> No. From docs/SAMBA: JBL> Smbclient only supports excluding a single file from the command line, JBL> not a file of patterns like GNU tar. So "exclude" is supported from a JBL> dumptype but not "exclude list". JBL> If you need multiple excludes, you may want to try to get amanda working JBL> under cygwin on the 'doze box itself. Someone has compared this approach to installing Windows on your Unix-box to backup the files on it ... This is still one of the major disadvantages in using Samba with AMANDA. (There seem to be loads of files on a MS-box that noone wants to back up.) The main obstacle in the current way of doing things is the lack of support for multiple excludes in the smbclient-binary, that is used by AMANDA to dump Windows-shares. I have repeatedly (is that english really ...?) posted questions about this on the samba-list without replies. I will put this on my todo-list and contact one of the Samba-developers, as I am in loose contact with at least one of them. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: excluding while backing up Windows box
On Wed, Mar 17, 2004 at 10:09:18PM +0100, Stefan G. Weichinger wrote: >I have repeatedly (is that english really ...?) posted questions about >this on the samba-list without replies. Yes, "repeatedly" is a perfectly good English word, and you used it in an appropriate context. :-} [The language is a little too flexible for its own good sometimes -- to say nothing of the "good" of those who use it. I am reminded of Victor Borge's line: "It's *your* language; I'm just trying to *use* it!"] Peace, david -- David H. Wolfskill [EMAIL PROTECTED]
Re: Firewall and Portrange Settings
Hi, Joshua, on Mittwoch, 17. März 2004 at 18:01 you wrote to amanda-users: JBL> On Wed, 17 Mar 2004 at 10:47am, Barry A. Trent wrote >> Wouldn't these be more appropriate as run-time >> options, perhaps in amanda.conf? I'm using pre-packaged builds for JBL> Yes they would -- patches accepted. :) If you look through the list JBL> archives, you'll find that there is agreement that there is a bunch of JBL> stuff decided at compile time that shouldn't be, but that it's not really JBL> all that easy to fix and there's more pressing development issues. >> several different flavors of Linux and I'd rather not have to >> compile/maintain a bunch of different executables if I can avoid it. JBL> A lot of us find it rather easy to admin amanda this way with scripts to JBL> ease compilation. >> 2) Is there some way to get a pre-compiled version of amanda to tell >> me what portrange settings it was compiled with? I know I can observe >> the sessions on the wire and figure it out that way, but I'm hoping >> there is an easier way. JBL> If you look in /tmp/amanda/amandad*debug, recent versions will tell you JBL> the compile time options. I know that I am talking from my subjective point of view, but I am still trying to think objectively: It is not that difficult to maintain AMANDA by compiling it from the sources. If you have once defined your configure-options and put it into a shell-script, upgrading to a new release is no more than # cd ; my-config.sh; make # cd ; make uninstall # cd ; make install As new releases or even snapshots of AMANDA compile clean on most platforms (thanks to the maintainers), there is no more effort needed. I do this all the time since I-don't-know-when and I don't see the advantage of applying rpms, that have been pre-compiled by some distro-maintainer, whose job is to stay "compatible". (You ask how to figure out which portrange settings a precompiled version uses. Why not put less energy into setting them yourself?) --- By compiling your own binaries you get the freedom to choose YOUR own setup, to set YOUR firewall-settings, to assure that YOUR version of AMANDA does exactly the job you want it to. And it stays YOUR setup with each new release of AMANDA. All this with a small shell-script. I think this is worth the effort of figuring out the configure-options. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: excluding while backing up Windows box
Hi, David, on Mittwoch, 17. März 2004 at 22:19 you wrote to amanda-users: DW> On Wed, Mar 17, 2004 at 10:09:18PM +0100, Stefan G. Weichinger wrote: >>I have repeatedly (is that english really ...?) posted questions about >>this on the samba-list without replies. DW> Yes, "repeatedly" is a perfectly good English word, and you used it in DW> an appropriate context. :-} Thanks a lot. As you may have guessed already, my mother-tongue is NOT english, otherwise I would not have asked ... If I am a bit tired, as I am right now after a long and exhausting day, I am not so sure anymore about english grammar. DW> [The language is a little too flexible for its own good sometimes -- to DW> say nothing of the "good" of those who use it. I am reminded of Victor DW> Borge's line: "It's *your* language; I'm just trying to *use* it!"] This describes my usage of the english language pretty well (at least in the context of mailing-lists ... ). Thanks for the philosophical (doubts again ...) quote, maybe I come back with another ... ;-) -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
build - gtar
IRIX 6.5.19 Amanda 2.4.2p2 I've installed gtar on a new amanda-server, a system that was never a client nor a server before. Currently its only client is itself. This server mounts /usr/local from another system (another IRIX system). gtar you ask ? .866 TBytes disk, xfsdump will not produce an output file that would untimately fit on the output tape (read Jukebox for 8 tapes with a single Quantum SDLT 320 drive, mtx is in play here). I don't know how to get amanda on the new system to find gtar, which was not available on the system I compiled amanda on ages ago. Is there an environmental variable or path I can set or do I need to recompile/reinstall, possibly affecting the old server and all of its clients ? (In which case I'll also move to the current release of amanda). thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: build - gtar
On Wed, 17 Mar 2004 at 4:39pm, Brian Cuttler wrote > I don't know how to get amanda on the new system to find gtar, which > was not available on the system I compiled amanda on ages ago. > > Is there an environmental variable or path I can set or do I > need to recompile/reinstall, possibly affecting the old server > and all of its clients ? (In which case I'll also move to the > current release of amanda). You need to recompile and let it find gtar at configure time. This shouldn't affect any of the other clients. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: build - gtar
* Brian Cuttler <[EMAIL PROTECTED]> [20040317 16:40]: > > IRIX 6.5.19 > Amanda 2.4.2p2 > > I've installed gtar on a new amanda-server, a system that was > never a client nor a server before. Currently its only client > is itself. This server mounts /usr/local from another system > (another IRIX system). > > gtar you ask ? .866 TBytes disk, xfsdump will not produce an > output file that would untimately fit on the output tape (read > Jukebox for 8 tapes with a single Quantum SDLT 320 drive, mtx > is in play here). > > I don't know how to get amanda on the new system to find gtar, which > was not available on the system I compiled amanda on ages ago. > > Is there an environmental variable or path I can set or do I > need to recompile/reinstall, possibly affecting the old server > and all of its clients ? (In which case I'll also move to the > current release of amanda). how did you compile amanda? Look in the amandad.debug file for GNUTAR. Just create a symlink to wherever you installed gtar, ie if you got gnutar from SGI freeware (/usr/freeware/bin/tar) and amanda expects /usr/blah/tar, then just ln -s /usr/freeware/bin/tar /usr/blah/tar should do the trick. jf > > > thanks, > > Brian > > --- >Brian R Cuttler [EMAIL PROTECTED] >Computer Systems Support(v) 518 486-1697 >Wadsworth Center(f) 518 473-6384 >NYS Department of HealthHelp Desk 518 473-0773 -- There's a crack in everything That's how the light gets in.
Re: Windows via samba tips?
On Wed, Mar 17, 2004 at 09:58:18PM +0100, Stefan G. Weichinger wrote: > I have to say first that I don't have the solution, but maybe we can > add another piece to the whole picture ... > > Please let me know, what Samba-release you use. > I bet it is > 2.2.x Nope. My samba is version 2.0.7-3.4, as packaged by Debian.
Re: build - gtar
Hi, Brian, on Mittwoch, 17. März 2004 at 22:39 you wrote to amanda-users: BC> I don't know how to get amanda on the new system to find gtar, which BC> was not available on the system I compiled amanda on ages ago. If there was no gnu-tar at compile-time, your amanda-binaries know nothing about gnu-tar. Simple as that. BC> Is there an environmental variable or path I can set or do I BC> need to recompile/reinstall, possibly affecting the old server BC> and all of its clients ? (In which case I'll also move to the BC> current release of amanda). Depends on the configure-options of your old server. You could compile the new server-binaries into other directories and so the two servers would not disturb each other. (/usr/local/etc/amanda vs. /usr/local/etc/amanda-new, for example) If there is only one new server and only one old server, it would be worth the effort of upgrading to 2.4.4p2 on both from my point of view. AFAI remember you think about that for quite a while now ... ;-) -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: build - gtar
Joshua, There is a ./configure switch --with-gnutar= ? Reinstalling on BALI will affect that server and all clients of its /usr/local - affects means replace the binaries, not 'breaks' not that they will care about gnutar since the DLE are all xfsdump. Or recompile with a different target for installation, something local to SAMAR and not /usr/local served from BALI. I just wanted to make sure I was on track, that I needed to re-build and couldn't just update the environment. I have no problem with building a more current version of amanda and installing it on BALI's served /usr/local for all of my SGI systems to use, just not something I want to do at 5pm. Actually, I have some additional SGI systems (some that share /usr/local and some that are isolated) that would also benifit from being able to segment the larger partitions. Its all good, just wanted to make sure I was on the right track. I wouldn't know what we would do without amanda. thanks, Brian > On Wed, 17 Mar 2004 at 4:39pm, Brian Cuttler wrote > > > I don't know how to get amanda on the new system to find gtar, which > > was not available on the system I compiled amanda on ages ago. > > > > Is there an environmental variable or path I can set or do I > > need to recompile/reinstall, possibly affecting the old server > > and all of its clients ? (In which case I'll also move to the > > current release of amanda). > > You need to recompile and let it find gtar at configure time. This > shouldn't affect any of the other clients. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University
Re: Windows via samba tips?
Hi, Dave, on Mittwoch, 17. März 2004 at 22:49 you wrote to amanda-users: DS> On Wed, Mar 17, 2004 at 09:58:18PM +0100, Stefan G. Weichinger wrote: >> I have to say first that I don't have the solution, but maybe we can >> add another piece to the whole picture ... >> >> Please let me know, what Samba-release you use. >> I bet it is > 2.2.x DS> Nope. My samba is version 2.0.7-3.4, as packaged by Debian. Ooooh, failed again ... ;-) 2.0.7 is gone some years now, there has been a lot of improvement inbetween. You don't tell us which AMANDA-release you use, either ... If it is nearly as old, I would recommend some updating. If the problems persist, tell us. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Amanda for windows?
Has there been any discussion or development on an Amanda client that can run on a Windows box? I have never looked at the source for Amanda nor the windows backup API, so this might be a stupid question. I just thought asking would be a good starting point. The Amanda/samba solution does not work well for my Exchange Server. It also has limited ability to filter out files that I do not want backed up. It is very limiting to have to explicitly exclude files or directories when doing a samba backup. I have quite a few NT servers that I would love to backup with Amanda and ax the crappy Backup Exec program we are using. But with functionality being where it is currently in Amanda, I am afraid I have no choice. Thanks for your answers. Michael
Re: Amanda for windows?
On Wed, 17 Mar 2004 at 4:08pm, Michael Kahle wrote > Has there been any discussion or development on an Amanda client that can > run on a Windows box? I have never looked at the source for Amanda nor the > windows backup API, so this might be a stupid question. I just thought > asking would be a good starting point. > > The Amanda/samba solution does not work well for my Exchange Server. It > also has limited ability to filter out files that I do not want backed up. > It is very limiting to have to explicitly exclude files or directories when > doing a samba backup. I have quite a few NT servers that I would love to > backup with Amanda and ax the crappy Backup Exec program we are using. But > with functionality being where it is currently in Amanda, I am afraid I have > no choice. Recent releases compile under cygwin... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Windows via samba tips?
--On Wednesday, March 17, 2004 23:06:38 +0100 "Stefan G. Weichinger" <[EMAIL PROTECTED]> wrote: > Hi, Dave, > > on Mittwoch, 17. März 2004 at 22:49 you wrote to amanda-users: > > DS> On Wed, Mar 17, 2004 at 09:58:18PM +0100, Stefan G. Weichinger wrote: >>> I have to say first that I don't have the solution, but maybe we can >>> add another piece to the whole picture ... >>> >>> Please let me know, what Samba-release you use. >>> I bet it is > 2.2.x > > DS> Nope. My samba is version 2.0.7-3.4, as packaged by Debian. The current Samba package is 2.2.3a-12.3 in stable (woody) and 3.0.2a-1 in testing (sarge). Perhaps it's about time to do an apt-get upgrade. Frank > > Ooooh, failed again ... > > ;-) > > 2.0.7 is gone some years now, there has been a lot of improvement > inbetween. > > You don't tell us which AMANDA-release you use, either ... > > If it is nearly as old, I would recommend some updating. > If the problems persist, tell us. > -- > best regards, > Stefan > > Stefan G. Weichinger > mailto:[EMAIL PROTECTED] > > > > -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: ideal dumpcicle
On Friday 21 March 2003 13:13, Sergio Pereira wrote: >Hi list, > >I'm trying to setup amanda to backup 52 weeks with incremental daily > and every week a full backup. My amanda.conf shows like: > >dumpcycle 7 >runspercycle 5 >tapecycle 55 tapes > >for sure I'm doing something wrong .. what is it? >when I run amadmin to check the due date for each disk I get: > >Due in 367 days: backupserver:/etc >Due in 361 days: backupserver:/var >Due in 362 days: backupserver:/home Based on the numbers above, this does NOT make sense. >question: how do I modify my amanda.conf to meet my 52 weeks >configuration? First, don't worry about either the 52 weeks, or the full backups when you use amanda. The only place the 52 weeks comes in is in determining if you actually need that many tapes (365 or more) actually on the shelf. You see, amanda does her own scheduleing based on the tapecycle, dumpcycle, and runspercycle you give her. You can, with creative scripting, force amanda into your form fitting box, but amanda won't be 100% happy & you'll be much better off to just let amanda do the schedueling as she tries to balance out things so about the same amount of data is saved on every run, thereby makeing much more efficient use of the available tape capacity. I fill a 4Gb tape to >95% for every run here by letting amanda think for herself. With your current settings of dumpcycle 7, runspercycle 5, and tapecycle 55, you are guaranteed that amanda will do a full dump of everything in the disklist "at some point in the 'runspercycle' of that dumpcycle of 7 days. Ergo, at least once a week. So thats fine, and if in the unlikely event you must do a recovery, then everything you need should be on the last 5 tapes amanda has written. However, if you want a full years backup on hand, 55 tapes will only give you 11 weeks before amanda will start asking for the first tape again. Amanda will not re-use a tape until the number of tapes in the 'tapecycle' have been used. With the above figures, you will have on hand the ability to restore the system to its state at the end of virtually any day in the past 11 weeks, or said another way, you'll have 11 full backups on hand. Most of us are happy with 2 or 3, like I'm currently using dumpcycle=8, runspercycle=8, and tapecycle=28, (small drive here, can't get it all in 7 days) so I have about 3.5 full backups at any one time. For business archival useage, and needing a year, then you'll need 260 tapes and tell her 260 in the tapecycle value.. I'm not 'in business' so to me, 260 tapes is serious overkill even at $2 a tape for DDS2's on ebay. :-) >thx all, > >sergio -- 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.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: Amanda for windows?
Hi, Joshua, on Mittwoch, 17. März 2004 at 23:29 you wrote to amanda-users: JBL> On Wed, 17 Mar 2004 at 4:08pm, Michael Kahle wrote >> Has there been any discussion or development on an Amanda client that can >> run on a Windows box? I have never looked at the source for Amanda nor the >> windows backup API, so this might be a stupid question. I just thought >> asking would be a good starting point. >> >> The Amanda/samba solution does not work well for my Exchange Server. It >> also has limited ability to filter out files that I do not want backed up. >> It is very limiting to have to explicitly exclude files or directories when >> doing a samba backup. I have quite a few NT servers that I would love to >> backup with Amanda and ax the crappy Backup Exec program we are using. But >> with functionality being where it is currently in Amanda, I am afraid I have >> no choice. JBL> Recent releases compile under cygwin... ;-) Michael, as you may read in another thread of today, the excluding-topic is a hot one, you are right. As I promised in the other thread I have contacted the Samba-Team to answer our questions regarding this exclusion topic. As soon as we have answers to this we will look for a better solution to this. cygwin may be be a help inbetween. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: ideal dumpcicle
On Wednesday 17 March 2004 13:32, Frank Smith wrote: >--On Friday, March 21, 2003 13:13:06 -0500 Sergio Pereira <[EMAIL PROTECTED]> wrote: >> Hi list, >> >> I'm trying to setup amanda to backup 52 weeks with incremental >> daily and every week a full backup. My amanda.conf shows like: >> >> dumpcycle 7 >> runspercycle 5 >> tapecycle 55 tapes >> >> for sure I'm doing something wrong .. what is it? >> when I run amadmin to check the due date for each disk I get: >> >> Due in 367 day20040317104426s: backupserver:/etc >> Due in 361 days: backupserver:/var >> Due in 362 days: backupserver:/home >> >> question: how do I modify my amanda.conf to meet my 52 weeks >> configuration? > >To have a years worth of backups, you would need a tapecycle of >at least 5 * 52 = 260 tapes. > >Maybe you need two separate configs, one always-full running weekly >with a tapecycle of at least 52 tapes, and one running daily with >at least 5 tapes (using your runspercycle). > I'd modify that a bit, to a tapecycle of 10 tapes so you have 2 recent fulls on hand in the everyday runs. Also, when using 2 configs, they should have seperate data dirs so they don't get confused. This means that the always-full run will need to be seperated by a day from any of the other configs normal runs, and you will have full backups in the daily schedule too. But cron can handle that without waking from a snooze. >Frank > >> thx all, >> >> sergio >> >> >> -- -- 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.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Has 2.4.5b 20040213 a problem?
Greets all; Having just returned from a long work trip, I fired up my cron entries for amanda, reset runtapes to 6, and figured amdump would use the last 2 tapes in the magazine, then I could run amflush to finish the job after reloading the magazine. Silly me... It couldn't find the next tape, and hasn't now in 3 runs of amflush. And I was sitting here, but did not hear it searching the magazine but its possible tvtime may have covered that up. It appears it writes the current tape in the first slot (I've done an "amtape /config/ reset" to reset it to the first slot in each case after cycling the written tape out and feeding it the cleaning tape, then moved the unused tapes to the top, and added the next tape in the sequence to the bottom slot so it could if it would, just run on thru the magazine until done) and then either doesn't search, or skips the next (2nd) slot each time. After the last failure, I sat down in front of the drive and watched it skip slot 2 for the first run of amcheck, but a rerun did scan slot 2 and find the right tape. If it starts from a "reset" condition, it (amflush/amcheck) should have checked slot 2 next after slot 1 (0 to amanda of course since amanda runs in base zero & thats a PITA), but didn't. Is this a bug, or am I being dense and missing something obvious? If I can get it all flushed before tonights run of amdump, then tonights run should "catch it up" and I can reset runtapes back to 1 and start getting back into balance. I have about 2 hours left. -- 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.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
amdump again
Hi, I've changed the labelstr to 'mylabel[0-9][0-9]*$' as Frank suggested. It's better now, but not perfect yet. B-) I try to archive /var/www and get this error every time: == FAILURE AND STRANGE DUMP SUMMARY: mymachine /dev/ida/c0d0p2 lev 0 FAILED [disk /ida/c0d0p2, all estimate failed] NOTES: planner: Adding new disk mymachine:/dev/ida/c0d0p2. driver: WARNING: got empty schedule from planner taper: tape mylabel01 kb 0 fm 0 [OK] == Content of disklist: mymachine /dev/ida/c0d0p2 always-full Content of the 'always-full' section in amanda.conf: options no-compress , index include list "/var/www" Filburt
