backup order and starttime
The starttime option works for making sure a backup occurs AFTER a certain time, but how can you make sure one occurs BEFORE a time? Do you have to specify a later starttime for every disk except the one you want to get backed up first? For example, if amanda starts running at 10pm, and some files get updated at midnight that you want backed up that night, you can give them a starttime of 12:30 or so. But if something gets changed at 3am and you want to backup the current data instead of the 3am data, how do you ensure that it gets backed up early enough in the run so that the data doesn't change during the backup and cause errors? Thanks for any insight, Frank --- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
odd 'selfcheck request timed out' problem
After installing and using Amanda without any problems not solvable by some RTFM'ing, I'm now stuck. My server is a recently upgraded Solaris box running 2.4.2. All my working clients are also Solaris but running the 2.4.1p1 version. The problem child is a new RH Linux 6.2 box that I just compiled and installed the same 2.4.2 source on. It appears to be making the connection but is not completing for some reason. The selfcheck.debug and amandad.debug from the client are included below. There is a firewall inbetween but it is currently set to allow all UDP traffic between the two hosts and it is not logging any rejected packets so I don't think it is the problem. Any clues would be appreciated. Thanks, Frank selfcheck.debug: /usr/local/libexec/selfcheck: version 2.4.2 checking disk /etc: device /etc: OK selfcheck: pid 26303 finish time Wed Nov 29 11:59:35 2000 amandad.debug: amandad: debug 1 pid 26302 ruid 999 euid 999 start time Wed Nov 29 11:59:35 2000 amandad: version 2.4.2 amandad: build: VERSION="Amanda-2.4.2" amandad:BUILT_DATE="Wed Nov 29 10:46:57 CST 2000" amandad:BUILT_MACH="Linux p4.hoovers.com 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unk nown" amandad:CC="gcc" amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/" GNUTAR="/bin/gtar" amandad:COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip" amandad:MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="p4.hoovers.com" DEFAULT_CONFIG="normal" amandad:DEFAULT_TAPE_SERVER="clone" amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/0bn" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY amandad:USE_AMANDAHOSTS CLIENT_LOGIN="backup" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" got packet: Amanda 2.4 REQ HANDLE 007-0005C6E8 SEQ 975520772 SECURITY USER backup SERVICE selfcheck OPTIONS ; GNUTAR /etc 0 OPTIONS |;bsd-auth;index;exclude-list=/export/home/backup/exclude.gtar; sending ack: Amanda 2.4 ACK HANDLE 007-0005C6E8 SEQ 975520772 bsd security: remote host clone.hoovers.com user backup local user backup amandahosts security check passed amandad: running service "/usr/local/libexec/selfcheck" amandad: sending REP packet: Amanda 2.4 REP HANDLE 007-0005C6E8 SEQ 975520772 OPTIONS ; OK /etc OK /usr/local/libexec/runtar executable OK /bin/gtar executable OK /etc/amandates read/writable OK /usr/local/var/amanda/gnutar-lists/. read/writable OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: got packet: Amanda 2.4 REQ HANDLE 007-0005C6E8 SEQ 975520772 SECURITY USER backup SERVICE selfcheck OPTIONS ; GNUTAR /etc 0 OPTIONS |;bsd-auth;index;exclude-list=/export/home/backup/exclude.gtar; amandad: It's not an ack amandad: sending REP packet: Amanda 2.4 REP HANDLE 007-0005C6E8 SEQ 975520772 OPTIONS ; OK /etc OK /usr/local/libexec/runtar executable OK /bin/gtar executable OK /etc/amandates read/writable OK /usr/local/var/amanda/gnutar-lists/. read/writable OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 26302 finish time Wed Nov 29 12:00:35 2000 -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
planner what if questions
Assuming a stable configuration that is configured to use a single tape per run, what happens as either more disks are added or the size of the data grows? It seems to do a good job of delaying or promoting dumps to accomodate fluctuations in the size of the disks, but if the total size is increasing over time, it will eventually be unable to back it all up. My question is, how will I be notified that this is occuring? Increasing numbers of 'full dump of xxx delayed' messages followed by appearances of 'last full dump of xxx overwritten in y days' ? Or will it give out some other warning? On a related note, if it all fits on one tape now and I change runtapes to 2, will it only use the second tape if it needs to or will it constantly be promoting dumps to fill the two tapes every day? Thanks for any insight, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
supported libraries database?
Is there a section in the FAQ-O-Matic that I didn't see containing lists of tape libraries known to work (or known not to work) with Amanda? Something along the lines of the linuxprinting.org database of how well various models of printers work with linux (http://www.linuxprinting.org/printer_list.cgi). It could be done similarly to the tateptypes, with notes of which changer script was used, modifications needed, or whether it wouldn't work at all. I'm in the market for a new library, and I'd prefer to narrow my search to only those that are known to work well with Amanda, without having to post to the list every few days asking 'what about the foo.com model X?'. In the meantime, anyone have any recommendations for a 2 drive 20-40 slot AIT library? Thanks, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Amanda + Linux 2.4.10 + Qualstar TLS-4440 = success
No question, just posting to get in the archives that this combination works. I originally started trying to use the scsi-changer tools for Linux (which also works controlling this library), but then saw Mark Holm's chg-qs-mtx script and ended up using that with mtx instead. If the FAQ-O-Matic gets resurrected, maybe a page can be added for libraries similar to the tapetypes section. When I was shopping around for a library I had to find a model number and do a search on the archives, and usually came up with very little. It would be much easier if there was a list of library/OS combos that worked (and the glue script used), a list of ones that worked with hacked up scripts (and an archive of the scripts) or with limited functionality, and a list of those combinations known not to work. This would make it much easier for Amanda users to upgrade their hardware, as well as make it easier for non-Amanda users to decide if they could switch to Amanda with their current hardware. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Compile options vs config file (was: 2 questions : 1) Replace a tape in a set 2) Specify port range)
The real question is not why it is the way it is (unless there's one that prevents it from being changed), but what would it take to change it to read a config file at runtime instead of it all being compiled in? Editing a config file to change a path, device, or hostname would be much easier than a recompile. Especially when you find that the compile options you set don't work (portranges come to mind, amanda won't run if the tcp and udp ports are not lower or higher than some unknown value). You can aleady make quite a few changes with command-line options, so parsing a config file shouldn't be any harder than parsing the command line. Frank --On Friday, December 07, 2001 09:37:20 -0500 Joshua Baker-LePain [EMAIL PROTECTED] wrote: On Fri, 7 Dec 2001 at 9:06am, Eric Veldhuyzen wrote So please explain to me, what is so great about setting this all at compile time instead of in a configuration file so that it can be determined at runtime? I certainly can't give a definitive answer to this. I *can* tell you that this question pops up every now and then, so you can search through the archives for previous discussions it. I was going to offer some guesses here, but it really wouldn't help. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Paralellism possible for offsite storage?
Even though the Amanda docs' recommendation for off-site storage is a separate config (always full, no record), I'm trying to minimize the client load and bandwidth while making a separate set of tapes for off-site storage. Is there a way to do either of the following: Write the same data to two drives simultaneously? Filling the tape might be an issue, but I guess if you hit EOM on either drive you could restart the current image on both. Leaving level 0s on the holding disk after a write so that something like amflush could make another tape of it? Some of my backups are across a WAN and take several hours, dragging the data across twice seems like a gross inefficiency. I could just make direct copies of the tapes, but two separate writes has better odds of having at least one good one. Thanks, Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Amanda install reality check
Forget about all fulls on weekend, incrementals weekdays Check your index files for Big Numbers. Make sure you can do a restore. Use Amanda in parallel with your existing backups until you are comfortable with your ability to restore your data. Frank --On Wednesday, February 06, 2002 16:26:44 -0500 Bort, Paul [EMAIL PROTECTED] wrote: 1. REBDA (Read Everything Before Doing Anything) 2. Be prepared to run the configure/install process a few times until you get it the way you want. 3. Remember to do both the server setup and client setup on the server. 4. Start by just backing up the backup server. 5. Start by changing tapes by hand. Add the changer once all the clients are working. 6. /tmp/amanda/*debug 7. Yes it's a complex install, but the reward is industrial-strength cross-platform backup and restore that you can hack to your specifications. (No Backup Exec bitterness here, no.) 8. Build your own. Whoever made the RPM or DEB didn't have your network in mind. Any other suggestions from the list? -Original Message- From: W. D. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 4:03 PM To: [EMAIL PROTECTED] Cc: KEVIN ZEMBOWER Subject: Re: Amanda install reality check Any hints, tips or gotchas that would be helpful for the 'uninitiated'? (Especially FreeBSD HP SureStore DAT 40) At 14:09 2/6/2002, KEVIN ZEMBOWER, wrote: For-what-it's-worth dept.: In the year that I've been a full-time Unix system administrator, I guess I've installed 40-50 different packages, mostly from source. Amanda was the second most time-consuming and difficult; only Xwindows was harder for me. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 gene [EMAIL PROTECTED] 02/06/02 01:49PM snip I seem to be really struggling to get this to work. I did think it would be easier than this ;-) /snip Gene Start Here to Find It Fast!© - http://www.US-Webmasters.com/start.htm -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Amanda install reality check
--On Wednesday, February 06, 2002 22:20:47 -0600 W. D. [EMAIL PROTECTED] wrote: At 16:46 2/6/2002, Frank Smith, wrote: Forget about all fulls on weekend, incrementals weekdays Does this mean do full backups each time? No. it just means you might need to change your mindset from 'traditional' backup methods, where you might run full backups on Friday night (or the 1st of the month or whatever) and incrementals on other nights, to letting Amanda intermingle full and incrementals on each run, thereby getting better use out of your tape capacity. Check your index files for Big Numbers. Big files? No, big numbers in front of each line in the index file, i.e.: 16230523 /export/home/myjunk instead of: /export/home/myjunk The numbers in front of each line are a result of using a bad version of tar, and if your index files contain them then you probably will be unable to restore much (if any) of your data. So if you see them, you better quickly get a known working version of tar and force a full backup of the affected filesystems ASAP. Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda install reality check
--On Thursday, February 07, 2002 13:13:37 +0100 Moritz Both [EMAIL PROTECTED] wrote: 2. Be prepared to run the configure/install process a few times until you get it the way you want. Inacceptable. Why the hell should OS software installs work the try and error way only? After reading the right documents (1.) I should be able to run configure, make and make install the correct way, maybe with a few options to configure, but not more. I agree with you, but Amanda has way too much config information compiled in that (in my opinion) is better suited for the config file. If the paths/users/portranges/etc were read from the config file then there would be little need for recompiling. Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
bad versions of tar, index files and restores
I ran across a machine using a bad version of tar (big numbers in the index files). That has been fixed, and a full backup is being forced tonight, but I'm wondering about backups on old tapes. I realize that I wouldn't be able to interactively use amrecover, but would a manual fsf and tar -x of a level 0 return a full backup of the directory, or is it all so much wasted tape? In other words, do corrupted indexes mean corrupted data or just partial incrementals? Just curious, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: question about amflush
--On Tuesday, February 26, 2002 20:47:41 +0100 Martin Oehler [EMAIL PROTECTED] wrote: What will happen, if I amflush all the backups in a holding disk to tape and the size of my backups is bigger than my tape capacity? Will amflush write on tape what's fitting, send a little error and everything is ok or will something bad happen? As I recall from my pre-changer days, it acts just like it does with amdump; it will send you a 'short write' error and ask for the next tape. Also, if your tape writes are slow (or you started late or whatever) and you don't think you will still be available to change the tape again after you run another amflush, you can leave the remainder on the holding disk until the next day after your backups run again (assuming you have space), and flush the rest tomorrow. However, you run a risk of needing to do a restore on files still in the holding disk (or having your holding disk crash), so the sooner you do your flushes the better. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: file too large
--On Wednesday, March 06, 2002 16:32:01 -0500 Charlie Chrisman [EMAIL PROTECTED] wrote: /-- countach.i /dev/sda3 lev 0 FAILED [data write: File too large] I get this for two of my clients? what does this mean? Probably that your Amanda server has a file size limit smaller than the size of the filesystem you are trying to back up on the client. Try setting chunksize in your amanda.conf to something your server can handle ( try 1 GB ). Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: file too large
I've never had amflush complain about chunks being cruft files. It writes them to tape and removes them. If amdump dies you might end up with cruft files (both chunks and full files), but an amcleanup followed by an amflush generally clears things out. Frank --On Thursday, March 07, 2002 12:30:54 -0500 Mike Cathey [EMAIL PROTECTED] wrote: Joshua, The annyoing thing about using this hack is that if you have to use amflush (something goes wrong), then it (amflush) gives you errors about removing cruft files for all of the files that split creates. An ingenious hack nonetheless... :) If you have the disk space, you could switch the holding partition to ReiserFS or maybe ext3 (it supports files larger than 2GB right?) I'm assuming his amanda server is running on linux... Cheers, Mike -- Mike Cathey - http://www.mikecathey.com/ Network Administrator RTC Internet - http://www.catt.com/ Joshua Baker-LePain wrote: On Wed, 6 Mar 2002 at 4:32pm, Charlie Chrisman wrote /-- countach.i /dev/sda3 lev 0 FAILED [data write: File too large] I get this for two of my clients? what does this mean? FAQ. Set your chunksize to something less then 2GB-32Kb. 1GB is fine -- there's no performance penalty. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: root-tar failing
Look in /tmp/amanda for runtar.*.debug file(s). In the debug file is the command line used to invoke tar, look for --exclude-from and make sure that the path and filename specified are as expected. If not, verify that your dumptype in amanda.conf includes exclude list exclude.gtar Good luck, Frank --On Friday, March 08, 2002 13:02:11 -0500 Jenn Sturm [EMAIL PROTECTED] wrote: -- I've configured my Linux box to backup my Irix box using tar, as recommended on this list. It works great for everything but the root paritition. I've tried dumptype comp-root-tar and root-tar, and it continues to fail. I tried creating an exclude.gtar file, and that doesn't seem to be helping any. Here's the contents of the exclude.gtar file. Does the hostname of the Irix box need to be in there? ./dev/fd ./tmp ./var/spool Here's the log from the failed backup: FAILED AND STRANGE DUMP DETAILS: /-- olympus/dev/root lev 1 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [olympus:/dev/root level 1] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - sendbackup: info end ? gtar: ./dev/fd: Cannot savedir: Function not implemented ? gtar: ./dev/fd: Warning: Cannot savedir: Function not implemented | gtar: ./tmp/.eventmond.cmd.sock: socket ignored | gtar: ./tmp/.eventmond.events.sock: socket ignored | gtar: ./tmp/.eventmond.info.sock: socket ignored | gtar: ./tmp/.mediad_socket: socket ignored | gtar: ./tmp/.mkpd_socket: socket ignored | gtar: ./tmp/.rtmond_socket: socket ignored | gtar: ./tmp/espdb.sock: socket ignored ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..TK/01: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/spool/90.olympus..OU: Warning: Cannot stat: No such file or directory | gtar: ./var/spool/lp/CMDSOCK: socket ignored | gtar: ./var/spool/postfix/private/bounce: socket ignored | gtar: ./var/spool/postfix/private/bsmtp: socket ignored | gtar: ./var/spool/postfix/private/cyrus: socket ignored | gtar: ./var/spool/postfix/private/defer: socket ignored | gtar: ./var/spool/postfix/private/error: socket ignored | gtar: ./var/spool/postfix/private/ifmail: socket ignored | gtar: ./var/spool/postfix/private/lmtp: socket ignored | gtar: ./var/spool/postfix/private/local: socket ignored | gtar: ./var/spool/postfix/private/rewrite: socket ignored | gtar: ./var/spool/postfix/private/smtp: socket ignored | gtar: ./var/spool/postfix/private/uucp: socket ignored | gtar: ./var/spool/postfix/private/virtual: socket ignored | gtar: ./var/spool/postfix/public/cleanup: socket ignored | gtar: ./var/spool/postfix/public/flush: socket ignored | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 3114987520 (2.9GB, 752kB/s) ? gtar: Error exit delayed from previous errors sendbackup: error [/usr/local/bin/tar returned 2] \ .---. | Jennifer Sturm | | System Administrator and Research Support Specialist | | Chemistry Department | | Hamilton College | | | | [EMAIL PROTECTED]| | 315-859-4745 | | www.chem.hamilton.edu | .---. | Duct tape is like the force. It has a light side, | | and a dark side, and it holds the universe together. | | -Carl Zwanzig | | | | | | One only needs two tools in life: WD-40 to make things| | go, and duct tape to make them stop. | | -G. Weilacher | .---. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: ERRROR: linux1: [access as amanda not allowed from amanda@Linux2.igorsputerfarm.local] amandahostsauth failed
--On Saturday, March 23, 2002 21:40:49 -0800 Mr Igor Vertiletsky [EMAIL PROTECTED] wrote: when I ran amcheck Linux1Set on the server I get this error: ERRROR: linux1: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed Whenever you get an error like that, look at the string containing the @, put what follows the @ on the left and what's before the @ on the right, and don't put the @ itself anywhere. For example, your error contains [EMAIL PROTECTED], so your line in .amandahosts should be: Linux2.igorsputerfarm.local amanda Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
effects of changing dumptype?
Will changing the dumptype of a filesytem in the disklist cause any problems later if I need to restore a backup using the previous dumptype, or does Amanda automagically figure out what was used? Should it only be done immediately before a level 0 or would it not matter if the incrementals were different from the full? I want to quit using compression on a few filesystems that don't compress well to save CPU, but have a few months worth of backups that are compressed. Also, would a switch between dump/tar handled the same way? Thanks, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: amrecover - I have obviously overlooked something
Also make sure you added lines for amandaidx (and amidxtape) in your inetd.conf (and /etc/services) and HUP'ed inetd. Frank --On Friday, April 05, 2002 11:05:36 -0500 Doug Johnson [EMAIL PROTECTED] wrote: .amandahosts contains the following: schroeder root hosts.allow contains the following lines for schroeder: ALL: 127.0.0.1 ALL: 192.168.4.98 I am assuming that it is amidxtape. The closest reference I can find is amidxtaped. I do not show a service running by this name though. Is amidxtaped called or is is supposed to be a service? Doug -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 10:35 AM To: Doug Johnson Cc: Amanda-Users (E-mail) Subject: Re: amrecover - I have obviously overlooked something On Fri, 5 Apr 2002 at 10:23am, Doug Johnson wrote ** AMRECOVER EXAMPLE * [root@schroeder amanda]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on schroeder ... amrecover: cannot connect to schroeder: Connection refused Do you have root listed in the .amandahosts on schroeder? Is amidxtape (or is it amandaidx) from schroeder allowed in hosts.allow? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: amrecover - I have obviously overlooked something
I'm not very familiar with xinetd, but yes, you need to have xinetd
be able to start those other two as well. Since my inetd.conf lines
are:
amanda dgram udp waitbackup /usr/local/libexec/amandad amandad
amandaidx stream tcp nowait backup /usr/local/libexec/amindexd amindexd
amidxtape stream tcp nowait backup /usr/local/libexec/amidxtaped amidxtaped
you should be able to set the xinetd fields accordingly (take note of
wait/nowait and tcp/udp differences.
Good luck,
Frank
--On Friday, April 05, 2002 11:48:50 -0500 Doug Johnson [EMAIL PROTECTED]
wrote:
I am running xinetd and this is the only file referencing amanda anything.
It is called amandad and it contains:
# default: off
#
# description: Part of the Amanda server package
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= operator
group = disk If I change this to root then
amcheck will fail.
groups = yes
server = /usr/local/libexec/amandad
}
I am assuming that I need one of these files for amandaidx and amidxtape. Is
this correct?
Doug
-Original Message-
From: Frank Smith [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 11:25 AM
To: Doug Johnson
Cc: Amanda-Users (E-mail)
Subject: RE: amrecover - I have obviously overlooked something
Also make sure you added lines for amandaidx (and amidxtape) in
your inetd.conf (and /etc/services) and HUP'ed inetd.
Frank
--On Friday, April 05, 2002 11:05:36 -0500 Doug Johnson
[EMAIL PROTECTED] wrote:
.amandahosts contains the following:
schroeder root
hosts.allow contains the following lines for schroeder:
ALL: 127.0.0.1
ALL: 192.168.4.98
I am assuming that it is amidxtape. The closest reference I can find is
amidxtaped. I do not show a service running by this name though. Is
amidxtaped called or is is supposed to be a service?
Doug
-Original Message-
From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 10:35 AM
To: Doug Johnson
Cc: Amanda-Users (E-mail)
Subject: Re: amrecover - I have obviously overlooked something
On Fri, 5 Apr 2002 at 10:23am, Doug Johnson wrote
** AMRECOVER EXAMPLE *
[root@schroeder amanda]# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on schroeder ...
amrecover: cannot connect to schroeder: Connection refused
Do you have root listed in the .amandahosts on schroeder? Is amidxtape
(or is it amandaidx) from schroeder allowed in hosts.allow?
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
--
Frank Smith
[EMAIL PROTECTED]
Systems Administrator Voice:
512-374-4673
Hoover's Online Fax:
512-374-4501
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: without tapes
--On Wednesday, April 10, 2002 13:56:02 -0500 Marc W. Mengel [EMAIL PROTECTED] wrote: On Wed, 3 Apr 2002, Juanjo wrote: Hi, Is it possible to run amanda without-tapes so it dumps only to holding disk? But what I mean is not to take off the tapes physically but disabling tape writing. I want to accumulate incrementals worth a week and flush them on friday to a tape... How can I do such a thing? Put /dev/null in for your tape device when running the amdumps, then set it to a real tape and do an amflush. Wasn't there a comment on this list before about using something non- existent (like /dev/nosuchdevice) instead of /dev/null because amanda was somehow 'aware' of /dev/null and would perform backups differently? You could just not have the correct tape in the drive and amanda will keep accumulating the backups in the holding disk. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Newbie question: amncheck - unary operator expected
--On Wednesday, April 10, 2002 14:26:34 -0500 Greg Wardawy [EMAIL PROTECTED] wrote: The current problem is that I'm getting the WARNING: tapedev is /dev/null, dumps will be thrown away but I have no tapedev /dev/null in my amanda.conf file. Here goes the beginning part of amanda.conf: changerfile /usr/local/etc/amanda/chg-scsi-linux changerdev /dev/sga tpchanger chg-zd-mtx I think you might also need tapedev specified in your amanda.conf, something like: tapedev /dev/nst0 # the no-rewind tape device to be used Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: multiple amdump per day overwrites level0 [long]
% Dumps: lev datestmp tape file origK compK secs 0 20020410 DailySet1-042 778770 479897 477 1 20020411 DailySet1-031654043151 $ amoverview config date 04 04 host disk 10 11 orion.pr /10 12 orion.pr /home10 11 *After the overwrite: amdump (tape04) l2/l1 (today) $ amadmin config find Scanning /usr/local/amanda/holdingdisk... date hostdisk lv tape or file file status 2002-04-11 orion.progiweb.home / 1 DailySet1-051 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-002 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-012 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-022 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-032 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-042 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-052 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-001 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-011 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-021 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-031 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-041 OK $ amadmin config info Current info for orion.progiweb.home /: Stats: dump rates (kps), Full: 655.0, 642.0, -1.0 Incremental: 783.0, 780.0, 776.0 compressed size, Full: 37.0%, 37.0%,-100.0% Incremental: 4.6%, 4.6%, 4.6% Dumps: lev datestmp tape file origK compK secs 0 20020410 DailySet1-041 492800 182109 278 1 20020411 DailySet1-051 65710 28604 23 2 20020411 DailySet1-042 17110 7831 Current info for orion.progiweb.home /home: Stats: dump rates (kps), Full: 1006.0, 1003.0, -1.0 Incremental: 4315.0, 4315.0, 4315.0 compressed size, Full: 61.6%, 61.6%,-100.0% Incremental: 66.0%, 66.0%, 66.0% Dumps: lev datestmp tape file origK compK secs 0 20020410 DailySet1-042 778770 479897 477 1 20020411 DailySet1-041654043151 $ amoverview config date 04 host disk 11 orion.pr /12 orion.pr /home11 No more level0, No warning, nothing ! Thank you and bye. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda overwrites level0 without warning
--On Thursday, April 11, 2002 03:37:15 +0200 Frederic Saincy [EMAIL PROTECTED] wrote: Hi, Frank Smith [EMAIL PROTECTED] writes: The planner logic might not be set up to handle this extreme case. I don't know very well amanda's internal and this is the occasion for me to look at the sources. If the planner can't, amdump must wonder: If i do this, can admin restore the system ?. If not, there is 2 solutions in an environment without tape changer: 1) do nothing 2) do a level0. I imagine all prefers the second solution. I gonna look at this extreme case further: i did it as a test, but imagine, for example, a bad written /etc/cronttab and the The_Big_Problem (r) once level0 was overwritten. Too bad. Bye. Even if it gave the warning it would do no good if it ran enough times before you read the daily reports, as the warnings won't stop it from overwriting the tape. If you aren't using a changer just append an mt offline command to your amdump command in cron and then Amanda can't overwrite a tape without your assistance. Once you get Amanda doing some real work it will probably become impossible to run through your entire set of tapes in a day, since Amanda won't run again if it is still running from the run before, and all the planners and dumpers take some time to complete. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Guidelines for using a tape library?
--On Thursday, April 11, 2002 03:26:08 + David Trusty [EMAIL PROTECTED] wrote: Hi, I have a Qualstar tape library, which has 20 tapes. The library can be configured to look like one massive tape drive, with the 20 physical tapes hidden from the host application. I can cause the unit to eject the current physical tape and load a new one by using the mt offl command. My question is this. Does anyone have any tips for using Amanda in this type of a configuration? In particular, I am interested in any tips regarding labeling of tapes, since when I advance the unit to the next physical tape, I cannot guarantee that it will still have an old Amanda label. What do you think? Thanks in advance! David Why not just leave it configured in its 'normal' state as a 20 slot changer? Then you can just tell Amanda what range of slots to use and amlabel the tapes in those slots. That's how I use our Qualstar 80 slot, and it is working fine like that. I don't think the 'just one really big tape' idea fits well with how Amanda works, but maybe someone else on the list can give some advantages to that approach. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Guidelines for using a tape library?
--On Thursday, April 11, 2002 04:21:10 + David Trusty [EMAIL PROTECTED] wrote: I am using the Qualstar under HPUX. Mine's on a Linux box. I haven't found a way to address the tapes individually. I see only two SCSI devices, whether I use the RANDOM or SEQUENTIAL modes on the Qualstar. Is that how yours works too? Does Amanda have some way of accessing the individual tapes? I'll verify with my docs at work tomorrow, but I believe that 'random' makes it work like a true changer and 'sequential' behaves more like a stacker. Amanda has changer scripts that can be configured to find and use the correct tape(s) for each run. Mine shows three devices, one is the changer mechanism (the scsi driver sees it as a Qualstar) and the other two are the two tape drives in the unit (the scsi driver shows those two as Sony). Look in your boot messages to see if you have something similar (its been many years since I've touched HPUX, someone else will have to chime in on how to probe scsi devices on HPUX). You may also need the mtx drivers to control the changer (http://mtx.sourceforge.net/) if HPUX doesn't have enough builtin support. Make sure you can load/unload/move tapes from the command line before you even bother with the amanda changer scripts or you will waste a lot of time and get very confused. Also, if a dump image is bigger than one physical tape, I don't think amanda would work. I'm just starting on the task now, so I'm not sure that would be the case. What is your experience in this area? With the released version that is true, although you can use GNU tar and backup subdirectories that are each smaller than a tape. I believe tape-spanning is in development but I don't know an ETA. I personally prefer tar over dump, but many on this list have the opposite opinion. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Order of dumps? (Want large ones first, I think)
Dave wrote: ... it would be very useful if I could tell it to write the latest backups of, say, the NFS server's /home and the partition that holds the company's primary database first ... The schedule is passed from planner to driver via a normal Unix shell pipeline in the amdump script. You could insert a filter of your own to fake the estimated time field down to zero to trick driver into doing important things first. Or, at 2.4.3, we could probably add a new dumporder flag to do things by priority, or something like that. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Wouldn't it be simpler to just set a 'starttime' value for all the 'unimportant' disks so that all the dumpers will do the 'important' ones first? FRank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Please help -- planner askfor: lev out of range -1..10: 10
--On Monday, April 22, 2002 11:42:46 -0600 Brashers, Bart -- MFG, Inc.
[EMAIL PROTECTED] wrote:
Hi Frank, thanks for your response!
To summarize what I think you've said, you are trying to back up
~200GB on a 40GB tape, and are dynamicly rewriting your disklist
entries into ~25GB chunks. You don't say how many tapes you have
in your runtapes and tapecycle, or if you have some kind of changer
configured (even if it is chg-manual).
The relevant parts of my amanda.conf file are:
dumpcycle 3 weeks
runspercycle 15
tapecycle 17 tapes
define dumptype mydumptype {
program GNUTAR
compress none
} (plus more of the usual options)
runtapes 1
tapedev /dev/nst0
I'm trying to avoid using chg-manual, and let amanda run on 1 tape per
night. I'd like to be able to use my tape drive for other non-amanda tasks
during the day ;-).
You could still use it during the day, as long as amdump or amcheck
weren't trying to use it. If you really don't want to set up a changer,
and if you have enough holding disk, you could lie to Amanda about
your tapetype and say it is 80GB, then planner will dump up to that
much. You will get a tape error in your daily report (since it will
hit EOT around 40GB), but you can then amflush it whenever it is
convenient.
FAILURE AND STRANGE DUMP SUMMARY:
beowulf/home/proj/mm5 lev 1 FAILED [dump larger than tape, skipping
incremental]
beowulf/var/mail lev 1 FAILED [dumps way too big, must skip
incremental dumps]
(and so on, for ~30 or so directories)
This says an incremental of /home/proj/mm5 is 40GB so it can't write
it to tape. The /var/mail error (dumps way too big) indicates that
the day's backup can't fit on the tapes allotted to it, so Amanda is
having to skip backups of those filesystems.
Ok, I'm confused. Each of these errors dump larger than tape and dumps
way too big refers not to the overall amanda run, BUT TO THAT PARTICULAR
DISK? That should be impossible. Each night _before_ amanda is run, my
ammakelist script would break up /home/proj/mm5 into sub-directories that
are each less than 25Gb. So it's impossible for the lev 1 to be larger than
25Gb, and it should fit on a tape. Not necessarily this tape, since the
amount to be written on any one night is generally larger than my
tapedrive...
[root]% du -h /var/spool/mail/
360k/var/spool/mail
There's no way the lev 1 on /var/spool/mail is larger than a tape. So these
errors dump larger than tape and dumps way too big must refer to the
total amount dumped to tape.
dumps way too big does refer to total backup size, but the other
warning, dump larger than tape refers to the individual filesystem.
Check the size of /home/proj/mm5. Perhaps its size changed between
the time your disklist was created and when amdump ran.
Increasing runtapes should help (although you may have to adjust
tapecycle and runspercycle unless you have extra tapes).
So my idea that I should add tapes (I recently went from 12 to 17) was
heading in the right direction. I have extra tapes in-house. Can I go to
dumpcycle 4 weeks
runspercycle 20
tapecycle 22 tapes
runtapes 1
or do I have to go to something like
dumpcycle 2 weeks
runspercycle 10
tapecycle 22 tapes
runtapes 2
Unless you can use compression to get more on a tape, it will take
quite a while to get everything backed up if you only use one tape
(5 or 6 days to do the first set of fulls without any incrementals).
I prefer having more than one full backup around, so I would prefer
the shorter dumpcycle. If your data doesn't change too much it might
only require two tapes for the first couple of weeks and then it
will level out and fit on one tape again. Definitely look into
compression, some data (especially text) compresses amazingly well.
If you are using hardware compression you may be able to increase
the size in your tapetype if you are not getting EOT errors.
much trimmed
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Increasing number ot tapes used.
--On Monday, April 22, 2002 20:23:01 +0100 Niall O Broin [EMAIL PROTECTED] wrote: I'm not long using Amanda (haven't finished a full dumpcycle yet) and I've decided that I'd like to use more tapes than I initially decided. I have dumpcycle 2 weeks runspercycle 10 tapecycle 14 tapes and I'd like to bump tapecycle up to 20 tapes or even a couple more because: a) I have the tapes already :-) b) Even if my backup load expands to nearly my full capacity (tape size * runspercycle) with tapecycle = 2 * runspercycle I'll always have 2 full dumps available. Is there any problem with changing tapecycle now ? No, you can increase it anytime, but if you like to feed your tapes in numerical order either add them in when it is about to use your first tape or follow the directions in the archive on editing your tapelist. Also, don't forget to label the new tapes (the first option is much easier, IMHO). Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: What to do when tape is full?
--On Tuesday, April 23, 2002 08:52:51 -0400 Joshua Baker-LePain [EMAIL PROTECTED] wrote: On Tue, 23 Apr 2002 at 1:30pm, Toralf Lund wrote Wouldn't append support be easy to implement? Seems to me that most of the code must be there already (since Amanda writes several dumps to one tape in its normal mode of operation.) Lack of append support is a design decision, AIUI. The thought is that it's better to not use some of a tape than to overwrite backups because, for some reason, the tape rewound itself when you weren't looking. Safety and redundancy are paramount in backups, not tape usage. YMMV, but that's the design decision made with amanda (which I happen to agree with). If you want to fill tapes to the max, then add the disk usages up by hand and 'amadmin force' enough filesystems each night to fill the tape. Or leave the tape out of the drive and let it go to to the holding disk, then amflush whenever you have a full tapes worth. As someone who has learned a lot the hard way, I concur with the 'no append' design decision. There is no way to redo a previous backup, and the one time you accidently overwrite a tape will be the time you most need a file that only existed on that tape. Power glitches, I/O errors, SCSI resets, other users, and various other things can easily cause a drive to rewind with your noticing, and they would all be fatal to your data. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Elaboration on tape changer behavior
--On Wednesday, April 24, 2002 13:23:08 -0700 John Koenig [EMAIL PROTECTED] wrote: Can those with experience with changers elucidate some details for me? What is the AMANDA/amtape policy when rolling over from the last tape to the first tape in my Backup Set? My config specifies the following: dumpcycle 2 weeks runspercycle 5 tapecycle 10 tapes In my changer the slot numbering is zero-based. So I have tapes in slots 0 thru 9. Since I do not have a working changer script between amtape and my tape library manager sw layer, I am manually running robot load commands (etc...). I have three general questions: 1) Will amtape manage the rollover from tape slot 9 to slot 0, and, in general, do the right thing? Is there any manual intervention on tape slot rollover? For example. must the admin tell AMANDA that it is OK to write over a tape (tape 00)? Yes, it knows to roll over from the last tape to the first, but see #3 below. 2) Is there any important information omitted from the document, AMANDA Tape Changer Support? Can it generally be trusted to specify the correct interfaces? I have found that some of the tape changer implementations in the AMANDA distribution do not correctly follow the API specifications in that document. I'll pass on this one. 3) Do people with single tape robots use multiple tape magazines; swapping them out after one tapecycle... as in Magazine A then Magazine B, then back to A? Or do some people just keep running tapes through the magazine, ad infinitum? Or do most people leave the same magazine installed until the tapes wear out? I presume this last question (3) is largely dependent upon one's goals... So if anybody cares to elaborate on changer methodologies used to achieve particular goals, then I would be grateful. Other will surely benefit as this is not an area that is discussed in much depth. You need at least a couple more tapes, since with your current setup if you ever have a tape error or an extra-large backup and need to amflush, it would need to overwrite an active tape. The other answer is, as you suspect, 'it depends'. If you do offsite rotations of your tapes, it is easier to do it a magazine at a time. If your robot holds several magazines you might want to cycle through one set for onsite backups and have a different Amanda config do offsite backups on another magazine that you replace each time. Even if you don't do offsite, swapping tapes a magazine at a time is much safer than swapping tapes. The tapes will last longer in a magazine (less likely to get banged around, dropped, dirtied, etc.), and you have fewer chances to get the tapes out of order. Magazines also stack better and are easier to store. I'm assuming your magazines can be swapped easily, if not then it might not be as favorable to swap them. Unfortunately, some vendors see magazines as an income opportunity and charge way too much for them. Also, do you need archival backups (to retrieve a file that was only around last June), or only the ability to restore what was there in the last few days or weeks. With your config, if a backup fails for some reason, and a file you need wasn't on the system in the last week, you may not have it (as you are just now about to overwrite your first tape, and whatever fulls it contains cannot be recreated with the following 4 incrementals so all you can recover from those filesytems of that week is the changed files. If the full of those filesystems can't be read from the one this week (due to a bad tape or whatever) you are SOL. I would recommend making sure you always have at least two full backups of everything, even if there are a couple of errors during your cycle. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amcheck problems
--On Sunday, April 28, 2002 09:46:55 -0600 Trevor Morrison [EMAIL PROTECTED] wrote: HI, I am getting the following when running amcheck Daily on my system: Amanda Tape Server Host Check - ERROR: tapelist dir /usr/local/share/amanda/Daily: not writable This is bad too. Amanda needs a place to write a list of tapes so it knows which tapes are to be used next. Probably just a permissions problem, make sure the user Amanda runs as can write here. Holding disk /amanda: 404144 KB disk space available, that's plenty (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/local/share/amanda/Daily/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/local/share/amanda/Daily/index: does not exist Server check took 9.687 seconds Amanda Backup Client Hosts Check ERROR: stud.hailix.com: [can not read/write /usr/local/var/amanda/gnutar-lists/.: No such file or directory] Client check: 1 host checked in 0.028 seconds, 1 problem found What is the structure of the file that amanda is looking for in gnutar-lists? I mean is it a text file and if it is could someone give me an example of what it looks like. I am using the dump type root-tar in the amanda.conf file and I did not alter it. I cannot get my backups to work until I can get this problem solved. TIA. Trevor gnutar-lists is supposed to be a directory, not a file. Amanda (well, probably GNU tar) saves files there containing times that files were backed up so it knows what is 'new' for incrementals. Just create the directory (as the Amanda user) and all should be well. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amcheck
--On Sunday, April 28, 2002 22:24:23 -0600 Trevor Morrison [EMAIL PROTECTED] wrote: HI, If I get the following error on the host being down where is the first place I should check to correct it?: Amanda Tape Server Host Check - Holding disk /amanda: 406040 KB disk space available, that's plenty ERROR: cannot overwrite active tape Daily-001 (expecting a new tape) You'll need a new tape before you can do a successful backup (unless it will all fit in your holding disk).. NOTE: skipping tape-writable test NOTE: info dir /var/etc/amanda/Daily/curinfo: does not exist NOTE: it will be created on the next run Server check took 9.780 seconds Amanda Backup Client Hosts Check WARNING: stud.hailix.com: selfcheck request timed out. Host down? Client check: 1 host checked in 29.999 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) I have already checked the xinetd.d/amanda file and corrected it. TIA. Trevor Have you looked through the suggestions in the FAQ-O-Matic? The amcheck page is at http://amanda.sourceforge.net/fom-serve/cache/16.html I think there are also some tests in the docs directory in the distribution. Check all that, and you still have no luck, try to give us more details, such as if the problem client is the same host as the server, the contents of /tmp/amanda/amandad.debug on the client, if there is a firewall in between, and the output from tests you have tried (such as what happens if you run amandad from the command line on the client as the Amanda user). Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Can I backup to disk Only
--On Monday, April 29, 2002 00:36:24 -0500 Shonne Beavers [EMAIL PROTECTED] wrote: I want to backup to the holding disk only and manually send to tape. Is that possible? I am new to Amanda, but I have heard how reliable it was and want to it. Thanx in advance. If the holding disk is large enough and if the reserve option is set to allow fulls to disk, if the correct tape is not in the drive all the backups will go to disk, which you can amflush later to tape. You might want to search the list archives for holding disk, as it does have some detractors on the list (due to things like a disk failure on the holding disk wiping out your backups). If you are going to always amflush the next day, it is low risk, but if you are thinking of leaving a week's worth of backups on disk before you flush in order to fill up a tape, then the risk is much greater. Just my opinion, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: what to do if I put in the wrong tape
--On Monday, April 29, 2002 10:11:56 -0600 John Rosendahl [EMAIL PROTECTED] wrote: Is there a procedure that people use when they forget to replace the tape/put in the wrong tape. Amanda stalls when this happens, is there a way to get it going again(with the right tape in of course). Normally Amanda writes none, some, or all of the backups to the holding disk (depending on its size and reserve setting) if the correct tape is unavailable, and then exits. What exactly do you see when it stalls? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda increment level?
--On Tuesday, April 30, 2002 01:21:20 +0300 Alexander Belik [EMAIL PROTECTED] wrote: I can't understand how amanda increment level? For example --disklist- www sda1 comp-high # / www sda2 comp-user-tar # /home www sda3 comp-root # /usr www sda5 comp-user-tar # /var --- dumpcycle 7 days runspercycle 9 tapecycle 1 tapes Amanda first night made llevel 0 next night made level 1 next day some partitions stay on level 1 some begin from level 0 and rest made level 2? -- [EMAIL PROTECTED]ICQ: 41776461 2:465/207@Fidonet Alexander Belik http://www.vnet.dn.ua[EMAIL PROTECTED] You plan to run Amanda 9 times in 7 days using only 1 tape? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Qualstar 4222 Tape Library
--On Tuesday, April 30, 2002 16:49:26 +0200 Toralf Lund [EMAIL PROTECTED] wrote: On 26/04 2002 16:47 Frank Smith wrote: --On Friday, April 26, 2002 12:42:31 +0200 Toralf Lund [EMAIL PROTECTED] wrote: Has anyone used Amanda with the Qualstar 4222 tape library? We have a customer that want to use one for backup, and we probably have to help with the setup... We use a Qualstar 4480 (a bigger model in the same family) and it works fine with Amanda. What does your tape changer config look like? I'm using the chg-qs-mtx script which Mark Holm modified from the chg-mtx script and posted to the list (search for Qualstar TLS 4212 in the archives and you'll find it, also get the fix in the followup). Relevant configurations are included below, modify to suit Before you get too involved in the changer script, make sure you can move tapes around using mtx from the command line, otherwise you will get very frustrated. Also, I don't really know *anything* about tape libraries, but I need to provide some useful information to a customer who has one, but don't know what to do with it, so any kind of input is welcome. System is a small server running Red Hat Linux 7.2. Libraries just let you further automate your backups, they don't do anything that you couldn't do sitting in front of a tape drive with a pile of tapes. Since there generally isn't someone next to the drive at all times, having a library lets you automate multi-tape backups and run backups nights, weekends, and holidays. They also keep your tapes from getting banged around so much. Good luck, Frank in amanda.conf= tpchanger chg-qs-mtx # tape-changer glue script tapedev /dev/nst0 # the no-rewind tape device to be used changerdev /dev/sg0 # the tape-changer device changerfile /usr/local/libexec/chg-qs-mtx.conf /usr/local/libexec/chg-qs-mtx.conf= # Number of the tape drive in changer as seen by MTX chgtapedev 0 # Barcode reader ? havereader 1 # First slot in Library to be used firstslot 1 # Last slot in Library to be used endslot 55 # Slot where the cleaning tape resides cleanslot 80 # How often do I clean (accesses of tape drive) cleancycle 1000 # Do we need to eject the tape: 1 - Yes, 0 - No needeject 1 = -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: problems with GNUtar and --sparse
Look at the GNU tar manual (not the man page) for a good explanation of what sparse files are and how --sparse handles them: http://www.gnu.org/manual/tar-1.12/html_node/tar_121.html Frank --On Tuesday, April 30, 2002 15:49:24 -0700 Luke Miller [EMAIL PROTECTED] wrote: I am having some problems with GNU tar and amanda. I am running amanda 2.4.2p2 with gnutar 1.13.19 (I have also tried 1.13.25) on Solaris 8 (sparc). The command line that I am running is: /usr/local/bin/tar --create --file /tmp/conf.tar --directory /export/raid/conf --one-file-system --sparse --listed-incremental /private/amanda/var/amanda/gnutar-lists/nfs-1c-bvtn_export_raid_conf_5.new --totals . Replace /tmp/conf.tar for - when it is run by amanda. When I run this is produces a tar file that is about 5 megs in size and contains 2556 entries. If I run the same command line but without the --sparse I get a tar file that is about 23 megs and has 9535 enties. So, what is the --sparse doing here that is causing it not to backup all the files? What is the best way around this? I would hack the code to remove --sparse but I want to have an understanding of what it is doing first. Thanks, Luke * * Luke Miller Unix System Administrator * * Integra Telecom 503-748-4549 * * -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: problems with GNUtar and --sparse
--On Tuesday, April 30, 2002 16:24:35 -0700 Luke Miller [EMAIL PROTECTED] wrote: That's helpful but I don't think it explains what I am seeing. When I have the --sparse option turned on, tar does not backup all the files that it should. There is at least one directory where it doesn't backup ANY files at all in it. Sorry, I missed the part about the number of files being less, I just thought the total size was less than expected. I have no idea how --sparse could affect the nuber of files. Good luck, Frank Thanks, Luke Look at the GNU tar manual (not the man page) for a good explanation of what sparse files are and how --sparse handles them: http://www.gnu.org/manual/tar-1.12/html_node/tar_121.html Frank --On Tuesday, April 30, 2002 15:49:24 -0700 Luke Miller millerlu@integraonli ne.com wrote: I am having some problems with GNU tar and amanda. I am running amanda 2.4 .2p2 with gnutar 1.13.19 (I have also tried 1.13.25) on Solaris 8 (sparc). The command line that I am running is: /usr/local/bin/tar --create --file /tmp/conf.tar --directory /export/raid/c onf --one-file-system --sparse --listed-incremental /private/amanda/var/amanda/ gnutar-lists/nfs-1c-bvtn_export_raid_conf_5.new --totals . Replace /tmp/conf.tar for - when it is run by amanda. When I run this is produces a tar file that is about 5 megs in size and con tains 2556 entries. If I run the same command line but without the --sparse I get a tar file th at is about 23 megs and has 9535 enties. So, what is the --sparse doing here that is causing it not to backup all th e files? What is the best way around this? I would hack the code to remove --sparse but I want to have an understanding of what it is doing first. Thanks, Luke * * Luke Miller Unix System Administrator * * Integra Telecom 503-748-4549 * * -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: ./configure error with amanda 2.4.2
Make sure you also have the readline 'development' package installed, as Amanda needs to find the header files so it can properly link to the libraries. Also, if it is installed in an odd place configure won't find it, so you would need to add some configure options. Frank --On Thursday, May 02, 2002 02:38:25 +0200 [EMAIL PROTECTED] wrote: Hi :-) I am trying to install Amanda 2.4.2 on my SuSE 7.2 Linux with kernel 2.4.18 but got stopped right away when running ./configure --with-user=amanda --with-group=disk. It tells me: Checking in readline in -lreadline--- (cached) No configure: warning: ***No readline library, no history and command line editing in amrecover ! configure: warning: ***vtblc headers not found - no QIC volume table support*** I have readline installed - when I enter rpm -q readline it returns readline-2.05-21 What's wrong ? -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Tape rotation problem?
--On Thursday, May 02, 2002 07:29:30 -0500 Michael Davis [EMAIL PROTECTED] wrote: I have amanda cofigured to use the tapeio code. I am running amanda-2.4.3b3 on all servers and clients. Attached is my amanda.conf and my changer.conf. Here is what amcheck reports: Amanda Tape Server Host Check - Holding disk /backups: 210982006 KB disk space available, using 210982006 KB amcheck-server: slot 7: date 20020422 label DailySet107 (active tape) amcheck-server: slot 1: date 20020502 label DailySet101 (active tape) amcheck-server: slot 2: date 20020422 label DailySet102 (active tape) amcheck-server: slot 3: date 20020422 label DailySet103 (active tape) amcheck-server: slot 4: date 20020426 label DailySet104 (active tape) amcheck-server: slot 5: date 20020427 label DailySet105 (active tape) amcheck-server: slot 6: date 20020430 label DailySet106 (active tape) ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 0.582 seconds Amanda Backup Client Hosts Check Client check: 4 hosts checked in 0.103 seconds, 0 problems found (brought to you by Amanda 2.4.3b3) How do I get amanda to automattically resuse the tapes? Change your config and/or get more tapes. In your amanda.conf you have: dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation You are saying you only need one level 0 every 4 weeks (dumpcycle) and during that time Amanda runs 20 times (runspercycle) using a set of 25 tapes (tapecycle). Since your changer is defined with 7 slots and Amanda has now used all those tapes, it is looking for the 8th tape which doesn't exist in the changer. It will later want tapes 9 - 25 before it will overwrite tape 1. If you really have 25 tapes, then you should put tapes 8 - 15 into your changer in place of tapes 1 - 7. If you really have only seven tapes then I would suggest changing the dumpcyle to 1 week, runspercycle to 5, and tapecycle to 7. If a daily run doesn't fit on one tape, then you would need more tapes. Actually, you need more tapes anyway so you would have more than one level 0 of a disk on tape in case of a read error during a restore. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Tape rotation problem?
--On Thursday, May 02, 2002 09:41:03 -0500 Michael Davis [EMAIL PROTECTED] wrote: Thanks for the help that fixed the problem. Based on your reply though it seems I had my cycles incorrect. I changed them to your recommendation, however, what I am trying to achieve is a 1 week cycle where there is a full backup on Sundays and incremental throughout the week. I thought the Amanda schedule did this by default when you setup the cycles correctly(which I now have done) Am I wrong? Amanda's normal way of doing things is to spread out the fulls across the dumpcycle so that it uses about the same amount of tape each day. This also helps level out the time each days backup takes and lets you backup more since it doesn't have to fit it all in one run. Having said that, when you first configure Amanda it knows that everything in your disklist needs a full, so your first run will be large and some disks may not make it to tape the first day, but then Amanda will start doing some fulls somewhat ahead of the dumpcycle schedule so they will eventually end up scattered throughout the cycle. This is probably the hardest part about switching to Amanda if you are used to doing weekend fulls and weekday incrementals. If you really, really want to force it to what you planned, then you need two Amanda configs, one that uses a dumptype of noinc that you only run on Sunday and one that uses nofull that runs weekdays. Check the archives since there are other details involved. This question comes up fairly often, but since I don't use Amanda that way I don't remember the details. Also, I saw no mention of the levels for the dumps in the man page for Amanda. Where can I find more information about these levels? The levels are just what dump (and gnu tar) use. Level 0 is a full, level 1 is the files changed since the last level 0, level 2 is files changed since the last level 1, etc., up to 9 or so. The more levels you use, the more tapes you need to read to do a restore. Amanda has several options relating to levels in its man page, search for full, incr, and bump to get started. Good luck, Frank Thanks, Michael Davis [EMAIL PROTECTED] Chief Technical Officerhttp://www.urbancom.net Urban Communications, Inc. Phone: 708-687-2090 Cell: 708-243-2850 After three days without programming, life becomes meaningless. - The Tao of Programming - Original Message - From: Frank Smith [EMAIL PROTECTED] To: Michael Davis [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, May 02, 2002 9:29 AM Subject: Re: Tape rotation problem? --On Thursday, May 02, 2002 07:29:30 -0500 Michael Davis [EMAIL PROTECTED] wrote: I have amanda cofigured to use the tapeio code. I am running amanda-2.4.3b3 on all servers and clients. Attached is my amanda.conf and my changer.conf. Here is what amcheck reports: Amanda Tape Server Host Check - Holding disk /backups: 210982006 KB disk space available, using 210982006 KB amcheck-server: slot 7: date 20020422 label DailySet107 (active tape) amcheck-server: slot 1: date 20020502 label DailySet101 (active tape) amcheck-server: slot 2: date 20020422 label DailySet102 (active tape) amcheck-server: slot 3: date 20020422 label DailySet103 (active tape) amcheck-server: slot 4: date 20020426 label DailySet104 (active tape) amcheck-server: slot 5: date 20020427 label DailySet105 (active tape) amcheck-server: slot 6: date 20020430 label DailySet106 (active tape) ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 0.582 seconds Amanda Backup Client Hosts Check Client check: 4 hosts checked in 0.103 seconds, 0 problems found (brought to you by Amanda 2.4.3b3) How do I get amanda to automattically resuse the tapes? Change your config and/or get more tapes. In your amanda.conf you have: dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation You are saying you only need one level 0 every 4 weeks (dumpcycle) and during that time Amanda runs 20 times (runspercycle) using a set of 25 tapes (tapecycle). Since your changer is defined with 7 slots and Amanda has now used all those tapes, it is looking for the 8th tape which doesn't exist in the changer. It will later want tapes 9 - 25 before it will overwrite tape 1. If you really have 25 tapes, then you should put tapes 8 - 15 into your changer in place of tapes 1 - 7. If you really have only seven tapes then I would suggest changing the dumpcyle to 1 week, runspercycle to 5, and tapecycle to 7. If a daily run doesn't fit on one tape, then you would need more tapes. Actually, you
Re: I need help getting amanda working
Is '0' a valid number for runspercycle (that's a rhetorical question for the developers on the list)? You're telling planner that Amanda is run 0 times during the 5 days of your dumpcycle. It might not be the reason you get no output, but if you're trying to do what I think you are (i.e. run Amanda 5 days a week), you should have a dumpcycle of 7 and a runspercycle of 5. You probably also want a larger tapecycle, since with 5 tapes for 5 runs you will be overwriting the only level 0 of some of your filesystems each day, and if it should fail you will not be able to restore all of your disks. Frank --On Monday, May 13, 2002 15:35:32 -0700 Doug Silver [EMAIL PROTECTED] wrote: On Mon, 13 May 2002, Andrew Falanga wrote: That's just it. I'm not getting any error's. Nothing. I'm not getting any mail sent to user amanda. I've thined out the comments from my conf file, and I'm pasting that in to this message. I don't get it. Andy org TestSet1 # your organization name for reports mailto afalanga # space separated list of operators at your site 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 5 days# the number of days in the normal dump cycle runspercycle 0 # the same as dumpcyle tapecycle 5 tapes # the number of tapes in rotation 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 est. runtapes 1 # number of tapes to be used in a single run of amdump [snip] logdir /var/amanda/log # log directory infofile /var/amanda/log/TestSet1/curinfo # database filename indexdir /var/amanda/log/TestSet1/index # index directory [snip] Well your configuration looks okay. So when you run 'amcheck TestSet1' it checks out okay and 'amdump TestSet1' nothing happens?? I'd look in the various configuration areas, i.e. /tmp/Amanda and /var/amanda/log/TestSet1 for information as to what Amanda is doing -- or not doing. -- ~~ Doug Silver Network Manager Urchin Corporationhttp://www.urchin.com ~~ -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: mtx
Why don't you ask about what you're trying to accomplish so that we can better help instead just giving yes/no answers? For example, if you tell us the platform you are using for your backup server and the library you have (or want), I'm sure you will get some recommendations on the best changer script to use. Frank --On Wednesday, May 15, 2002 14:02:03 -0400 fil krohnengold [EMAIL PROTECTED] wrote: Next question - folks using chg-mtx with it? -- fil krohnengold systems administrator - IT american museum of natural history [EMAIL PROTECTED] -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: 500 Access not allowed: (but should be)
--On Thursday, May 16, 2002 14:29:15 + Kevin Hancock [EMAIL PROTECTED] wrote: Hi I cannot recover my amanda backups. My tape server is missie, this is where the tape drive and amanda server is. I am trying to run amrecover from a client. These are Redhat systems. On the server amanda runs as user amanda and on the client amanda runs as operator. I installed from RPM and this is the default. Redhat 6.2 username is operator Redhat 7.2 username is amanda [root@ /root]# amrecover -t missie.doamin.com -s missie.doamin.com -C DailySet1 AMRECOVER Version 2.4.1p1. Contacting server on missie.doamin.com ... 220 missie AMANDA index server (2.4.2p2) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed In the server's (missie) ~amanda/.amandahosts you need: grumpy.doamin.com root The [access as X not allowed from Y@Z] message is telling you how Amanda is actually trying to be authenticated, so just put whatever shows as Y and Z in the message in the .amandahosts file in the reverse order like so: Z Y I have added clientnameroot Almost, but the client is apparently presenting itself as clientname.domin.name clientnameamanda clientnameoperator to the /home/amanda/.amandahosts file on the server but still I get this error. From what I can see user amanda is allowed from grumpy. Any ideas why this is happening? Thanks Kevin Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Pointer to info on holding disk requirements?
As with most things, it all depends on what you want to accomplish. You could get by without any holding disk, forcing all your backups to go directly to tape, but this would take longer since whenever the tape drive caught up with the data stream it would have to stop and reposition itself. Any tape error would cause the backups to not be done. Also, you need a much longer backup window since the backups would have to be don serially. With a holding disk as large as one or two of your largest partitions, Amanda can spool the backup images to the holding disk, and when an image is complete Amanda can flush it to tape in one continuous stream while collecting other images on the holding disk. This speeds up your backups and shortens your required backup window. If a tape error occurs then whatever complete images that will fit on the holding disk will continue and can be flushed to tape later. With a holding disk as large as your complete backup, you will still get a complete backup run even if you forget to put a tape in the drive. This also helps if there is a tape error early in the run and on holidays. You can also increase the number of dumpers running in parallel to shorten your backup window. There are also people on the list with large tapes and small daily runs that let backups accumulate on the holding disk until they have a tape's worth, and then flush the collected backups to tape. There have been discussions on the list on risks vs. merits of leaving backups on disk for extended periods of time, though. Hope this helps, Frank --On Monday, May 20, 2002 10:02:31 -0500 Brad Felmey [EMAIL PROTECTED] wrote: We're converting from Alexandria to Amanda. The differences are rather, well, stark. I've been reading a lot of various online Amanda resources, but what I really need to determine is holding disk requirements. I'm sure this info is concisely covered somewhere, but I'm slogging through tons of the same stuff over and over looking for it. I may even have looked right at the info I need without recognizing it. May I respectfully request a pointer to a resource to determine my holding disk requirements? Thank you, -- Brad Felmey -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Me again, still getting WARNING: host: selfcheck request time d out. Host down?
server02.ct
0.0.0.0broadcast broadcast
some of amanda.conf:
dumpuser backup
inparallel 4
netusage 51200 Kbps
dumpcycle 3 weeks
runspercycle 15
tapecycle 20 tapes
runtapes 1
tpchanger chg-manual
tapedev /dev/nst0
changerfile /root/amanda-data/changer-status
changerdev /dev/null
tapetype DAT
infofile /root/amanda-data/daily
logdir /var/log/amanda/daily
indexdir /root/amanda-data/daily
tapelist /root/amanda-data/daily/tapelist
define tapetype DAT {
comment Archive Python 04687-XXX
length 4000 mbytes
filemark 100 kbytes
speed 800 kbytes
}
disklist:
server02.ct sda1comp-root
server02.ct sda2comp-user
server02.ct sdb1comp-user
xinetd entries:
service amanda
{
disable= no
bind = 10.1.0.3
log_on_success += USERID
log_on_failure += USERID
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/local/libexec/amandad
}
service amandaidx
{
disable= no
bind = 10.1.0.3
log_on_success += USERID
log_on_failure += USERID
socket_type = stream
protocol = tcp
wait = no
user = backup
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable= no
bind = 10.1.0.3
log_on_success += USERID
log_on_failure += USERID
socket_type = stream
protocol = tcp
wait = no
user = backup
server = /usr/local/libexec/amidxtaped
}
Following are my debug files for amcheck.
amcheck.debug:
amcheck: debug 1 pid 24151 ruid 417 euid 0 start time Wed May 22 10:29:30
2002
amcheck: dgram_bind: socket bound to 0.0.0.0.929
amcheck: pid 24151 finish time Wed May 22 10:30:00 2002
selfcheck.debug:
selfcheck: checking disk sdb1
selfcheck: device /dev/sdb1
selfcheck: OK
selfcheck: checking disk sda2
selfcheck: device /dev/sda2
selfcheck: OK
selfcheck: checking disk sda1
selfcheck: device /dev/sda1
selfcheck: OK
selfcheck: pid 8251 finish time Wed May 22 10:29:30 2002
amandad.debug:
got packet:
Amanda 2.4 REQ HANDLE 000-48C30708 SEQ 102200
SECURITY USER backup
SERVICE selfcheck
OPTIONS ;
DUMP sdb1 0 OPTIONS |;bsd-auth;compress-fast;
DUMP sda2 0 OPTIONS |;bsd-auth;compress-fast;
DUMP sda1 0 OPTIONS |;bsd-auth;compress-fast;
sending ack:
Amanda 2.4 ACK HANDLE 000-48C30708 SEQ 102200
amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Invalid argument
bsd security: remote host broadcast user backup local user backup
amandahosts security check passed
amandad: running service /usr/local/libexec/selfcheck
amandad: sending REP packet:
Amanda 2.4 REP HANDLE 000-48C30708 SEQ 102200
OPTIONS ;
OK /dev/sdb1
OK /dev/sda2
OK /dev/sda1
OK /sbin/dump executable
OK /bin/gzip executable
OK /etc/dumpdates read/writable
OK /dev/null read/writable
OK /tmp/amanda has more than 64 KB available.
OK /tmp/amanda has more than 64 KB available.
OK /etc has more than 64 KB available.
amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Invalid argument
You can see that amanda is communicating ONLY over the broadcast. Thanks,
and only thanks, to my manipulation of /etc/hosts and .amandahosts, this is
producing any output at ALL. If I remove the broadcast hosts and
.amandahosts entry, selfcheck doesn't even RUN.
In any case, this is how I interpret the above output (please correct me if
I'm wrong). The client is contacting the server over the broadcast address
0.0.0.0 as we have discovered amanda always does, however, that's it. It's
not contacting the server over a unicast address at all! amandad receives
the request, validates the user, and processes the request. Upon attempting
to send back the output, it fails, because you can not have one-to-one
communication on a broadcast address (i.e. Invalid argument).
Why does not the client try to use the unicast address I have specified in
the disklist? Even though the entries clearly resolve, I have tried using
the IP also with the same results. Why is amcheck only binding to 0.0.0.0
and not 10.1.0.3? What am I doing wrong?
Thank you,
Cory Visi
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: AMANDATES file
--On Wednesday, May 29, 2002 12:18:42 -0400 Brook Hurd [EMAIL PROTECTED] wrote: I have been trying to do some research regarding the AMANDATES file, but I was unable to find any documentation on the purpose of this document. I would appreciate peoples insights on this file. Thanks, Brook Its used as the functional equivalent to dump's /etc/dumpdates so that Amanda can keep track of what levels were done when on which filesystems. The file contains lines like these: / 0 1022467489 / 1 1022639983 / 2 1018233593 /mnt/srv/backups 0 1022467139 /mnt/srv/backups 1 1022639924 /mnt/srv/home/app 0 1022381269 /mnt/srv/home/app 1 1022639885 /mnt/srv/home/app 2 1018233460 Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Dump Program Not available
Amanda uses the full path to all the backup/restore programs that it was configured with (and are fixed at compile time). So if Amanda was built with your dump program as /usr/sbin/dump. but now it is /sbin/dump or /usr/local/bin/dump, then you will get the 'program not available' error even though 'dump' is somewhere in the Amanda user's path. (Disclaimer: I'm a 'tar' user, and am assuming Amanda deals with ufsdump, vxdump, and other variants of dump in a similar way to the way it finds GNU tar.) Somewhere near the beginning of /tmp/amanda/amandad.*.debug you can find the full command path that Amanda is trying to run. You can then either make a link from there to the real program, or (probably better for the long term) rebuild Amanda with the correct path. Good luck, Frank --On Saturday, June 01, 2002 14:08:30 -0400 Kaan Saldiraner [EMAIL PROTECTED] wrote: Hello, Thanks for the responce .. I ran this command while su - to amanda export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin Now amanda user can infact run the dump and restore without doing /sbin/dump ..etc. But when i do amcheck on my server It is still giving me the same error. DUMP Porgram not available RESTORE program not available Thanks, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 01, 2002 8:07 AM To: Kaan Saldiraner Subject: RE: Dump Program Not available It sounds like your environment for the amanda user does not have the path to the dump command. su - to the amanda user account and see if you can run dump from the command line. If not you need to add it to the path for the amanda user. Just my 2 cents. Wade Hello, Thanks for the response but i think that the solution that you have gave me is for something else... Thanks for your response .. My problem is that amanda doesn't see that the machine has Dump already.. Maybe permission problem -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 8:37 PM To: Kaan Saldiraner; [EMAIL PROTECTED] Subject: Re: Dump Program Not available On Friday 31 May 2002 05:21 pm, Kaan Saldiraner wrote: Hello, I just installed a client and when i do amcheck for the Server it gives me this error ERROR: machine.domain.com: [DUMP program not available] ERROR: machine.domain.com: [RESTORE program not available] I rpmed the dump program and recompiled amanda on the client after and still the same error Any ideas?? Thanks Kaan Saldiraner Steltor Inc. (514)733-8500 x6503 www.steltor.com Either see if its listed in inetd.conf if your system usesd inetd, or see if there is an amanda in /etc/xinetd.d. If so, edit it to change the disable = yes line to disable = no, then restart /etc/rc.d/int.d/xinetd. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.96+% setiathome rank, not too shabby for a hillbilly - This message was sent using Endymion MailMan. http://www.endymion.com/products/mailman/ -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Hmmmm...all of a sudden I'm strange
Its nothing to worry about. It just means that file was in the process of being compressed when tar got the directory contents but was finished (and the tmp file gone) when tar actually tried to add it to the archive. You should have the uncompressed version of the file on the tape and will get the compressed version backed up on the next run. Frank --On Monday, June 10, 2002 10:15:04 -0500 Rebecca Pakish [EMAIL PROTECTED] wrote: Which wouldn't be so shocking, if it were just me. But it's my amanda backup report, and that makes me uncomfortable. Is this something to worry about? I can see the index file in question, and it looks okay. What's the deal with the .tmp? FAILED AND STRANGE DUMP DETAILS: /-- slaw /home lev 0 STRANGE sendbackup: start [slaw:/home level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end ? gtar: ./amanda/uadaily/index/in-db2.unterlaw.com/_var_www/20020608_0.gz.tmp: Warning: Cannot stat: No such file or directory | Total bytes written: 15011840 (14MB, 3.6MB/s) sendbackup: size 14660 sendbackup: end \ Rebecca A. Pakish Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184 -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: 2 tape strategy
--On Monday, June 10, 2002 17:12:08 -0300 Fernan Aguero [EMAIL PROTECTED] wrote: Hi! I am running amanda-2.4.2p2 succesfully with 2 hosts (1 server, 1 client). All disklist entries (level 0 dump) fit well on a DDS-4 40GB using software compression (about 24 GB now). I have only 4 tapes in use and momentarily just 2 (I am keeping 2 of them as archival tapes as I am burning some of the data on CDs, and will return them to the tapecycle as soon as they get done). This is how I've set my conf file: dumpcycle 7 runspercycle 2 tapecycle 2 tapes Based on this I'd expected amanda to run just twice every 7 days. However, amanda still runs everyday. Is it possible to do this? (if i set a dumpcycle of 30 and runspercycle of 1, would amanda run just once per month?) Amanda runs whenever you (or cron) make it run. 'runspercycle' is just for planner's benefit so it can schedule appropriate dump levels. IF you only want Amanda to just run twice a week, just have it scheduled that way in cron. I am currently forcing level 0 dumps in every run because otherwise amanda would almost always overwrite the only level 0 dump for a filesystem. Since all lev 0 dumps are only a few megabytes ( 100 MB), is it possible to have amanda append these to the end of each tape, thus leaving the level 0 dumps untouched? Currently I have this problem because on weekends amanda would run without being forced to do a lev 0 dump and thus would leave things in the holding disk that need to be flushed on Monday. That day, I will be left with only 1 level 0 dump in tape for each filesystem. If you want more level 1s and have enough holding disk, you could run Amanda daily without a tape (and adjust your config file accordingly), and amflush twice a week. There is the added risk of losing your backups if your holding disk fails. Frank Thanks in advance, Fernan PS: I know that just getting more tapes would be the ideal solution, but that is not economically possible in the short term. I'll appreciate comments on how to make amanda run as tapewise as it can, given my shortage of tape media. -- | F e r n a n A g u e r o | B i o i n f o r m a t i c s | | [EMAIL PROTECTED] | genoma.unsam.edu.ar | -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: GNU tar and SAMBA backups
Does /usr/local/bin/tar exist (and is it executable) on edinburgh ? Frank --On Friday, June 14, 2002 16:29:27 +0100 Kenny MacPherson [EMAIL PROTECTED] wrote: I'm moving over to use SAMBA based AMANDA backups, and have to start using gnutar. If my amcheck tells me... ERROR: edinburgh: [GNUTAR program not available] ERROR: edinburgh: [can not read/write /usr/local/var/amanda/gnutar-lists/.: No such file or directory] Client check: 1 host checked in 1.178 seconds, 2 problems found Where am I going wrong? I have downloaded, configured, make'd and installed GNU tar from www.gnu.org, I have re-configured, make-d and installed Amanda with the additional --with-gnutar=/usr/local/bin/tar I see a few websites/FAQs refer to gtar and can someone also confirm if gnutar is the same as tar from GNU??? Regards Kenny -- Kenny MacPherson IT Manager DDI: +44 131 272 7091 Wolfson Microelectronics Ltd. http://www.wolfsonmicro.com t: +44 131 272-7000 f: +44 131 272-7001 Registered in Scotland 89839 This message may contain confidential or proprietary information. If you receive this message in error, please immediately delete it, destroy all copies of it and notify the sender. You must not use or disclose any part of this message if you are not the intended recipient. We may monitor all Email communication through our networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise. We take reasonable precautions to ensure our Emails are virus free. However, we cannot accept responsibility for any virus transmitted by us and recommend that you subject any incoming Email to your own virus checking procedures. Wolfson Microelectronics Limited is a company incorporated in Scotland having its Registered Office at 20 Bernard Terrace, Edinburgh EH8 9NX -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: GNU tar and SAMBA backups
Check /tmp/amanda/amandad.debug to see if GNUTAR=/usr/local/bin/tar appears in the list of configuration options near the top of the file. If not, I suspect you didn't clear the cached configure output from your original build before you re-ran configure with your new options. Frank --On Friday, June 14, 2002 16:51:47 +0100 Kenny MacPherson [EMAIL PROTECTED] wrote: Yes it does!! edinburgh.root(7)= ls -al /usr/local/bin/tar -rwxr-xr-x 1 root other 835584 Jun 14 13:08 /usr/local/bin/tar -- Kenny MacPherson IT Manager DDI: +44 131 272 7091 -Original Message- From: Frank Smith [mailto:[EMAIL PROTECTED]] Sent: 14 June 2002 16:48 To: Kenny MacPherson; [EMAIL PROTECTED] Subject: Re: GNU tar and SAMBA backups Does /usr/local/bin/tar exist (and is it executable) on edinburgh ? Frank --On Friday, June 14, 2002 16:29:27 +0100 Kenny MacPherson [EMAIL PROTECTED] wrote: I'm moving over to use SAMBA based AMANDA backups, and have to start using gnutar. If my amcheck tells me... ERROR: edinburgh: [GNUTAR program not available] ERROR: edinburgh: [can not read/write /usr/local/var/amanda/gnutar-lists/.: No such file or directory] Client check: 1 host checked in 1.178 seconds, 2 problems found Where am I going wrong? I have downloaded, configured, make'd and installed GNU tar from www.gnu.org, I have re-configured, make-d and installed Amanda with the additional --with-gnutar=/usr/local/bin/tar I see a few websites/FAQs refer to gtar and can someone also confirm if gnutar is the same as tar from GNU??? Regards Kenny -- Kenny MacPherson IT Manager DDI: +44 131 272 7091 Wolfson Microelectronics Ltd. http://www.wolfsonmicro.com t: +44 131 272-7000 f: +44 131 272-7001 Registered in Scotland 89839 This message may contain confidential or proprietary information. If you receive this message in error, please immediately delete it, destroy all copies of it and notify the sender. You must not use or disclose any part of this message if you are not the intended recipient. We may monitor all Email communication through our networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise. We take reasonable precautions to ensure our Emails are virus free. However, we cannot accept responsibility for any virus transmitted by us and recommend that you subject any incoming Email to your own virus checking procedures. Wolfson Microelectronics Limited is a company incorporated in Scotland having its Registered Office at 20 Bernard Terrace, Edinburgh EH8 9NX -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Suggestions Please -- help!
that is because amanda renamed *_1.new to *._1. [root]% cat /tmp/amanda/sendbackup.20020619232309.debug sendbackup: debug 1 pid 25488 ruid 507 euid 507 start time Wed Jun 19 23:23:09 2002 /usr/libexec/sendbackup: version 2.4.2p2 sendbackup: got input request: GNUTAR /home/proj/bpa-9584 1 2002:6:12:8:57:52 OPTIONS | ;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; parsed request as: program `GNUTAR' disk `/home/proj/bia-9584' lev 1 since 2002:6:12:8:57:52 opt `|;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;' sendbackup: exclude list file /usr/local/lib/amanda/exclude.gtar does not exist, ignoring sendbackup: try_socksize: send buffer size is 65536 sendbackup: stream_server: waiting for connection: 0.0.0.0.54744 sendbackup: stream_server: waiting for connection: 0.0.0.0.54745 sendbackup: stream_server: waiting for connection: 0.0.0.0.54746 waiting for connect on 54744, then 54745, then 54746 sendbackup: stream_accept: connection from 192.168.1.88.54747 sendbackup: stream_accept: connection from 192.168.1.88.54748 sendbackup: stream_accept: connection from 192.168.1.88.54749 got all connections sendbackup-gnutar: doing level 1 dump as listed-incremental from /var/amanda/gnutar-lists/server_home_proj_bia-9584_0 to /var/amanda/gnutar-lists/server_home_proj_bia-9584_1.new sendbackup-gnutar: doing level 1 dump from date: 2002-06-12 8:57:53 GMT sendbackup: started index creator: /bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' sendbackup: spawning /usr/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /home/proj/bia-9584 --one-file-system --listed-incremental /var/amanda/gnutar-lists/server_home_proj_bia-9584_1.new --sparse --ignore-failed-read --totals . sendbackup-gnutar: /usr/libexec/runtar: pid 25494 sendbackup: index created successfully sendbackup: pid 25488 finish time Wed Jun 19 23:41:09 2002 Next I'd look for GNUTAR in /tmp/amanda/amandad*debug and see where the GNU tar is that Amanda is running, then run that exact path with --version to see which version of GNU tar is being used. Anything prior to 1.13.19 is evil in one way or another. It's GNUTAR=/bin/gtar [root]% /bin/gtar --version tar (GNU tar) 1.13.19 Copyright 2001 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. [root]% grep bia amandad.20020619*debug amandad.20020619165501.debug:GNUTAR /home/proj/bia-9584 0 OPTIONS | ;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; amandad.20020619165501.debug:OK /home/proj/bpa-9584 amandad.20020619210502.debug:GNUTAR /home/proj/bia-9584 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar amandad.20020619210502.debug:GNUTAR /home/proj/bia-9584 1 2002:6:12:8:57:52 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar amandad.20020619210502.debug:GNUTAR /home/proj/bia-9584 2 2002:6:19:6:28:23 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar amandad.20020619210502.debug:/home/proj/bia-9584 0 SIZE 16919390 amandad.20020619210502.debug:/home/proj/bia-9584 1 SIZE 16919390 amandad.20020619210502.debug:/home/proj/bia-9584 2 SIZE 16919390 amandad.20020619232309.debug:GNUTAR /home/proj/bia-9584 1 2002:6:12:8:57:52 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; For some reason the level 1 (and 2) tars estimate the same size as a level one. Id suggest you experiment running tar manually with all the options Amanda uses (as in the /tmp/amanda/files) and try to see why tar thinks all the files are new. Possibly try the 1.13.25 from alpha.gnu.org. I think this answers all the questions people sent me, and I still see nothing wrong. I'm stumped! Bart -- Bart Brashers MFG Inc. Air Quality Meteorologist 19203 36th Ave W Suite 101 [EMAIL PROTECTED]Lynnwood WA 98036-5707 http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040 Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: GNU Tar for SunOS 4.1.3 Amanda client
NFS can work, but if you didn't already have exports and mounts on the machines then not all of the needed daemons would have been running (the rc scripts check for exports mounts and only start certain daemons if they exist. You can start the daemons manually (look for what the rc scripts skip in 'if' tests). tar and rsh should work, but rsh may be disabled in inetd.conf or blocked by firewalls, tcpwrappers/ipchains/iptables or not allow access by root. Try rsh-ing to the SunOS box from your linux box, SunOS was a lot more permissive by default than current OS's. Do you have any free space on the SunOS box so that you could tar directories and then FTP them over? If you use tar's compression option and can delete directories after you FTP them, you should be able to start with smaller directories and work your way up through the big ones. Good luck, Frank --On Friday, June 21, 2002 11:39:06 -0500 Jonathan R. Johnson [EMAIL PROTECTED] wrote: Dear Amanda users, We have a legacy Sun Sparc II server (SunOS 4.1.3) that was, until recently, our only file server with a tape drive (an Exabyte 8200, 2.3 Gb capacity). We're in the process of centralizing files onto a RedHat 7.2 server running Amanda 2.4.2p2 (from the RPM -- no problems) with a Sony AIT-1 (SDX-300C) tape drive. Unfortunately, getting files off the Sun is proving to be tricky, due in large part to its outdated networking software. I briefly tried to use NFS to mount a server file system on the Sun and copy over the files, but the NFS mount didn't work right...not my strong suit, anyway. I've also tried various combinations of tar and rsh, to no avail so far. For now, I had hoped to just configure Amanda on it, even though this server will be taken off line as soon as its files have been securely set up on the new file server. My first hurdle, though, is that the GNU tar 1.13.25 from ftp://alpha.gnu.org/gnu/tar is not compiling properly (we compiled and installed gcc 2.3.3 a long time ago), encountering parsing errors in intl/loadmsgcat.c. Maybe this isn't the simplest way to take our files off this server... I'd love some suggestions here. Ideally someone just knows where I can get tar 1.13.19 or newer precompiled for SunOS 4.1.3. Otherwise, I'd probably have to recompile gcc with updated sources, etc. In the short term, I suppose I could try using the existing dump software. We need to back this thing up before it dies!! :-) Regards, Jonathan -- / Jonathan R. Johnson | Every word of God is flawless. \ |Minnetonka Software, Inc.| -- Proverbs 30:5 | \ [EMAIL PROTECTED] | My own words only speak for me. / -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Warning - old messages being resent to list
Before replying to a message, check the sent date. A batch of old messages is being re-injected into the list. Frank -- Frank Smith [EMAIL PROTECTED] Systems AdministratorVoice: 512-374-4673 Hoover's OnlineFax: 512-374-4501
Re: localhost: selfcheck request timed out. Host down?
Did you remember to HUP inetd after changing inetd.conf? Also, check your system logs to see if inetd had a problem with your entry. Don't worry about your .amandahosts yet, if it was having a problem with that you would be getting a different error similar to access as amanda not allowed from user@localhost Frank --On Monday, April 15, 2002 18:38:17 +0100 Axel Schaefer [EMAIL PROTECTED] wrote: Hi amanda-users. I'm new to Amanda and want to use it for some backups. In the first (and yet the only) case, the backup server is equals the backup client. I know, that my question is a FAQ, but the Answers on FAQ-O-MATIC didn't solve the problem (so, this is a NEWBIE-ALERT! =;-)). If I try to use: amanda@linux: amcheck -c DailySet1 the following error appears: /- | Amanda Backup Client Hosts Check | | WARNING: localhost: selfcheck request timed out. Host down? | Client check: 1 host checked in 30.007 seconds, 1 problem found | | (brought to you by Amanda 2.4.2p2) \- I've checked the inetd.conf, and I think, that the amanda.conf in /etc/amanda/DailySet1 is OK. I only set new paths to the infofile, logdir, indexdir, tapelist. The .amandahosts (in var/lib/amanda) shows this: amanda@ll11:~ less .amandahosts localhost amanda localhost root I've commented out both lines and tried it with only root-access and amanda-access. IIRC, amanda uses one line for the client (root) and one line for the server (amanda). So it seems OK, if localhost amanda is set (isn't it?). I'm a bit irritated if the the server-client works properly, when it's is on one computer. Can you help? Thanks. AxxL -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: problems with GNUtar and --sparse
--On Tuesday, April 30, 2002 16:24:35 -0700 Luke Miller [EMAIL PROTECTED] wrote: That's helpful but I don't think it explains what I am seeing. When I have the --sparse option turned on, tar does not backup all the files that it should. There is at least one directory where it doesn't backup ANY files at all in it. Sorry, I missed the part about the number of files being less, I just thought the total size was less than expected. I have no idea how --sparse could affect the nuber of files. Good luck, Frank Thanks, Luke Look at the GNU tar manual (not the man page) for a good explanation of what sparse files are and how --sparse handles them: http://www.gnu.org/manual/tar-1.12/html_node/tar_121.html Frank --On Tuesday, April 30, 2002 15:49:24 -0700 Luke Miller millerlu@integraonli ne.com wrote: I am having some problems with GNU tar and amanda. I am running amanda 2.4 .2p2 with gnutar 1.13.19 (I have also tried 1.13.25) on Solaris 8 (sparc). The command line that I am running is: /usr/local/bin/tar --create --file /tmp/conf.tar --directory /export/raid/c onf --one-file-system --sparse --listed-incremental /private/amanda/var/amanda/ gnutar-lists/nfs-1c-bvtn_export_raid_conf_5.new --totals . Replace /tmp/conf.tar for - when it is run by amanda. When I run this is produces a tar file that is about 5 megs in size and con tains 2556 entries. If I run the same command line but without the --sparse I get a tar file th at is about 23 megs and has 9535 enties. So, what is the --sparse doing here that is causing it not to backup all th e files? What is the best way around this? I would hack the code to remove --sparse but I want to have an understanding of what it is doing first. Thanks, Luke * * Luke Miller Unix System Administrator * * Integra Telecom 503-748-4549 * * -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: FileTooLargeError-2.4.2p2
sendbackup: started index creator: /bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' index tee cannot write [Broken pipe] thanks for any direction -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda crontab error
What is the exact error you get from cron? Generally problems from cron are related to it using /bin/sh for a shell instead of whatever you might be (ksh, bash, csh, etc.) and that it is only using the default system path (which is bare bones by default). There's also the outside chance that the Amanda user's home directory is automounted and isn't accessible at the time cron needs it. I don't think any of those things would result in a tape error, though, so maybe the exact error might give us a hint as to where to look next. Frank --On Wednesday, June 26, 2002 16:47:01 -0500 Robert Renzetti [EMAIL PROTECTED] wrote: System = SunOS 5.6 Problem = When Amanda's crontab runs, amcheck cannot find the tape, but when amcheck is run manually from the command line, it finds the tape fine. Crontab = 0 16 * * 1-5/opt/bin/amcheck -m geo 45 0 * * 2-6/opt/bin/amdump geo;mt -f /dev/rmt/0 off The crontab was created with amanda user logged in, in amanda's home dir as amanda_crontab. Then as amanda user I ran crontab amanda_crontab and then to make sure the changes took effect, crontab -l. The crontab file is in place. But when cron runs the file, /opt/bin amcheck -m geo errors out by not finding the tape. However, if I enter the same command (as amanda user) at the command line, it works fine, finds the tape and OKs the job. Help? Robert Renzetti Computer Systems Manager Geology Geophysics Texas AM University (979) 845-1366 -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Unable to connect to host
Forget about the .amandahosts file for now, you're not getting that far.
Try restarting xinetd, either a stop/start or kill -USR2. Sending a HUP
just makes xinetd write a state file and doesn't reread its config.
Make sure the amanda line is in /etc/services.
Also check /tmp/amanda/selfcheck.*.debug for errors.
Frank
--On Tuesday, July 02, 2002 09:03:34 -0700 Dean Lambourn [EMAIL PROTECTED] wrote:
I am in the process of setting up amanda 2.4.3b3 for a tapeless backup on a Redhat
7.2 server. As a test, I am trying to backup the amanda server to itself.
Unfortunately, it is unable to connect. When I configured amanda, I set it up to not
use the
.amandahosts file. I am able to rsh to server from the server as the user amanda so
the problem is not .rhosts or hosts.equiv files and it is able to resolve the host
name.
When I run amcheck, here is the error message I receive:
Amanda Backup Client Hosts Check
WARNING: toast.pcf.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.005 seconds, 1 problem found
(brought to you by Amanda 2.4.3b3)
I have added a .amandahosts file in case it was trying to use it:
/home/amanda/.amandahosts
toast amanda
localhost amanda
osiris amanda
Here is the relevant file for the xinetd configuration:
/etc/xinetd.d/amanda
service amanda
{
socket_type = dgram
wait = yes
protocol = udp
user = amanda
groups = yes
server = /usr/amanda/backup/libexec/amandad
disable = no
}
Any suggestions would be greatly appreciated.
--
Dean Lambourn
Systems Administrator
Pacific Coast Feather Company
[EMAIL PROTECTED]
(206) 336-2332
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: quick question?
--On Wednesday, July 17, 2002 15:20:53 -0400 C White [EMAIL PROTECTED] wrote: i just wanted to make sure i had my amanda configured properly i want it to run a backup every weeknight, mon-fri i only want it to do one full backup every week, with incrementals the rest of the time and i have six tapes in the 5 for backups and a 6th one for flushes here is my configuration: dumpcycle 5 days runspercycle 1 tapecycle 6 tapes You probably want: dumpcycle 7 days(a full at least once a week) runspercycle 5 (you're running Amanda 5 times during that time period) tapecycle 12 (6 would technically work, but you run the risk of overwriting your last full dump if you have problems. 2 x runspercycle + a couple of spares is a much safer number. If you have trouble restoring from a tape, having another backup from two weeks ago is much better than no backup at all) Good luck, Frank is this correct or have i missed something here? everything else is running fine, however i've only been running it since monday this week ;-) everyday at 4 amcheck looks to see if i need to change the tape, and that is working fine, and every midnight the backup seems to run properly, and the logs look fine, today it even reported to me that it was going to move the full dump of 3 of the directories ahead 5 days Full dump of filezzz:/home promoted from 5 days ahead, or am i reading that wrong all i all i am quite happy with amanda and i look forward to implementing it here at work in the near future -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Times from amreport
--On Sunday, July 21, 2002 12:30:05 -0400 Jon LaBadie [EMAIL PROTECTED] wrote: On Sun, Jul 21, 2002 at 12:28:52PM +0200, Ulrik Sandberg wrote: On Sun, 21 Jul 2002, Frank Smith wrote: For example, cron started one config at 9:30PM, sent the report email at 11:23PM, and reported the following: Estimate Time (hrs:min)0:06 Run Time (hrs:min) 1:57 Dump Time (hrs:min)4:12 1:57 2:14 Tape Time (hrs:min)0:33 0:20 0:12 You get away with 6 minutes of Estimates, but mine takes an hour and a half. So it may be a relevant question for me. :-) Yeah Frank, how do you get such quick estimates? Even my unix boxes take 30 min. The pc's an extra 2 hrs. I didn't realize it was supposed to take longer ;-), I just grabbed my latest report. That particular config's disklist has 83 entries from 25 hosts. Most are small, the largest single entry is about 11GB. The used filesytem sizes total about 65GB, daily writes to tape are 7-10GB. All entries use tar, almost all use client compressed tar. Original daily size is 13-16GB). OS's are Linux and Solaris, and some of the larger directories are NFS mounted on the backup server (they are on an NFS server appliance). I don't do any Samba shares. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Times from amreport
--On Sunday, July 21, 2002 12:28:52 +0200 Ulrik Sandberg [EMAIL PROTECTED] wrote: On Sun, 21 Jul 2002, Frank Smith wrote: For example, cron started one config at 9:30PM, sent the report email at 11:23PM, and reported the following: Estimate Time (hrs:min)0:06 Run Time (hrs:min) 1:57 Dump Time (hrs:min)4:12 1:57 2:14 Tape Time (hrs:min)0:33 0:20 0:12 This would lead me to believe that run time is wall clock time that Amanda ran, and dump time is the total time dumpers were running (i.e., 4 dumpers running in parallel for 1 hour would be 4 hours of dump time). Run Time is Total Wall Clock Time, Estimates included. Thanks. Since estimates, dumpers, and tapers can all run in parallel I don't think you can add up any of the times and get anything meaningful. Please define all run in parallel. My feeling is that no Dump will start until all Estimates are finished. If that's correct, then there could no parallelism (multiple sendsize, but zero Dumpers) during the Estimate phase, right? You get away with 6 minutes of Estimates, but mine takes an hour and a half. So it may be a relevant question for me. :-) -- Ulrik Sandberg Sorry, my best answers don't usually happen at 3am. The estimates have to finish first so the proper scheduling can be done, then the dumpers and tapers can run in parallel. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Multiple configs
--On Saturday, July 20, 2002 19:51:01 -0500 Craig Hancock [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello all, I was wondering what is the best wato configure amanda. I basically have a 2 dape drives and a 40 tape autoloaders and I want to make 2 configs. I found very little information about how to setup this up and I was wondering if someone can point me into the right direction. Craig Hancock It's just like having one config with two major caveats: 1. Be very careful if the same disklist entry is in both configs. The info for dumpdates can get clobbered and screw up the incrementals. If you just want the second config to do fulls for offsite storage, set record to no and allwaysfull. 2. Make sure that the run times don't overlap. Only one can run at a time unless you compile two versions with different names and portranges. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: FW: tape labels
Amanda needs to use the non-rewinding tape device, in your case probably
/dev/nst0. Look for 'tapedev' in your amanda.conf file.
Frank
--On Monday, July 22, 2002 18:27:43 +0100 jane mattley [EMAIL PROTECTED] wrote:
I am new to Amanda and have just installed and configured as per
installation docs I am trying to label my first tape using the following
command:
amlabel -f DailySet1 DailySet11
But I get the following message:
rewinding, reading label, not an amanda tape
rewinding, writing label DailySet11, checking label
amlabel: no label found, are you sire /dev/st0 is non-rewinding
My tape device is rewinding but how I specify this in my amanda.conf file?
I would be grateful for any help.
Jane Mattley.
Support Team
Studio 2 Online Ltd
Now Supplying Computer Hardware Software, Call for a Quote
We guarantee to beat any Like for Like E-Commerce Quote
Update your website for FREE with CMS
Sales : 0116 2425811Support : 0906 756 0364
Email : mailto:[EMAIL PROTECTED] Web: http://www.s2o.co.uk/
Legal Disclaimer:-
Internet communications are not secure and therefore Studio 2 Online does
not accept legal responsibility for the contents of this message. The
information in this email is confidential and may be legally privileged. It
is intended solely for the addressee and therefore access to this email by
anyone else is unauthorised. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be taken
in reliance on it, is prohibited and may be unlawful, furthermore please
contact the sender immediately by replying or by calling 0870 7417226 and
delete this message and any attachment permanently from your system. Any
views or opinions presented are solely those of the author and do not
necessarily represent those of Studio 2 Online. Although Studio 2 Online
operates anti-virus programmes, it does not accept responsibility for any
damage whatsoever that is caused by viruses being passed.
Thank you for your co-operation
begin 600 alert.txt
M*BHJ*BHJ*BH@(!.971W;W)K($%SV]C:6%T97,@1W)O=7!3:EE;0@17AC
M:%N9V4@(`@(`@(`@*BHJ*BHJ*BHJ*@T**BHJ*BHJ*BH@($%L97)T(=E
M;F5R871E9!A=#H@36]N9%Y+!*=6QY(#(R+`R,#`R(#$R.C0P.C4W(%!-
M($-E;G1R86P@1%Y;EG:'0@5EM90T**BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ
M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ
M*BHJ*@T*#0H-E1H92!F:6QE($%45#`P,#(X+FAT;2!H87,@8F5E;B!R97!L
M86-E9X-E!L96%S92!C;VYS=6QT('EO=7(@861M:6YIW1R871OB!F;W(@
M9G5R=AEB!H96QP#0IA;F0@F5M96UB97(@=\@75O=4@6]UB!T:6-K
E970@;G5M8F5R.B!/03,U.#1?,3`R-S,U.38U-U]%6$-(04Y'10==
`
end
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Permissions, configuration, and errors, oh my!
--On Tuesday, July 23, 2002 12:10:25 -0400 Dave Belfer-Shevett [EMAIL PROTECTED] wrote: [operator@tub]:~$ amcheck tub Amanda Tape Server Host Check - Holding disk /dumps: 69886570 KB disk space available, that's plenty amcheck-server: slot 1: date 20020723 label qbn-backup01 (active tape) amcheck-server: slot 2: slot 2 is empty amcheck-server: slot 3: slot 3 is empty amcheck-server: slot 4: slot 4 is empty amcheck-server: slot 0: slot 0 is empty ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/adm/amanda/tub/curinfo/tub/_dev_dsk_c0t0d0s1: does not exist Server check took 81.639 seconds Second - the message is saying there's a labelled tape in the drive (qbn-backup01) which I created with 'amlabel'. But it seems to think that's not a writable tape, its expecting a new one. Can I tell amanda no, that's your tape. Go toss data on it! or am I misunderstanding how tape labelling / allocation work? I'll leave the (edited out) dump permission question for others, but your tape problem is due to Amanda thinking it has already used qbn-backup01. It may not actually have anything written to it, but if Amdump made a run then the tape is marked as 'active' and won't be overwritten until it goes through the rest of your tapecycle. While you are testing just do an 'amrmtape tub qbn-backup01' and then you can re-use it. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Is this OK? Ignoring cruft file
/usr 1 101601056 10.4 N/A N/A0:09 117.4 dilbert /usr/local 1 270 64 23.7 N/A N/A0:05 13.0 dilbert /var 1 239906752 28.1 N/A N/A0:17 399.2 jansen_en_janssen/.kde1 10 64 640.0 N/A N/A0:09 7.2 jansen_en_janssen/.kde2 1 20 64 320.0 N/A N/A0:09 7.4 jansen_en_janssen/bin 1 10 64 640.0 N/A N/A0:09 7.2 jansen_en_janssen/boot088307968 90.2 N/A N/A0:13 616.1 jansen_en_janssen/dev 1 70 64 91.4 N/A N/A0:09 7.2 jansen_en_janssen/etc 081301792 22.0 N/A N/A0:09 194.8 jansen_en_janssen/home1 10 64 640.0 N/A N/A0:09 7.3 jansen_en_janssen/lib 1 60 64 106.7 N/A N/A0:05 13.7 jansen_en_janssen/opt 14750 448 9.4 N/A N/A0:09 48.9 jansen_en_janssen/raid/apps 1 152401088 7.1 N/A N/A0:05 215.0 jansen_en_janssen/raid/libs 0 560890 151712 27.0 N/A N/A1:241810.1 jansen_en_janssen/raid/local 0 1353420 285632 21.1 N/A N/A2:291913.7 jansen_en_janssen/raid/xic_bin12890 416 14.4 N/A N/A0:05 81.8 jansen_en_janssen/raid/xic_fun0 10 64 640.0 N/A N/A0:09 7.3 .. .. .. jansen_en_janssen/raid/xic_libs 0 907540 775680 85.5 N/A N/A 11:291125.5 jansen_en_janssen/raid/xic_local 1 360980 338464 93.8 N/A N/A3:021859.8 jansen_en_janssen/root1 750 96 12.8 N/A N/A0:09 10.9 jansen_en_janssen/sbin1 20 64 320.0 N/A N/A0:09 7.3 jansen_en_janssen/tmp 12620 160 6.1 N/A N/A0:11 15.2 jansen_en_janssen/usr 1 183509696 52.8 N/A N/A0:19 511.9 jansen_en_janssen/var 0 1158750 876768 75.7 N/A N/A 20:55 698.6 (brought to you by Amanda version 2.4.2p2) -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Is this OK? Ignoring cruft file
--On Thursday, August 15, 2002 11:45:52 -0400 Gene Heskett [EMAIL PROTECTED] wrote: On Thursday 15 August 2002 11:01, Frank Smith wrote: --On Thursday, August 15, 2002 11:47:24 +0200 Edwin Hakkennes [EMAIL PROTECTED] wrote: Hi all, I added a 'big' disk to my disklist yesterday. About 8G. Flushing the files from the holding disk results in NOTES: amflush: beosrv-1._redhat.0.2: ignoring cruft file. amflush: beosrv-1._redhat.0.3: ignoring cruft file. taper: tape xic03 kb 13511296 fm 58 [OK] Should I worry about this? Did only 2G of the backup actually make it to the tape? It wrote 13.5G to tape, and according to your output below, 7.6G of that was from your beosrv-1 /redhat disklist entry. I think the cruft file messages are just a result of the somewhat asynchronous nature of amanda. The chunk files are removed after each set is written to tape but may not be all gone yet when Amanda scans for other chunk sets to flush to tape. Anything that it doesn't know what to do with is reported as 'cruft', whether it is some odd file put in the holding disk or a chunk that isn't part of a complete set (the chunk files are named as host.filesystem.level.chunknumber). 'Notes' are just informative, 'strange' needs to be examined, it may or may not be a problem, and 'warning' you better pay attention to. Frank Hummm, this brings up an interesting thought, Frank. If amanda removed the chunk files as they were written, then how would amanda go about the case of hitting EOT in the middle of the last chunk file, finding that it has perms (via runtapes=2 for instance) to use the next tape in the magazine, at which point amanda supposedly restarts that disklist entries dump from the top. If there were 4 chunk files, 3 of which had been written and deleted when this occured, it seems to me that amanda would find herself between a rock and a hard place to be able to restart that particular disklist entries dump. It certainly wouldn't be very time efficient to redo the whole entry although that does seem to be the only way to recover. So how is this scenario resolved by amanda? I said that the chunks were removed after the set was written. I haven't looked at that part of the code, just observed my holding disk in various situations, so I may not be completely correct. It appears that after all of the set of chunks belonging to a single disklist entry are successfully flushed to tape, those chunks are deleted from the disk. If a tape error occurs anytime during the flush of a set of chunks all of that set remains on disk so a subsequent amflush can start over with the first chunk of the set. I believe Edwin's 'notes' was the result of Amanda successfully flushing all of the chunks of his 'redhat' directory, but after taper returned ok a command was given to remove those chunks while amflush went ahead and rescanned the holding disk looking for anything else that needed to be flushed. Since it can take a second or two to remove large files, a couple of the chunks were still there when the scan occurred, but since the first chunk was already gone Amanda saw the other two as cruft. Of course, when Edwin looked at the disk later it was all gone by then. Frank -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Labels and Barcodes
--On Thursday, August 15, 2002 14:52:26 -0400 Jason Greenberg [EMAIL PROTECTED] wrote: What's the difference between labels and barcodes? Why, when I label tapes, does the VolumeTag= not show up for that tape? As I understand it, the 'label' is the header record that is the first record on the tape. 'barcode' is the paper barcode on the outside of the tape. Some changer scripts can associate the two if you have a barcode reader in your library, some can't. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Labels and Barcodes
--On Friday, August 16, 2002 09:08:07 -0400 Jason Greenberg [EMAIL PROTECTED] wrote: Then how do you set the barcode? Is it a physical label? If my libary reads bar codes, will it also print them? It is a physical (usually paper) label normally on the edge of the tape cartridge that is facing out when the tape is in the drive or magazine (similar to the UPC code on most products that the cashier scans when you buy just about anything). I doubt if any libraries print barcode labels (except possibly some of the room-sized robotics systems). You can either buy them from places like colorflex or print your own. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amrecover - can't talk to tape server
Does your inetd.conf (or equivalent) have an entry for amidxtape? You'll need one for amandaidx to if it is also your index server. Frank --On Friday, August 16, 2002 12:33:54 -0400 Jason Greenberg [EMAIL PROTECTED] wrote: Any idea what could cause this? the same thing happens when connecting from the tape server (local or remote). amrecover add passwd Added /passwd amrecover extract Extracting files using tape drive /dev/nst0 on host 192.168.100.1 The following tapes are needed: E04 Restoring files into directory /home/jg/recover-tmp Continue? [Y/n]: y Load tape E04 now Continue? [Y/n]: y cannot connect to 192.168.100.1: Connection refused amrecover - can't talk to tape server -- Jay -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: file system sizes
If you've been saving your daily reports, just grep for the level 0's over a dumpcycle and add them up. Frank --On Friday, August 16, 2002 14:16:45 -0500 Wayne Byarlay [EMAIL PROTECTED] wrote: Can anybody recommend the best way to estimate whether all my filesystems will fit onto one tape? Right now I'm running a 15-day incremental cycle, but I want to remove friday from that cycle, and do a full backup. The problem is, it'll take me a LONG time to login to each server, df -k, etc. to estimate the sizes. I'm guessing that maybe Amanda might have this info stored away in some secret file somewhere, or I can use some deft command-line switches to audit all my file systems. Any ideas? wab. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amrecover unable to connect to remote client
You need amandaidx and amidxtape entries on the server in order to restore. Note that they are 'stream tcp nowait' services as opposed to the 'dgram udp wait' used for the amanda entry. All the clients need is the single amanda entry. You also need an entry in .amandahosts on the server of the form client.domain.com root in order to allow root on the client to connect to the server and restore files. Frank --On Sunday, August 18, 2002 05:16:44 +0100 Mark Cooke [EMAIL PROTECTED] wrote: Hi, I have just tried to restore some files from my tape server to my client and keep getting connection refused ( I ended up restoring them to the tape server at a tmp location and then using scp to get them to the client) Am I correct in thinking that to restore to clients you have to have amandaidx as well as amanda in /etc/xinetd.d in the clients xinetd.d directory ? (thus using RH, you have to install amanda-server rpm as well) as I have specified in both .amandahosts that root can connect (just in case) cheers Mark -- --- To steal ideas from one person is plagiarism; to steal from many is research. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Diagnosing an elusive fault on a critical system [long]
] via686a 8548 0 (unused) eeprom 3040 0 (unused) i2c-proc6368 0 [via686a eeprom] i2c-isa 1156 0 (unused) i2c-viapro 3848 0 (unused) i2c-core 12864 0 [via686a eeprom i2c-proc i2c-isa i2c-viapro] binfmt_misc 5924 1 nfsd 68512 8 (autoclean) lockd 50720 1 (autoclean) [nfsd] sunrpc 61520 1 (autoclean) [nfsd lockd] autofs 10564 0 (autoclean) (unused) 8139too12672 1 ipchains 34568 1 st 25844 0 (unused) ext3 58912 4 jbd38500 4 [ext3] raid5 16864 3 xor 5912 0 [raid5] raid1 12324 1 sym53c8xx 55300 0 (unused) sd_mod 11836 0 (unused) scsi_mod 92824 3 [st sym53c8xx sd_mod] Thanks in advance, especially if you actually read this far!! Only a true Linux fan would have stayed awake to this, the 390th line of this message. :) Regards, Jonathan -- / Jonathan R. Johnson | Every word of God is flawless. \ |Minnetonka Software, Inc.| -- Proverbs 30:5 | \ [EMAIL PROTECTED] | My own words only speak for me. / -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Diagnosing an elusive fault on a critical system [long]
If I read your crontab comments correctly, you run amanda every night but only have a tape in the drive on Friday nights? If so, and if the Friday night/Sat. AM run is the only time you have crashes, then I would lean towards either a power supply problem or a scsi driver problem, although Edwin Hakkennes' comments about bad RAM are a possibility. Since bad power can manifest itself as all kinds of strange problems, you might want to check your voltages under load before you get too deep into hardware swapping. Frank --On Monday, August 19, 2002 15:07:54 -0500 Jonathan Johnson [EMAIL PROTECTED] wrote: Dear Frank (et al.), On Mon, 19 Aug 2002 14:16:22 -0500, Frank Smith [EMAIL PROTECTED] wrote: I doubt it is an Amanda problem (you might want to also try the linux-managers mailing list http://www.linuxmanagers.org/ ), but I'll toss out some suggestions of things to look at anyway: Thanks for the mail list tip -- I've subscribed and will try that venue as well. If this really is going to be an 'omni-server', 128M seems a little small. Probably not your crash problem unless you're filling up swap, which you seem to have enough of. Some day I hope to upgrade the ram, which is why I partitioned an amount of swap space ( 512 Mb) that is pretty ridiculous for a system with only 128 Mb. The 300W power supply may also be too small, especially if your tape drives are internal. I'm trying to figure out what the potential aggregate power consumption of the system's components might be -- there are surprisingly few technical specifications that state this, though! :( It could be the kernel. We have had serious issues with the virtual memory manger in a few of the mid 2.4 series, although the earlier and later versions worked fine. Perhaps I'll go with the latest RH 7.2 updated version then and try patching it myself. Is 2.4.9-34 an improvement on 2.4.9-31, though? I've tried to remain RPM-based as much as possible to make life simpler for everyone; I even used the amanda RPMs that came with RH 7.2 (and I'd do it again, bub!). Sometimes, though, one has to live on the cutting edge... To make it relevant to Amanda-users, what's special about Saturday? Are you only running backups once a week, or do you run a different config then? Glad you asked. Here's our Crontab, with e-mail addresses removed: # $Id: Crontab,v 1.5 2002/08/16 21:04:55 amanda Exp $ # # Crontab entries for automated backup with amanda. # # The backup schedule expects no tape Sa-Th, but degraded dumps are # performed. 20 12,16 * * 0-4,6 /usr/sbin/amcheck -clm DailySet1 30 22 * * 0-4,6 /usr/sbin/amdump DailySet1 # The degraded dumps are flushed Fr a.m. There is no mt offline # because the amcheck.[N] file does not get generated with amflush -f # (and then the output goes to stdout). So the first subsequent # amcheck will be responsible for seeing if we finished the flush, # ejected the tape, and inserted the requisite tape. 20 9 * * 5 /usr/sbin/amcheck -m DailySet1 50 9 * * 5 /usr/sbin/amcheck -M... DailySet1 30 10 * * 5 echo -e \ny\n | /usr/sbin/amflush DailySet1 # Expect to label a new tape on the afternoon of the last Friday of # each month I was rather proud of this little snippet of shell programming... :) 10 12 * * 5 [ `date -d 1 week +\%m` != `date +\%m` ] \ /usr/sbin/amlabel DailySet1 `date +DailySet1o\%Y\%m` # The full dump is run Fr late p.m. Part of our current setup is to # make sure that the Perforce depot is properly set up for backup. 20 12 * * 5 /usr/sbin/amcheck -m DailySet1 30 12 * * 5 ls DailySet1/index | \ xargs -l /usr/sbin/amadmin DailySet1 force \ /dev/null 20 13-16 * * 5 /usr/sbin/amcheck -M... DailySet1 20 22 * * 5 ./p4backup 30 22 * * 5 /usr/sbin/amdump DailySet1; \ /bin/mt -f /dev/st0 offline # The new tape labeled on the last Friday of the previous month # should be marked as not reusable. 10 6 1 * * /usr/sbin/amadmin DailySet1 no-reuse \ `date -d yesterday +DailySet1o\%Y\%m` This should answer your question as well as display some ideas about Amanda automation. It works very well so far. I thought about multiple configs, but then the coordination of indexes, dump dates, etc. just gets needlessly complex. So I just bully around a single config. Good luck, Frank --On Monday, August 19, 2002 13:15:39 -0500 Jonathan Johnson [EMAIL PROTECTED] wrote: snip -- / Jonathan R. Johnson | Every word of God is flawless. \ |Minnetonka Software, Inc.| -- Proverbs 30:5 | \ [EMAIL PROTECTED] | My own words only speak for me. / -- Frank Smith[EMAIL PROTECTED] Systems Administrator
Re: amandahostsauth failing -- why?
--On Tuesday, August 20, 2002 15:19:14 -0700 Schlomo Schwartz [EMAIL PROTECTED] wrote: --- Jim Summers [EMAIL PROTECTED] wrote: 1. the amanda hosts exists on all participants 2. format correct? hostname amandausername || hostname.domain amandausername 3. the file is in the amanda user home. Here's the contents of my /var/lib/amanda/.amandahosts lin01 amanda lin01.foobar.com amanda localhost amanda localhost.localdomain amanda Didn't your original post give an error message about amanda@lino02 (I can't check it in the archives since yahoo stripped most of the error thinking it was an email address). Look for the error message that says [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed and make sure that whatever is after the '@' is the first field and the name before the at (amanda in this case) is the second field in your amanda hosts. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: mt rewind strangness
--On Tuesday, August 27, 2002 10:28:02 -0400 Jon LaBadie [EMAIL PROTECTED] wrote: Has anyone else noted this behavior? mt rewind returns (completes) before tape is rewound Yes, it seems to be fairly a common behavior of tape drives. Back in the days when I had to write shell scripts to do backups, I always threw in a sleep call after any tape command. Not all commands needed it, but wasting a few seconds on a several hour job was much better than the random error that would cause the entire job to fail. Frank Specifically, When I issue an mt rewind from a shell command line, the tape begins to rewind (lights on drive blinking) and after about 10 seconds the mt command completes and I get my shell prompt for the next command. However, the tape has not yet rewound completely, the drive lights are still blinking. If I issue a second mt command (another rewind or status) that command blocks until the tape is completely rewound before executing and returning. I'm wondering if this is why my amcheck command sometimes fails to find the correct tape in my changer though amdump always does. Perhaps amcheck does an mt rewind and it returns before the tape drive is done rewinding. Then amcheck might issue a command that times-out rather than blocking and thus amcheck thinks that slot has no or the wrong tape. Just musing. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Backing the backup server
--On Tuesday, August 27, 2002 13:27:10 -0500 Craig Hancock [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am trying to backup the backup server in amanda and I am a little confused on how to go about it from the documentation you setup a .amandahosts file on the server and the client. Is an entry for the backup server need to be there. If so what should the connect as user be 1) amanda 2) root For backups, the user is amanda (or whatever you defined it to be if you changed it), and the line should be server.domain.name amanda Don't forget to make sure that amanda owns it and it is only readable (and writable) by amanda. If this is not the case then how does one configure the backup server? The amandahosts file on the server should contain the same line as on the clients, except that you will need additional lines on the server in the form of client.domain.name root in order to restore directly on the clients. Frank Craig Hancock -- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9P+Y5awsElDuSDs0RAgxoAJ40NBfXWSP5dwsRK6AWZRXP6fNm+wCgpWf4 MwLEwsq3TDVGR8ntq3+w65k= =qTeY -END PGP SIGNATURE- -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Trivial question - No Flames please
Some manufacturers advertise them as 10GB, but they are really 5GB native capacity. The 160m 8mm tapes are 7GB native. Compression can make your data anywhere from somewhat larger to considerably smaller, depending on what it is. Repetitive text files like web logs can compress amazingly well, already compressed files like most image, music, and video files, and .Z and .gz files, will get a little bigger if you try to compress them again. Frank (sorry if this gets posted twice, my mail client freaked and I don't know if it went out before or not) --On Sunday, September 01, 2002 20:24:27 -0700 Potts, Ross A. [EMAIL PROTECTED] wrote: I think I have been looking in all the wrong places. What size is a 112 Meter 8mm tape with and without compression? I just inherited a butt-load of them and decided to use them for daily incrementals (nothing above 500 MB a day) Thanks! Ross -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda-2.4.3b4 and tar exclude lists working?
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin [EMAIL PROTECTED] wrote: Hello, I just installed and configured amanda-2.4.3b4-20020829 on a Linux box with an ecrix tape library and I might be stumbling on some bug and/or feature: relative path exclude list don't seem to be used at all... Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see that this version is supposed to have this fixed... Is this really the case? I can provide debug files on demand. Do you have an exclude list properly defined in your dumptype? Are you using tar? Is the exclude list file in the top level of the directory you're trying to back up and is it in the correct format? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda-2.4.3b4 and tar exclude lists working?
--On Tuesday, September 03, 2002 11:41:29 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
* Frank Smith ([EMAIL PROTECTED]) [20020903 11:18] thus spake:
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
Hello,
I just installed and configured amanda-2.4.3b4-20020829 on a Linux box
with an ecrix tape library and I might be stumbling on some bug and/or
feature: relative path exclude list don't seem to be used at all...
Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see
that this version is supposed to have this fixed... Is this really the
case? I can provide debug files on demand.
Do you have an exclude list properly defined in your dumptype?
Are you using tar?
Is the exclude list file in the top level of the directory you're trying
to back up and is it in the correct format?
I've been using amanda for a few years now and I'm fully aware of all
the quirks in setting up exclude lists. I have 3 other servers running
2.4.2p2 with relative exclude lists with tape libraries (exb-200,
adic-218 and stk-L40) with no problems whatsoever. For this one, I
decided to jump ahead with 2.4.3b4...maybe I'll go back to 2.4.2p2.
Anyways, yes, I'm using tar (GNU tar) 1.13.19.
Here are the dumptypes from amanda.conf:
---
amanda.conf
---
define dumptype global {
comment Global definitions
index yes
record yes
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
priority low
}
define dumptype high-tar-raid-epilepsy {
root-tar
comment partitions dumped with tar
priority high
exclude list .amanda-gnutar-exclude-list.txt
}
---
disklist entry
---
blade /raid/epilepsy high-tar-raid-epilepsy
---
On the host blade (amanda server and client) I created a file called
/raid/epilepsy/.amanda-gnutar-exclude-list.txt:
[root@blade]# cd /raid/epilepsy/
[root@blade]# ls -la .amanda-gnutar-exclude-list.txt
-rw---1 amanda disk 123 Sep 2 08:18
.amanda-gnutar-exclude-list.txt
---
exclude file
---
[root@blade]# cat .amanda-gnutar-exclude-list.txt
./diffusion/
./extra-TLE/
./F_MRI/
./MRI_misc/
./MT/
./neda/
./PREVIOUS/
./relaxo/
./restore/
./samson/
./thalamus/
./TLE/
Yes, it looks like you have it set up correctly, maybe it is a 2.4.3b4
thing (I'm still running 2.4.2p2). What issues are you seeing with
the latest version?
Unrelated question:
Doesn't the trailing slash on your exclude list entries mean that only
those directories themselves are skipped and not any subdirectories?
I leave off the slash to prune the directory tree at that point, and
can't think of too many uses for excluding a directory while backing
up its subdirectories. Or possibly my idea of exclude syntax is off.
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: 2.4.3b4 gnutar exclude troubles
--On Tuesday, September 03, 2002 13:14:45 -0500 Ben Lutgens [EMAIL PROTECTED]
wrote:
With 2.4.3b3 I was getting MISSING RESULT errors. the b4 release seems
to
have at least fixed that, but it's still not excluding the files/dirs
listed in the exclude list.
Disklist entry:
homer.sistina.com /home/homer comp-user-tar
Dumptype as follows:
define dumptype comp-user-tar {
user-tar
priority medium
compress client best
exclude file ./amanda.exclude
===
Shouldn't that line be:
exclude list ./amanda.exclude
Frank
}
./amanda.exclude on homer in /home/homer looks like so:
./blutgens
./llama
./tool
./amandahatesme
./gnutarisbeingapunk
./*/.mozilla/*/*/Cache
The overall size of /home/homer is 37G. My exclude list contains
directories which make up 66% of that space (I have 20Gb tapes, and was
going to break it into 3 pieces) in the report where I learn that it's
failed I see:
In /tmp/amanda/sendsize on homer I see:
endsize[5041]: argument list: /bin/tar --create --file /dev/null
--directory
/home/homer --one-file-system --listed-incremental
/etc/amanda/gnutar-lists/homer.sistina.com_home_homer_0.new
--sparse --ignore-failed-read --totals --exclude-from
/tmp/amanda/sendsize._home_homer.20020903112939.exclude .
Which looks odd to me since the file
/tmp/amanda/sendsize._home_homer.20020903112939.exclude contains only
./amanda.exclude
Which i do not believe would work. Shouldn't the file:
sendsize._home_homer.20020903112939.exclude e a copy of
amanda.exclude? or a `cat /path/to/amanda.exclude`
Or am I the only one having a problem with the GNUTAR exclude files?
--
Ben Lutgens|
http://people.sistina.com/~blutgens/
System Administrator | http://www.sistina.com/
Sistina Software Inc. |
If you love something set it free, if it doesn't come back to you
hunt it down and set it on fire -- George Carlin
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: statistics
It all depends. Does your largest disklist entry fit on your holding
disk? Look further down in your daily report and look at the times
for dumper and taper for each disklist entry. My guess is that you
are doing one or more direct to tape dumps across the network, which
can be extremely slow since the tape may have to repeatedly stop and
reposition itself as the data trickles in.
Frank
--On Thursday, September 05, 2002 15:29:39 -0700 greg [EMAIL PROTECTED] wrote:
Does this look right?
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:06
Run Time (hrs:min)11:48
Dump Time (hrs:min) 11:42 11:42 0:01
Output Size (meg) 24171.424171.40.0
Original Size (meg) 54320.454318.32.1
Avg Compressed Size (%)44.5 44.51.5 (level:#disks
...)
Filesystems Dumped3 2 1 (1:1)
Avg Dump Rate (k/s) 587.4 588.00.8
Tape Time (hrs:min) 11:41 11:41 0:00
Tape Size (meg) 24171.524171.50.1
Tape Used (%) 64.5 64.50.0 (level:#disks
...)
Filesystems Taped 3 2 1 (1:1)
Avg Tp Write Rate (k/s) 588.5 588.5 29.3
It is saying it took 11 hrs to dump 54GB or 24GB compressed. I have a
quantum DLT8000-40 which is rated
at 6MB/s or 12MB/s compressed. 11hrs seems a long time even considering
gzip as the software compression.
Is there something I am missing here?
-greg
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: confused by nightly dump report
151.41:41 1440.8 castor/apoa 0 1373439 287456 20.9 45:51 104.53:22 1420.9 castor/home1 0 980031 332736 34.0 27:48 199.53:55 1418.0 castor/home3 1 1187487 204928 17.3 25:06 136.12:26 1405.5 denali/ 0 466047 213984 45.9 17:44 201.22:32 1408.1 denali/home9 0 1012095 439008 43.4 36:33 200.25:09 1420.9 denali/images0 378111 258016 68.2 18:06 237.53:03 1412.6 etal / 0 5474815 1298240 23.7 120:50 179.1 15:16 1416.9 etal /network 1 63 32 50.80:380.80:02 34.5 etal /usr/local 0 1047327 336992 32.2 25:29 220.43:57 1422.9 lyra / 1 9183 512 5.60:559.30:02 310.4 lyra /db8 1 13482783 838208 6.2 42:05 332.09:46 1431.1 lyra /db9 1 511 32 6.30:047.20:02 39.1 lyra /ndevelop 0 3263903 1432288 43.9 24:22 979.7 16:47 1421.9 lyra /ndevelop2 1 511 32 6.30:370.90:02 39.8 mira / 0 1263423 44 34.8 19:06 383.85:07 1431.1 mira /bkup-db 1 10950175 1078016 9.8 107:47 166.7 12:39 1420.1 mira /db6 0 127 32 25.20:02 12.90:02 35.7 mira /home1 0 4436575 1437472 32.4 91:17 262.5 16:46 1429.4 mira /usr 1 426207 157216 36.96:52 381.31:54 1379.4 mira /var 1 22857569120 30.23:17 351.70:53 1295.0 newton/ 128415 4000 14.11:07 59.90:04 1125.4 newton/export0 800479 317408 39.7 16:05 328.83:43 1422.8 newton/home101 4959 1600 32.30:50 32.10:01 1165.8 newton/home1114131111616 28.11:34 123.70:09 1326.6 newton/home4 1 1700639 584800 34.4 27:53 349.56:52 1419.3 newton/logsback 0 3638303 3631456 99.8 89:49 673.9 89:49 673.8 newton/nfsamba 0 945535 322144 34.1 17:01 315.63:47 1420.6 newton/nfsamba2 1 95 32 33.70:02 12.90:02 40.0 newton/opt 0 1376415 333184 24.2 29:04 191.13:55 1420.0 newton/sol2 1 83804776096 9.18:15 153.80:53 1440.6 newton/usr3 119711 8032 40.71:13 110.10:06 1280.6 newton/usr4 0 FAILED newton/usr5 1 12140738304 31.63:34 178.90:28 1370.5 newton/wclrspool 1 533855 250912 47.0 12:32 333.72:58 1412.1 panther / 0 2629215 1160640 44.1 48:22 400.0 13:32 1429.6 panther /data 110513 5344 50.80:15 356.10:05 1019.0 (brought to you by Amanda version 2.4.1p1) - End of forwarded message from [EMAIL PROTECTED] - -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Spam's a sacrific, at least there's no viruses.
comments about line length, spam, posting policies, and HTML deleted Some general observations on this and previous related threads: Amanda is free software. The amanda-users mailing list is free. Someone (not me) administers the list and pays for it. When someone gets something for free, they can suggest changes to the person(s) responsible for providing it. The person(s) giving things away are not obligated to make any requested changes, but may if they choose, and public opinion may or may not be a factor in that decision. If suggestions aren't taken, accept the fact that not everyone's opinions and priorities are the same. Everything in life has pros and cons, mailing lists are no exception. No list will fit everyone's needs. Subscribe to the one's that best fit your needs, unsubscribe from the ones that don't. If anyone knows how to run the perfect mailing list, they should start one and show the world how its done. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Working with multiple tape drives----- Ammended
--On Monday, April 27, 2020 18:01:38 -0400 Gene Heskett [EMAIL PROTECTED] wrote: On Wednesday 11 September 2002 12:50, Quinn, Richard C. - Collinsville IT wrote: E: Working with multiple tape drives- Ammended Date: Wed, 11 Sep 2002 11:50:51 -0500 From: Quinn, Richard C. - Collinsville IT [EMAIL PROTECTED] To: Gene Heskett [EMAIL PROTECTED], [EMAIL PROTECTED] Yes, my box is a Sparc E-450 running Sol 6. I am using the SST driver for Solaris 6. I think it(SST Driver) is the predecessor to Solaris' sgen driver for Sol 7 and 8. Here are the boot messages for the Jukebox robotic arm and its 2 QUANTUM drives Sep 4 12:30:12 sun1 unix: sst3:found Changer device at tgt0, lun0 Sep 4 12:30:12 sun1 unix: sst3:Vendor/Product ID = STK 9730 Sep 4 12:30:12 sun1 unix: sst3 at pci1000,f7: Sep 4 12:30:12 sun1 unix: target 0 lun 0 Sep 4 12:30:12 sun1 unix: sst3 is /pci@1f,4000/scsi@4,1/sst@0,0 And try as I might, includeing hilighting the cmplete message, there is something in the listing that prevents me from quoting it all. The bottom line is that for this, I think you are going to need the manuals on this device. Its entirely possible it has a problem. I find it different in that it finds the robot at address 0, and the two drives at address 1 and 2. But properly set in amanda.conf and chg-scsi.conf, I don't believe that to be a problem. You may have to either take it to a winderz box and check it with their software, or return it to the vendor with your impression of the problem. You might also see if you can install mtx on your server (it requires GNU make and possibly a few other things not standard on Solaris) and use that to control your changer. If you can use mtx commands to control your library from the command line then it should be straightforward to use Amanda's chg-mtx driver instead of chg-scsi. I believe mtx accesses the changer through a raw device, bypassing the scsi driver, and can sometimes do more with some changers. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Too many taper retries
--On Thursday, September 12, 2002 11:03:48 +0800 Alvin Ko [EMAIL PROTECTED] wrote: I used amanda 2.4.2p2 with a DDS-3 tape drive to do a full backup of my Linux last night. In the amanda.conf file, I used chg-manual as the changer with 3 tapes. My /export/home folder has 23GB data. I had labeled three tapes (Tape-01, Tape-02, Tape-03) and then start the backup. 3 hours later, she asked me to insert backup tape into slot 1. When amdump completed, I got the following report. --- These dumps were to tapes Tape-01, Tape-02, Tape-03. The next 3 tapes Amanda expects to used are: a new tape, a new tape, a new tape. FAILURE AND STRANGE DUMP SUMMARY: localhost /export/home lev 0 FAILED [too many taper retries] ... NOTES: ... taper: tape Tape-01 kb 12013824 fm 7 writing file: No space left on device taper: retrying localhost:/export/home.0 on new tape: [writing file: No space left on device] taper: tape Tape-02 kb 12004832 fm 1 writing file: No space left on device taper: retrying localhost:/export/home.0 on new tape: [writing file: No space left on device] taper: tape Tape-03 kb 0 fm 0 [OK] driver: Could not rmdir /mnt/hdc1/20020911: Directory not empty --- She could not backup my /export/home folder into multiple tapes. Anybody knows why? Best Regards, Alvin K. T. Ko Amanda can not backup any filesystem that is bigger than a single tape. Evidently your tapetype has a size listed greater than the actual capacity of your tape or Amanda wouldn't even have tried. You mentioned DDS3 which has a 12GB raw capacity, and that is about how much taper says it wrote before getting the 'no space' error. If your data is highly compressible, you might be able to get it to fit using compression, otherwise you will have to split your disklist entry for /export/home into a few (or several) subdirectories that will each fit on a tape and use tar to do the backups (dump usually either won't back up subdirectories or will be unable to keep track of the dumpdates for them). Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Tape DDS-3 values
--On Thursday, September 12, 2002 15:54:43 +0200 Kablan BOGNINI [EMAIL PROTECTED]
wrote:
I am using HP DDS-3 tapes for my backup. I've tried to
get the correct values for my tape. But tapetype gives
this result:
define tapetype HP-DDS3-DAT {
comment just produced by tapetype program
length 9860 mbytes
filemark 0 kbytes
speed 840 kps
}
I think this is not correct because I've a DDS-3 125M
tape with 12GB.
Could someone give me more accurate values for this
tape or point me to doc ?
You probably have compression enabled on your drive, and
it is making tapetype's data bigger. Try turning off the
compression and re-running tapetype.
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: [Amanda-users] Re: Tape DDS-3 values
Good drives and tapes rarely have errors. If you are getting frequent tape errors you should investigate why; your tapes and/or drives could be in need of cleaning/repair/replacement. Since failing drives and tapes don't get better, just worse, you will be continually adding more workarounds (shorter backup cycles, duplicate backups, duplicating data on your systems, archiving in error-tolerant formats, etc.) and still always live in fear of having to attempt a restore. I've been there, done that, and its certainly no fun. If your company won't pay to repair or replace whatever it takes, and you don't have any other employment options at the moment (I know times are tough in IT), be sure to document your problems, send memos, add it to your reports, so when (not if) you are unable to restore critical data due to tape errors you won't be the one escorted out the door. Frank --On Saturday, September 14, 2002 13:16:10 +1000 Jason Thomas [EMAIL PROTECTED] wrote: we had the same problem, we now store the data uncompressed on the tape. And still get frequent errors. On Fri, Sep 13, 2002 at 06:14:46PM +0100, Niall O Broin wrote: On Fri, Sep 13, 2002 at 10:25:29AM -0400, Jon LaBadie wrote: Is it a real, or theoretical, problem? I.e. has anybody experienced bit errors in a gzip'ed document? For me the incidence is low enough that I don't feel a need to use bzip2 for that extra protection. The value of your data may lead to a different conclusion. I brought this up and it's not theoretical - I've had problems with gzipped tar files coming back off tapes. I definitely have problems with my tape drive but as mentioned, such errors in a tar file would only have caused problems with some files - with the gzipped tar file, you're done for once you hit an error. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.53702 secs) *** Qmail-Scanner Envelope Details End ***
Deja vu all over again
What's up with last week's postings getting re-injected into the list? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Processing Time
--On Thursday, September 19, 2002 08:52:31 -0400 Jason Greenberg [EMAIL PROTECTED] wrote: I cron schedule my Amanda dump for 12:45 am, but it doesn't complete until about 9:00am. If I look at my switch graphs, the data transfer only takes about 1 hour. What is it doing the rest of the time??? Look at your daily report, it tells you how long it took to dump and tape each disklist entry and the total dump and tape time. If you want to know what's going on while Amanda is still running, then run amstatus and it will tell you. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: What can you say about this?
--On Thursday, September 19, 2002 09:48:22 -0500 Neil
[EMAIL PROTECTED] wrote:
This was the report I got last night during my amdump test. What can you say about
it?
I tried doing an mt erase 0 but looks like that the previous label is still there.
I even tried su amanda -c amlabel -f Daily Daily01, it forces it but I got a
feeling that the old label is still there.
What would be the command to totally erase everything on my tape, including the
labels?
amlabel -f does rewrite the label no matter what label used to be there.
It looks like Amanda took the Daily01 label and did a backup to it.
It also appears that might have been the only tape you labeled and
Amanda is looking for another tape matching labelstr in your config, so
it was looking for Daily001. If you had already labeled a Daily02 it
would have asked for that.
If you were expecting Amanda to keep writing to the same tape, it
won't until you've completed tapecycle number of runs.
Frank
REPORT---
From: User Amanda [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: 19 Sep 2002, 02:06:09 AM
Subject: Daily AMANDA MAIL REPORT FOR September 19, 2002
These dumps were to tape Daily01.
The next tape Amanda expects to use is: Daily001.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 0:51
Dump Time (hrs:min)0:46 0:46 0:00
Output Size (meg)2062.2 2061.90.4
Original Size (meg) 2062.2 2061.90.4
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped3 2 1 (1:1)
Avg Dump Rate (k/s) 761.2 763.1 49.5
Tape Time (hrs:min)0:47 0:46 0:00
Tape Size (meg) 2062.3 2061.90.4
Tape Used (%) 106.9 106.80.0 (level:#disks ...)
Filesystems Taped 3 2 1 (1:1)
Avg Tp Write Rate (k/s) 756.4 757.4 102.5
NOTES:
planner: buko.restricted.dyndns.org /var 20020919 0 [dumps too big, full dump
delayed]
taper: tape Daily01 kb 2111840 fm 3 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
buko.restric / 0 44480 44512 --0:361246.1 0:56 796.4
buko.restric /usr0 20668802066912 -- 45:31 756.8 45:32 756.6
buko.restric /var1 360416 --0:07 49.5 0:04 102.5
(brought to you by Amanda version 2.4.3b4)
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Permission denied errors
--On Friday, September 20, 2002 11:43:51 -0400 Ashwin Bijur [EMAIL PROTECTED] wrote: We use amanda 2.4.2p2 on Red Hat Linux 7.3. We have nfs mounted a directory on the amanda server called /xtreme23/scratch. Some of the subdirectories and files under the scratch directory have permission 600. The /etc/exports file on the xtreme23 machine has the scratch directory exported with read and write permissions (/scratch *(rw)). When we run amanda, we get an error message saying Permission Denied for these files. Now as user=amanda and group=disk, we should be able to backup these files. What are we doing wrong? I'm assuming you are using tar (since I don't think you can use dump on an NFS mount). Amanda uses the runtar wrapper script, which is suid root so that tar can run as root (since tar accesses via the filesystem it has to run as root to access all the files). Most OS's map NFS access requests from UID 0 (root) to nobody or some other non-root user for security reasons. You probably need to change your export options on xtreme23 to include the no_root_squash option (or whatever its called on the NFS server's OS) for the export to the Amanda server so that root on the Amanda server has root access to /xtreme23/scratch, so tar can see all of the files. Frank Thanks in advance, Ashwin Bijur Assistant Systems Administrator. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: fullbackup
--On Friday, September 20, 2002 17:46:28 +0200 Marcus Schopen [EMAIL PROTECTED] wrote: I'd like to set up a second set of tapes for making a full backup each sunday. My daily set with a set of 24 tapes is running from monday to saturday (dumpcycle 6 and tapecycle 24). For the weekly full backuo I have a set of 20 tapes. Amanda should write a full backup to each tape, so I have weekly full backups for the last 20 weeks. Is this the right configuration to force amanda to make a fullback each time: dumpcycle 0 tapecycle 20 maxcycle 0 Contab entry would be 0 8 * * 7 backup /usr/sbin/amdump DudeWeeklySet Thanks Marcus Looks OK. Don't forget to use a dumptype with 'record no' for your weekly or you will hose your daily schedule. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: fullbackup
--On Friday, September 20, 2002 21:46:48 +0200 Marcus Schopen [EMAIL PROTECTED] wrote: Frank Smith wrote: --On Friday, September 20, 2002 17:46:28 +0200 Marcus Schopen [EMAIL PROTECTED] wrote: I'd like to set up a second set of tapes for making a full backup each sunday. My daily set with a set of 24 tapes is running from monday to saturday (dumpcycle 6 and tapecycle 24). For the weekly full backuo I have a set of 20 tapes. Amanda should write a full backup to each tape, so I have weekly full backups for the last 20 weeks. Is this the right configuration to force amanda to make a fullback each time: dumpcycle 0 tapecycle 20 maxcycle 0 Contab entry would be 0 8 * * 7 backup /usr/sbin/amdump DudeWeeklySet Thanks Marcus Looks OK. Don't forget to use a dumptype with 'record no' for your weekly or you will hose your daily schedule. Thanks for answering that fast. But I don't understand the 'record no' thing. The DudeWeeklySet is a totaly different config. Why or how can it overwrite my daily stuff that runs on a different config with a different set of tapes. Thanks Marcus Dump keeps track of the times and levels of the last dump of each filesystem by saving the times in /etc/dumpdates. Since tar doesn't really have the same concept of levels, Amanda fakes it by writing similar information in /etc/amandates. Neither one has any idea of multiple configs, so the same file will get updated each time you run any of your configs. So when your 'weekly full' runs it will update the file, and then when your 'daily' runs, it will be expecting to back up files newer than the last 'daily' run, but dump or tar look for files newer than the times in the dumpdates/amandate file and will only be backing up files newer than the time of the 'weekly' run. The end result is that your daily set of tape may be unable to restore the entire filesystem. Your weekly set should be OK since its always a full. Frank that y -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: fullbackup
--On Friday, September 20, 2002 20:58:42 -0400 Gene Heskett [EMAIL PROTECTED] wrote: On Friday 20 September 2002 16:32, Frank Smith wrote: --On Friday, September 20, 2002 21:46:48 +0200 Marcus Schopen [EMAIL PROTECTED] wrote: Frank Smith wrote: --On Friday, September 20, 2002 17:46:28 +0200 Marcus Schopen [EMAIL PROTECTED] wrote: I'd like to set up a second set of tapes for making a full backup each sunday. My daily set with a set of 24 tapes is running from monday to saturday (dumpcycle 6 and tapecycle 24). For the weekly full backuo I have a set of 20 tapes. Amanda should write a full backup to each tape, so I have weekly full backups for the last 20 weeks. Is this the right configuration to force amanda to make a fullback each time: dumpcycle 0 tapecycle 20 maxcycle 0 Contab entry would be 0 8 * * 7 backup /usr/sbin/amdump DudeWeeklySet Thanks Marcus Looks OK. Don't forget to use a dumptype with 'record no' for your weekly or you will hose your daily schedule. Thanks for answering that fast. But I don't understand the 'record no' thing. The DudeWeeklySet is a totaly different config. Why or how can it overwrite my daily stuff that runs on a different config with a different set of tapes. Thanks Marcus Dump keeps track of the times and levels of the last dump of each filesystem by saving the times in /etc/dumpdates. Since tar doesn't really have the same concept of levels, Amanda fakes it by writing similar information in /etc/amandates. Neither one has any idea of multiple configs, so the same file will get updated each time you run any of your configs. So when your 'weekly full' runs it will update the file, and then when your 'daily' runs, it will be expecting to back up files newer than the last 'daily' run, but dump or tar look for files newer than the times in the dumpdates/amandate file and will only be backing up files newer than the time of the 'weekly' run. The end result is that your daily set of tape may be unable to restore the entire filesystem. Your weekly set should be OK since its always a full. Frank that y Excellent explanation Frank, thanks, I needed that. But this also points out that the fix would appear to be fairly simple, just a matter of moving the location of this dumpdates/amandates file to where ever that keyword points to in the individual amanda.conf. Or is this something thats carved into whatever stone dump/tar is cut from, and not an amanda function? The latter case, amandates, certainly seems to indicate its an actual amanda function and therefore subject to being whatever the coders want it to be including its location. I don't think amandates' location is configurable (unless its been added into the beta releases). It would be a nice feature to have though. Of course, dumpdates' location is set in stone in most dump programs. I guess you could compile your own, but it would still be the same for all configs unless you built multiple amandas each configured with a seperate dump executable. I think it would be nice if Amanda was friendlier to multiple configs so the run times could overlap as well, but I would suspect that would also be quite a bit of work. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda reports and some questions
--On Friday, September 20, 2002 22:35:33 -0500 Neil [EMAIL PROTECTED] wrote: Hi guys, Looks like my amanda is getting better. :) Take a look at the email report that amanda sent me. http://restricted.dyndns.org/amandareport.txt And here is my new amanda.conf. http://restricted.dyndns.org/amanda.conf And here is my new disklist. http://restricted.dyndns.org/disklist.txt I only have 1 tape HP DDS-2. Then I wanted to do a full backup of my whole freebsd system everyday at 11pm. Since it's just 1 tape, is it alright if I configured my device in amanda.conf as /dev/nrsa0 (non-rewinding)? Please comment on my amanda.conf. Thank you in advance. Neil If you really want to do what you're saying, your dumpcycle should be 1 day, not 1 week. If at all possible, get more tapes. Every time you start your backup you are destroying the only backup you have. If some files get deleted or corrupted and you don't notice it before 11pm on the day it happens, you won't be able to recover. If you ever get a tape error you have no backup. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Use of tape changers?
--On Friday, September 20, 2002 21:19:43 -0400 Gene Heskett [EMAIL PROTECTED] wrote: I'd think that rather than larger tapes, faster drives would be higher on the list, if for no other reason than to get the darned job done before the offices open in the morning. Here, it occasionally is still running when the 4am stuff comes due, but this DDS2 I use is a slower drive, less than 400kb/second. Obviously a busier machine would need a faster drive. The upside of the DDS2 is the price of the tapes, they are almost a non-issue at less than 50 bucks a ten pack on ebay. Another option to a faster tape drive is more holding disk space. If your holding disk is as large as your backups (and your reserve is set appropriately) you can shorten your backup window to just the time your dumpers take, and even if it takes 10 or 15 hours to write it to tape it won't impact the clients. Even if you don't have enough disk for the entire backup, whatever you can add to it will help (assuming your tape drive is the limiting factor. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: reporting
--On Monday, September 23, 2002 18:02:16 +0100 Mike Brodbelt [EMAIL PROTECTED] wrote: . Secondly, as my filesystems have grown, my reports have become less tidy - the columns of figures are running together. Is there an easy way to tell amanda to space the columns on reports out a bit more?? man amanda, look for 'columnspec', also look in the comments of the default amanda.conf. I use: columnspec OrigKB=1:8,OutKB=1:8,DumpRate=1:7,TapeRate=1:6 but you just need to look at your reports to see which columns can be made narrower or wider for the ranges of numbers you get. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: restoring of data
--On Monday, September 23, 2002 17:28:00 -0500 Neil [EMAIL PROTECTED] wrote: Is it possible to restore data to an amanda-client machine but the commands will be executed on the amanda-server console? Thanks. Neil Amanda is designed to restore data onto the machine running amrecover or amrestore. I'm sure there are some tricky ways around it (such as NFS mounting the client on the server, or using dd/tar/restore directly to read the tape and pipe it to rsh on the client), but it wasn't made that way. You could restore to the Amanda server and then rsync/scp the data back to the client, but why? If you are just trying to avoid physically going to the client, just ssh to it and run amrecover remotely. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
