ADSM-L

Re: [ADSM-L] TDP for SQL in a cluster and setting passwords...

2013-09-09 09:04:02
Subject: Re: [ADSM-L] TDP for SQL in a cluster and setting passwords...
From: Rick Adamson <RickAdamson AT BILOHOLDINGS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 9 Sep 2013 13:00:07 +0000
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [208.62.154.89]
x-forefront-prvs: 09645BAC66
x-forefront-antispam-report: 
SFV:NSPM;SFS:(377454003)(189002)(199002)(129404003)(13464003)(77096001)(56816003)(69226001)(15974865002)(80022001)(66066001)(74316001)(74366001)(46102001)(551544002)(19580395003)(19580405001)(83322001)(31966008)(47446002)(51856001)(74662001)(74502001)(83072001)(49866001)(47736001)(50986001)(47976001)(74706001)(4396001)(81342001)(74876001)(81542001)(76482001)(33646001)(81686001)(80976001)(76576001)(76796001)(54316002)(63696002)(76786001)(77982001)(81816001)(59766001)(56776001)(79102001)(65816001)(54356001)(53806001)(24736002)(80792004);DIR:OUT;SFP:;SCL:1;SRVR:BY2PR05MB062;H:BY2PR05MB062.namprd05.prod.outlook.com;CLIP:208.62.154.89;RD:InfoNoRecords;MX:1;A:1;LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: biloholdings.com
X-Barracuda-Connect: 
mail-bl2lp0205.outbound.protection.outlook.com[207.46.163.205]
X-Barracuda-Start-Time: 1378731611
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://148.100.49.27:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at marist.edu
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 
QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.140474
        Rule breakdown below
         pts rule name              description
        ---- ---------------------- 
--------------------------------------------------

Hi Wanda,
When it comes to SQL on a Win2008 server, I use an account that has local a=
dministrator and sysadmin access to SQL, then I disable the UAC for admins =
(User Account Control: Run all administrators in Admin Approval Mode). With=
out this policy change I could not get the services to operate correctly.

Optional, remove logon rights from the account used to manage the service t=
o minimize security risks.

Also, it is my experience that many times it is not acceptable to the busin=
ess to fail the active instance of the cluster over to the passive server t=
o sync the scheduler password. I log into the active machine, install/updat=
e the scheduler service, change the properties so it does not affect the gr=
oup if it fails, then bring it online. If it works successfully I export th=
e password key for the SQL client from the registry, log onto the passive n=
ode, install the service (which will have errors), then import the registry=
 key.=20

Hope this helps....
-Rick Adamson



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Pr=
ather, Wanda
Sent: Sunday, September 08, 2013 11:59 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TDP for SQL in a cluster and setting passwords...

TDP for SQL 6.4, Win2K8, SQL in a 2-node active-passive cluster

TSM scheduler was installed on both nodes of the cluster, made a cluster re=
source, registry key set as per instructions in the TDP for SQL 6.4 user gu=
ide.

Then the nodes were de-registered from TSM.
Now we have to put them back (long story, don't ask).
Nobody knows what the TSM password was, of course.

So I reset the password on the TSM server end.
Now trying to reset it on the nodes, with no success.
I tried using the client setup wizard to change the password on the client =
end; I tried running dsmc sched on the client end and responding to the pro=
mpt, from both the active and passive side.
But the password doesn't get changed, and authentication with the server st=
ill fails with "scheduler needs to prompt for password" when we bring the r=
esource online in cluster manager.

Not sure if I'm suffering from an authority issue, or a clustering issue.
To reset the scheduler password, do I have to first make the scheduler serv=
ice NOT a cluster resource again?

Thanks for any insight...
W

Wanda Prather  |  Senior Technical Specialist  | Wanda.Prather AT icfi DOT com  
| =
 www.icfi.com ICF International  | 401 E. Pratt St, Suite 2214, Baltimore, =
MD 21202 | 410.539.1135 (o)

<Prev in Thread] Current Thread [Next in Thread>