Hi Niall,
amverify use ammt and amdd which understand the file: driver.
They must be installed at the same place as your amverify program.
'make install' do it.
If amverify dont' find them, it will use the system mt and dd program
which dosn't understand the file: driver.
Jean-Louis
On Tue, Sep 10, 2002 at 01:01:26AM +0100, Niall O Broin wrote:
> On Sun, Sep 08, 2002 at 07:54:29PM -0400, Jean-Louis Martineau wrote:
>
> > Try this patch, tell me it works.
>
> in response to this request
>
> > On Fri, Sep 06, 2002 at 03:26:56PM -0700, Adnan Olia wrote:
> > > Hi all,
> > >
> > > I have a question. Can you run amverify on a tapeless backup in
> > > Amanda. I have no tape drives or tape changes and I am backing up
> > > my machines completely on my amanda server.
> > >
> > > When I run:
> > > amverify DailySet1
> > > I get:
> > > No tape changer...
> > > Not a character special device: file:/home/backup
>
> I've seen no response from Adnan but I'm on the same path myself i.e.
> starting to use the file: device. I applied the patch and it does get rid of
> the specific error message but then I get something like
>
>
> amanda@backup:/etc/amanda/TIZ> amverify TIZ
> No tape changer...
> Tape device is file:/backup/a...
> Verify summary to niall AT makalumedia DOT com
> Defects file is /tmp/amanda/amverify.13907/defects
> amverify TIZ
> Tue Sep 10 01:30:30 CEST 2002
>
> Using device file:/backup/a
> Waiting for device to go ready...
>
>
>
> and there it will wait, forever. Looking at the amverify script shows that
> it's not going to work with the file: device without a major rewrite. It
> uses mt extensively (in the above, it's waiting for an 'mt -f $DEVICE stat'
> to complete successfully. When $DEVICE is a directory, it will be left
> waiting :-(
>
> Later in amverify, it also waits for an 'mt -f $DEVICE rewind' to complete
> successfully which again will be a long wait when $DEVICE is a directory.
>
> And later, to read the tape label, it's using dd if=$DEVICE which again
> won't be a whole lot of use when $DEVICE is a directory.
>
> To actually read each backup file and pass it to the restore utility to see
> if it can create a catalog, it uses amrestore on $DEVICE - again, this isn't
> going to work when $DEVICE is a directory.
>
>
> I have to say that I'm more than a little concerned about this. I'm not so
> worried that amverify won't work, because I'd see the main use of amverify
> being to check a tape, and people probably don't want to do this quite so
> much when using disk (although amverify should work, or perhaps at the
> moment give an apropriate error message if the file: device is used) BUT I
> am worried about restoring from my backups.
>
> Have any of you who are using the file: device given it a good shakedown
> testing recovery of files or entire partitions ?
>
>
>
>
> Kindest regards,
>
>
>
>
> Niall O Broin
--
Jean-Louis Martineau email: martineau AT IRO.UMontreal DOT CA
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLE Tel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7 Fax: (514) 343-5834
|
