TSM 5.3.1.0 compatibility with VCS 4.3???

[Spiff01]

Good day,

wondering if anyone knows if Tivoli Storage Manager 5.3.1.0 is compatible with Veritas Cluster Service 4.3?

Reason I am asking is that we have implemented a few Windows 2003 servers that are using VCS 4.3 and are being backed up by TSM.

The TSM backup client installed on the machines is 5.3.1.0.

Currently what is happening is that we want to have the backups scheduled, but they are failing, so we have to create a TDPSQL job and run it manually to get the backup done.

I have been looking around, but hoping someone here has some experience/knowledge on if they can be used together.

I know the older versions of TSM client cannot see the VCS Clusters.

anyway let me know

Thanks
James

 

[mccleld]

Could you give a little more detail as to why the VCS controlled jobs are failing? Any particular error/issue?

 

[Spiff01]

Actually what is happening now is the TDPSQL jobs are not even running and when we try to manually run it, it is not seeing the virtual instances correctly

Here is our setup
Physical nodes (C:\, system state, etc):
NAMF217119 (DCR)
NAMF217120 (DCR)
NAMF217121 (ACR)
Virtual SQL Servers (TDP SQL):
NAMF217124 (can run on NAMF217119 and NAMF217121)
NAMF217125 (can run on NAMF217120 and NAMF217121)
NAMF217126 (can run on NAMF217120 and NAMF217121)

Example,

NAMF217120 is seeing the virutal instances as local drives

NAMF217119 is seeing the virtual instances as local drives and is not seeing the actual local drive at all - C drive

Now I have taken a look at the DSMSCHED log and the DSMERROR logs (there is to SQLFULL log as it will not run to create the log)
Getting a few ANS1512E, ANS1468E, ANS1228E ANS1802E errors,
I have looked them up not much to them Scheduled failed, processing stops, etc

I guess what I am looking for is a reason to why TSM is reporting VCS nodes incorrectly...
I have a ticket in with TSM support, and Veritas said they are not sure what the issue is...
gotta love it

Thanks in advance
James

 

[comtec17]

This could be a dns issue, have you reviewed the nslookup from each host?

 

[Spiff01]

actually i think we found one of the issues. Our options file seemed to be corrupted/created messy, we have corrected the options files and the regular TSM backups are working - they are seeing the local drives as local drives (seeing C drive as local instead of one of the Virtual instances as local)

Thanks for the assistance

James