Chris,

I remember you asking about this last year as well.
You are correct that Data Protection for SQL does not have
a "VERIFYONLY" function at this time. To be completely honest
we have only heard this request from one or two customers.

Since it means that you need to read and restore all of the data from the
backup set anyway, many people have decided to just do the actual
restore to an alternate server to do a *real* verification that their
data will restored and actually see it work, versus a message that
says "The backup set is valid."

I encourage you to submit an official requirement through your
IBM representative that you need this function added to Data Protection
for SQL. If the requirement is heard from enough customers, the priority
will rise and it has a much better chance of being implemented.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/31/2004
11:27:52 AM:

> As long as I'm posting, here's a question for Del.  There is one glaring
> omission in the TDP client for SQL Server, namely the lack of any
command
> that would expose Microsoft's RESTORE VERIFYONLY command.  This command
> saves tons of time in verifying backups, since it greatly simplifies the
> process.  Are there any plans by IBM to build something into the TDP
Client
> for SQL Server that will let us run this command?  It really doesn't
seem
> like it should be very hard to do, and it's a big enough omission that
> initially we considered scrapping TDP for SQL because of it - and we
still
> consider this from time to time.  It's really an integral part of the
T-SQL
> backup and restore API.
>
> Thanks for any response,
> Chris