Re: My tape drive dissappeared after updating the operating syste m - now what?
Hi, This is an external Tape-unit? if yes, you should be able to powercycle it without rebooting the system and without any bad sideffects to the system itself. (This is my experience with the linux-servers under my control) Christoph Jeff Q Silverman wrote: On Mon, 15 Jul 2002, Bort, Paul wrote: ok, it's got a tape, but it's not rewound. Can you try this with a scratch tape in the drive? (This will erase everything on the tape.) mt -f /dev/nst0 rewind mt -f /dev/nst0 status At this point, something strange happens: SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 13344 bytes. Density code 0x61 (unknown to this mt). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN By way of contrast, a properly working tape drive would show SCSI 2 tape drive: File number=0, block number=1, partition=0. Tape block size 0 bytes. Density code 0x41 (unknown to this mt). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN So clearly, there is a problem with the density code and the tape block size. One of my co-workers suggested rebooting the system and cycling power on the tape drive while the system was done. dd if=/dev/zero of=/dev/nst0 bs=32k count=1 mt -f /dev/nst0 status mt -f /dev/nst0 rewind dd if=/dev/nst0 of=/tmp/zeroes This fails with a write not multiple of tape block size mt -f /dev/nst0 rewoffl mt -f /dev/nst0 status /tmp/zeroes should be 32K long, and all 0x0s. Any other advice? This is a production system and I am reluctant to reboot it. Jeff Jeff Silverman, sysadmin for the Research Computing Systems (RCS) University of Washington, School of Engineering, Electrical Engineering Dept. Box 352500, Seattle, WA, 98125-2500 [EMAIL PROTECTED] http://rcs.ee.washington.edu/BRL/people/jeffs/ -Original Message- From: Jeff Q Silverman [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 1:36 PM To: Bort, Paul Cc: 'Jeff Q Silverman'; [EMAIL PROTECTED] Subject: RE: My tape drive dissappeared after updating the operating syste m - now what? jeffs@truk /atm/cowiche/home/jeffs 1000 $ sudo mt -f /dev/nst0 status Password: SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 13344 bytes. Density code 0x61 (unknown to this mt). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN jeffs@truk /atm/cowiche/home/jeffs 1001 $ I symlinked /dev/tape to /dev/nst0. Jeff Silverman, sysadmin for the Research Computing Systems (RCS) University of Washington, School of Engineering, Electrical Engineering Dept. Box 352500, Seattle, WA, 98125-2500 [EMAIL PROTECTED] http://rcs.ee.washington.edu/BRL/people/jeffs/ On Mon, 15 Jul 2002, Bort, Paul wrote: Jeff, You didn't include the results of `mt -f /dev/nst0 status`, which might give some information about the state of the drive. Also, I hope you're using /dev/nst0 instead of /dev/st0 in your amanda configuration, or your backups may be no good. You can continue to do backups to your holding disk, which you can then flush to tape later. -Original Message- From: Jeff Q Silverman [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 12:06 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: My tape drive dissappeared after updating the operating system - now what? I have been using amanda without a problem for over two years. This weekend, I updated the operating system on my amandaa server and the tape drive broke. I assume that the problem is a software problem with the operating system. With a tape in the drive, the command cat /dev/st0 causes the process to hang in a sleep (wait for I/O) state. I assume that the cat command ought to output the contents of the tape to the next file mark, right? dmesg has the following information (edited for relevence, I hope) Linux version 2.4.9-12smp ([EMAIL PROTECTED]) (gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-85)) #1 SMP Tue Oct 30 18:16:48 EST 2001 (scsi0) Adaptec AIC-7892 Ultra 160/m SCSI host adapter found at PCI 0/9/0 (scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs (scsi0) Downloading sequencer code... 396 instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0 Adaptec AIC-7892 Ultra 160/m SCSI host adapter blk: queue c17fc418, I/O limit 4095Mb (mask 0x) Vendor: SEAGATE Model: ST318416N Rev: 0004 Type: Direct-Access ANSI SCSI revision: 03 blk: queue c17fc218, I/O limit 4095Mb (mask 0x) Vendor: ADIC Model: FastStor DLT Rev: 0133 Type: Medium Changer ANSI SCSI revision: 02 blk: queue c17fc018, I/O limit 4095Mb (mask 0x) Vendor: QUANTUM Model: DLT8000 Rev: 0232 Type: Sequential-Access ANSI SCSI revision: 02 blk: queue c15c9a18,
Backup with Onstream ADR50
Hi All, [if this is more appropriate for hackers, please inform me] I've been struggling with an OnStream ADR 50 drive (Not the SC-50) for the last two weeks. Everytime it seems to work with a small (test) backup, and it consistently fails for backup the real (big) data. I now understand that this is caused by a firmware bug in the ADR50. (Amanda closes the file upon starting the write of the next file, which might not occur before the drive timeouts, resulting in unreadble tapes) As a workaround, it has been suggested to dump to harddisk, and flush lateron. This means that there are no timeouts, as all data is readily available on the holding disk. This seems to work, but is a kludge. Now I have a few questions: 1) How can I configure amanda to flush to tape only after all dumps are done? Except for not inserting a tape untill the following morning. Would removing the write permission for amanda on the drive work (and running amflush as root?) and running it as follows (as root) dump.sh su -c amanda amdump DailySet1 amflush DailySet1 amverify DaiySet1 mt -f /dev/nst0 offline 2) I also would like to keep the files on disk (for quicker restores). How can I configure amanda not to delete these files after flushing, or only those that have a certain age? 3) Question to the hackers: Is it possible to change amada behaviour so that after a file is written to tape, it is closed immediately? Or does that interfere with normal amanda behaviour? Adminstrativa: I'm using RedHat 7.2 on a PIII 800MHz, with an Onstream ADR 50 SCSI LVD drive, firmware 2.39.
Re: Amcheck: access accepted!
Many thanks to all who helped. All is working so far. I changed the dump user to amanda, and ran amcheck as su amanda. Thanks again, Trevor. - Original Message - From: Martin Hepworth [EMAIL PROTECTED] To: Trevor Fraser [EMAIL PROTECTED] Sent: Wednesday, July 17, 2002 11:34 AM Subject: Re: Amcheck: acess denied Trevor yeah looks like you've got username access problems. make sure that both the client and server are compiled with the userid=amanda group=somegroup settings and make sure that the amanda user exists on both systems. Also as another poster mentioned, make sure you've got xinetd setup correctly. and then run amcheck as the amanda user. -- Martin Trevor Fraser wrote: - Original Message - From: Martin Hepworth [EMAIL PROTECTED] To: Trevor Fraser [EMAIL PROTECTED] Sent: Tuesday, July 16, 2002 5:10 PM Subject: Re: Amcheck: acess denied trevor didn't get the attachment -- martin Trevor Fraser wrote: Hi Martin. Thanks for your reply. My amcheck.x.debug says: amcheck:debug 1pid 3541ruid 0euid 0start time Tue Jul 16 16:08:37 2002 amcheck:dgram_bind: socket bound to 0.0.0.0.698 =*this changes from debug to debug* amcheck:pid 3541 finish time Tue Jul 16 16:08:37 2002 Please find amamdad.xx.debug file attached. Thanks, Trevor. Trevor What do the debug files say in /tmp/amanda on both the client and server? -- Martin
[no subject]
Hy, I already worked with amanda a bit some while ago. Now, working for a different employer, we're thinking about starting to use it here, too. As i forgeot most of things to know about when using amanda, I was looking for the Book, but i saw it is already three years old. Can i still use it for learning to do Backup with amanda, or did the software changed significyntly in the meantime? Is Amanda at all still in use and in development (i saw the web isn't uopdatet for a while, too) TIA, Henning
Unix Backup and Recorvery still up to date?
Sorry, forgot to set a good subject, here again: Hy, I already worked with amanda a bit some while ago. Now, working for a different employer, we're thinking about starting to use it here, too. As i forgeot most of things to know about when using amanda, I was looking for the Book, but i saw it is already three years old. Can i still use it for learning to do Backup with amanda, or did the software changed significyntly in the meantime? ps: Is Amanda at all still in active use and development (i saw the web isn't updatet for a while, too)? TIA, Henning
Re: Strange tape problem
On Wed, 2002-07-17 at 02:24, Jon LaBadie wrote: On Tue, Jul 16, 2002 at 05:06:31PM +0100, Phil Launchbury wrote: On Tue, 2002-07-16 at 15:50, Gene Heskett wrote: On Tuesday 16 July 2002 06:13, Phil Launchbury wrote: What's going on? Amanda is expecting Tape1 and amdump fails yet amtape quite clearly shows the tape in the slot! Didja change the tape label string specification to match something like ^Tape[0-9][0-9]? This is the labelstr line in amanda.conf, and mine, for DailySet1 looks like this: labelstr^DailySet1-[0-9][0-9]*$ # label constraint regex: all tapes must match Yes - I set up the tape label string in the amanda.conf.. Just in case, could you show us your labelstr line? Sure - here you go.. labelstr Tape[0-9][0-9]*$ Also, from your first posting, dumpcycle 2 days# the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days tapecycle 6 tapes # the number of tapes in rotation Those are wierd and improper settings. It says you will get a level zero (full) dumps every 2 days. During those 2 days you are going to run amdump 10 times a day. And you will be overwriting your 6 tapes 3+ times in every 2 day dumpcyle. Don't sound kosher to me :)) Indeed.. I have changed it to: dumpcycle 7 days runspercycle 7 tapecycle 6 tapes Cheers, Phil. -- === Phil Launchbury, Senior Systems Administrator Wind River Systems UK Ltd [EMAIL PROTECTED]
Re: Unix Backup and Recorvery still up to date?
Hi, [EMAIL PROTECTED] wrote: Sorry, forgot to set a good subject, here again: Hy, I already worked with amanda a bit some while ago. Now, working for a different employer, we're thinking about starting to use it here, too. Nice to hear ;-) As i forgeot most of things to know about when using amanda, I was looking for the Book, but i saw it is already three years old. Can i still use it for learning to do Backup with amanda, or did the software changed significyntly in the meantime? The book is still recomended. amanda didn't change very much, if you use 2.4.2, in 2.4.3b3 there are a few new features like autoflush, but the basics are unchanged. ps: Is Amanda at all still in active use and development (i saw the web isn't updatet for a while, too)? Yes, reading the messages here on the list it seems as if amanda is still used heavily widespread all over the world. And yes development goes on. But unlike some commercial software development is focusing on amanda, not on the webpage ;-) Christoph TIA, Henning
RE:
AMANDA is still actively being developed and used around the world. The Book is still a very good starting point, as the core functionality hasn't changed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 7:22 AM To: [EMAIL PROTECTED] Subject: Hy, I already worked with amanda a bit some while ago. Now, working for a different employer, we're thinking about starting to use it here, too. As i forgeot most of things to know about when using amanda, I was looking for the Book, but i saw it is already three years old. Can i still use it for learning to do Backup with amanda, or did the software changed significyntly in the meantime? Is Amanda at all still in use and in development (i saw the web isn't uopdatet for a while, too) TIA, Henning
RE:
On Wed, 17 Jul 2002, Bort, Paul wrote: AMANDA is still actively being developed and used around the world. This is a good opportunity to remind everyone to take a few minutes to append their organization to the Who is using Amanda? question in the FAQ-O-Matic. http://amanda.sourceforge.net/cgi-bin/fom?file=319 -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
Configure error
Hi, I am trying to compile amanda vers 2.4.3b2 on my solaris 2.6 box. I am getting an error regarding the C Compiler not being able to create executables. I did a google search on the particular error and saw postings relating to the absence of 'ar' and 'ld', both of which are present on my box. Anyways: I run my configure command: ./configure --with-user=amanda --with-group=backup --prefix=/usr/local/amanda --exec-prefix=/usr/local/amanda checking build system type... sparc-sun-solaris2.6 . checking for gcc... /usr/local/bin/gcc checking for C compiler default output... configure: error: C compiler cannot create executables I am running gcc version 2.95.3 20010315 (release) ld and ar are both under /usr/local/bin, which is listed first in $PATH. Going off of what config.log told me, there is an if statement in the configure script that didn't get executed. Before I dig any deeper into the configure script, I want to find out if this is something more obvious that I could easily fix. Any ideas? Thanks, Rich Quinn
I need some help
Hopefully someone can help me solve my problems... I've now completed yet another tape cycle with many many FAILED disks. I think some disks never got dumped at all. Every day in the email report I see pages of lev 0 FAILED [dumps too big, but cannot incremental dump new disk] and lev 1 FAILED [dumps way too big, must skip incremental dumps]. I did solve my previous problem where one 16Gb disk was getting a full dump every singe day, by deleting it from my disklist. :( I never figured out why it was being dumped every day. Is there a way I can get amanda to tell me how many tapes I need? She should be able to report how many Gbs of each level there were to be dumped each day. I have about 170Gb of data to be backed up right now, and 22 40Gb DLT8000 tapes in my tape cycle (2 weeks; 2 tapes per day). How can I figure out if that's enough? Thanks, 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
Re: I need some help
On Wed, 17 Jul 2002 at 10:21am, Brashers, Bart -- MFG, Inc. wrote I did solve my previous problem where one 16Gb disk was getting a full dump every singe day, by deleting it from my disklist. :( I never figured out why it was being dumped every day. Do you have record yes set in your dumptype(s)? What are dumpcycle, tapecycle, runspercycle, and runtapes set to? Is there a way I can get amanda to tell me how many tapes I need? She should be able to report how many Gbs of each level there were to be dumped each day. You can look in the amdump.N files for the estimate sizes amanda collects. I have about 170Gb of data to be backed up right now, and 22 40Gb DLT8000 tapes in my tape cycle (2 weeks; 2 tapes per day). How can I figure out if that's enough? How are you doing the 2 tapes per day? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
help with amrecover
I am running amanda with a Spectralogic Bullfrog Ait-2 library. When I try to perform an amrecover, my session looks something like this. -- The following tapes are needed: csd4 csd5 csd7 Restoring files into directory /backup Continue? [Y/n]: Y Load tape csd4 now Continue? [Y/n]: Y amrecover: error reading tape: Connection reset by peer extract_list - child returned non-zero status: 1 Continue? [Y/n]: n Can anyone point me in the right direction on how to make this work? I have tried to manually load the tapes before continuing with no success. Thanks
Re: Who is using Amanda
Is it just me and my old browser or is the append link at the bottom broken? Brandon D. Valentine wrote: On Wed, 17 Jul 2002, Bort, Paul wrote: AMANDA is still actively being developed and used around the world. This is a good opportunity to remind everyone to take a few minutes to append their organization to the Who is using Amanda? question in the FAQ-O-Matic. http://amanda.sourceforge.net/cgi-bin/fom?file=319 -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED] -- Scott Sanders Systems Administrator Concepts Direct, Inc. 2950 Colorful Ave. Longmont, CO 80504
RE: I need some help
I did solve my previous problem where one 16Gb disk was
getting a full dump every singe day, by deleting it from
my disklist. :( I never figured out why it was being dumped
every day.
Do you have record yes set in your dumptype(s)? What are
dumpcycle, tapecycle, runspercycle, and runtapes set to?
dumpcycle 2 weeks
runspercycle 10
tapecycle 22 tapes
record yes is on in my dumptype global, and not over-ridden anywhere.
I should mention that I have 3 configurations for amanda: Daily, archive,
and mirror. Daily is what you expect, archive is a full dump for off-site
storage, and mirror is a full dump for off-site of just that one server (a
linux box that rsync's the local Win2K boxes once a day). The full dump
set-ups have record no, following advice I found on this list. Could they
be interfering?
Is there a way I can get amanda to tell me how many tapes I
need? She should be able to report how many Gbs of each
level there were to be dumped each day.
The command amadmin yourconfig balance informs you about the
size of full backups it did (or will do) on each day in your
cycle.
%amadmin Daily balance
new disk server:/usr/local ignored.
new disk server:/var/mail ignored.
new disk server:/etc ignored.
new disk server:/data/pnw ignored.
new disk server:/data/usgs ignored.
...many more like this -- lots never got dumped...
due-date #fs orig KBout KB balance
---
7/17 Wed 29 18968010 18968448 +50.8%
7/18 Thu0 0 0 ---
7/19 Fri2 20302290 20302336 +61.5%
7/20 Sat0 0 0 ---
7/21 Sun0 0 0 ---
7/22 Mon3 14186670 14186688 +12.8%
7/23 Tue2 1014600 1014624 -91.9%
7/24 Wed2172740172768 -98.6%
7/25 Thu6989530989632 -92.1%
7/26 Fri4 29481800 29481856 +134.4%
7/27 Sat0 0 0 ---
7/28 Sun0 0 0 ---
7/29 Mon2 7050580 7050624 -43.9%
7/30 Tue6 16981300 16981408 +35.0%
7/31 Wed1 16601290 16601312 +32.0%
---
TOTAL 57 125748810 125749696 12574969 (estimated 10 runs per
dumpcycle)
(8 filesystems overdue, the most being overdue 34 days)
Ok, so she's very much out of balance. And she dumped 126Gb during my
2-week dumpcycle. 22 tapes * 40Gb per tape (about) is 880Gb, definitely
enough. But this does not really say how much data was level 0, and how
much was level 1, etc.
I run amoverview Daily and noticed (in addition to lots of strings of E's
for other disks)
date 06 06 06 07 07 07 07 07 07 07 07 07 07 07 07
07 07 07 07
host disk 28 29 30 01 02 03 04 05 06 07 08 09 10 11 12
13 14 15 16
server /data/ds353.4_upa 1 1 1 11 1 1 1 1
1 1
So it looks like this disk is getting an incremental dump nearly everyday.
These files are static, and haven't changed in 6 months. This disk
contains only 302Mb, but perhaps this is a symptom of a larger problem?
I have about 170Gb of data to be backed up right now, and
22 40Gb DLT8000 tapes in my tape cycle (2 weeks; 2 tapes
per day). How can I figure out if that's enough?
How are you doing the 2 tapes per day?
I lie to amanda, and tell here there's one tape of size 80Gb, and run
amflush manually each day when I get in to the office. If I were running 1
tape per day with a 4 week tape cycle, and I'm actually generating more than
40Gb per day of level 1, then there will be no space left ever to do the
level 0 dumps, right?
runtapes 1
tapetype DLT8000x2
define tapetype DLT8000x2 {
comment Two tapes on DLT8000 40 Gb Hardware Compression
length 78000 mbytes
filemark 2362 kbytes
speed 2 kps
}
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
Re:
On Wednesday 17 July 2002 07:21, [EMAIL PROTECTED] wrote: Hy, I already worked with amanda a bit some while ago. Now, working for a different employer, we're thinking about starting to use it here, too. As i forgeot most of things to know about when using amanda, I was looking for the Book, but i saw it is already three years old. Can i still use it for learning to do Backup with amanda, or did the software changed significyntly in the meantime? Is Amanda at all still in use and in development (i saw the web isn't uopdatet for a while, too) Its at the instant, fairly stable with the last release I'm running dated July 2,02. Generally speaking, the framework hasn't changed enough to cause it to be incompatible with revious versions in quite some time. However, things are being fine-tuned all the time. Welcome back. :-) TIA, Henning -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.07% setiathome rank, not too shabby for a WV hillbilly
Re: Unix Backup and Recorvery still up to date?
On Wednesday 17 July 2002 07:41, [EMAIL PROTECTED] wrote: Sorry, forgot to set a good subject, here again: Hy, I already worked with amanda a bit some while ago. Now, working for a different employer, we're thinking about starting to use it here, too. As i forgeot most of things to know about when using amanda, I was looking for the Book, but i saw it is already three years old. Can i still use it for learning to do Backup with amanda, or did the software changed significyntly in the meantime? ps: Is Amanda at all still in active use and development (i saw the web isn't updatet for a while, too)? Late snapshots are available from a site at the iro.umontreal.ca/~martinea/amanda pages, I hope I got that address close enough. I'm running the latest 2.4.3b3 release. There is also a 2.5.0beta release there, which has additional facilities to allow backup to dedicated disk storage, but I've not used it. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.07% setiathome rank, not too shabby for a WV hillbilly
Re: Strange tape problem
On Wednesday 17 July 2002 08:13, Phil Launchbury wrote: On Wed, 2002-07-17 at 02:24, Jon LaBadie wrote: On Tue, Jul 16, 2002 at 05:06:31PM +0100, Phil Launchbury wrote: On Tue, 2002-07-16 at 15:50, Gene Heskett wrote: On Tuesday 16 July 2002 06:13, Phil Launchbury wrote: What's going on? Amanda is expecting Tape1 and amdump fails yet amtape quite clearly shows the tape in the slot! Didja change the tape label string specification to match something like ^Tape[0-9][0-9]? This is the labelstr line in amanda.conf, and mine, for DailySet1 looks like this: labelstr^DailySet1-[0-9][0-9]*$ # label constraint regex: all tapes must match Yes - I set up the tape label string in the amanda.conf.. Just in case, could you show us your labelstr line? Sure - here you go.. labelstr Tape[0-9][0-9]*$ Also, from your first posting, dumpcycle 2 days# the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days tapecycle 6 tapes # the number of tapes in rotation Those are wierd and improper settings. It says you will get a level zero (full) dumps every 2 days. During those 2 days you are going to run amdump 10 times a day. And you will be overwriting your 6 tapes 3+ times in every 2 day dumpcyle. Don't sound kosher to me :)) Indeed.. I have changed it to: dumpcycle 7 days runspercycle 7 tapecycle 6 tapes Cheers, Phil. This is still a somewhat foobared setup. dumpcycle is the maximum number of days that can go by before a level 0 (full) must be done. runspercycle can be any number up to dumpcycle and be ok. But tapecycle, which means the number of tapes in the rotation should be at least 2x the runspercycle else you will be in a situation wherein the last full backup is overwritten before the next full is due. Amanda may not like that, and you sure won't if something miss-fires and you need to do a full restore, but don't have a full to use as a restore base. Tapes, compared to your data, are dirt cheap, specially if they're DAT's. Get em on ebay. Usually around 30 to 35 USD for a ten pack of new ones in DDS2 sizes. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.07% setiathome rank, not too shabby for a WV hillbilly
Re: Configure error
On Wednesday 17 July 2002 12:15, Quinn, Richard C. - Collinsville IT wrote: Hi, I am trying to compile amanda vers 2.4.3b2 on my solaris 2.6 box. I am getting an error regarding the C Compiler not being able to create executables. I did a google search on the particular error and saw postings relating to the absence of 'ar' and 'ld', both of which are present on my box. Anyways: I run my configure command: ./configure --with-user=amanda --with-group=backup --prefix=/usr/local/amanda --exec-prefix=/usr/local/amanda checking build system type... sparc-sun-solaris2.6 . checking for gcc... /usr/local/bin/gcc checking for C compiler default output... configure: error: C compiler cannot create executables I am running gcc version 2.95.3 20010315 (release) ld and ar are both under /usr/local/bin, which is listed first in $PATH. Going off of what config.log told me, there is an if statement in the configure script that didn't get executed. Before I dig any deeper into the configure script, I want to find out if this is something more obvious that I could easily fix. Any ideas? I've been watching this go by for a couple of days now, and it sure looks to me as if something in the gcc package group is missing from your system. Packed up into rpms for linux, its about 6 packages all told, so you might want to see if you've got the solaris equ to the gcc group and libstdc all in the same versions, and modutils, binutils of late release but not the same version number family as gcc. They should track, but don't, and it can be confusing to the initiate. Thanks, Rich Quinn -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.07% setiathome rank, not too shabby for a WV hillbilly
Re: Unix Backup and Recorvery still up to date?
On Wed, 17 Jul 2002 at 2:29pm, Gene Heskett wrote I'm running the latest 2.4.3b3 release. There is also a 2.5.0beta release there, which has additional facilities to allow backup to dedicated disk storage, but I've not used it. 2.4.3b3 has that ability... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: I need some help
On Wed, 17 Jul 2002 at 11:54am, Brashers, Bart -- MFG, Inc. wrote Do you have record yes set in your dumptype(s)? What are dumpcycle, tapecycle, runspercycle, and runtapes set to? dumpcycle 2 weeks runspercycle 10 tapecycle 22 tapes record yes is on in my dumptype global, and not over-ridden anywhere. I should mention that I have 3 configurations for amanda: Daily, archive, and mirror. Daily is what you expect, archive is a full dump for off-site storage, and mirror is a full dump for off-site of just that one server (a linux box that rsync's the local Win2K boxes once a day). The full dump set-ups have record no, following advice I found on this list. Could they be interfering? Nope -- that's not your problem... How are you doing the 2 tapes per day? I lie to amanda, and tell here there's one tape of size 80Gb, and run amflush manually each day when I get in to the office. If I were running 1 *This* is your problem. What is your reserve set to, and how much holding disk space do you have? When amanda hits EOT unexpectedly, it goes into degraded mode. By default, amanda reserves 100% of the holding disk space for degraded mode backups, which are incrementals only. If you set reserve to a low number, then you free space for full backups in degraded mode. So, amanda was probably going into degraded mode every night and didn't have any space for level 0s. Thus the can't incremental new disk and dumps too big messages. Also, are you using software or hardware compression? Depending on your data, you should be able to get more than 40GB on DLT8K tapes... tape per day with a 4 week tape cycle, and I'm actually generating more than 40Gb per day of level 1, then there will be no space left ever to do the level 0 dumps, right? If amanda estimates that any dump (whether full or incremental) is bigger than a tape, it will tell you that, won't dump the disk, and will do everything else that it can. Some lies are ok to tell amanda, this one isn't. As I see it, you've got a couple of options: 1) Set runtapes to two and use chg-manual. Not optimal, as I don't think you can run amdump out of CRON as it needs you to tell it when you've put in the next tape. 2) Split up any partitions with large incrementals using tar so that you're sure every disklist entry will fit on a tape. There may be others, as well. But that's a big, bad lie you're telling amanda there. You could try cranking your reserve down if you want to continue your lying ways. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
quick question?
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 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
Re: quick question?
On Wed, 17 Jul 2002 at 3:20pm, C White 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 is this correct or have i missed something here? Looks good. 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 Enjoy! -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: quick question?
Good question as I'm at about the same point with amanda. I think the way you have it set up will only dump once during your 5 day long dumpcycle. Gene Heskette wrote this in response to an earlier question and it cleared things up a bit for me. Hope this helps. dumpcycle is the maximum number of days that can go by before a level 0 (full) must be done. runspercycle can be any number up to dumpcycle and be ok. But tapecycle, which means the number of tapes in the rotation should be at least 2x the runspercycle else you will be in a situation wherein the last full backup is overwritten before the next full is due. C White 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 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 -- Scott Sanders Systems Administrator Concepts Direct, Inc. 2950 Colorful Ave. Longmont, CO 80504 (303) 682-7110 Phone (303) 682-7140 Fax
Re: Configure error
On Wed, Jul 17, 2002 at 01:46:30PM -0500, Quinn, Richard C. wrote: Scott Sanders [EMAIL PROTECTED] wrote: Try setting the variable CC=gcc;export CC CC was already set to gcc and /usr/local/bin is listed first in $PATH It sounds like your gcc may have been compiled to use the native SUNW assembler and linker, in which case the (I assume) GNU ld and as in /usr/local/bin won't cut it -- the assembly syntax is different. Make sure the packages listed in http://www.science.uva.nl/pub/solaris/solaris2.html#q6.2 are installed and try it with /usr/ccs/bin ahead of /usr/local/bin in your $PATH. -- Mike Delaney [EMAIL PROTECTED] ...Microsoft follows standards. In much the same manner that fish follow migrating caribou. Now I have this image in my mind of a fish embracing and extending a caribou. -- Paul Tomblin and Christian Bauernfeind in the SDM
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
Windows-XP
Dear amanda-users, Has anyone given any thought to (or done) a port of amandad to Windows-XP? Windows-XP appears to have certain restrictions with samba. For example, I can't access (and therefore can't backup) the /WINDOWS directory through samba under Windows-XP. (Or am I missing something here.) I think it would be better if amandad was actually running on XP and amanda clients could connect to it instead of samba. Has anyone tried this? Thanks, Dick P.S. amanda-hackers please reply to: [EMAIL PROTECTED]
RE: I need some help
How are you doing the 2 tapes per day? I lie to amanda, and tell here there's one tape of size 80Gb, and run amflush manually each day when I get into the office. If I were running 1 *This* is your problem. What is your reserve set to, and how much holding disk space do you have? Holding disk /tmp/amanda/dump: 57492036 KB disk space available, that's plenty. When amanda hits EOT unexpectedly, it goes into degraded mode. By default, amanda reserves 100% of the holding disk space for degraded mode backups, which are incrementals only. If you set reserve to a low number, then you free space for full backups in degraded mode. So, amanda was probably going into degraded mode every night and didn't have any space for level 0s. Thus the can't incremental new disk and dumps too big messages. That's a good explanation. I checked my amanda.conf file: # reserve 30 # percent so it's reserving 100% by default. Also, are you using software or hardware compression? Depending on your data, you should be able to get more than 40GB on DLT8K tapes... Yes, I was trying to get it to *work* first, then tweak for optimization. I can definitely up that -- I'm using hardware compression (drawbacks) because if I don't, it runs for 12 hours doing all the gzipping... tape per day with a 4 week tape cycle, and I'm actually generating more than 40Gb per day of level 1, then there will be no space left ever to do the level 0 dumps, right? If amanda estimates that any dump (whether full or incremental) is bigger than a tape, it will tell you that, won't dump the disk, and will do everything else that it can. Some lies are ok to tell amanda, this one isn't. As I see it, you've got a couple of options: 1) Set runtapes to two and use chg-manual. Not optimal, as I don't think you can run amdump out of CRON as it needs you to tell it when you've put in the next tape. A big drawback. :( 2) Split up any partitions with large incrementals using tar so that you're sure every disklist entry will fit on a tape. By that do you mean make sure the size as reported by /usr/bin/du is less than 20Gb? That's what I do, via a script. So I make sure it fits on *half* a tape, to leave the other half for daily incrementals. But what happens when nearly every day, the daily incrementals are, say, 30Gb? There may be others, as well. But that's a big, bad lie you're telling amanda there. You could try cranking your reserve down if you want to continue your lying ways. I'll try cranking it down to 10%, and wait a few days to see what she does. Then maybe I should switch (back) to dumpcycle 4 weeks runspercycle 20 tapecycle 22 tapes runtapes 1 I think I had a problem with that before. Yes I remember now, I had a disklist entry that was larger than my tape, and amanda *wasn't* telling me, and when it got to level 9 there was a bug that caused amdump to crash. But perhaps that's fixed now. My script that checks for large disks is fixed, anyway. 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
RE: Windows-XP
Windows-XP appears to have certain restrictions with samba. For example, I can't access (and therefore can't backup) the /WINDOWS directory through samba under Windows-XP. (Or am I missing something here.) You're missing something. The Windows NT family of Windows contains Administrative shares that are created on bootup. They are: \\servername\c$ for root access to C:\ \\servername\d$ for root access to D:\ (etc) \\servername\admin$ for access to %SystemRoot% These shares are set for access for Administrators only. -- Adam Smith Information Technology Officer SAGE Automation Ltd [EMAIL PROTECTED] http://www.sageautomation.com Phone : (08) 8276 0703 Fax : (08) 8276 0799 Mobile: 0414 895 273
Re: I need some help
I picked and chose from 3 of Bart Brasher's postings:
==
Is there a way I can get amanda to tell me how many tapes I need?
Let me try some numbers:
I have about 170Gb of data to be backed up right now
I'm assuming that is not disk capacity, but total disk space used already.
From your amadmin balance output:
TOTAL 57 125748810 125749696 12574969 (estimated 10 runs per
amanda has seen 57 file systems (disklist entries) containing 126GB of the 170,
but you said some have never been backed up, so that is reasonable.
dumpcycle 2 weeks
runspercycle 10
Using the 170GB number and 10 runs, that is nominally 20GB on average of full
backups per run. With over 60 disklist entries to spread over the 10 runs,
amanda will probably be able to stick reasonably close to that number.
Unless 1 or 3 are really huge.
... , and I'm actually generating more than 40Gb per day of level 1,
So that seems to me you should have an average of approximately 60GB of data
being backed up daily, 20GB level 0's plus 40GB incrementals.
Conservatively you estimate your tapes at 40GB capacity.
I have ... 40Gb DLT8000 tapes
So it sounds to me like 2 tapes per day is reasonable. And if the data is
reasonably compressible, many days one would be enough.
I do have concerns about your holding disk and the way you are trying to
use multiple tapes.
The reserve situation has been addressed by others.
But about your holding disk, amcheck says:
Holding disk /tmp/amanda/dump: 57492036 KB disk space available, that's plenty.
And yet 57GB is not plenty when you are backing up an average of 60GB.
Your use of your tapes is ?imaginative?.
I lie to amanda, and tell here there's one tape of size 80Gb, and run
amflush manually each day when I get in to the office.
runtapes 1
tapetype DLT8000x2
define tapetype DLT8000x2 {
comment Two tapes on DLT8000 40 Gb Hardware Compression
length 78000 mbytes
filemark 2362 kbytes
speed 2 kps
}
Do you then amlabel pairs of tapes the same - nah, sorry.
You use them in pairs and have 22 tapes, so shouldn't you actually list
your tapecycle as 11, not 22? Of course that is only 1 more than a
dumpcycle. Cutting it kinda close.
Couldn't you give a correct tape type, specify runtapes as 2. With
modifications to chg-manual, I'll bet you could have the first tape in
the drive at the start of the overnight amdump and then finish only
the second tape the next morning.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
