Imtiyaz

It may not be relevant in your case, but the gotcha we came across when
trying to run TSM B/A Client backups concurrently with Replication Manager
 snapshots was the following.

TSM backups of local disks were performed using VSS for open-file support.
Left to it's own devices, VSS was using the SAN disk for the shadow
storage as it was the one with the most free space. Because it also uses
VSS, when RM came to snap the SAN disk, it failed due to the presence of
the shadow storage for the C: and D: drive backups.

The solution was relatively straight-forward - we simply defined
shadowstroage associations for the local disks to ensure that the shadow
storage for the TSM backups remained on local disk:

vssadmin add shadowstorage /for=c: /on=d:
vssadmin add shadowstorage /for=d: /on=d:

Regards
Neil Schofield
Infrastructure Platform Technologies Manager
Yorkshire Water

-----------------------------------------
Find out how our new character Numptee is causing all sorts of
problems by putting the wrong things down his toilet and drains -
check out his videos and look at what you can do to help keep your
drains running free.

Visit http://www.yorkshirewater.com/binit

The information in this e-mail is confidential and may also be
legally privileged. The contents are intended for recipient only
and are subject to the legal notice available at
http://www.keldagroup.com/email.htm Yorkshire Water Services
Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682