I used it for a customer who was implementing remote fibre connections to
tape. (This was in a campus environment, so the fibre was less than 25Km,
but had to go across a bridge connector of some sort.) We wanted a way to
prove that it was working OK, so I turned on CRC check for the remote tapes,
which in this case was the copy storage pool.
Audit now has a nice parm where you can say audit all volumes "written since
timestamp". So every morning the copy pool tapes got created, and every
afternoon an admin schedule ran audits against the ones created in the last
24 hours.
This wasn't a huge environment, and I didn't monitor the DB closely. But I
didn't notice any impact on the DB size. And it's certainly easy to
implement.
W
On Fri, Jul 31, 2009 at 3:21 PM, Skylar Thompson
<skylar2 AT u.washington DOT edu>wrote:
> Wanda Prather wrote:
> > My understanding of the function is that if you turn on CRCDATA=YES, TSM
> > creates the checksum and saves it in the DB. To detect a problem, you
> then
> > need to run an AUDIT on the volumes.
>
> Interesting. Do you know the impact on DB size that it has?
>
> --
> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S048, (206)-685-7354
> -- University of Washington School of Medicine
>
|
