Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Sql\s+Agent\s+2000\s+and\s+TDP\s+2\.2\s+for\s+SQL\s+for\s+a\s+cluster\s+configuration\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Sql\s+Agent\s+2000\s+and\s+TDP\s+2\.2\s+for\s+SQL\s+for\s+a\s+cluster\s+configuration\.\s*$/: 2 ]

Total 2 documents matching your query.

1. Sql Agent 2000 and TDP 2.2 for SQL for a cluster configuration. (score: 1): Author: Bruce Lowrie <b.e.lowrie AT DOWCORNING DOT COM>; Date: Fri, 8 Feb 2002 14:25:47 -0500; My SQL expert is having an issue with the SQL Agent and TDP for SQL in a Windows 2000 clustered environment using MSSQL 2000 . When you run a backup from the SQL agent the DSM.OPT file must have the; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-02/msg00559.html (12,118 bytes)
2. Re: Sql Agent 2000 and TDP 2.2 for SQL for a cluster configuration. (score: 1): Author: Del Hoobler <hoobler AT US.IBM DOT COM>; Date: Fri, 8 Feb 2002 15:06:52 -0500; backup When running this in a cluster, you should be using the exact same NODENAME in the dsm.opt file for TDP for SQL CLI or GUI. If you use different NODENAMEs the backups will be going to differe; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-02/msg00576.html (11,772 bytes)

Current List: 1 - 2
Page: [1]