> Greetings ADSMers,
> I have a customer with an unusual request, but what they want is a
> perfectly legitimateconcern. They have some very critical data that
> need to archive on a daily basis, and then they want to delete the data
> as soon as a good copy gets to tape. There is too much data being
> generated this way to keep it around for more than a few days.
> The problem is, they don't exactly trust tape, and with good
> reason. They use DLT7000s, and they get a bad tape about once a month
> or so. The backups and archives go straight to tape, and seem to be
> fine, but then when they try to make a copy storage pool to send the
> data offsite, they find a bad tape, and some of the data can't be read.
> With backups this is not too critical, since usually the original is
> still there, and the next backup picks it up once the bad tape is
> deleted.
> But with the archives, the goal is to be able to delete the original
>
> copy as soon as the archive gets done. The only way I can think of to
> satisfactorily handle this is to archive the file, then wait a couple
> days, and then from a script figure out if a certain file has been
> archived, and also that the copy storage pool copy has also been
> successfully made. This proves at least that the first copy was a good
> one, otherwise the backup storage pool would have failed. Once the
> script determines that there are two copies of the archive, then it is
> considered safe to delete the original.
> Does anybody already have a script that does something like this?
> Is is hard to find out if a certain file has made it to the copy storage
>
> pool?
>
> Thanks for any suggestions.
> John Schneider
>
> ***********************************************************************
> * John D. Schneider Email: jdschn AT attglobal DOT net * Phone: 636-349-4556
> * Lowery Systems, Inc.
> * 1329 Horan Disclaimer: Opinions expressed here are
> * Fenton, MO 63026 mine and mine alone.
> ***********************************************************************
|
