Re: preparing archive tapes (new thread)

[Gene Heskett]

On Monday 21 January 2019 03:52:18 Stefan G. Weichinger wrote:

> Am 17.01.19 um 12:10 schrieb Stefan G. Weichinger:
> > The idea is to let the normal runs write to storage "daily" and
> > additionally keep the dumped files in the holdingdisk.
> >
> > After having all DLEs there I want to do something like:
> >
> > amflush daily -o storage=archive
> >
> > and get all FULL backups flushed to that specific set of tapes.
>
> (making good progress)
>
> Does the "storage" value get stored into the tarballs in the holding
> disk?
>
> I have files there dumped via "amdump -o storage=archive" and now want
> to flush them to "storage=daily"
>
> amflush always stops immediately and amstatus shows a column
> "(archive)" for each DLE.
>
> I even commented the second storage definition from amanda.conf,
> didn't help ... so I assume it's somewhere in the tarball itself. Will
> try to read it via amrestore now.

Are you using tapes yet Stefan? If useing vtapes, that file would likely 
be visible by an ls on that tapes disk directory.

Using vtapes on a 2T spinning rust disk, and my wrapper script, I show 
for last nights run:
root@coyote:/home/amanda# ls /amandatapes/Dailys/data/
0.Dailys-5000019.coyote._home_gene_src.0
  
00038.GO704._usr_local.0 00057.coyote._usr_music.1
1.GO704._root.000020.coyote._home_gene_Mail.0   
  
00039.picnc._boot.0  00058.coyote._usr_dlds_books.1
2.shop._root.0 00021.coyote._home_gene.4
  
00040.GO704._var_lib_amanda.000059.coyote._usr_dlds_tgzs.1
3.GO704._var_amanda.1  00022.coyote._home_amanda.1  
  
00041.GO704._etc.0   00060.coyote._usr_dlds_misc.1
4.GO704._usr_lib_amanda.1  00023.coyote.Downloadsam.1   
  
00042.coyote._usr_lib.0  00061.coyote._home_gene_Music.1
5.shop._var_amanda.0   00024.coyote._home_gene_Download.1   
  
00043.coyote._usr_local.100062.coyote._home_gene_Videos.1
6.shop._usr_local.100025.coyote._home_ups.1 
  
00044.coyote._lib.0  00063.coyote._boot.1
7.lathe._usr_src.0 00026.coyote._home_nut.1 
  
00045.coyote._opt.2  00064.coyote._bin.1
8.shop._usr_lib_amanda.1   00027.coyote.Downloadsnz.1   
  
00046.coyote._usr_share.100065.coyote._sbin.1
9.lathe._etc.0 
00028.coyote._GenesAmandaHelper-0.61_config-bak.5  
00047.coyote._home_gene_Pictures.1   00066.coyote._home_gene_LCNC-isos.1
00010.lathe._var_lib_amanda.0  00029.coyote._GenesAmandaHelper-0.61.0   
  
00048.coyote._usr_src.1  00067.coyote._usr_sbin.1
00011.shop._etc.0  00030.coyote._var.4  
  
00049.coyote._usr_pix.1  00068.coyote._usr_games.1
00012.lathe._var_amanda.1  00031.picnc._.0  
  
00050.coyote._usr_bin.1  00069.coyote.PublicAAZ.1
00013.lathe._usr_lib_amanda.1  00032.coyote._root.0 
  
00051.coyote._etc.1  00070.coyote.PublicAap.1
00014.lathe._usr_local.1   00033.lathe._home.0  
  
00052.coyote._usr_include.1  configuration.tar
00015.lathe._root.000034.shop._home.0   
  
00053.coyote.PublicAqz.1 indices.tar
00016.shop._lib_firmware.0 00035.coyote._home_gene_PublicB.0
  
00054.coyote._usr_movies.1
00017.shop._var_lib_amanda.0   00036.GO704._home.0  
  
00055.coyote._home_gene_Documents.1
00018.lathe._lib_firmware.000037.GO704._lib_firmware.0  
  
00056.coyote._CoCo.1

The pair of tar files are from my wrapper. The configuration.tar is the 
complete configuration that made the rest of that backup, and the 
indices.tar is the complete database, most importantly containing all 
the indice's from this backup, so I could do a bare metal on a new disk 
recovery to the status of my systems a/o around 3AM this morning.

Copyright 2018 by Maurice E. Heskett

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: preparing archive tapes (new thread)

[Stefan G. Weichinger]

Am 22.01.19 um 18:30 schrieb Debra S Baddorf:

> The first block is a text description of the dump and how to use it.
> 
> dd if=tapeOrFilename  of=whatever   bs=YourBlockSize  count=1
> 
> should show that first block.Use skip=1  for put the actual dump to a 
> useable file.
> 
> (DD command from memory;  I may be slightly off)

yes, thanks

no "storage" or "archive" or "daily" inside "whatever" ;-)

I just decided to let the dumpfiles stored in the holdingdisk for a week
or so until they are outdated anyway. The new amdump-runs go to storage
"daily" and related tapes ok.

No real solution but acceptable workaround.

Re: preparing archive tapes (new thread)

[Debra S Baddorf]

> On Jan 21, 2019, at 2:52 AM, Stefan G. Weichinger  wrote:
> 
> Am 17.01.19 um 12:10 schrieb Stefan G. Weichinger:
> 
>> The idea is to let the normal runs write to storage "daily" and
>> additionally keep the dumped files in the holdingdisk.
>> 
>> After having all DLEs there I want to do something like:
>> 
>> amflush daily -o storage=archive
>> 
>> and get all FULL backups flushed to that specific set of tapes.
> 
> (making good progress)
> 
> Does the "storage" value get stored into the tarballs in the holding disk?
> 
> I have files there dumped via "amdump -o storage=archive" and now want
> to flush them to "storage=daily"
> 
> amflush always stops immediately and amstatus shows a column "(archive)"
> for each DLE.
> 
> I even commented the second storage definition from amanda.conf, didn't
> help ... so I assume it's somewhere in the tarball itself. Will try to
> read it via amrestore now.
> 

The first block is a text description of the dump and how to use it.

dd if=tapeOrFilename  of=whatever   bs=YourBlockSize  count=1

should show that first block.Use skip=1  for put the actual dump to a 
useable file.

(DD command from memory;  I may be slightly off)

Deb Baddorf

Re: preparing archive tapes (new thread)

[Stefan G. Weichinger]

Am 17.01.19 um 12:10 schrieb Stefan G. Weichinger:

> The idea is to let the normal runs write to storage "daily" and
> additionally keep the dumped files in the holdingdisk.
> 
> After having all DLEs there I want to do something like:
> 
> amflush daily -o storage=archive
> 
> and get all FULL backups flushed to that specific set of tapes.

(making good progress)

Does the "storage" value get stored into the tarballs in the holding disk?

I have files there dumped via "amdump -o storage=archive" and now want
to flush them to "storage=daily"

amflush always stops immediately and amstatus shows a column "(archive)"
for each DLE.

I even commented the second storage definition from amanda.conf, didn't
help ... so I assume it's somewhere in the tarball itself. Will try to
read it via amrestore now.