I'll have to do a similar setup in the near future.

All the BCV volumes will be mounted on the TSM server and then backed up to the 
LTO library. In the dsm.opt client file, the different drives (where the BCV's 
will be mounted) are bound to the correct management class.

What happens if one of the mounts of the BCV volumes fails? Then there is a 
drive specified in the dsm.opt file that doesn't exist. Anybody knows what 
happens in such a case? Can you mount the BCV volumes as a pre-exec command of 
the backup and umount them as a post-exec command of the backup?

Any sharings in the backup of BCV's through TSM are more than welcome.

Thanks,

Kurt
------------------------
     "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote:
------------------------

>We are working on automating the backup of EMC BCV's (3 NT/Oracle hosts)
>which are mounted to a NT server(dedicated to mounting bcv volumes and
>running the TSM backup client).
>
>The overall process includes:
>
>Mount volumes (job dependencies based on successful mounts per host group)
>Run Scheduled TSM backup job
>Unmount volumes
>Notify Application team of successful job for all BCV volumes
>
>So- as we are refining the process, I've started to search for documented
>procedures or best practices for this kind of environment. There is not much
>in terms of Redbooks or whitepapers, so I was wondering if the TSM community
>knows of any good resources--
>
>Thanks for all of your help and input! John
>
>
>
>_________________________________________________________________
>Broadband? Dial-up? Get reliable MSN Internet Access.
>http://resourcecenter.msn.com/access/plans/default.asp
>