Re: TDP for SQL problem ACO5091E or ACO5422E

We use the /sqlserver parameter.

The complete command we use is:

tdpsqlc backup PRD full /tsmoptfile=dsm.opt /config=tdpsql.cfg

Met vriendelijke groet, with kind regards,

Richard van Denzel
Consultant
IBM CATE, TSM Certified Consultant
____________________________________________________________
Solution Professional Services B.V.
____________________________________________________________
Transistorstraat 167, 1322 CN Almere
Postbus 50044, 1305 AA Almere.

T:   +31 (0)36 880 02 22
F:   +31 (0)36 880 02 44
M:  +31 (0)652 663 978
W:  www.sltngroup.com
E:   rvandenzel AT sltngroup DOT com
____________________________________________________________
Solution Professional Services B.V. is onderdeel van SLTN GROUP
IBM Premier Business Partner
____________________________________________________________




Bill Boyer <bill.boyer AT VERIZON DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05-01-2004 15:41
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TDP for SQL problem ACO5091E or ACO5422E


I believe that for clusters you need to specify the /SQLSERVER= parameter
of
the virtual SQL server name in the cluster. The default is to logon to the
"local" instance, which on a cluster there isn't one.

Bill Boyer
DSS, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Richard van Denzel
Sent: Monday, January 05, 2004 9:24 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TDP for SQL problem ACO5091E or ACO5422E


Hi All,

I have a strange problem with TDP for MS-SQL 5.2.1.0 (running on TSM
Server 5.2.1.3 on Windows 2003 Server).

When I put CLUSTERNode yes in the DSM.OPT I get error ACO5091E, which
basically tells me that I'm using PASSWORDACCESS GENERATE but there is no
password (how come that the normal BA-client is working then?).
When I put CLUSERNode no in the DSM.OPT I get error ACO5422E, telling me
that an ODBC error occurred with MS-SQL (now PASSWORDACCESS GENERATE
works).

The above system is part of an active-passive Microsoft cluster.

On another (non-cluster) system I've got the same software running and
this will backup with the TDP for SQL without problems.

Has anyone got a clue to what is going on? Or perhaps someone has
experienced the same problem and knows a solution for it?

Met vriendelijke groet, with kind regards,

Richard van Denzel
Consultant
IBM CATE, TSM Certified Consultant
____________________________________________________________
Solution Professional Services B.V.
____________________________________________________________
Transistorstraat 167, 1322 CN Almere
Postbus 50044, 1305 AA Almere.

T:   +31 (0)36 880 02 22
F:   +31 (0)36 880 02 44
M:  +31 (0)652 663 978
W:  www.sltngroup.com
E:   rvandenzel AT sltngroup DOT com
____________________________________________________________
Solution Professional Services B.V. is onderdeel van SLTN GROUP
IBM Premier Business Partner
____________________________________________________________