nicing down the client
I have a user who is complaining that when amanda backups are running, the server he is access is 100% busy with gzipping the amanda backup that it is sending to the backup server and the server is too slow for him to do his stuff on. I've tried to look up how to configure the client but haven't found much information and there is no amanda.conf file installed by default with the RPMs I've been using. I'm using amanda-2.4.4p3-1. Does anyone have a suggestion for how to lower the priority of the amanda client? I'm also not sure if this is going to do it for him because I'm guessing he is being disk-limited not cpu-limited. Any suggestions would be appreciated. Thanks, Don
Re: nicing down the client
Ok, I added: nice= 15 to my /etc/xinetd.d/amanda configuration file and will see how that goes. Thanks for the tip! Don Ian Turner wrote: Don, The easiest way is to lower the priority of the amandad daemon that runs on the client. If you are using xinetd, you can just add a nice entry to the amandad service. If you are using BSD inetd, you can use the nice program; change the command from amanda dgram udp wait amandabackup /usr/sbin/amandad to amanda dgram udp wait amandabackup /usr/bin/nice /usr/sbin/amandad Cheers, --Ian
Re: Restore from multiple configs
Jon, thanks for the suggestions. I will give them a try (carefully :)) Don Jon LaBadie wrote: On Tue, Jun 26, 2007 at 10:29:45AM -0700, Don Murray wrote: Just a couple of minor things, but if it ain't broke, don't fix it. I'm going to ignore your details and key on the concept : you want to have a weekly and a daily back up. I wanted to do this too and went down the path of investigating multiple configurations like you are doing. But it really bugged me that I have to basically do 2 level-0 backups a week, one for the weekly and one for the daily (since the daily backup configuration isn't aware of the weekly). My reason for having a weekly backup is because I want to be able to archive the tapes periodically, but I don't need to have the 2 configurations fully separate. After messing around, I finally figured out that what I wanted was a single configuration with a forced level 0 on saturday night. So, I set up a single daily configuration. Inside /etc/amanda/daily I added a scripts called forceall that looks like this: -bash-3.00$ cat forceall #!/bin/sh /usr/sbin/amadmin daily force \ windsor / \ gilmore / \ gilmore /backedup/project \ gilmore /backedup/home \ gateway2 / \ imap / \ asterisk / - so yes, I have to specify all my disk entries in this file, which is a pain and a possible issue when you change the entries - but my disk configuration is pretty stable. The amadmin command documents the force command as: force [ hostname [ disks ]* ]+ I.e. the disk names, and even the host names are optional. If you are forcing every DLE to a level 0 this suggests you could simplify your script to just listing hostnames, and even omitting them. My crontab looks like: # # minute (0-59) # | - hour (0-23) # | | -- day of month (1-31) # | | | --- month (1-12) # | | | | day of the week (0-7 sunday = 0 or 7) # | | | | | # * * * * * # check the configuration each evening 00 20 * * 0-5 /usr/sbin/amcheck -m daily # run pgrdaily every weekday and Saturday morning 05 03 * * 1-6 /usr/sbin/amdump daily # on Saturday morning, make sure its a level 0 00 03 * *6 /etc/amanda/daily/forceall amdump doesn't run on Sunday, giving the Saturday job enough chance to dump everything as it can take more than 24 hours for a full level 0. But each Saturday before the dump, I run the forceall script that tells amanda to make the next run a level 0. I'd be concerned that the forceall was missed. Yeah 5 minute difference is not much. But another way you could set up your crontab is to do the amdump daily only 5 times a week and on Saturday do a combination of forceall amdump daily. Do you set up your dumptype to do incronly so it will never do a level 0 on its own? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Restore from multiple configs
Hi Harald, I'm going to ignore your details and key on the concept : you want to have a weekly and a daily back up. I wanted to do this too and went down the path of investigating multiple configurations like you are doing. But it really bugged me that I have to basically do 2 level-0 backups a week, one for the weekly and one for the daily (since the daily backup configuration isn't aware of the weekly). My reason for having a weekly backup is because I want to be able to archive the tapes periodically, but I don't need to have the 2 configurations fully separate. After messing around, I finally figured out that what I wanted was a single configuration with a forced level 0 on saturday night. So, I set up a single daily configuration. Inside /etc/amanda/daily I added a scripts called forceall that looks like this: -bash-3.00$ cat forceall #!/bin/sh /usr/sbin/amadmin daily force \ windsor / \ gilmore / \ gilmore /backedup/project \ gilmore /backedup/home \ gateway2 / \ imap / \ asterisk / - so yes, I have to specify all my disk entries in this file, which is a pain and a possible issue when you change the entries - but my disk configuration is pretty stable. (I also created an unforceall is the same with the force parameter changed to unforce for testing.) My crontab looks like: # # minute (0-59) # | - hour (0-23) # | | -- day of month (1-31) # | | | --- month (1-12) # | | | | day of the week (0-7 sunday = 0 or 7) # | | | | | # * * * * * # check the configuration each evening 00 20 * * 0-5 /usr/sbin/amcheck -m daily # run pgrdaily every weekday and Saturday morning 05 03 * * 1-6 /usr/sbin/amdump daily # on Saturday morning, make sure its a level 0 00 03 * *6 /etc/amanda/daily/forceall amdump doesn't run on Sunday, giving the Saturday job enough chance to dump everything as it can take more than 24 hours for a full level 0. But each Saturday before the dump, I run the forceall script that tells amanda to make the next run a level 0. This is working really well for me. Any weekend I have a level 0 set of tapes that I can pull and put into the safe or off-site backup, but I don't have to pay the overhead of doing 2 level 0's, one for the weekly and one for the daily/cycle. I just thought I would suggest this as an alternative to a 2 configuration setup. When I pull the tapes, I have a system for marking the out-going tapes as being not reused, and then adding the new tapes into the rotation. If you are interested in going ahead with the above kind of idea I can send you the details on that too. Anyway, hopefully you find this idea interesting. Don (ps: and I know this isn't really the recommended way of doing things... the recommended way is just let amanda schedule it all - but I've found this to work very well for me. I usually only pull my archive once a month and I have considered changing the cronjob to only force the level 0 once a month rather than once a week - but my backups do occassionally have a glitch and fail to run, so having them go weekly allows me to just wait for next week if there was a problem, rather than having to either wait a month or manually mess with something.) Harald Schioeberg wrote: Hello again. In my struggle to get a working amanda config (working for my strange setup :) I reached the following decision: I'll use two configs, - Weekly, which does level-0 dumps to tape (using chg-zd-mtx) - Daily, which does incrementals to a virtual tape on disk (using chg-disk) As it is cumbersome to restore stuff from different configs, I wrote chg-multiplex, which acts as a super-changer and combines the two configs for restore purposes. If you like the idea, have a look at: http://wiki.zmanda.com/index.php/Chg-multiplex If you don't: sorry for the spam :) -- Harald Schioeberg Technische Universitaet Berlin | T-Laboratories | FG INET www: http://www.net.t-labs.tu-berlin.de Phone: +49-(0)30-8353-58476 | Fax: +49-(0)391 534 783 47
Re: dead processes
Joshua Baker-LePain wrote:
On Mon, 23 Apr 2007 at 1:53pm, Don Murray wrote
Note the selfchecks that are running with D process state - meaning they
are sleeping in the kernel and are uninterruptible and therefore unkillable.
So - it looks like I need to reboot my client before I can get a backup from
it again, which is a little harsh.
I was wondering whether anyone knows why Amanda client 2.4.4 would get wedged
like that, is there something I can do to minimize the problem? Also, if
anyone has ideas about avoiding the estimate issues all together, I would
appreciate any advice.
Look in /tmp/amanda on the clients for the *debug files relating to the
hung processes. They should have more details on what went wrong. Also,
the alternate estimate methods went in before 2.5 -- I'm running 2.4.5p1
and 'man amanda.conf' says estimate client|calcsize|server.
Joshua - thanks for the reply.
Whenever I include estimate calcsize or estimate client in my
amanda.conf I get :
/etc/amanda/daily/amanda.conf, line 36: configuration keyword expected
/etc/amanda/daily/amanda.conf, line 36: end of line expected
on the estimate line. I've tried as a general parameter and I've
tried within a particular dump type definition. Maybe I'm doing
something wrong? There doesn't appear to be an amanda.conf man page
installed by the RPM but I did go to
/usr/share/doc/amanda-server-2.4.4p3 and grepped for calcsize. There
is mention of it in the whats.new file... says it must be installed
with setuid to root. Which I believe it is:
[EMAIL PROTECTED] amanda-server-2.4.4p3]# locate calcsize
/usr/lib/amanda/calcsize
[EMAIL PROTECTED] amanda-server-2.4.4p3]# cd /usr/lib/amanda
[EMAIL PROTECTED] amanda]# ls -l calcsize
-rwsr-x--- 1 root disk 19401 Jun 28 2004 calcsize
So the calcsize program exists but I am too daft to enable it in the
amanda.conf file. Is this incorrect - this is the kind of definition
where if I comment out the estimate line, all is good, otherwise I get a
check error.
define dumptype remote {
global
compress client fast
estimate calcsize
}
As for the selfcheck hanging up.
The log files are kept in /var/log/amanda on this system.
selfcheck is the process that is hung and its log isn't very helpful...
[EMAIL PROTECTED] amanda]# cat selfcheck.2007042021.debug
selfcheck: debug 1 pid 12910 ruid 33 euid 33: start at Fri Apr 20
20:00:01 2007
/usr/lib/amanda/selfcheck: version 2.4.4p3
selfcheck: time 0.000: checking disk /backedup/home
I'm also pasting below the run up in the amandad.date.debug file to
the first ERROR encountered. It all seems ok to me until it gets to the
ERROR amandad busy.
I sure wish I didn't have to reboot to get rid of those hung processes.
Each time I try to run amcheck I get:
Amanda Backup Client Hosts Check
ERROR: NAK gilmore: amandad busy
Client check: 4 hosts checked in 10.120 seconds, 1 problem found
:(
Don
Amanda 2.4 REQ HANDLE 001-28D005F7 SEQ 1177124409
SECURITY USER amanda
SERVICE selfcheck
OPTIONS features=feff9ffe0f;maxdumps=1;hostname=gilmore;
GNUTAR /backedup/home 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /backedup/project 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/vancouver 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/spruce 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/princeedward 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/nootka 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/glen 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/fs2 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/burrard 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR / 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/tmp;exclude-optional;
amandad: time 30.047: received dup P_REQ packet, ACKing it
amandad: time 30.047: sending ack:
Amanda 2.4 ACK HANDLE 001-28D005F7 SEQ 1177124409
amandad: time 60.048: got packet:
Amanda 2.4 REQ HANDLE 001-28D005F7 SEQ 1177124409
SECURITY USER amanda
SERVICE selfcheck
OPTIONS features=feff9ffe0f;maxdumps=1;hostname=gilmore;
GNUTAR /backedup/home 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /backedup/project 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/vancouver 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/spruce 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/princeedward 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-optional;
GNUTAR /nonbackedup/work3/backups/nootka 0 OPTIONS
dead processes
Hi all, I am running Amanda for a linux network backup. The server is a Fedora Core 3 box with : amanda-2.4.4p3-1 amanda-client-2.4.4p3-1 amanda-server-2.4.4p3-1 The client is a Centos 4.3 box with : amanda-client-2.4.4p3-1 I occasionally get failures to backup this client (it is the big one with a large list of DLEs). The errors are always time-outs during estimates. Like this: gilmore/backedup/home lev 0 FAILED [Estimate timeout from gilmore] gilmore/backedup/project lev 0 FAILED [Estimate timeout from gilmore] ... It seems like this happens about 1 out of every 5 runs... so far I've just learned to skip a day and hope nothing bad happens that day - not very good. My assumption was that I should upgrade to 2.5.x as then I can use the lighter, less accurate estimate methods rather than the default estimate method. However, this weekend I had a fail with a data timeout: gilmore/nonbackedup/work3/backups/glen lev 0 FAILED [data timeout] Now whenever I do a amcheck I get: WARNING: gilmore: selfcheck reply timed out. Meanwhile, on the client gilmore if I check all the amanda processes I get: [EMAIL PROTECTED] amanda]# ps aux | grep amanda amanda 11570 0.0 0.0 3104 884 ?DApr20 0:00 /usr/lib/amanda/sendbackup amanda 12910 0.0 0.0 3944 796 ?DApr20 0:00 /usr/lib/amanda/selfcheck amanda8768 0.0 0.0 2400 796 ?D11:48 0:00 /usr/lib/amanda/selfcheck amanda9104 0.0 0.0 2888 888 ?Ss 13:36 0:00 amandad amanda9105 0.0 0.0 3432 792 ?D13:36 0:00 /usr/lib/amanda/selfcheck amanda9106 0.0 0.0 00 ?Z13:36 0:00 [amandad] defunct Note the selfchecks that are running with D process state - meaning they are sleeping in the kernel and are uninterruptible and therefore unkillable. So - it looks like I need to reboot my client before I can get a backup from it again, which is a little harsh. I was wondering whether anyone knows why Amanda client 2.4.4 would get wedged like that, is there something I can do to minimize the problem? Also, if anyone has ideas about avoiding the estimate issues all together, I would appreciate any advice. Don
BogusMonth 0, 0 ??
Hi everyone, I just had a weird thing happen. I had already received my
AMANDA MAIL REPORT for my daily backup for today. But 5 hours after I
received the usual backup report, I got another email, this time from
user [EMAIL PROTECTED] rather from the usual [EMAIL PROTECTED].
The subject was:
MYDOMAIN AMANDA MAIL REPORT FOR BogusMonth 0, 0
I have appended the result below. It has all the correct DLE's reported.
Ordinarily I wouldn't worry about this, I'd just let it go and see if it
happens again. But since I will be leaving town for the holidays in a
few days I thought I would ask if anyone has seen this before and has
any ideas about why it would happen. I'm just worried about impending
difficulties while I'm out of town.
Thanks in advance,
Don
(Note: the actual domain has been changed to protect the innocent :))
The message:
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: MYDOMAIN-04.
FAILURE AND STRANGE DUMP SUMMARY:
amreport: ERROR could not open log /var/lib/amanda/mydaily/log: No
such file or directory
windsor/ RESULTS MISSING
gilmore/ RESULTS MISSING
gilmore/nonbackedup/work3/backups/burrard RESULTS MISSING
gilmore/nonbackedup/work3/backups/fs2 RESULTS MISSING
gilmore/nonbackedup/work3/backups/glen RESULTS MISSING
gilmore/nonbackedup/work3/backups/nootka RESULTS MISSING
gilmore/nonbackedup/work3/backups/princeedward RESULTS MISSING
gilmore/nonbackedup/work3/backups/spruce RESULTS MISSING
gilmore/nonbackedup/work3/backups/vancouver RESULTS MISSING
gilmore/backedup/project RESULTS MISSING
gilmore/backedup/home RESULTS MISSING
imap / RESULTS MISSING
asterisk / RESULTS MISSING
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
Re: BogusMonth 0, 0 ??
Its very weird. I have checked the /var/log/cron logs and there doesn't
appear to be anything suspicious. I have checked with amstatus both
my main daily backup and the couple of test configurations I had and the
results all make sense. amcheck gives me the right answer for which
is the next tape.
I have also checked /etc/crontab and amanda's crontab and its all sane.
what is weird is that it is using the org from the daily
configuration, and the DLE's as well, but the
/var/lib/amanda/daily/amdump.1 only shows me the last successful one.
Very strange. Well, I have a couple of days to go before I leave so I
will watch the upcoming backup carefully...
Don
Frank Smith wrote:
Don Murray wrote:
Hi everyone, I just had a weird thing happen. I had already received my
AMANDA MAIL REPORT for my daily backup for today. But 5 hours after I
received the usual backup report, I got another email, this time from
user [EMAIL PROTECTED] rather from the usual [EMAIL PROTECTED].
The subject was:
MYDOMAIN AMANDA MAIL REPORT FOR BogusMonth 0, 0
Perhaps some forgotten root cron (or 'at') job that was an attempt to run
monthly backups? Amanda doesn't run itself, so perhaps you can look in
wherever your system cron logs are and track it down that way. Probably
not a big issue since it failed, although you might want to run amcheck to
see that it didn't muck with your changer or mark a tape as used (since
its been my experience even a totally failed backup marks the current tape
as used).
Frank
I have appended the result below. It has all the correct DLE's reported.
Ordinarily I wouldn't worry about this, I'd just let it go and see if it
happens again. But since I will be leaving town for the holidays in a
few days I thought I would ask if anyone has seen this before and has
any ideas about why it would happen. I'm just worried about impending
difficulties while I'm out of town.
Thanks in advance,
Don
(Note: the actual domain has been changed to protect the innocent :))
The message:
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: MYDOMAIN-04.
FAILURE AND STRANGE DUMP SUMMARY:
amreport: ERROR could not open log /var/lib/amanda/mydaily/log: No
such file or directory
windsor/ RESULTS MISSING
gilmore/ RESULTS MISSING
gilmore/nonbackedup/work3/backups/burrard RESULTS MISSING
gilmore/nonbackedup/work3/backups/fs2 RESULTS MISSING
gilmore/nonbackedup/work3/backups/glen RESULTS MISSING
gilmore/nonbackedup/work3/backups/nootka RESULTS MISSING
gilmore/nonbackedup/work3/backups/princeedward RESULTS MISSING
gilmore/nonbackedup/work3/backups/spruce RESULTS MISSING
gilmore/nonbackedup/work3/backups/vancouver RESULTS MISSING
gilmore/backedup/project RESULTS MISSING
gilmore/backedup/home RESULTS MISSING
imap / RESULTS MISSING
asterisk / RESULTS MISSING
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
Amcheck host name lookup problem
Hello again, I am adding new hosts/DLE to my amanda backup configuration. I have been backing up some partitions for a few weeks with no problem. I have recently added a few more hosts. My current disklist looks like: windsor sda3 local-root # windsor root partition gilmore sda1 remote-root# gilmore root partition imapmd1 remote-root# imap root partition fs2 /dev/hda3 remote-root # fs2 root partition asterisksda2 remote-root# asterisk root partition Windsor is the amanda server. Gilmore, imap, fs2 and asterisk are all linux hosts. I had 2 problems when I ran amcheck. 1) when I used just hda3 for the parition on fs2, amcheck error says ERROR: fs2: [could not access hda3 (hda3): No such file or directory] But when I switch this to hda1 there is no problem. I have double checked that hda3 does exist :) hda1 is the /boot partition, hda3 is the / partition. When I switch the DLE to /dev/hda3 it returns no error. I have not run this backup yet and I have a feeling its going to just backup the directory /dev/hda3 (which will just show up as a single node?). 2) the other problem I have is that the asterisk host has the following error: ERROR: asterisk: [addr 192.168.0.63: hostname lookup failed] We are using a YP system. I can do a ypcat hosts.byname and I can see the asterisk host. I can't see any reason why this host should be considered different from the other ones that are successful, such as fs2, imap and gilmore. Does anyone have any experience with these kinds of errors and can give me some advice on them? The backup did run successfully on the other remote file systems. Thanks, Don Murray
archive level 0 backups
Hello list - thanks for your help in the past - I now have my amanda configuration running stably on a subset of my partitions with my 8-tape changer for a few weeks without trouble. I've tested file recovery with amrecover and all is good. I only have one last hurdle to overcome before I can declare complete success. One of the missions of our backups is to provide an archival backup for offsite storage at least once per month. I was hoping to get some advice on this issue. From the zmanda wiki I have gleaned that the typical way to do this is create an additional amanda configuration called archive that runs once per month (or whatever) and forces a level 0 on all things you want to archive. This is fine, except that a full level 0 on all systems is going to cause some strain on the infrastructure (network and disk activity for example). I was wondering if it is possible instead to cache the latest level0's from the daily backups and have them written to tape. My holding disk is big enough to hold a copy of all level 0's, and it is not necessary for my once-a-month backup to have level 0's all from the same day. Since I am already paying the price to get a full set of level 0's once per week with my daily tape cycle, is it possible to leverage this into a easier monthly backup? I hope this makes some sense to people and would really appreciate any advice on this issue. Thanks in advance, Don
Problems with chg-scsi parameters
Hello Amanda-ites,
I have had a baby test Amanda installation running for a week with
vtapes, but today I wanted to take the next step which is to create a
new configuration for use with our Dell PV-122T 8-tape changer. I
believe I am not setting up my chg-scsi configuration correctly as
amcheck fails apparently due to my configuration of the tape changer.
Every time I run amcheck I get the following result:
$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /holding/amanda: 405373112 KB disk space available, using
394887352 KB
amcheck-server: could not get changer info: param. not set in your config
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.028 seconds, 0 problems found
(brought to you by Amanda 2.4.4p3)
I was trying to carry on and label my tapes and this happens each time I
try to run amtape, so the tape is not labelled or added to my tapelist.
Any suggestions would be great. I am attaching below all the
information I can think to include. BTW, I have tried to follow the
suggestions in chg-scsi.notes in
/usr/share/doc/amanda-server-2.4.4p3/ and also I've tried to google more
information but so far I seem to be missing something critical.
Thanks in advance,
Don
$ cat /proc/scsi/scsi
...
Host: scsi4 Channel: 00 Id: 05 Lun: 00
Vendor: DELL Model: PV-122T Rev: K17r
Type: Medium Changer ANSI SCSI revision: 02
Host: scsi4 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: ULTRIUM-TD2 Rev: 3AYD
Type: Sequential-AccessANSI SCSI revision: 03
Machine is running FC3
-bash-3.00$ uname -a
Linux windsor.XXX.com 2.6.9-1.667smp #1 SMP Tue Nov 2 14:59:52 EST 2004
i686 i686 i386 GNU/Linux
I have installed amanda using yum:
-bash-3.00$ rpm -qa | grep amanda
amanda-2.4.4p3-1
amanda-client-2.4.4p3-1
amanda-server-2.4.4p3-1
#
# amanda.conf - sample Amanda configuration file. This started off life as
# the actual config file in use at CS.UMD.EDU.
#
# If your configuration is called, say, csd, then this file normally goes
# in /etc/amanda/csd/amanda.conf.
#
# your organization name for reports
org Geeks
# space separated list of operators at your site
mailto [EMAIL PROTECTED]
dumpuser amanda # the user to run dumps under
inparallel 4# maximum dumpers that will run in parallel
netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 7 days# the number of days in the normal dump cycle
#runspercycle 4 weeks# the number of amdump runs in dumpcycle days
tapecycle 7 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week (just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle
### ### ###
# WARNING: don't use `inf' for tapecycle, it's broken!
### ### ###
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 300# number of seconds per filesystem for estimates.
#etimeout -600 # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.
runtapes 1 # number of tapes to be used in a single run of amdump
tpchanger chg-scsi# the tape-changer glue script
tapedev 0
changerfile /etc/amanda/daily/changer.conf
#rawtapedev /dev/null # the raw device to be used (ftape only)
#changerdev /dev/sg4
tapetype quantum-lto2
labelstr ^GEEK-[0-9][0-9]*$ # label constraint regex: all tapes must match
holdingdisk hd1 {
comment main holding disk
# where the holding disk is
directory /holding/amanda
use -10 Gb # how much space can we use on it
}
infofile /var/lib/amanda/daily/curinfo# database filename
logdir /var/lib/amanda/daily# log directory
indexdir /var/lib/amanda/daily/index # index directory
# tapelist is stored, by default, in the directory that contains amanda.conf
# tapetypes
define tapetype quantum-lto2 {
comment grabbed from http://wiki.zmanda.com/index.php/Tapetype_definitions;
length 186368 mbytes
filemark 0 kbytes
speed 2781 kps
}
define dumptype global {
comment Global definitions
program GNUTAR
index yes
record yes
# This is quite useful for setting global parameters, so you don't have
# to type them everywhere. All dumptype definitions in this sample file
# do include these definitions, either directly
Problems with chg-scsi parameters
Hi all - I sent this in yesterday and didn't see it show up on the yahoo
group set of messages so I think it got dropped. I wonder if it is
because I used attachments rather than pasting the .conf files into the
email text... maybe this is why it failed. So I am retrying with hopes
that it gets through this time.
I hope someone has some ideas for me.
Thanks,
Don
Hello Amanda-ites,
I have had a baby test Amanda installation running for a week with
vtapes, but today I wanted to take the next step which is to create a
new configuration for use with our Dell PV-122T 8-tape changer. I
believe I am not setting up my chg-scsi configuration correctly as
amcheck fails apparently due to my configuration of the tape changer.
Every time I run amcheck I get the following result:
$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /holding/amanda: 405373112 KB disk space available, using
394887352 KB
amcheck-server: could not get changer info: param. not set in your config
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.028 seconds, 0 problems found
(brought to you by Amanda 2.4.4p3)
I was trying to carry on and label my tapes and this happens each time I
try to run amtape, so the tape is not labelled or added to my tapelist.
Any suggestions would be great. I am attaching below all the
information I can think to include. BTW, I have tried to follow the
suggestions in chg-scsi.notes in
/usr/share/doc/amanda-server-2.4.4p3/ and also I've tried to google more
information but so far I seem to be missing something critical.
Thanks in advance,
Don
$ cat /proc/scsi/scsi
...
Host: scsi4 Channel: 00 Id: 05 Lun: 00
Vendor: DELL Model: PV-122T Rev: K17r
Type: Medium Changer ANSI SCSI revision: 02
Host: scsi4 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: ULTRIUM-TD2 Rev: 3AYD
Type: Sequential-AccessANSI SCSI revision: 03
Machine is running FC3
-bash-3.00$ uname -a
Linux windsor.XXX.com 2.6.9-1.667smp #1 SMP Tue Nov 2 14:59:52 EST 2004
i686 i686 i386 GNU/Linux
I have installed amanda using yum:
-bash-3.00$ rpm -qa | grep amanda
amanda-2.4.4p3-1
amanda-client-2.4.4p3-1
amanda-server-2.4.4p3-1
#
# amanda.conf - sample Amanda configuration file. This started off life as
# the actual config file in use at CS.UMD.EDU.
#
# If your configuration is called, say, csd, then this file normally goes
# in /etc/amanda/csd/amanda.conf.
#
# your organization name for reports
org Geeks
# space separated list of operators at your site
mailto [EMAIL PROTECTED]
dumpuser amanda # the user to run dumps under
inparallel 4# maximum dumpers that will run in parallel
netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 7 days# the number of days in the normal dump cycle
#runspercycle 4 weeks# the number of amdump runs in dumpcycle days
tapecycle 7 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week (just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle
### ### ###
# WARNING: don't use `inf' for tapecycle, it's broken!
### ### ###
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 300# number of seconds per filesystem for estimates.
#etimeout -600 # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.
runtapes 1 # number of tapes to be used in a single run of amdump
tpchanger chg-scsi # the tape-changer glue script
tapedev 0
changerfile /etc/amanda/daily/changer.conf
#rawtapedev /dev/null # the raw device to be used (ftape only)
#changerdev /dev/sg4
tapetype quantum-lto2
labelstr ^GEEK-[0-9][0-9]*$ # label constraint regex: all tapes must match
holdingdisk hd1 {
comment main holding disk
# where the holding disk is
directory /holding/amanda
use -10 Gb # how much space can we use on it
}
infofile /var/lib/amanda/daily/curinfo # database filename
logdir /var/lib/amanda/daily # log directory
indexdir /var/lib/amanda/daily/index# index directory
# tapelist is stored, by default, in the directory that contains amanda.conf
# tapetypes
define tapetype quantum-lto2 {
comment grabbed from
Re: Problems with chg-scsi parameters
Hi Pavel, Thanks for your help. Making those changes has allowed me to label a tape. I am in the process of labeling the 7 I want to use now, thanks. I guess the only thing I'm wondering now is whether what is in changer.conf is making a difference... I used the examples from the chg-scsi documentation. Is it the same for chg-zd-mtx? I felt that file was a bit of a mess because I was trying things almost at random in it. Anyway, things are now progressing. Here it the mtx status after labeling the first tape and then doing an mtx -f /dev/sg4 next to load the second tape. The mtx status returns the following: -bash-3.00$ mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 8 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 2 Loaded) Storage Element 1:Full Storage Element 2:Empty Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Thanks again Don [EMAIL PROTECTED] wrote: Hello, 1. Try changing these parameters in your amanda.conf: tpchanger chg-zd-mtx tapedev /dev/nst0 changerdev /dev/sg0 changerfile /etc/amanda/daily/changer.conf#Make sure this path is correct 2. try to label a tape 3. Run mtx -f /dev/sg0 status and post the output Pavel Thanks -Original Message- From: Don Murray [EMAIL PROTECTED] Sent: Wed, November 22, 2006 3:54 pm To: amanda-users@amanda.org Subject: Problems with chg-scsi parameters Hi all - I sent this in yesterday and didn't see it show up on the yahoo group set of messages so I think it got dropped. I wonder if it is because I used attachments rather than pasting the .conf files into the email text... maybe this is why it failed. So I am retrying with hopes that it gets through this time. I hope someone has some ideas for me. Thanks, Don Hello Amanda-ites, I have had a baby test Amanda installation running for a week with vtapes, but today I wanted to take the next step which is to create a new configuration for use with our Dell PV-122T 8-tape changer. I believe I am not setting up my chg-scsi configuration correctly as amcheck fails apparently due to my configuration of the tape changer. Every time I run amcheck I get the following result: $ amcheck daily Amanda Tape Server Host Check - Holding disk /holding/amanda: 405373112 KB disk space available, using 394887352 KB amcheck-server: could not get changer info: param. not set in your config Amanda Backup Client Hosts Check Client check: 1 host checked in 0.028 seconds, 0 problems found (brought to you by Amanda 2.4.4p3) I was trying to carry on and label my tapes and this happens each time I try to run amtape, so the tape is not labelled or added to my tapelist. Any suggestions would be great. I am attaching below all the information I can think to include. BTW, I have tried to follow the suggestions in chg-scsi.notes in /usr/share/doc/amanda-server-2.4.4p3/ and also I've tried to google more information but so far I seem to be missing something critical. Thanks in advance, Don $ cat /proc/scsi/scsi ... Host: scsi4 Channel: 00 Id: 05 Lun: 00 Vendor: DELL Model: PV-122T Rev: K17r Type: Medium Changer ANSI SCSI revision: 02 Host: scsi4 Channel: 00 Id: 06 Lun: 00 Vendor: IBM Model: ULTRIUM-TD2 Rev: 3AYD Type: Sequential-AccessANSI SCSI revision: 03 Machine is running FC3 -bash-3.00$ uname -a Linux windsor.XXX.com 2.6.9-1.667smp #1 SMP Tue Nov 2 14:59:52 EST 2004 i686 i686 i386 GNU/Linux I have installed amanda using yum: -bash-3.00$ rpm -qa | grep amanda amanda-2.4.4p3-1 amanda-client-2.4.4p3-1 amanda-server-2.4.4p3-1 # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, csd, then this file normally goes # in /etc/amanda/csd/amanda.conf. # # your organization name for reports org Geeks # space separated list of operators at your site mailto [EMAIL PROTECTED] dumpuser amanda # the user to run dumps under inparallel 4# maximum dumpers that will run in parallel netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 7 days# the number of days in the normal dump cycle #runspercycle 4 weeks# the number of amdump runs in dumpcycle days tapecycle 7 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle
General backup advice help?
Hello list, I've been lurking on the list a few days (not really long enough to be opening my mouth, but here it goes). I am a relatively novice sysadmin looking for a better backup setup than our handcrafted scripts. Amanda looks interesting but I am worried that it will not necessarily solve my problem. So I was hoping to beg your indulgence for a moment and see if anyone has any advice for me. My main concern is that we have to be up round the clock these days as we have people connecting during their work day, 9 hours different from ours. So having major services disrupted in the middle of the night for backups doesn't seem a viable solution anymore, as it hits the other people in the middle of the day. We are a small business. We have 2 main linux servers each with about 200G to back up. Backing up a full 200G volume across the network takes about 7 hours currently. I understand from the documentation that Amanda will attempt to balance the time taken for backups through its scheduling process. However, it seems to me that when you have to do a level 0 of size X, you have to do it, and so you will take the full 7 hours. The bad news is that currently these systems are set up with the full 200G on single partitions. Does anyone have any advice for these problems? 1) reducing the time for large volume network backups - is it possible to do less than a full partition? 2) reducing the system resources on systems backing up (i.e. can the amanda-client be run with a low priority)? 3) can you tell that we're just screwed and need to seriously rethink how we do this? If so, got any ideas? :) Again, sorry for the generic, non-Amanda-specific questions. If anyone has suggestions for the right forum to ask these questions on, I would love to hear from them. Thanks, Don
Re: General backup advice help?
Hi Jon, thanks for the reply! Jon LaBadie wrote: My main concern is that we have to be up round the clock these days as we have people connecting during their work day, 9 hours different from ours. So having major services disrupted in the middle of the night for backups doesn't seem a viable solution anymore, as it hits the other people in the middle of the day. Up is less a concern to me than connected. Are some of these people working on laptops or other computers that are not accessible to your backup server except at certain times? Actually for those people the main issue is that some key services (like the email server) are shut down during backups. This is a tangential issue I guess because by getting smoother backups I'm just going to make their outages shorter, but the outage will still be there. I'm not backing up from Europe, no. So connectivity is not an issue. If you are willing to use tar as as your backup program (many, many amanda sites do that) then there is not problem. You say you have basically 400GB of data. The basic unit of backup for amanda is called a DiskList Entry (DLE) after the name of a config file. With tar as the backup program you can specify directory tree's as a DLE rather than filesystems. So you could have a DLE for /boot, /var, /home, /usr/local, /usr (without local), /opt, /database, and one for / without all the others. This is done by including or excluding files and directories in the DLE config. Now with 16 DLE's from two systems (or even more is you wish), amanda can spread the level 0's of those 16 items over your dumpcycle (typically a week). So on a typical day, only 2 or 3 of the DLEs will get a level 0 and on average your daily backups will be 1/7th of your 400GB or about 60GB/day. I have heard of this but I thought that you can only use a directory rather than a partition for a level 0 backup. If I need daily L1 backups, is it still possible with the above scheme? If it is, then I think thats definitely the way I will go! Thanks again, Don
