TSM TDP for SQL

Question

TSM TDP for SQL

paul Stapleton

SSC-Addicted

Points: 472
More actions
December 14, 2004 at 8:11 am

#109347

Hi
i am trying to backup a SQL database that is on a non standard port, i have many other DB's backing up using a standard Radia delivered SQL agent, they all seem to backup fine and have no trouble at all (they are all on SQL port 1433 the standard one).

This lone server has been set up by a different internal group and is using a non standard SQL port, nothing else seems to be different but the TDP is unable to back it up, I can only assume that this is the problem and i am guessing, anyone know if this sounds as if i am on the right lines and or how to alter the TDP to look for the DB on the right port?

Any help on this would be appreciated

Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Steve Jones - SSC Editor SSC Guru Points: 736455 More actions · Answer 1

Does Veritas not have a solution? They should connect by instance name, where the ports are resolved by querying 1434 for the port of that instance.

Any reason you don't want to backup to disk and then grab thsoe files with the TSM?

Jason Hall Hall of Fame Points: 3906 More actions · Answer 2

Don't you specify port number in the .opt file that TDP uses. I think there is a *.opt file that includes connection strings used to specify how the client connects to the server.

I may be wrong on this however so please correct me if I am wrong.

sa24 SSCrazy Eights Points: 8027 More actions · Answer 3

You can use the command below. Specify the instancename for the /sqlserver parameter.

C:\Progra~1\Tivoli\TSM\TDPSql\tdpsqlc backup master full /sqlauth=int /tsmoptfile=C:\Progra~1\Tivoli\TSM\TDPSql\dsm.opt /sqlserver=servername /logfile=C:\Progra~1\Tivoli\TSM\TDPSql\sqllog_full_System.log

If you use GUI, change the value of parameter servername to the instance name i.e. servername\instance_name in tdpsql.cfg file

paul Stapleton SSC-Addicted Points: 472 More actions · Answer 4

All

thanks for your resplies we have now tracked down the problem and i have added it below, It turned out to be something other than the port.

Thanks for your help though

The reason that the SQLTDP was not connecting to the SQL server is that the default instance of SQL was not standard.

The standard default instance name for is the server name i.e servername, in this case the default instance is called servername\radia

The following entries have been added to the tdpsql.cfg file and now the backups are working

FROMSQLserver servername\radia

SQLSERVer servername\radia