ADSM-L

Re: Verification

2001-08-23 06:04:57
Subject: Re: Verification
From: "Warren, Matthew James" <matthewjames.warren AT EDS DOT COM>
Date: Thu, 23 Aug 2001 11:06:17 +0100
Do they really want to do this? If they do not trust that the file is being
backed up correctly by TSM, will they trust the fact TSM say's it has been,
even if it could verify the file?

The only way I can think of actually getting a byte by byte verificatiuon
that a file has been stored correctly by TSM is to do a restore of the file
and attempt to use it. If it works, the backup was fine.

Are they worried about things like copy serialisation? Are there files that
they think may not backup correctly for a particular reason?



_______________________________
Matthew Warren.          GZPTXW
MatthewJames.Warren AT eds DOT com <mailto:MatthewJames.Warren AT eds DOT com>
EDS Core Infrastructure,
UK Technical Services Group,
Wavendon Tower, Milton Keynes.
_______________________________


> -----Original Message-----
> From: Matthew Large [mailto:matthew.large AT PHOENIXSM DOT COM]
> Sent: 23 August 2001 09:47
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Verification
>
>
> Hi All,
>
> I have been asked by a customer if it is possible for TSM to
> verify and
> confirm the existence of the copy of the data on the
> tape/disk, against the
> actual file. I really think he means for TSM to re-read the
> file it just
> wrote and compare it with the file on the client. I have
> explained that we
> check all the characteristics of the file at the end of the
> backup, but he
> wants a full verification. Can anyone offer any more than I?
>
> Cheers all,
> Matthew Large
>
>
> http://www.phoenixitgroup.com
> ******************Internet Email Confidentiality
> Footer*******************
>
> Phoenix IT Group Limited is registered in England and Wales
> under company
> number 3476115.  Registered Office: Technology House,
> Hunsbury Hill Avenue,
> Northampton, NN4 8QS
>
> Opinions, conclusions and other information in this message
> that do not
> relate to the official business of our firm shall be
> understood as neither
> given nor endorsed by it.
>
> No contracts may be concluded on behalf of our firm by means of email
> communications.
>
> Confidentiality: Confidential information may be contained in
> this message.
> If you are not the recipient indicated (or responsible for
> delivery of the
> message to such person), you may not take any action based on
> it, nor should
> you copy or show this to anyone; please reply to this email
> and highlight
> the error to the sender, then delete the message from your system.
>
> Monitoring of Messages: Please note that we reserve the right
> to monitor and
> intercept emails sent and received on our network.
> Warning:  Internet email is not 100% secure. We ask you to
> understand and
> observe this lack of security when emailing us. We do not accept
> responsibility for changes made to this message after it was sent
>
> Viruses: Although we have taken steps to ensure that this
> email and any
> attachments are free from any virus, we advise that in
> keeping with good
> computing practice the recipient should ensure they are
> actually virus free.
>
<Prev in Thread] Current Thread [Next in Thread>