TDP install error on SQL Server

jcosu86

ADSM.ORG Member
Joined
Jul 16, 2015
Messages
42
Reaction score
0
Points
0
PREDATAR Control23

I am trying to install and configure TSM/TDP for Microsoft SQL Server and am not able to get past an error.

TSM/TDP version: 7.1.2
SQL Server version: 2008 R2

The error is :

ACO5098E Error obtaining VSS information from Local DSMAgent Node: 'sql01dev.ode.state.oh.us'.
ANS1033E (RC-53) An invalid TCP/IP address was specified.

dsm.opt:

NODENAME sql01dev.ode.state.oh.us
TCPSERVERADDRESS soctsm4.odn.state.oh.us
TCPCLIENTADDRESS 208.108.224.108
TCPCLIENTPORT 1501
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
.
. (removed multiple "EXCLUDE" lines)
.
PASSWORDAccess generate
TCPPort 1500
HTTPport 1581
MANAGEDSERVICES WEBCLIENT SCHEDULE
WEBPORTS 1582 1583

The TDP SQL Client acceptor service is running and listening. There are no firewall issues.

I can't find any solution to the error anywhere that helps.

Thanks.
 
PREDATAR Control23

I can ping and telnet to that address and its IP. They can telnet to mine. There doesn't appear to be any issues there. Where is the DSMAgent node defined?
 
PREDATAR Control23

Are you able to login to the TSM server from the node using the CLI?

What does the dsmerror.log file records as an error?
 
PREDATAR Control23

I can log on to the TSM server using the TSM backup-archive client and copy os files. I cannot use TDP with SQL Server. My network and server admins assumed it was a firewall issue, so they opened ports. The new error is:

ACO5098E Error obtaining VSS information from Local DSMAgent Node: 'sql01dev.ode.state.oh.us'.
ANS1532E (RC5722) Proxy Rejected: Proxy authority has not been granted to this node.
Completed


My network admin assures me that the correct proxy authority has been granted to the server.

Contents of dsmerror.log is exactly what I received when trying the backup:

10/13/2015 15:07:24 ANS1532E Proxy Rejected: Proxy authority has not been granted to this node.
 
PREDATAR Control23

Proxy authority is NOT a network issue but a TSM server issue. Grant proxy authority between the BA and SQL client which is generally 2 different node names.
 
PREDATAR Control23

We set up our Oracle database TSM/TDP backup with no problem. The TSM node name is the server name and the TDP is the server name with an "_ora". Where should this be configured in SQLServer? I know in a dsm.opt file, but I'm not sure which one.
 
PREDATAR Control23

I guess I shouldn't call him a "network" admin, he's more of the TSM Admin.
 
PREDATAR Control23

There are 2 OPT files in a BA and TDP for SQL setup. the BA is in ..\baclient\dsm.opt, the TDP for SQl is in ..\tdpsql\dsm.opt.

These files should have the corresponding node names.
 
PREDATAR Control23

Oracle seems pretty straightforward.

For TSM we have it defined as (examples) "prod" and "TSM"
For TDP we have it defined as "prod_ora" and "TSM_ora"

I am not sure what the configuration for sql should be.

There are "dsm.opt" files as well as a "custom.opt". All parameters currently configured in those files were given to us by the TSM admins. I"m not sure they are right.
 
PREDATAR Control23

Ok. In Oracle, we have the dsm.opt in ba/bin defined. There is also dsm.sys. There are dsm.opt and dsm.sys files in api/bin as well. In SQL there is nothing in the api folder, the baclient has a dsm.opt file - should that be sql01dev or sql01dev_sql? The same question goes for tsm\tsm\tdpsql. There is also a tdpsql.cfg file that seems to be in play.

Also, Oracle has the TSM server identified by soctsm4 and prod in api and in ba it is soctsm4_ora and prod_ora. Does that make sense?
 
PREDATAR Control23

Have you read the link I posted above?

Windows only uses *.opt files and does not work with multi stanza configuration files like *.sys.

Also, node names for the BA and TDP should be different: abc and abc_sql is one example. If you have sql01dev.ode.state.oh.us for the BA node name (which is fully qualified name), I suggest you simplify by using just sql01dev and sql01dev_sql for the BA and TDP node names.

Here is an example of how the TDP dsm.opt looks like:

Code:
*======================================================================*
*                                                                      *
* IBM Tivoli Storage Manager for Databases                             *
*                                                                      *
* Data Protection for Microsoft SQL Server                             *
*                                                                      *
* Sample Options File                                                  *
*                                                                      *
*======================================================================*

CLUSTERnode       NO
PASSWORDAccess    Generate

