SV: amvault report - *** THE DUMPS DID NOT FINISH PROPERLY!

[Gunnarsson, Gunnar]

This has worked in all previous version of Amanda.
.
>Ah, so this is using the amzfs-snapshot scripts?

>Jean-Louis, did something change here?  I don't recall if we have a way for a 
>script to change the diskdevice for a DLE?  Did that work in
3.1 and not in 3.2?


Tnanks Gunnar Gunnarson

SV: amvault report - *** THE DUMPS DID NOT FINISH PROPERLY!

[Gunnarsson, Gunnar]

Snapshot is created but not used see below in 3.2.0beta3

Sat Oct  9 22:23:08 2010: amgtar: Spawning "/usr/local/bin/tar 
/usr/local/bin/tar --create --verbose --file - --directory / --one-file-system 
--no-check-device --listed-incremental 
/var/opt/lib/amanda/gnutar-lists/hansabck_1.new --sparse --ignore-failed-read 
--totals ." in pipeline

but in 3.1.1 snapshot is created and used - the config is the same.

 Sat Oct  9 20:10:26 2010: amgtar: Spawning "/usr/local/bin/tar 
/usr/local/bin/tar --create --verbose --file - --directory 
//.zfs/snapshot/amanda-_-current --one-file-system --no-check-device 
--listed-incremental/var/opt/lib/amanda/gnutar-lists/tx5019__0.new --sparse 
--ignore-failed-read --totals ." in pipeline

ok it's different machines but I downgraded the client and the log was 
overwritten.

> Hmm, I don't think we made any changes to how GNU Tar is invoked that would 
> cause it to no longer be able to read special device files - it never could 
> do that.  If you still have a sendbackup debug log from 3.1.x, can you 
> compare the tar invocation to the one made by 3.2.0?

Thanks Gunnar Gunnarsson

SV: amvault report - *** THE DUMPS DID NOT FINISH PROPERLY!

[Gunnarsson, Gunnar]

ok then I must overide the tapetype def with -o option in the amvault command.
 
>No, it needs to be in the tapetype.  It's weird, I know, but there are some 
>difficult problems with combining those two sections.


Thanks Gunnar Gunnarsson

SV: amvault report - *** THE DUMPS DID NOT FINISH PROPERLY!

[Gunnarsson, Gunnar]

>OK.  You should adjust the length in your tapetype definition, then - your 
>tape appears to be at least 550% longer than you have configured.

Can I add the tape length to:

define changer vault {
tpchanger "chg-manual"
tapedev "tape:/dev/rmt/0n"
changerfile "changer.conf"
}



> Not sure what you mean by this - what was delayed?
The holding disk was filled up before vtape was written.


>You probably should be excluding ./devices?

This worked in verions 3.1.1 something is changed 3.2.0beta3 nothing else has 
changed on the system. I testaed another Solaris client with this version and 
got the same problem.


FAILED DUMP DETAILS:
  /-- hansabck / lev 1 FAILED [/usr/local/bin/tar exited with status 2: see 
/tmp/amanda/client/hansa/amgtar.20101008223221000.debug]
  sendbackup: info BACKUP=APPLICATION
  sendbackup: info APPLICATION=amgtar
  sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc 
|/opt/sfw/libexec/amanda/application/amgtar restore [./file-to-restore]+
  sendbackup: info COMPRESS_SUFFIX=.gz
  sendbackup: info end
  ? /usr/local/bin/tar: ./devices/ramdisk-root: Cannot savedir: No such file or 
directory
  ? /usr/local/bin/tar: ./devices/ramdisk-root/: Warning: Cannot stat: No such 
file or directory
  ? /usr/local/bin/tar: ./dev/fd: file changed as we read it
  ? /usr/local/bin/tar: ./devices: file changed as we read it
  ? /usr/local/bin/tar: ./devices/e...@c0: file changed as we read it
  ? /usr/local/bin/tar: ./devices/e...@c0/ser...@0,ca: file changed as we 
read it
  ? /usr/local/bin/tar: ./devices/iscsi: file changed as we read it
  ? /usr/local/bin/tar: ./devices/n...@80: file changed as we read it
  ? /usr/local/bin/tar: ./devices/options: file changed as we read it
  ? /usr/local/bin/tar: ./devices/pci-performance-count...@0: file changed as 
we read it
  ? /usr/local/bin/tar: ./devices/p...@0: file changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0: file changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1: file changed as we read 
it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1/p...@0: file changed as 
we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1/p...@0/p...@1: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1/p...@0/p...@1/p...@0: 
file changed as we read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@1/p...@0/u...@0: file changed as we 
read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@1/p...@0/u...@0,1: file changed as 
we read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@1/p...@0/u...@0,2: file changed as 
we read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@1/p...@0/u...@0,2/h...@4: file 
changed as we read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@1/p...@0/u...@0,2/stor...@2: file 
changed as we read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@1/p...@0/u...@0,2/stor...@2/d...@0,0:
 file changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1/p...@0/p...@2: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1/p...@0/p...@2/netw...@0: 
file changed as we read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@2/netw...@0,1: file changed as we 
read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1/p...@0/p...@3: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@1/p...@0/p...@3/netw...@0: 
file changed as we read it
  ? /usr/local/bin/tar: 
./devices/p...@0/p...@0/p...@1/p...@0/p...@3/netw...@0,1: file changed as we 
read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@2: file changed as we read 
it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@2/s...@0: file changed as 
we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@2/s...@0/s...@0,0: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@2/s...@0/s...@1,0: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@2/s...@0/s...@2,0: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@2/s...@0/s...@3,0: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@8: file changed as we read 
it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@8/p...@0: file changed as 
we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@8/p...@0/p...@1: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@8/p...@0/p...@2: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@8/p...@0/p...@8: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@8/p...@0/p...@9: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@8/p...@0/p...@a: file 
changed as we read it
  ? /usr/local/bin/tar: ./devices/p...@0/p...@0/p...@9: file 

SV: amvault report - *** THE DUMPS DID NOT FINISH PROPERLY!

[Gunnarsson, Gunnar]

No I was wrong about it only delayed the flushing until at the end. Is that a 
new behaviour in versioh 3.2.0 ?

The only problem I got was on the client side for the root filesystem zfs.

  /-- hansabck / lev 1 FAILED [/usr/local/bin/tar exited with status 2: see 
/tmp/amanda/client/hansa/amgtar.20101008223221000.debug]
  sendbackup: info BACKUP=APPLICATION
  sendbackup: info APPLICATION=amgtar
  sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc 
|/opt/sfw/libexec/amanda/application/amgtar restore [./file-to-restore]+
  sendbackup: info COMPRESS_SUFFIX=.gz
  sendbackup: info end
  ? /usr/local/bin/tar: ./devices/ramdisk-root: Cannot savedir: No such file or 
directory
  ? /usr/local/bin/tar: ./devices/ramdisk-root/: Warning: Cannot stat: No such 
file or directory

-- GG

 
> Let's take this back on the list.