Jeff,
It looks like you forgot to specify the correct
option file on the launch of the GUI. You are specifying the
the correct SQL Server instance... but you also need to
tell Data Protecion for SQL what TSM API options file to use
(which tells it which NODENAME to use):
For instance 1:
TDPSQL /sqlserver=serverx\instance1
/tsmoptfile=c:\tsm\tdpsql\tdpnode1.opt
For instance 2:
TDPSQL /sqlserver=serverx\instance2
/tsmoptfile=c:\tsm\tdpsql\tdpnode2.opt
Thanks,
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/11/2005
09:36:36 AM:
> Firstly, i apologise for initially posting this without a subject line!
> (untitled). So......
>
> Hi,
>
> I have an interesting TDP for SQL problem. Similar issues have been
> addressed many times on the forum, but this is a bit different, i think.
>
> I have:
> Windows server running multiple (x2) SQL server instances
> SQL server called SERVERX
> One instance called INSTANCE1 and the other called INSTANCE2
> TDP
> TSM 5.2.2 server on Z/os 1.5
>
> My configuration:
> I have defined two TDP nodes, i.e. TDPNODE1 and TDPNODE2
> Two DSM.OPT files (TDPNODE1.opt and TDPNODE2.opt) with appropraite node
> names
> Command files (one for log, one for incremental and one for full
backups).
> This is the contents of the LOG command file:
>
> @ECHO OFF
> set sql_dir="C:\Tsm\TDPSql"
> cd /d %sql_dir%
> echo Current date is:>> C:\TSM\tdpsql\logs\sqlbkup.log
> date /t < NUL >> C:\TSM\tdpsql\logs\sqlbkup.log
> echo Current time is:>> C:\TSM\tdpsql\logs\sqlbkup.log
> time /t < NUL >> C:\TSM\tdpsql\logs\sqlbkup.log
> start /b /wait tdpsqlc backup * log
/tsmoptfile=c:\tsm\tdpsql\tdpnode1.opt
> /logfile=c:\tsm\tdpsql\logs\sqlbkup.log
> start /b tdpsqlc backup * log /tsmoptfile=c:\tsm\tdpsql\tdpnode2.opt
> /logfile=c:\tsm\tdpsql\logs\sqlbkup.log /sqlserver=serverx\instance2
>
> Scheduled service
> TSM schedule with OBJECTS field using a command file on the windows
server
> I backup logs, daily incr and full weekly
>
>
> This configuration works just fine. I get two filespaces for each
nodename
> (meta and data for each).
> Node name is TDPNODE1
> Filespace name of SERVERX\TDPNODE1\meta\0000
> Filespace name of SERVERX\TDPNODE1\data\0001
> and
> Node name is TDPNODE2
> Filespace name of SERVERX\TDPNODE2\meta\0000
> Filespace name of SERVERX\TDPNODE2\data\0001
>
> My problem?
> Running via the schedule is good. The backups run and are written to the
> correct filespaces.
>
> If i run a backup for TDPNODE1 from the GUI, this works fine.
> But, if i run a backup for TDPNODE2 from the GUI, it creates filespaces
> with TDPNODE1 as the node name but filespace names of
> SERVERX\TDPNODE2\meta\0000 and SERVERX\TDPNODE2\data\0001, and
increments
> the fsid count.
>
> So, the problem only occurs at the GUI. Yes, i have followed the red
book
> where it states clearly that to use the GUI for operations of another
SQL
> server instance, create a shortcut to tdpsql.exe and specify another
> instance:
> /sqlserver=server_instance_name.
>
> I can get by because the normal method of backup, via the schedules,
works
> good. But if the DBA decides to do a manual/GUI backup, the data is
written
> to a different filespace.
>
> I noted Del's comments last month that perhaps some subscribers on the
> list will share experiences of their environment, so i though i'd ask
the
> question.
>
> Any thoughts?
>
>
> Jeff White
>
>
>
>
*************************************************************************
>
> This e-mail may contain confidential information or be privileged.
> It is intended to be read and used only by the named recipient(s).
> If you are not the intended recipient(s) please notify us
> immediately so that we can make arrangements for its return: you
> should not disclose the contents of this e-mail to any other person,
> or take any copies. Unless stated otherwise by an authorised
> individual, nothing contained in this e-mail is intended to create
> binding legal obligations between us and opinions expressed are
> those of the individual author.
>
> The CIS marketing group, which is regulated for Investment Business
> by the Financial Services Authority, includes:
> Co-operative Insurance Society Limited Registered in England number
> 3615R - for life assurance and pensions
> CIS Unit Managers Limited Registered in England and Wales number
> 2369965 - for unit trusts and PEPs
> CIS Policyholder Services Limited Registered in England and Wales
> number 3390839 - for ISAs and investment products bearing the CIS name
> Registered offices: Miller Street, Manchester M60 0AL Telephone
> 0161-832-8686 Internet http://www.cis.co.uk E-mail cis AT cis.co DOT uk
>
> CIS Deposit and Instant Access Savings Accounts are held with The
> Co-operative Bank p.l.c., registered in England and Wales number
> 990937, P.O. Box 101, 1 Balloon Street, Manchester M60 4EP, and
> administered by CIS Policyholder Services Limited as agent of the Bank.
>
> CIS is a member of the General Insurance Standards Council
>
> CIS & the CIS logo (R) Co-operative Insurance Society Limited
>
>
********************************************************************************
|
