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.
On Fri, Jul 31, 2009 at 2:52 PM, Skylar Thompson <[email protected]>wrote: > Michael Glad wrote: > > A quick question: does TSM 5.5.x checksum data in sequential disk > > storage pools > > e.g by storing a file checksum either in the database or on-disk thereby > > allowing for the > > detection of any silent data corruption caused by os/hw issues? > > Not by default, but you can set CRCDATA=YES for any given storage pool. > > -- > -- Skylar Thompson ([email protected]) > -- Genome Sciences Department, System Administrator > -- Foege Building S048, (206)-685-7354 > -- University of Washington School of Medicine >
