I would like you to check the dsm.sys used to do the backups and the logs
generated for you to have a wider view of the problem. I don't have it at
this time but i'm working to get them.
Int he mean time, here are some other characteristics of the environment:

I'm using the 3.7.1 adsm client level.
The TSM 3.7.1 is running in the same cluster as the client.
There are two groups I want to manage.
    GROUP 1 contains the TSM resources (IP Address, TSM Server Service and
Disk D: where the TSM     server is actually installed) and resources for
other applications. I want to backup this drive D:
    GROUP 2 contains resources for other apps including a drive F: that i'm
interested in backing up.
DOMAIN is set to D:
The schedule fails with 'error opening the object \\cluster_name\d$' and
'Invalid path specification' on the    dsmsched.log.

> Hi Gerardo,
>
> some questions concerning your environment:
>
> 1. At which adsm client level you are working at the moment ( 3.1.0.*
resp.
> 3.7.*.* ) ?
>     In level 3.1.0.7 there were some problems recognizing the shared
> cluster disks from
>     some specific hw.
> 2. What does your option " domain ....." in your BA-Client option file
> exactly look like ?
>      You have to specifiy the UNC - name of the cluster resource, e.g.
> "\\clustername\e$" to
>       get this recognized as a cluster resource during the scheduled
> backup.
>
>
> Mit freundlichen Gr|_en / Best regards
>
> Martin Hansen
> Microsoft Certified Professional ( MCP ) - Systems Engineer
> ===================================================
>
> IBM Global Services
> ITS SD
> AIX Software Support ADSM/TSM
> Email: mhansen AT de.ibm DOT com