Re: one DLE per single tape?
On Mon, 29 Aug 2011 19:02:12 -0400
Jon LaBadie wrote:
> Nothing strange there. It attempted to put it a DLE, or depending on
> your configuation, a chunk of the DLE on to a tape but it didn't
> fit. Thus it retried that DLE or chunk on the next tape and
> succeeded.
Hmm, that's a bit strange because Eacho DLE was selected in a way to
fit on the tape.
> > STATISTICS:
> > Total Full Incr. Level:#
> >
> > Estimate Time (hrs:min) 0:00
> > Run Time (hrs:min) 14:23
> > Dump Time (hrs:min)13:11 13:11 0:00
> > Output Size (meg) 736042.0 736042.00.0
> > Original Size (meg) 647112.1 647112.10.0
> > Avg Compressed Size (%)113.7 113.7--
>
> Looks like you should not be trying to compress these data.
Good catch.
Here is my config:
define dumptype simple-gnutar-local {
auth "local"
compress none
program "GNUTAR"
record no
}
which means that it could be only due to hardware compression or not?
>
> > DLEs Dumped4 4 0
> > Avg Dump Rate (k/s) 15874.315874.3--
> >
> > Tape Time (hrs:min)14:22 14:22 0:00
> > Tape Size (meg) 736042.0 736042.00.0
> > Tape Used (%) 378.3 378.30.0
> > DLEs Taped 7 7 0
> > Parts Taped7 7 0
>
> You are not splitting your DLE into chunks (parts == DLEs).
This is also strange...I have 4 tapes only and 4 DLEs defined...From
where it arrives to 7?
Sincerely,
Gour
--
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahaprabhu)
http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
--
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahaprabhu)
http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
signature.asc
Description: PGP signature
Re: one DLE per single tape?
On Mon, Aug 29, 2011 at 06:08:04PM +0200, Gour-Gadadhara Dasa wrote: > On Mon, 29 Aug 2011 10:47:08 -0400 > Jon LaBadie wrote: > > > If you want each DLE on its own tape, consider running each > > DLE in a separate amdump run. > > > $ amdump > > Thank you. I somehow 'missed' that feature. :-( > > Should I say that only today I discovered there is 'amstatus'. :-( > > So, each day learning something new... > > I did run amdump according to the config which I presented and it seems > that each DLE is on its own tape. > > For the testing purposes I have extracted one small directory and now > running amcheckdump to try to verify everything is OK 'cause I see some > strange things in my amreport: > > > [amanda@atmarama slidesng] amreport slidesng > Hostname: atmarama.noip.me > Org : Scanned Slides NG > Config : slidesng > Date: August 28, 2011 > > These dumps were to tapes slides-1, slides-2, slides-3, slides-4. > The next 4 tapes Amanda expects to use are: slides-1, slides-2, > slides-3, slides-4. FAILURE DUMP SUMMARY: > atmarama.noip.me /slides/tape1 lev 0 FAILED [data write: Broken pipe] > atmarama.noip.me /slides/tape1 lev 0 partial taper: No space left on > device atmarama.noip.me /slides/tape1 lev 0 was successfully retried > atmarama.noip.me /slides/tape2 lev 0 FAILED [data write: Broken pipe] > atmarama.noip.me /slides/tape2 lev 0 partial taper: No space left on > device atmarama.noip.me /slides/tape2 lev 0 was successfully retried > atmarama.noip.me /slides/tape4 lev 0 FAILED [data write: Broken pipe] > atmarama.noip.me /slides/tape4 lev 0 partial taper: No space left on > device atmarama.noip.me /slides/tape4 lev 0 was successfully retried > Nothing strange there. It attempted to put it a DLE, or depending on your configuation, a chunk of the DLE on to a tape but it didn't fit. Thus it retried that DLE or chunk on the next tape and succeeded. > STATISTICS: > Total Full Incr. Level:# > > Estimate Time (hrs:min) 0:00 > Run Time (hrs:min) 14:23 > Dump Time (hrs:min)13:11 13:11 0:00 > Output Size (meg) 736042.0 736042.00.0 > Original Size (meg) 647112.1 647112.10.0 > Avg Compressed Size (%)113.7 113.7-- Looks like you should not be trying to compress these data. > DLEs Dumped4 4 0 > Avg Dump Rate (k/s) 15874.315874.3-- > > Tape Time (hrs:min)14:22 14:22 0:00 > Tape Size (meg) 736042.0 736042.00.0 > Tape Used (%) 378.3 378.30.0 > DLEs Taped 7 7 0 > Parts Taped7 7 0 You are not splitting your DLE into chunks (parts == DLEs). > Avg Tp Write Rate (k/s) 14570.314570.3-- > > USAGE BY TAPE: > Label Time Size % DLEs Parts > slides-12:27 199236614k 100.0 2 2 > slides-22:27 199236118k 100.0 2 2 > slides-32:27 199235822k 100.0 2 2 > slides-41:55 155998480k 78.3 1 1 > > FAILED DUMP DETAILS: > /-- atmarama.noip.me /slides/tape1 lev 0 FAILED [data write: Broken > pipe] sendbackup: start [atmarama.noip.me:/slides/tape1 level 0] > sendbackup: info BACKUP=/usr/local/bin/gtar > sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ... > sendbackup: info end > \ > /-- atmarama.noip.me /slides/tape2 lev 0 FAILED [data write: Broken > pipe] sendbackup: start [atmarama.noip.me:/slides/tape2 level 0] > sendbackup: info BACKUP=/usr/local/bin/gtar > sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ... > sendbackup: info end > \ > /-- atmarama.noip.me /slides/tape4 lev 0 FAILED [data write: Broken > pipe] sendbackup: start [atmarama.noip.me:/slides/tape4 level 0] > sendbackup: info BACKUP=/usr/local/bin/gtar > sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ... > sendbackup: info end > \ > > NOTES: > planner: Adding new disk atmarama.noip.me:/slides/tape1. > planner: Adding new disk atmarama.noip.me:/slides/tape2. > planner: Adding new disk atmarama.noip.me:/slides/tape3. > planner: Adding new disk atmarama.noip.me:/slides/tape4. > taper: tape slides-1 kb 199236614 fm 2 [OK] > taper: tape slides-2 kb 199236118 fm 2 [OK] > taper: tape slides-3 kb 199235822 fm 2 [OK] > taper: tape slides-4 kb 155998480 fm 1 [OK] > > > DUMP SUMMARY: > DUMPER STATS > TAPER STATS HOSTNAME DISKL ORIG-kBOUT-kB COMP% > MMM:SSKB/s MMM:SSKB/s -- > -- -- atmarama.noi > -ides/tape1 0 157545230 157545230 -- 117:58 22259.1 118:00 22252.2 > atmarama.noi -id
Re: holding disk not used?
On 08/17/2011 03:35 PM, Jean-Francois Malouin wrote:
I think I got it now.
The amanda.conf used the following holding disk definition:
define holdingdisk "holddisk" {
directory "/holddisk/charm"
use -50Gb
chunksize 0
}
So I changed it to:
holdingdisk "holddisk" {
directory "/holddisk/charm"
use -50Gb
chunksize 0
}
'define holdingdisk' define it, but it is not used, you could have added
a simple line:
holdingdisk "holddisk"
to tell amanda to use the defined holdingdisk, or using the older syntax
like you did.
Jean-Louis
Re: one DLE per single tape?
On 08/29/2011 10:47 AM, Jon LaBadie wrote: If you want each DLE on its own tape, consider running each DLE in a separate amdump run. $ amdump 3.3.1 (not yet released) have a new 'max-dle-by-volume' setting. You can set it to 1. Jean-Louis
Re: one DLE per single tape?
On Mon, 29 Aug 2011 10:47:08 -0400
Jon LaBadie wrote:
> If you want each DLE on its own tape, consider running each
> DLE in a separate amdump run.
> $ amdump
Thank you. I somehow 'missed' that feature. :-(
Should I say that only today I discovered there is 'amstatus'. :-(
So, each day learning something new...
I did run amdump according to the config which I presented and it seems
that each DLE is on its own tape.
For the testing purposes I have extracted one small directory and now
running amcheckdump to try to verify everything is OK 'cause I see some
strange things in my amreport:
[amanda@atmarama slidesng] amreport slidesng
Hostname: atmarama.noip.me
Org : Scanned Slides NG
Config : slidesng
Date: August 28, 2011
These dumps were to tapes slides-1, slides-2, slides-3, slides-4.
The next 4 tapes Amanda expects to use are: slides-1, slides-2,
slides-3, slides-4. FAILURE DUMP SUMMARY:
atmarama.noip.me /slides/tape1 lev 0 FAILED [data write: Broken pipe]
atmarama.noip.me /slides/tape1 lev 0 partial taper: No space left on
device atmarama.noip.me /slides/tape1 lev 0 was successfully retried
atmarama.noip.me /slides/tape2 lev 0 FAILED [data write: Broken pipe]
atmarama.noip.me /slides/tape2 lev 0 partial taper: No space left on
device atmarama.noip.me /slides/tape2 lev 0 was successfully retried
atmarama.noip.me /slides/tape4 lev 0 FAILED [data write: Broken pipe]
atmarama.noip.me /slides/tape4 lev 0 partial taper: No space left on
device atmarama.noip.me /slides/tape4 lev 0 was successfully retried
STATISTICS:
Total Full Incr. Level:#
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 14:23
Dump Time (hrs:min)13:11 13:11 0:00
Output Size (meg) 736042.0 736042.00.0
Original Size (meg) 647112.1 647112.10.0
Avg Compressed Size (%)113.7 113.7--
DLEs Dumped4 4 0
Avg Dump Rate (k/s) 15874.315874.3--
Tape Time (hrs:min)14:22 14:22 0:00
Tape Size (meg) 736042.0 736042.00.0
Tape Used (%) 378.3 378.30.0
DLEs Taped 7 7 0
Parts Taped7 7 0
Avg Tp Write Rate (k/s) 14570.314570.3--
USAGE BY TAPE:
Label Time Size % DLEs Parts
slides-12:27 199236614k 100.0 2 2
slides-22:27 199236118k 100.0 2 2
slides-32:27 199235822k 100.0 2 2
slides-41:55 155998480k 78.3 1 1
FAILED DUMP DETAILS:
/-- atmarama.noip.me /slides/tape1 lev 0 FAILED [data write: Broken
pipe] sendbackup: start [atmarama.noip.me:/slides/tape1 level 0]
sendbackup: info BACKUP=/usr/local/bin/gtar
sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ...
sendbackup: info end
\
/-- atmarama.noip.me /slides/tape2 lev 0 FAILED [data write: Broken
pipe] sendbackup: start [atmarama.noip.me:/slides/tape2 level 0]
sendbackup: info BACKUP=/usr/local/bin/gtar
sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ...
sendbackup: info end
\
/-- atmarama.noip.me /slides/tape4 lev 0 FAILED [data write: Broken
pipe] sendbackup: start [atmarama.noip.me:/slides/tape4 level 0]
sendbackup: info BACKUP=/usr/local/bin/gtar
sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ...
sendbackup: info end
\
NOTES:
planner: Adding new disk atmarama.noip.me:/slides/tape1.
planner: Adding new disk atmarama.noip.me:/slides/tape2.
planner: Adding new disk atmarama.noip.me:/slides/tape3.
planner: Adding new disk atmarama.noip.me:/slides/tape4.
taper: tape slides-1 kb 199236614 fm 2 [OK]
taper: tape slides-2 kb 199236118 fm 2 [OK]
taper: tape slides-3 kb 199235822 fm 2 [OK]
taper: tape slides-4 kb 155998480 fm 1 [OK]
DUMP SUMMARY:
DUMPER STATS
TAPER STATS HOSTNAME DISKL ORIG-kBOUT-kB COMP%
MMM:SSKB/s MMM:SSKB/s --
-- -- atmarama.noi
-ides/tape1 0 157545230 157545230 -- 117:58 22259.1 118:00 22252.2
atmarama.noi -ides/tape2 0 155998480 155998480 -- 116:35 22302.9
116:36 22298.2 atmarama.noi -ides/tape3 0 183946790 183946790 --
135:25 22640.8 135:27 22634.0 atmarama.noi -ides/tape4 0 165152310
165152310 -- 421:23 6532.2 421:25 6531.6
(brought to you by Amanda version 3.2.2)
What do you think about it?
Sincerely,
Gour
--
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahaprabhu)
http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
--
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahapr
Re: one DLE per single tape?
On Mon, Aug 29, 2011 at 08:03:57AM +0200, Gour-Gadadhara Dasa wrote:
> Hello!
>
> I've 3 different sets of multimedia data which I want to backup for
> longer-term archival with occassional restore of some specific data. At
> the moment the data is backed up using 3 different configurations:
>
> * movies-hi8
> * movies-vhs
> * slides (scanned 35mm slides)
>
> Each set is backed on the set of tapes spanning 4 or 5 of them, but
> this makes restore (too) long procedure, so I'd like to redo my backup
> in order that there is no tape spanning, iow, that data from each tape
> can be restored separately.
>
> In order to do that, I modified my old configuration for e.g. slides,
> and created 4 DLEs in my disklist looking like:
>
> atmarama.noip.me /slides/tape1 /mnt/backup
> { simple-gnutar-local
> include append "./gmp/1" "./gmp/2"
> include append "./nmp/1" "./nmp/2" "./nmp/3/" "./nmp/4"
> }
>
> atmarama.noip.me /slides/tape2 /mnt/backup/ {
> simple-gnutar-local
> include append "./np/1" "./np/2"
> include append "./si/1" "./si/2" "./si/3" "./si/4"
> }
>
> [...]
>
> hoping it would put each DLE on a separate tape (I've tweaked the sets
> so that each DLE can fit on a single LTO-2 tape.
>
> However, by inspecting logs while the backup is still going on, I'm not
> sure the job will be done successfully, here is the part of the current
> log (when the 2nd tape is loaded):
>
> START planner date 20110828224319
> DISK planner atmarama.noip.me /slides/tape1
> START driver date 20110828224319
> DISK planner atmarama.noip.me /slides/tape2
> DISK planner atmarama.noip.me /slides/tape3
> STATS driver hostname atmarama.noip.me
> DISK planner atmarama.noip.me /slides/tape4
> INFO planner Adding new disk atmarama.noip.me:/slides/tape1.
> INFO planner Adding new disk atmarama.noip.me:/slides/tape2.
> INFO planner Adding new disk atmarama.noip.me:/slides/tape3.
> INFO planner Adding new disk atmarama.noip.me:/slides/tape4.
> STATS driver startup time 0.008
If you want each DLE on its own tape, consider running each
DLE in a separate amdump run.
$ amdump
--
Jon H. LaBadie j...@jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
Re: SV: amvault-3.2.3
Gunnar,
Thanks for the patch, I committed it.
Jean-Louis
On 08/02/2011 07:54 AM, Gunnarsson, Gunnar wrote:
ok type casting to int solved my problem with Total size printing.
<$total_kb += int $dump->{'kb'};
---
$total_kb += $dump->{'kb'};
Thanks Gunar Gunnarsson
Från: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] För
Gunnarsson, Gunnar
Skickat: den 2 augusti 2011 11:43
Till: amanda-users@amanda.org
Ämne: amvault-3.2.3
Hi,
Upgraded to 3.2.3 from 3.2.0 to fix split and LEOM handling.
amvault is not listning the size of the dumps see below. I'm running Solaris
sparc 10 perl version v5.8.4.
amvault --dry-run -o mailto=vault --fulls-only --src-timestamp 20110709-20110801
--dst-changer vault --label-template "daily-1%%" --autolabel any daily tx5019
daily-19 94 tx5019 / 20110710200103 0
daily-24 29 tx5019 /export/home 20110714200102 0
daily-38 114 tx5019 /export 20110723200103 0
daily-41 161 tx5019 / 20110725200103 0
daily-45 26 tx5019 /export/home 20110729200103 0
Total Size: NaN KB
Thanks Gunnar Gunnarsson
