On Thu, Sep 25, 2003 at 02:53:52PM +0200, Stefan G. Weichinger wrote: > > Currently I run amverify after every amdump. My backup window leaves > me enough time to do that and so I have "amverified" that the tapes I > wrote are at least readable. At the particular installation amverify > takes ~30-60 minutes (DDS-3 tapes) depending on tape usage. > > I would recommend doing amverify at least once a week to detect tape > errors before it is too late. Doing amverify on another tape-drive, as > Greg assumes, would be even better, but exceeds the budget of my > customers ... > > As I am not in place that often, I would like to have some automated > amrecover-run that restores some files of the actual tape. > > So it would be like: > > 1500 amcheck > 2200 amdump && amverify && automated_amrecover > > I think about including a small DLE containing testfiles, which is > dumped full every run and can be used to be recovered via a script. > > Has anyone done something like that?
Similar to a question I asked Greg, have you any idea how to handle a multiple tape backup situation? What if the DLE you want to test was on the first tape of several used that day? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
