Re: Problem backing up: "no backup size line"

2017-10-26 Thread Jobst Schmalenbach 
On Thu, Oct 26, 2017 at 01:16:35PM +0200, Michael M?skens (m...@muessi.nl) 
wrote:
> hi,
> > 
> > But I also do not know how to check this: GNU tar state file 
> > /var/lib/amanda/gnutar-lists/XYZSOMETHING.new is corrupted.
> 
> did you solve that problem by now? I???m not sure, but deleting the .new-file 
> in  /var/lib/amanda/gnutar-lists/ could help you with that.
> 

Darn. Should have explained better.

I have a snapshot system that takes a snapshot every 3 hours including the 
amanda dirs.
So I went back (on all machines that amanda is involved backing up) to restore 
the amanda stuff to a time I new it works ... then start a backup again ... 
this still happened.

In my spare time I am currently reading the source to learn/research what is 
going on but it's not the .new file.

Jobst


-- 
186,262 miles/second :  Not just a good idea, it's the LAW.

  | |0| |   Jobst Schmalenbach, General Manager
  | | |0|   Barrett & Sales Essentials
  |0|0|0|   +61 3 9533 , POBox 277, Caulfield South, 3162, Australia

Re: approaches to Amanda vaulting?

2017-10-26 Thread Stefan G. Weichinger 
Am 2017-10-25 um 12:56 schrieb Stefan G. Weichinger:

> All this is kind of non-intuitive, at least for me so far.

hello, anyone?

:-P

Re: Problem backing up: "no backup size line"

2017-10-26 Thread Michael Müskens 
hi,

> Now I get the following error: "no backup size line", in the log it looks 
> like this
> 
>  FAIL dumper 192.168.0.1 /boot 20171024230002 1 [no backup size line]
>sendbackup: start [192.168.0.1:/boot level 1]
>sendbackup: info BACKUP=/bin/tar
>sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
>sendbackup: info end
>sendbackup: error [no backup size line]
>  PARTIAL chunker 192.168.0.1 /boot 20171024230002 1 [sec 0.174 kb 11 kps 
> 246.4]
> 
> But I also do not know how to check this: GNU tar state file 
> /var/lib/amanda/gnutar-lists/XYZSOMETHING.new is corrupted.


did you solve that problem by now? I’m not sure, but deleting the .new-file in  
/var/lib/amanda/gnutar-lists/ could help you with that.

greets,
Michael
—
Michael Müskens
Cologne, Germany



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: List Contents of gnutar-list files

2017-10-26 Thread Debra S Baddorf 
One way is to start a recover:
  root>  amrecover  
setdisk  /myDLE
ls
cd  
ls
repeat until you are sure the contents you wanted is in there.
Recover 1 or 2 of the files, (to a scratch area)  to be sure you
wholly trust the contents.

Actually, another way,  once you’ve done   
root>  amrecover 
  setdisk  /myDLE
is to go to your log directory,  in another window,  while that first
window is STILL paused there, and has not exited am recover.
The content listing will be sitting in the  logs /index /  name-of-DLE
directory,  unpacked,  but only for as long as you are still inside the
amrecover process.
You can copy that file elsewhere, and your purloined copy will stick 
around.

Deb Baddorf
Fermilab


> On Oct 24, 2017, at 9:33 PM, Jobst Schmalenbach  wrote:
> 
> Hi
> How can I see the contents of gnutar-list files?
> 
> I tried tar/gunzip, ckecked amadmin etc but it seems I cannot read the 
> content.
> 
> Need to know whats in those files to see whether my inclusion/exclusion list 
> is correct and why it takes too much time to backup one particular host.
> 
> 
> Jobst
> 
> 
> 
> 
> -- 
> Computers run on smoke, once the smoke gets out they don't work anymore!
> 
>  | |0| |   Jobst Schmalenbach, General Manager
>  | | |0|   Barrett & Sales Essentials
>  |0|0|0|   +61 3 9533 , POBox 277, Caulfield South, 3162, Australia

Re: List Contents of gnutar-list files

2017-10-26 Thread Jon LaBadie 
On Wed, Oct 25, 2017 at 01:33:53PM +1100, Jobst Schmalenbach wrote:
> Hi
> How can I see the contents of gnutar-list files?
> 
> I tried tar/gunzip, ckecked amadmin etc but it seems I cannot read the 
> content.
> 
> Need to know whats in those files to see whether my inclusion/exclusion list 
> is correct and why it takes too much time to backup one particular host.
> 
gnutar has had several formats for the gnutar list incremental files.
Starting with about version 1.16 the format included null bytes.

It is not pretty, but this awk command can make the file readable.

  awk 'BEGIN{RS="[\n\0]" ; ORS="\n"} {print}'  

The output is grouped by directories, here are two examples.

0
1483174597
191920908
64768
2374981
./usr/share/doc/amanda-3.3.3   <= the directory path
YCOPYRIGHT <=   ordinary files
YNEWS  <=   in the directory
YREADME


0
1471672919
831712838
64768
5505376
./usr/src/kernels/3.10.0-327.28.3.el7.x86_64/arch/mips/bcm63xx
YKconfig
YMakefile
Dboards<= a subdirectory


HTH
Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)