Re: win32
On Thu 19 Sep 02 16:32, Christophe Kalt wrote: Also, it seems that it would be much less work to actually port the existing (UNIX) amanda source (at least or at most?;) the client parts. Having a separate project really doesn't seem right. Erm... ever tried to port code from Unix to Windows? Ever wonder why there is so little Opensource Windows code? ..Brian -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
Re: Hostname lookups[continued]
Martinez, Michael - CSREES/ISTM wrote: When I first installed amanda I had this problem too, and fixed it by making sure .amanahosts had correct permissions and correct contents. Here's the specs, in the case when an Amanda server is also an Amanda Client. Server .amandahosts (perms 400) server.com amanda server.com root client1.com root client2.com root client3.com root Client .amandahosts (perms 660) --- server.com amanda Michael Martinez System Administrator Heya there Just to check I changed the permissions to 777 still no luck My .amandahosts file looks like yours. Mozzi
Re: newbie needs help deciphering vauge error message
Just to followup - it turns out that the package installed all the setuid programs as user bin (solaris 2.6 package from sunfreeware.com - one I recommended to someone on the list!). (thanks to Jon LaBadie for point out that /tmp/amanda can have errors in there if you stare long enough). chowning them to root fixed the problem, and I can now backup remote clients. However, I can't backup the backup server itself. It seems for some reason it's never reading the ~amanda/.amandahosts file (ls -lu ~amanda/.amandahosts shows the datestamp not changing between running amcheck or amdump, and the last time I used cat on the file. Because amcheck and amdump are setuid root, I can't run truss on them to see where it's trying to read it from. Is there some way I can find out which directories it's looking for .amandahosts ? I've already su'd to the amanda user, and catted this file, so amcheck *should* be able to view it. John
Tapetype for Onstream ADR^2 120 and ADR50
Hi All,
As requested in one of the FAQ's I hereby post the tapetype output of my
new OnStream ADR^2 120 G drive.
This is a SCSI-LVD drive with 60G native capacity, used on a RedHat 7.2
machine with the standard
RedHat provided amanda RPM's. It works like a charm.
I also use an ADR50 drive, which operates fine as long as there is no
tape in it during the actual backup.
(Everything is backed up to holdingdisk first). In the morning I stick a
tape in and run amflush
and amverify. The 120G drive doesn't need this workaround.
Adapter Configuration:
SCSI Adapter: Adaptec AIC-7892 Ultra 160/m SCSI host adapter
Ultra-160/m LVD/SE Wide Controller at PCI 0/14/0
(Adaptec 29160)
I use stinit to initialize both drives at boot-up time. For
completeness, I post the stinit.def scripts as well.
It is called at the end of rc.local. (man stinit)
If you have any questions, please mail me at [EMAIL PROTECTED]
I'll try to put this in the FAQ-O-Matic as well.
Regards,
Edwin Hakkennes
Zarlink Semiconductor XIC B.V.
stinit.def
-
This file contains example definitions for different kinds of tape
# devices. If the user agrees with the definitions, they can be used
# in the definition file stinit.def by changing the manufacturer and
# model fields to correspond the real tape device being defined.
# The common definitions that can usually be used
manufacturer=OnStream model=ADR50 Drive {
scsi2logical=1
mode1 blocksize=32768 compression=0
}
manufacturer=OnStream model=ADR Series {
scsi2logical=1
mode1 blocksize=32768 compression=0
}
--
Tapetypes
--
##OnStream ADR120 Tape specification (120/60 GB Tape)
define tapetype ADR120 {
comment just produced by tapetype program
length 57136 mbytes
filemark 0 kbytes
speed 3205 kps
lbl-templ /etc/amanda/labels/DIN-A4-XIC.ps
}
##OnStream ADR50 Tape specification (50/25 GB Tape)
define tapetype ADR50 {
comment Tape type generated
length 21056 mbytes
filemark 0 kbytes
speed 1579 kps
lbl-templ /etc/amanda/labels/DIN-A4-XIC.ps
# lbl-templ /usr/share/doc/amanda-server-2.4.2p2/examples/DIN-A4.ps
}
Re: Can Amanda put its index on a tape?
This one's in the possible planned features. I think its under file-0,file-n. If you write the index database at the _end_ of the tape, then its alright. But Amanda's gotta have the facility for locking partition ordering. The one bit of an amanda tape that is ALREADY fixed is the 32k tape trailer label. Could a list be put in there without significant disruption. Just like the first file, and the first 32k of each dump file are in part intended for human consumption, I picture putting an advert in the header file, and a plain text list in the tape trailer. Simplisticly, I immagine generating this from the log.date file that amanda leaves behind, or from the equivalent of running amadmin conf export. I also recommend keeping the amanda catalog information on a partition that is dumped always-full. Chris Ritson
Re: newbie needs help deciphering vauge error message
On Fri, Sep 20, 2002 at 08:55:36AM +0100, John P. Looney wrote: Just to followup - it turns out that the package installed all the setuid programs as user bin (solaris 2.6 package from sunfreeware.com - one I recommended to someone on the list!). (thanks to Jon LaBadie for point out that /tmp/amanda can have errors in there if you stare long enough). chowning them to root fixed the problem, and I can now backup remote clients. I was unaware of the SFW package before your mention of it. Since then I've been in contact with Steve Christian (sp?) who maintains SFW and I'm going to work with him to enhance the Solaris offerings. I don't have a Sparc system with which to try things on. I did note the pkgmap list showing the bin, not root suid, and planned to mention that to him. Glad to see it is a real problem and I would not have been whistiling in the wind. Please note any other problems you might have had including the lack of use/installation instructions. Or how it might have been better (ex. should it create the amanda user dir, and a config dir with example amanda.conf files?). Personal email might be most appropriate. I'm going to make a general request for similar info from other who might have used the SFW package. However, I can't backup the backup server itself. It seems for some reason it's never reading the ~amanda/.amandahosts file (ls -lu ~amanda/.amandahosts shows the datestamp not changing between running amcheck or amdump, and the last time I used cat on the file. Because amcheck and amdump are setuid root, I can't run truss on them to see where it's trying to read it from. Is there some way I can find out which directories it's looking for .amandahosts ? I've already su'd to the amanda user, and catted this file, so amcheck *should* be able to view it. Ummm, directories in .amandahosts? That should be a file, not a directory. I think it should also be owned by amanda_user and permissions 600 otherwise it is not looked at. In the file, list the tapehost by fqdn I believe. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Dumps causing trouble after migration
Hi, I've been backing up my main server with amanda for some time, and recently I've upgraded the machine, and reinstalled the OS and software. The box in question is running Debian Woody, with XFS filesystems, and amanda 2.4.2p2 (I rebuilt the package, to make sure it found xfsdump). All of my filesystems are coming up with strange dump summaries:- /-- castor sda5 lev 0 STRANGE sendbackup: start [castor:sda5 level 0] sendbackup: info BACKUP=/sbin/xfsdump sendbackup: info RECOVER_CMD=/sbin/xfsrestore -f... - sendbackup: info end | xfsdump: using file dump (drive_simple) strategy | xfsdump: version 3.0 - Running single-threaded | xfsdump: level 0 dump of castor:/root | xfsdump: dump date: Thu Sep 19 23:10:53 2002 | xfsdump: session id: e93d1cfc-888b-44a4-9f0a-7bd1571bd36b | xfsdump: session label: | xfsdump: ino map phase 1: skipping (no subtrees specified) | xfsdump: ino map phase 2: constructing initial dump list | xfsdump: ino map phase 3: skipping (no pruning necessary) | xfsdump: ino map phase 4: skipping (size estimated in phase 2) | xfsdump: ino map phase 5: skipping (only one dump stream) | xfsdump: ino map construction complete | xfsdump: estimated dump size: 10547520 bytes | xfsdump: /var/lib/xfsdump/inventory created | xfsdump: creating dump session media file 0 (media 0, file 0) | xfsdump: dumping ino map | xfsdump: dumping directories ? sh: /sbin/sed: No such file or directory | xfsdump: dumping non-directory files | xfsdump: ending media file | xfsdump: media file size 8950880 bytes | xfsdump: dump size (non-dir files) : 8598056 bytes | xfsdump: dump complete: 2 seconds elapsed | xfsdump: Dump Status: SUCCESS sendbackup: size 8742 sendbackup: end Looking through this, the only thing I can see wrong is the reference to sed. My old machine had sed in /bin, not /sbin, as does the new one. Can anyone tell me what's causing the problem? Mike.
Disks offline again
Well no one answered my previous post but I hope this will ring a bell with someone. For some reason when the estimates are retrieved they get a -1k for all directories. I forced an fsck but that did not help. got result for host gator20.triparish.net disk /var: 0 - -1K, -1 - -1K, -1 - -1K got result for host gator20.triparish.net disk /usr: 0 - -1K, -1 - -1K, -1 - -1K Any ideas Thank you, Lewey Taylor Computer Sales Services, Inc. (985) 879-3219
Re: win32
Brian, Tried that, but there is alot of UNIXism in amanda. I did go the cygwin route a couple of years ago. It kind of worked. I am currently rewriting the whole client side in perl. To get it to work you just have to download ActiveState perl and my script, that's it. I am also looking at using this perl code to backup UNIX/Linux plus any other type of systems (ie. OSX) that supports perl. Should have some code for people to look at early next week. Jim On Thu 19 Sep 02 16:32, Christophe Kalt wrote: Also, it seems that it would be much less work to actually port the existing (UNIX) amanda source (at least or at most?;) the client parts. Having a separate project really doesn't seem right. Erm... ever tried to port code from Unix to Windows? Ever wonder why there is so little Opensource Windows code? ..Brian -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
RE: Hostname lookups[continued]
Remember, you gotta check the .amandahosts on both the client and the server (they will be different) and you shouldn't make any amanda stuff mod 777 Also remember that amanda by default communicates over ports 10080 - 10083 so you gotta make sure these ports are available and make sure all your network stuff is right Michael Martinez System Administrator -Original Message- From: Mozzi [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 2:35 AM To: Martinez, Michael - CSREES/ISTM Cc: 'Gene Heskett'; amanda Subject: Re: Hostname lookups[continued] Martinez, Michael - CSREES/ISTM wrote: When I first installed amanda I had this problem too, and fixed it by making sure .amanahosts had correct permissions and correct contents. Here's the specs, in the case when an Amanda server is also an Amanda Client. Server .amandahosts (perms 400) server.com amanda server.com root client1.com root client2.com root client3.com root Client .amandahosts (perms 660) --- server.com amanda Michael Martinez System Administrator Heya there Just to check I changed the permissions to 777 still no luck My .amandahosts file looks like yours. Mozzi
Re: Help compile tapetype.c
On Friday 20 September 2002 01:22, Neil wrote: I have downloaded from sourceforge. Which could explain things if the cvs repository is in mid-patch or something. Get the latest amanda-2.4.3b4-20020919.tar.gz from http://www.iro.umontreal.ca/~martinea/amanda If that won't build, then you are missing other things on your system, I've already built and installed it this morning. I got this when I 'make tapetype': [root@coyote tape-src]# make tapetype source='tapetype.c' object='tapetype.o' libtool=no \ depfile='.deps/tapetype.Po' tmpdepfile='.deps/tapetype.TPo' \ depmode=gcc3 /bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64 -g -O2 -c `test -f tapetype.c || echo './'`tapetype.c /bin/sh ../libtool --mode=link gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o tapetype tapetype.o ../common-src/libamanda.la libamtape.la ../common-src/libamanda.la -lm -lreadline -ltermcap -lnsl gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o tapetype tapetype.o ./.libs/libamtape.a ../common-src/.libs/libamanda.a -lm -lreadline -ltermcap -lnsl [root@coyote tape-src]$ Note that my actual command line to the compiler used gcc, not cc, so I still suspect that you don't have ALL the development stuff installed. I tried make tapetype in tape-src direcoty. This is what I got. [snip] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Hostname lookups[continued]
On Friday 20 September 2002 02:35, Mozzi wrote: Martinez, Michael - CSREES/ISTM wrote: When I first installed amanda I had this problem too, and fixed it by making sure .amanahosts had correct permissions and correct contents. Here's the specs, in the case when an Amanda server is also an Amanda Client. Server .amandahosts (perms 400) server.com amanda server.com root client1.com root client2.com root client3.com root Client .amandahosts (perms 660) --- server.com amanda Michael Martinez System Administrator Heya there Just to check I changed the permissions to 777 still no luck My .amandahosts file looks like yours. Mozzi Mozzi, those perms must be exactly as above, she won't take excessive perms for security reasons. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: win32
On Sep 19, Brian Jonnes wrote: | On Thu 19 Sep 02 16:32, Christophe Kalt wrote: | Also, it seems that it would be much less work to actually | port the existing (UNIX) amanda source (at least or at most?;) | the client parts. Having a separate project really doesn't | seem right. | | Erm... ever tried to port code from Unix to Windows? yes, i've done it a few times, and have maintained programs that could be compiled natively on either platform. Depending on what the application is/does and how it was written, it isn't hard at all. this doesn't say anything about how feasible this would be for amanda, i haven't looked at the code this closely.
Re: Weird permission problem running amdump
Hi, Frank, and everyone else. My guess is that the permission problem is higher up. Try su - amanda and then try to cd down the directory structure. The index, pip, and _users5 directories should be created automatically during the backup run. As the amanda user, see if you can create a file in /home/amanda/DailySet1/. Yep, no problem. If not, verify that amanda owns /home/amanda/ and everything below it. I did a chown -R amanda:disk on /home/amanda early on. amanda owns everything. If /home/amanda is mounted from a remote server, make sure amanda can write to it. It's not. It's local. Chances are you set it up as root and some or all of the files and directories are still owned by root with hostile permissions. That was the first thing that came to my mind. I'm going to redo everything from scratch today and see if things turn out better. Regards, Caitems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Weird permission problem running amdump
Hi, Gene, The only thing that comes to mind quickly is probably related to the question/statement you do have a user amanda, who is a member of group disk, don't you? Yes, of course. I think that was done automagically when I installed the amanda rpms. As I said in my response to Frank, I'm going to rip everything out (after saving my amanda.conf file and disklist file) and start over. Regards, Cait
Re: Weird permission problem running amdump
Caitlyn M. Martin wrote: Hi, Gene, The only thing that comes to mind quickly is probably related to the question/statement you do have a user amanda, who is a member of group disk, don't you? Yes, of course. I think that was done automagically when I installed the amanda rpms. As I said in my response to Frank, I'm going to rip everything out (after saving my amanda.conf file and disklist file) and start over. Regards, Cait When you rip it out...try building it yourself instead of depending on an RPM. =G=
Re: Weird permission problem running amdump
On Friday 20 September 2002 10:03, Caitlyn M. Martin wrote: Hi, Gene, [...] As I said in my response to Frank, I'm going to rip everything out (after saving my amanda.conf file and disklist file) and start over. The saveing isn't required, if they exist, they are not overwritten by the installer. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Permission denied errors
Hi, 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? Thanks in advance, Ashwin Bijur Assistant Systems Administrator. Combustion Research and Flow Technology, Inc. 174 North Main Street Building 3, P.O.Box 1150 Dublin, PA 18917 Tel: (215) 249-9780
fullbackup
Hi, 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 -- Marcus Schopen(0 P.O. Box 10 25 25 //\ Deutsche Zope User Group D-33525 Bielefeld V_/_www.dzug.org
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
Anyone using HP 40x6e changer?
Anyone using a HP 40x6e changer? I'm banging my head against the wall trying to get chg-zd-mtx to not generate lots of syntax errors. I'd appreciate a working amanda.conf and changer.conf if anyone has one. I've got the device answering correctly at the scsi level to ID5 LUN 0 1, but the glue scripts aren't parsing the status data correctly. thanks 1,000,000 in advance. -Pete
How long does it take?
Does it really take long for tapetype to finish? I executed it and still got no generated text after 15 mins. But I was seeing an incrementing file(s). Thank you. Neil
Re: Weird permission problem running amdump
On Friday 20 September 2002 11:06, Gene Heskett wrote: On Friday 20 September 2002 10:03, Caitlyn M. Martin wrote: Hi, Gene, [...] As I said in my response to Frank, I'm going to rip everything out (after saving my amanda.conf file and disklist file) and start over. The saveing isn't required, if they exist, they are not overwritten by the installer. I should have qualified that by saying the tarballs installer won't. I have NDI whether the rpm does or not. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: How long does it take?
On Friday 20 September 2002 13:34, Neil wrote: Does it really take long for tapetype to finish? I executed it and still got no generated text after 15 mins. But I was seeing an incrementing file(s). Thank you. Neil On big, slow drives, it might take over a day to run. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Weird permission problem running amdump
On Fri, 2002-09-20 at 15:07, Gene Heskett wrote: I should have qualified that by saying the tarballs installer won't. I have NDI whether the rpm does or not. I did use the rpms, I did reinstall, and everything worked. I have no clue what went wrong the first time. All I know I successfully backed up two servers. I'm now expanding my disklist to include all the servers with clients installed so that we can get a more complete backup tonight. Thanks, Cait
Re: fullbackup
Hei Frank, 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 -- Marcus Schopen(0 P.O. Box 10 25 25 //\ Deutsche Zope User Group D-33525 Bielefeld V_/_www.dzug.org
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
Use of tape changers?
Greetings. We've been happily running Amanda on a number of different systems around here for several years. Up to this point, we've always used a single tape drive (usually high-capacity) on each tape server. Now we're getting to the point where disk capacity is exploding. Tape capacity is increasing as well, of course, but it appears that we'll soon be in a situation where one large tape drive will be inadequate. Maybe we're there already. This has lead us to consider alternatives to our somewhat simple-minded approach to backups. One alternative would be to make finer subdivisions of the file systems that we back up (with GNU tar). I.e., instead of backing up simply: /home we might put separate entries in the disklist file for: /home/annie /home/bob . . . /home/zelda or whatever. That seems mildly tedious and probably would cause us at least to have to modify our number of tapes per cycle, buy additional tapes, etc. Another thought we had was to throw additional money at the problem and buy some kind of tape changer. But I have what seems to me to be a fundamental question about changers that I don't see answered in the FAQ's or .../docs, etc. I.e., if we have some kind of a tape changer, does it allow us to exceed Amanda's one-tape-per-session limit? Can we make a single virtual tape out of multiple tapes in the changer? Or is it the function of the tape changer simply to let Amanda run unattended for as many sessions as there are tapes in the changer, but still using only one tape per session? Thanks. - Mike == Michael Hannonmailto:[EMAIL PROTECTED] Dept. of Physics 530.752.4966 University of California 530.752.4717 FAX Davis, CA 95616-8677
Re: Weird permission problem running amdump
On Friday 20 September 2002 15:43, Caitlyn M. Martin wrote: On Fri, 2002-09-20 at 15:07, Gene Heskett wrote: I should have qualified that by saying the tarballs installer won't. I have NDI whether the rpm does or not. I did use the rpms, I did reinstall, and everything worked. I have no clue what went wrong the first time. All I know I successfully backed up two servers. I'm now expanding my disklist to include all the servers with clients installed so that we can get a more complete backup tonight. Excelent! Do keep us posted, and if it works for you, be prepared to help other newbies get started with the rpms. Most of us here tend to build from scratch, using the same old configure script to build each succeeding release so we each have a personal bag of tricks. That way, its very rare that we actually see a difference when we install a new version unless we're looking at a specific item known or wished to be next on the hit list to fix. This mailing list is, by and large, fairly clean of spam, or my filters are suddenly working 100%. What I'm trying to say is that the signal to noise ratio is tolerable, and the newbees do need a seasoned user to hold their hand until the new wears off the bee. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: fullbackup
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. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Use of tape changers?
On Friday 20 September 2002 19:57, Michael Hannon wrote: Greetings. We've been happily running Amanda on a number of different systems around here for several years. Up to this point, we've always used a single tape drive (usually high-capacity) on each tape server. Now we're getting to the point where disk capacity is exploding. Tape capacity is increasing as well, of course, but it appears that we'll soon be in a situation where one large tape drive will be inadequate. Maybe we're there already. This has lead us to consider alternatives to our somewhat simple-minded approach to backups. One alternative would be to make finer subdivisions of the file systems that we back up (with GNU tar). I.e., instead of backing up simply: /home we might put separate entries in the disklist file for: /home/annie /home/bob . . . /home/zelda or whatever. That seems mildly tedious and probably would cause us at least to have to modify our number of tapes per cycle, buy additional tapes, etc. Since the data itself isn't going to change/grow, only the housekeeping, I wouldn't think the expansion would be too notable unless you not only have an annie, but an alice, 2 alecias with variations on the spelling, ad infinitum. Another thought we had was to throw additional money at the problem and buy some kind of tape changer. But I have what seems to me to be a fundamental question about changers that I don't see answered in the FAQ's or .../docs, etc. I.e., if we have some kind of a tape changer, does it allow us to exceed Amanda's one-tape-per-session limit? Conditionally yes. The condition being that no one disklist entry can be larger than the tape, because the automatic changer advance when it hits EOT on that tape causes it to advance the changer, and restart that disklist entry on the next tape from square one. Can we make a single virtual tape out of multiple tapes in the changer? Some changers claim they can, and mine does, but I have not ever seen it work in practice here, nor do I need it, but my system is only 46gigs, which amanda cheerfully uses about half a 4gig tape per nightly run to back it all up on a 1 week dumpcycle. Or is it the function of the tape changer simply to let Amanda run unattended for as many sessions as there are tapes in the changer, but still using only one tape per session? Once amanda has optimized her scheduleing, there is a chance that one tape per session may well be enough. Thats so here, and the main reason for the changer is so I don't have to swap tapes quite as often, its a 4 slot magazine with a cleaning tape in the last slot. At my age, I still tend to forget it, darn it. But there is a runtapes argument in your amanda.conf which can allow amanda to use 2 or more tapes per session *if* she needs to. 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. -- Cheers Mike, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
amanda reports and some questions
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
