Re: What's the easiest way to do a backup and verify?

From: Loren M. Lang (lorenl_at_alzatex.com)
Date: 03/13/05

  • Next message: Volodymyr Kostyrko: "Re: logo design competition"
    Date: Sun, 13 Mar 2005 00:26:56 -0800
    To: Jerry McAllister <jerrymc@clunix.cl.msu.edu>
    
    
    

    On Mon, Mar 07, 2005 at 09:47:31AM -0500, Jerry McAllister wrote:
    > >
    > > Is there an easy way to combine a backup and verify when doing backups
    > > with dump?
    > >
    > > On Windows NT it's just a matter of checking a box. I seem to recall
    > > the last time I looked into this on UNIX there was no easy way to
    > > accomplish a verify operation for a backup, but perhaps things have
    > > changed with FreeBSD 5.3 (?).
    > >
    > > I've never had a problem with backup (I backup to DAT tape), but I'd
    > > feel better if every backup was followed by a verify to make sure the
    > > tape is readable.
    >
    > Actually, if used frequently for backups - such as every day, DAT is
    > notoriously prone to failure. So, it is a good idea to check dumps
    > made to DAT. Unfortunately, there is not a reasonable way to
    > automatically do it. There is a verify, but it cannot work on a
    > running system, because it compares files (inodes) on the tape back
    > to the ones on disk. Any changes mean an error, even if it was a
    > real change in the file between the time it was written and the
    > time it was read back.
    >
    > The only real thing you can do is to read back the tape and look
    > for a couple of files with fairly high inode numbers for each file
    > system dumped. If you can read them, you can assume the tape
    > is readable.

    I'm not very familiar with tapes, but I think that the dump is written
    straight out to something like /dev/st0 right? So then wouldn't a
    second dump of the same snapshot diffed to the tape device be a good for
    a verify?

    Position tape at beginning of dump
    dump / | diff - /dev/st0

    Though I don't have much experience with either dump or tapes to verify.

    >
    > ////jerry
    >
    > >
    > > --
    > > Anthony
    > >
    > _______________________________________________
    > freebsd-questions@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

    -- 
    I sense much NT in you.
    NT leads to Bluescreen.
    Bluescreen leads to downtime.
    Downtime leads to suffering.
    NT is the path to the darkside.
    Powerful Unix is.
    Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
    Fingerprint: CEE1 AAE2 F66C 59B5 34CA  C415 6D35 E847 0118 A3D2
     
    
    


    • application/pgp-signature attachment: stored

  • Next message: Volodymyr Kostyrko: "Re: logo design competition"

    Relevant Pages

    • Re: newbie: weekly tape backup advice
      ... > I need some help setting up a tape backup system. ... It depends a little on the size of your disk compared to your tape ... If your critical data change is a lot and a full backup of it will take ... back up and then do incremental backups (level 1 dump) other days. ...
      (freebsd-questions)
    • Re: NTBackup
      ... the good part of that is 'I use a cleaning tape', ... recalibration' is a one shot affair for DDS, ... Backup Status ... Operation: Verify After Backup ...
      (microsoft.public.windows.server.sbs)
    • Re: Backup advice
      ... Dump is OS ... backup strategy is pretty much "I don't want to be screwed if my RAID ... I think the only reason to do just one full backup ... I have been running Amanda for years, on tape because the tape drive ...
      (freebsd-questions)
    • Verify problems
      ... I used the wizard to set up backup to a SCSI DAT tape. ... Everything goes fine until verify. ...
      (microsoft.public.windows.server.sbs)
    • Re: Backing up
      ... is just the point that was made by others, that any backup system is ... I don't bother to verify this. ... one tape. ... My usual apprach to that sort of `issue' is multiple copies. ...
      (uk.comp.sys.mac)