On Mar 6, 2015, at 5:19 PM, Debra S Baddorf <[email protected]> wrote:

> Omitting the  SRC-TIMESTAMP  flag   finally does produce something,  but it 
> yields
> ALL the dumps I’ve ever done.   Not helpful,   but it points to where a 
> problem is.
> 
 The results still LIST  the same timestamp  that I was previously trying to use
(on the few dumps that ARE the ones that I wanted to include)


VTAPE-3 1  <fqdn>   /home 20150208180002 0
VTAPE-3 2  <fqdn>   /var 20150208180002 0
VTAPE-4 1  <fqdn>  /mnt/disk3 20150208180002 0
plus 21 more valid dumps
plus scads of OTHERS  that I’m not seeking

Deb







> Deb
> 
> 
> On Mar 6, 2015, at 5:12 PM, Debra S Baddorf <[email protected]> wrote:
> 
>> 
>> On Mar 6, 2015, at 5:10 PM, Debra S Baddorf <[email protected]> wrote:
>> 
>>> 
>>> On Mar 6, 2015, at 4:43 PM, Jean-Louis Martineau <[email protected]> 
>>> wrote:
>>> 
>>>> On 03/06/2015 04:59 PM, Debra S Baddorf wrote:
>>>>> I’ve run AMVAULT  on machine A and copied my dumps to vtapes.
>>>>> I’ve  scp’ed  the vtapes  to machine B,   along  with the
>>>>>     tapelist   entries   and  the   log.<datestamp>.0 files
>>>>> 
>>>>> AMVAULT  on machine B insists  that there are “no disks to vault”.
>>>>> Can anybody think of anything I’m missing?
>>>> 
>>>> Do 'amadmin CONF find' list the dump?
>>>> Do the tapelist and log are at the right place
>>>> $ amgetconf CONF tapelist
>>>> $ amgetconf CONF logdir
>>>> 
>>> 
>>> amadmin  daily   find      found the 4 of them that I explicitly tried,  
>>> one by one
>> 
>> amadmin daily find   | grep VTAPE         found all 24 of them,  correctly
>> 
>> 
>>> 
>>> $ amgetconf daily tapelist
>>> /usr/local/etc/amanda/logs/daily/tapelist
>>> bash-4.1$ grep VTAPE /usr/local/etc/amanda/logs/daily/tapelist
>>> 20150306143401 VTAPE-4 no-reuse BLOCKSIZE:512
>>> 20150306142427 VTAPE-3 no-reuse BLOCKSIZE:512
>>> 20150305163021 VTAPE-1 no-reuse BLOCKSIZE:512
>>> 0 VTAPE-2 reuse BLOCKSIZE:512
>>> 
>>> 
>>> Yes,   I did amgetconf    and then cut & pasted the result.   The VTAPEs 
>>> are in that file.
>>> 
>>> Ditto for the logdir — amgetconf,   cut & pasted  and grepped for  VTAPE  
>>> in those files.
>>> 
>>> 
>>> 
>>> Deb
>>> 
>>> 
>>> 
>>> 
>>> 
>>>>> 
>>>>> I can grep  through the log.<datestamp>.0   files on machine B   and find 
>>>>> the  DLEs  and
>>>>> the names of the Vtapes.     My reverse  AMVAULT  command looks like this:
>>>>> 
>>>>> amvault --dry-run --src-timestamp 20150208180002 --fulls-only -o 
>>>>> tpchanger=vtapes-on-spool
>>>>> --dst-changer LTO5-Robot  --label-template "ad5-%"  daily
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> FWIW,  back on machine A  the amvault command had the tapes  in the   DST 
>>>>>  position:
>>>>> amvault   --src-timestamp 20150208180002 --fulls-only   --dst-changer  
>>>>> vtapes-on-spool
>>>>> --label-template "VTAPE-%%%"  daily
>>>>> 
>>>>> and the “from”  changer was the main one in the configuration.
>>>>> 
>>>>> Deb Baddorf
>>>>> Fermilab
>>>>> 
>>>>> 
>>>>> On Dec 5, 2014, at 8:27 AM, Jean-Louis Martineau <[email protected]> 
>>>>> wrote:
>>>>> 
>>>>>> It is a lot easier if you can plug the LTO2 tape drive directly on the 
>>>>>> machine B, that way you can use amvault to copy the dump directly from 
>>>>>> the LTO2 tapes to the LTO5 tapes.
>>>>>> 
>>>>>> You can do it from both machines:
>>>>>> - run amvault on machine A to copy the dump to vtapes
>>>>>> - transfer the vtapes to machine B including the
>>>>>>   -tapelist entries and the
>>>>>>   -log.<datestamp>.0 files.
>>>>>> - run amvault on machine B to copy the dump from vtapes to LTO5.
>>>>>> 
>>>>>> Jean-Louis
>>>>>> 
>>>>>> On 12/04/2014 06:33 PM, Debra S Baddorf wrote:
>>>>>>> If I want to copy my backups that are already on LTO2 tapes  and move 
>>>>>>> them onto
>>>>>>> LTO5 tapes,    is   AMVAULT  the way to go?
>>>>>>> 
>>>>>>> I will soon get rid of most of my older tape drives and  I want to 
>>>>>>> preserve some of the backups
>>>>>>> done on those tapes.   Machine A will still have the old tape drive 
>>>>>>> available for a while.  I’d like
>>>>>>> to read the backups onto disk on machine A,   and then copy them over 
>>>>>>> the network,
>>>>>>> over to machine B,    and write them to a newer tape drive on machine B.
>>>>>>> 
>>>>>>> It looks like  AMFETCHDUMP  will de-compress the files and
>>>>>>> try to undo the backups,  so I don’t think I want that.    Should I use 
>>>>>>> AMVAULT
>>>>>>> on both machine A and machine B?    I could tell machine A  to read 
>>>>>>> from  the
>>>>>>> old tape drive as the secondary media  (per terminology in the man page)
>>>>>>> and write to  “disk”  as the  “tertiary”   media.     Then  I copy the 
>>>>>>> files
>>>>>>> over to machine B     and reverse the process.    Will this work?
>>>>>>> 
>>>>>>> 
>>>>>>> (Machine B  isn’t here yet.  Also,  forgive my up casing the AMANDA 
>>>>>>> words,
>>>>>>> but my mac  keeps trying to respell everything and my brain won’t cope 
>>>>>>> with
>>>>>>> that today.  )
>>>>>>> 
>>>>>>> Deb Baddorf
>>>>>>> Fermilab
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> TL;DR  :
>>>>>>> 
>>>>>>> I’ve only got a year’s worth of data on LTO2 tape, so this seems worth 
>>>>>>> doing.  I had older yet
>>>>>>> SDLT tapes before that,  lots of them.  Those I won’t try to convert, 
>>>>>>> but will save the
>>>>>>> heroics until someone absolutely requires some old data.   Learning a 
>>>>>>> little about AMVAULT
>>>>>>> wouldn’t hurt me either, so this seems like a worthwhile project.
>>>>> 
>>>> 
>>> 
>> 
> 


Reply via email to