*======================================================================*
* TCP/IP Communication Options                                         *
*======================================================================*
COMMMethod        TCPip
TCPServeraddress  TSM_Server_name
TCPPort           1500
TCPWindowsize     63
TCPBuffSize       32

*======================================================================*
* Named Pipes Communication Options                                    *
*======================================================================*
*COMMMethod       NAMEdpipe
*NAMedpipename      \\.\pipe\tsmpipe

*======================================================================*
* - Compression Options                                                *
*                                                                      *
*   Use the "COMPRESSION" option to compress the data before sending   *
*   it to the IBM Tivoli Storage Manager server. Use the               *
*   "COMPRESSALWAYS" option to specify whether to continue compressing *
*   the data if it grows during compression.                           *
*                                                                      *
*======================================================================*
COMPRESSIon       NO
*COMPRESSAlways    NO

*======================================================================*
*                                                                      *
* - Scheduling Options                                                 *
*                                                                      *
*   The default scheduling mode is the client polling method.          *
*   To use server prompted scheduling, you must be sure to use a tcp   *
*   client port different than the one used by the regular backup      *
*   client.                                                            *
*                                                                      *
*======================================================================*
SCHEDMODE             Polling
*SCHEDLOGRetention     14
*SCHEDMODE             Prompted
*TCPCLIENTADDRESS      yy.yy.yy.yy
*TCPCLIENTPORT         1502

*======================================================================*
* Include/Exclude Processing                                           *
*                                                                      *
* For a more complete description of include/exclude processing refer  *
* to the Data Protection for Microsoft SQL Server Installation and     *
* User's Guide.                                                        *
*======================================================================*

*======================================================================*
* The following include statements assign all meta objects to          *
* management class SqlDbMetaMgmtClass and all data objects to          *
* SqlDbDataMgmtClass                                                   *
*======================================================================*
*INCLUDE "\...\meta\...\*"     SqlDbMetaMgmtClass
*INCLUDE "\...\data\...\*"     SqlDbDataMgmtClass

*======================================================================*
* The following include statements assign all log meta objects to      *
* management class SqlLogMetaMgmtClass and all log data objects to     *
* SqlLogDataMgmtClass                                                  *
*======================================================================*
*INCLUDE "\...\meta\...\log*"  SqlLogMetaMgmtClass
*INCLUDE "\...\data\...\log*"  SqlLogDataMgmtClass

*======================================================================*
* The following exclude statements exclude all log backups for         *
* databases master and msdb                                            *
*======================================================================*
EXCLUDE "\...\master\...\log*"
EXCLUDE "\...\msdb\...\log*"                                                       
EXCLUDE "\...\model\...\log*"
EXCLUDE "\...\distribution\...\log*"
EXCLUDE "\...\dba\...\log*"


*======================================================================*
* The following exclude statement excludes the "db1" database          *
* from being compressed (if compression is enabled for backups.)       *
*======================================================================*
*EXCLUDE.COMPRESSION "\...\db1\...\*"

NOdename sql01dev_sql
 
PREDATAR Control23

Yes, I read the link - it helped me understand more what is going on. I used your dsm.opt as an example and rebuilt the dsm.opt on our sql server. Interesting new error:

Volume Shadow Copy Service (VSS) Information
--------------------------------------------

ACO5098E Error obtaining VSS information from Local DSMAgent Node: 'sql01dev_sql.ode.state.oh.us'.
ANS1353E (RC53) Session rejected: Unknown or incorrect user ID entered

Completed

I think we may be making progress. I know you use "tdpoconf password" to set the password in oracle. How is it done in SQL?

OK - dsmutil. Tryihng it now.
 
PREDATAR Control23

I think we may be making progress. I know you use "tdpoconf password" to set the password in oracle. How is it done in SQL?

OK - dsmcutil. Trying it now.

Nope. dsmc -optfile=<path_to_TDP_for_SQL_OPT_file>

system will prompt you for userid and password IF done for the first time. If password access is set to generate, next time access will not require to enter user ID and password.
 
PREDATAR Control23

I get:
ANS1353E (RC53) Session rejected: Unknown or incorrect user ID entered

No matter what I put in (sql01dev, sql01dev_sql, fully qualified for both...)
 
PREDATAR Control23

ok, I can now connect to tsm now (changed the NOdename to sql01dev_sql.ode.state.oh.us in the dsm.opt file in tdpsql). But still can't connect to TDP
 
PREDATAR Control23

ok, I can now connect to tsm now (changed the NOdename to sql01dev_sql.ode.state.oh.us in the dsm.opt file in tdpsql). But still can't connect to TDP

Look at the error logs to get more insight on what is happening. You can't troubleshoot without knowing what is going on.
 
Top