Q: tapeless Amanda
Hi, I'm trying to configure a tapeless amanda ... I've configured many directories as the amanda tapeless HowTo said ( /backup/amanda/GARBI[01..11] - 11 directories for 11 slots). I want to label each slot, but when I do: $amtape mypolicy slot 1 $amlabel mypolicy mylabel slot 1 amtape returns amtape: could not load slot 1: file:/backup/amanda/GARBI01: not a device file. The same with amlabel. About config: * Debian Woody * /backup/amanda and /backup/amanda/GARBI* - chmod 770 and chown backup:backup applied * created GARBI*/data directories * changer.conf - file:/backup/amanda/GARBI[01..11] for each slot descriptor * amanda.conf - using a HARD-DISK device (5 mbytes) and hard-disk-tar descriptor * Must I have an chg-multi script on my Debian? (I don't found it) Any idea? thanks in advance, -- Raúl Cruz Tech Manager, Wild-Spain.com Tel/Fax (+34) 925 867636 www.wild-spain.com - Information on Nature and Outdoor travel in Spain -
Q: expecting a new tape
Hi, Yesterday I forced a full backup with amadmin. Today, amcheck mailed to me the following: These dumps were to tape FURV-POLICY01. The next tape Amanda expects to use is: a new tape. . . NOTES: planner: Forcing full dump of xaloc:/dev/sdc2 as directed. taper: tape FURV-POLICY01 kb 9993888 fm 5 [OK] DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - kannagara/etc1 210 32 15.2 0:00 121.9 0:0010897.3 xaloc/dev/sdc1 1 100 32 32.0 0:00 365.9 0:0011161.5 xaloc/dev/sdc2 0 105975605950496 56.1 50:231968.4 50:231968.2 xaloc/dev/sdd1 2 41909504043104 96.5 22:053052.1 31:132158.4 xaloc/etc1 750 64 8.5 0:00 192.9 0:0012009.0 I don't understand The next tape Amanda expects to use is: a new tape. The amcheck man page says about this: The tape is not OK and a new tape was expected. what's that? ... Is the full backup invalid? do I need a new fresh and blank tape into my policy? or simply can I choose some registered tape from my policy? Must I do the full backup again? Best regards, Raúl Cruz Carmona [EMAIL PROTECTED]
Q: amanda, samba and winpc
Hi,
I've decided to add a winpc into my backup planning. I've followed the doc
amanda-common/doc/SAMBA.gz from my Debian.
Thus, into my disklists appears
xaloc//garbi/H$comp-user-tar - the amanda server xaloc must to connect
through Samba to //garbi/H$
and into my /etc/amandapass
//garbi/H$login%passwordSTQ
I've tried to connect with smblient from xaloc to garbi (into another workgroup, STQ)
and it worked ok. Amcheck said nothing strange...
but today, when I arrived, amanda had still not reported any information (by mail, as
a result of latest backup), and forcing with amreport this is the result:
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: FURV-POLICY04.
FAILURE AND STRANGE DUMP SUMMARY:
xaloc /dev/sdc2 RESULTS MISSING
xaloc /dev/sdc1 RESULTS MISSING
xaloc /etc RESULTS MISSING
xaloc /dev/sdd1 RESULTS MISSING
kannagara /etc RESULTS MISSING
xaloc //garbi/H$ RESULTS MISSING
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
kannagara/etc MISSING --
xaloc//garbi/H$MISSING --
xaloc/dev/sdc1 MISSING --
xaloc/dev/sdc2 MISSING --
xaloc/dev/sdd1 MISSING --
xaloc/etc MISSING --
(brought to you by Amanda version 2.4.2p2)
what's happening??, I don't understand why amanda have troubles and reply with
RESULTS MISSING.
I need help!!!
Best Regards,
Raúl Cruz
[EMAIL PROTECTED]
Re: Q: tape problem
Hi Jon, Therefore I've various possibilities: 0 - To Check connections ( though the problem only occurs with the tape 04) 1 - To update the soft from my PowerVault ( from dell ) 2 - To Cleaning heads 3 - To change the tape 04 How can I check the state of de tape surface ( any command )? or to delete contents, re-initialize the tape... Best regards, - Original Message - From: Jon LaBadie [EMAIL PROTECTED] To: Raúl Wild-Spain [EMAIL PROTECTED] Sent: Thursday, June 26, 2003 3:10 PM Subject: Re: Q: tape problem On Thu, Jun 26, 2003 at 08:52:59AM +0200, Raúl Wild-Spain wrote: Hi Jon, I add below notifications from my Debian ( log check). You can see many strange errors, specially Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark. repeatedly. I don't understand what happens ... 3. you have holding disk space available but have not set a chunk size below the maximum file size limit of your holding disk. --- LOG CHECK --- Unusual System Events =-=-=-=-=-=-=-=-=-=-= Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark. Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error When you get errors like this, at the kernel level, it seldom (as in virtually never) is due to the software running at the time. Problems in the software generally cause things like core dumps and other wierd things but without significant kernel messages. Most often it is in the driver or likely the hardware. My first thought is, as always with SCSI devices, check connections, cables, terminators. Nine-plus times out of ten it is that. Note too that last item Medium Error. It could even be as simple as dirty head or failed tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Q: tape problem
Hi Jon, 1. you are writing to a dds2 tape, 3.8GB max size, and /dev/sdc2 is more than 4 GB, even compressed. it's a dds4 tape, you know, 20Gb and 40Gb compressed. My backups aren't greater than 6Gb totally ( when full dump ). these indications aren't normal , the tape must to have more than 3.8 Gb 2. you have no holding disk available for /dev/sdc2 so it is writing directly to tape. for some reason this is too slow and some timeout is kicking in. I add below notifications from my Debian ( log check). You can see many strange errors, specially Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark. repeatedly. I don't understand what happens ... 3. you have holding disk space available but have not set a chunk size below the maximum file size limit of your holding disk. --- LOG CHECK --- Unusual System Events =-=-=-=-=-=-=-=-=-=-= Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark. Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc sendbackup[20682]: index tee cannot write [Broken pipe] Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark.
Q: tape problem
Hi! I've a tape in my amanda policy that not works properly. The text following is an
amanda report and is always the same with this tape (and always with /dev/sdc2, always
the same scenario) ...somebody knows what it happens and how to solve this problem?
This is the only tape with this problem.
best regards,
Raul
[EMAIL PROTECTED]
--- AMANDA REPORT ---
These dumps were to tape FURV-POLICY04.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: FURV-POLICY05.
FAILURE AND STRANGE DUMP SUMMARY:
xaloc /dev/sdc2 lev 0 FAILED [out of tape]
xaloc /dev/sdc2 lev 0 FAILED [data write: Connection reset by peer]
xaloc /dev/sdc2 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:06
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.20.00.2
Original Size (meg) 0.90.00.9
Avg Compressed Size (%)17.6--17.6 (level:#disks ...)
Filesystems Dumped4 0 4 (1:4)
Avg Dump Rate (k/s) 262.3-- 262.3
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.30.00.3
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 4 0 4 (1:4)
Avg Tp Write Rate (k/s) 369.2-- 369.2
FAILED AND STRANGE DUMP DETAILS:
/-- xaloc /dev/sdc2 lev 0 FAILED [data write: Connection reset by peer]
sendbackup: start [xaloc:/dev/sdc2 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
\
NOTES:
taper: tape FURV-POLICY04 kb 3712 fm 5 writing file: Input/output error
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
kannagara/etc1 200 32 16.0 0:00 130.0 0:00 196.5
xaloc/dev/sdc1 1 60 32 53.3 0:00 560.8 0:00 789.2
xaloc/dev/sdc2 0 FAILED ---
xaloc/dev/sdd1 1 60 32 53.3 0:00 411.3 0:00 624.2
xaloc/etc1 590 64 10.8 0:00 277.7 0:00 351.7
(brought to you by Amanda version 2.4.2p2)
Q: Amrecover / troubles
Hi! I'm trying to recover a file from a recent backup with amrecover. So logged as root I want to lauch amrecover -C furv, but the response are: 500 Access not allowed: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed Can anyone help to me? Best regards, Raúl Cruz [EMAIL PROTECTED]
Q: finally!!! my first backup ... but :-)
Finally! yesterday I did my first backup and it seems ok, but I've some doubts about various messages: FAILURE AND STRANGE DUMP SUMMARY: xaloc /dev/sdc2 lev 0 STRANGE FAILED AND STRANGE DUMP DETAILS: /-- xaloc /dev/sdc2 lev 0 STRANGE sendbackup: start [xaloc:/dev/sdc2 level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./notesdata/mail/sdelamoc.nsf: file changed as we read it ? gtar: ./notesdata/mail/spaxtonl.nsf: file changed as we read it ? gtar: ./notesdata/mail/xguardio.nsf: file changed as we read it | Total bytes written: 4793784320 (4.5GB, 3.3MB/s) sendbackup: size 4681430 sendbackup: end \ I've looked at the index files of _dev_sdc2 and the list seems to be ok. Then I suppose the mentioned users was connected ( from home) when amanda did the backup (0:45). It seems, true? No problem with the rest of filesystems ( or it seems ). Best Regards, Raúl [EMAIL PROTECTED]
Q: NOTE by amcheck
Hi! After my first succesfully try with amanda I've been changed my disklist to adjust them not for filesystems but for the important directories I want to backup. In this case amcheck says the following: NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.notesini: does not exist NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.notesini: does not exist NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.recursosBD: does not exist NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.recursosBD: does not exist NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.namesBD: does not exist NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.namesBD: does not exist NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.mail: does not exist NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.mail: does not exist NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.aplicacionsFURV: does not exist NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.aplicacionsFURV: does not exist Should I suppose that amanda will create the necessary directories and files when needed although it not indicates NOTE: it will be created on the next run? or I must to do this by hand? The man page of amcheck isn't clear about this ... - comment : - /.x are softlinks to every directory or file I want to backup Best Regards, Raúl [EMAIL PROTECTED]
Re: Q: finally!!! my first backup ... but :-)
Ok! thanks, Christoph (and Toomas again), but ... does it exist any solution in these cases? or must I have to be satisfied and try a post-backup (manually or not) of these files ? thanks again, - Original Message - From: Christoph Scheeder [EMAIL PROTECTED] To: Raúl Wild-Spain [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, March 06, 2003 11:20 AM Subject: Re: Q: finally!!! my first backup ... but :-) Hi, Your guess is correct, this messages are the result of an active filesystem. The backup itself is ok, but these specific files will probably be bad, as they have been modifyd while tar was reading them. Christoph Raúl Wild-Spain schrieb: Finally! yesterday I did my first backup and it seems ok, but I've some doubts about various messages: FAILURE AND STRANGE DUMP SUMMARY: xaloc /dev/sdc2 lev 0 STRANGE FAILED AND STRANGE DUMP DETAILS: /-- xaloc /dev/sdc2 lev 0 STRANGE sendbackup: start [xaloc:/dev/sdc2 level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./notesdata/mail/sdelamoc.nsf: file changed as we read it ? gtar: ./notesdata/mail/spaxtonl.nsf: file changed as we read it ? gtar: ./notesdata/mail/xguardio.nsf: file changed as we read it | Total bytes written: 4793784320 (4.5GB, 3.3MB/s) sendbackup: size 4681430 sendbackup: end \ I've looked at the index files of _dev_sdc2 and the list seems to be ok. Then I suppose the mentioned users was connected ( from home) when amanda did the backup (0:45). It seems, true? No problem with the rest of filesystems ( or it seems ). Best Regards, Raúl [EMAIL PROTECTED]
Q: .amandahosts failed
Hi! I've problems with my amanda (and my first backup). The original problem was this (from amreport): xaloc /.furvbackup lev 0 FAILED [xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed I've created into /home/dump (the home dir of my user backup which is the default configuration from my linux debian) the file .amandahosts with these lines: localhost backup xaloc backup and I've changed the permissions to 660. Now, amreport says the following: ERROR: xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed ... basically the same. Why??? Can anyone help to me? Best regards, Raúl [EMAIL PROTECTED]
Re: .amandahosts failed / Solved!!!
Sorry!!! It seems I needed to specify a fully-qualified name. Now with: xaloc.stq.urv.es backup amcheck don't says amandahostsauth failed thanks again and sorry, Raúl [EMAIL PROTECTED] - Original Message - From: Raúl Wild-Spain [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 10:06 AM Subject: Q: .amandahosts failed Hi! I've problems with my amanda (and my first backup). The original problem was this (from amreport): xaloc /.furvbackup lev 0 FAILED [xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed I've created into /home/dump (the home dir of my user backup which is the default configuration from my linux debian) the file .amandahosts with these lines: localhost backup xaloc backup and I've changed the permissions to 660. Now, amreport says the following: ERROR: xaloc: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed ... basically the same. Why??? Can anyone help to me? Best regards, Raúl [EMAIL PROTECTED]
Q: amanda documentation / soft links vs backups
Hi! I've found into the amanda documentation (FAQ.gz) various ways to perform a backup. I've some doubts because my english is a little bad ( I'm spanish and my alternative language is french) and I would like to make some questions about this. The FAQ says the following: -- You may create short-named links in some directory closer to the root (/) so as to reduce the length of names. I.e., instead of backing up /usr/home/foo and /usr/home/bar, create the following links: /.foo - /usr/home/foo /.bar - /usr/home/bar then list /.foo and /.bar in the disklist. Another approach is to group sub-directories in backup sets, instead of backing up them all separately. For example, create /usr/home/.bkp1 and move `foo' and `bar' into it, then create links so that the original pathnames remain functional. Then, list /usr/home/.bkp1 in the disklist. You may create as many `.bkpN' directories as you need. -- then, my doubt is the following: if I create a hidden directory /.furvbackup and into this a make some soft-links to the areas I want to backup, does it will work right? and another, I suppose there isn't problem to backup directories ( not partitions or disks) with amanda, is it right?, example, into disk list -mypc /path/to/directory always-full Best regards, Raúl [EMAIL PROTECTED]
Q: troubles / my first backup with amanda
Hi! recently I've installed amanda in a linux debian. By following an FAQ (or the man page, I don't remember) I've created a hidden directory /.furvbackup and into this multiple softlinks to the areas I want to backup. Into disklist I've: localhost/.furvbackupcomp-high The first amreport says the following: --- These dumps were to tape FURV01. The next tape Amanda expects to use is: FURV02. FAILURE AND STRANGE DUMP SUMMARY: localhost /.furvbackup lev 0 FAILED [disk /.furvbackup offline on localhost?] STATISTICS: NOTES: planner: Adding new disk localhost:/.furvbackup. driver: WARNING: got empty schedule from planner taper: tape FURV01 kb 0 fm 0 [OK] DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - localhost-furvbackup 0 FAILED --- Why my amanda fails? Is the syntax of disklist bad or wrong? comment: The owner and group of /.furvbackup and softlinks are root:root. Best Regards, Raúl, [EMAIL PROTECTED]
Re: Q: simple but how ?
Hi!Toomas,
I've indicated 40Gb because my PowerVault is configured as yours, to compress data by
hardware ( I think in a 2:1 ratio by default). I don't use any software to compress
data, and all the data I should backup are locally to server. Do you think in this
scenario will I have problems with amanda if I indicate 40Gb -tapes in my descriptors
(or seemed, 35Gb if 40Gb is too much optimistic) ?
I will make use of your filemark and speed values, much thanks ;-)
Best regards,
- Original Message -
From: Toomas Aas [EMAIL PROTECTED]
To: Ra.l Wild-Spain [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 5:56 PM
Subject: Re: Q: simple but how ?
Hi!
define tapetype DDS-4-40{
comment DDS-4 PowerVault with compression
DDS-4-20
length 4 mbytes
}
This length number is probably too optimistic. This assumes that your
data compresses with a 2:1 ratio, which is rarely seen in real life.
FWIW, here's my tapetype with DDS4 drive using hardware compression:
define tapetype DDS4 {
comment DDS4 using hardware compression
length 25000 Mbytes
filemark 0 Kbytes
speed 2816 Kbytes
}
The length number is really just a guess (I think I underestimate the
compression a little, but since I only have 10 GB of data this is not
an issue for me right now). The speed number is taken from avg tp
write rate as reported by Amanda's nightly run.
--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* One way to be happy ever after is not to be after too much.
Q: simple but how ?
Hi! I've installed in my debian the amanda system. Thank's to amcheck it seems my
config is ok, but I've some doubts and questions (it's no clear for me).
1) My tape is a PowerVault (the server is a dell poweredge 4400) and I make use of
dds4 tapes ( 40gb ). I've typed the following descriptors in my amanda.conf:
define tapetype DDS-4-20{
comment DDS-4 PowerVault without compression
length 2 mbytes
filemark 65 kbytes
speed 1255 kps
}
define tapetype DDS-4-40{
comment DDS-4 PowerVault with compression
DDS-4-20
length 4 mbytes
}
Then my tapetype var is: tapetype DDS-4-40
Do I suppose this will work properly? Have anyone experience with DDS-4 tapes and
amanda?
2) I still haven't the tapes (quantity) , but I must demonstrate to my boss that
amanda works and will work. Then, I've only 2 tapes dds4 and I thinked the following:
- doing a full backup every week (on friday night) ( simple ;-) ).
I've labeled the tapes ( tape01, tape02) and I would like to configure my amanda.conf
to this way. (the first week amanda demands to me tape01 .. the next week tape02 ...
01 ... 02 .. )
I've tried to configure my amanda.conf but I'm not sure it's ok. I've the following:
dumpcycle 0
runspercycle 2
tapecycle 2 tapes
runtapes 1
tapetype DDS-4-40
... etc
and my crontab.amanda runs amdump every friday night.
Is this ok? I must to change anything?
Best regards,
Raúl Cruz Carmona
[EMAIL PROTECTED]
