Actually, you should consider using the Exchange Site Services account to
run the schedule;  we had the same problem, went back to the books (via IBM
friend) which reminds you to use the admin account for the db engine - as it
sometimes has special rights that either local system lacks or standard SA
lacks.  Best practices, use an account that is known to and used by dba's to
support the db environment (regardless of which db you're using, they all
have this "problem" in common).  Everything else you say here is great
stuff!

Regards,
Don

Don France

Technical Architect - Unix Engineering/P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph:   (408) 257-3037


 -----Original Message-----
From:   James Thompson [mailto:mezron AT HOTMAIL DOT COM]
Sent:   Thursday, April 19, 2001 10:00 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Can't backup MSCS shared disk using schedule

Have the scheduler service sign on as the account that successfully performs
manual backups.

When using the dsmcutil commands of INSTALL, UPDATE, and UPDATEPW, make sure
you use /clusternode:yes and /clustername:  EVERY time.

Make sure the scheduler service that is backing up the cluster group has an
options file that contains 'clusternode yes' as well.

As a bare minimum you should have to define four scheduler services.  Two on
each node in the cluster.  One for local disk resources and one for cluster
disk resources.

You also need to be using different nodenames for the local and cluster
scheduler services.

James Thompson

p.s. if you are losing you password it is most likely caused by not
specifying clusternode: and clustername: in the dsmcutil command.

>From: Shawn Pritchard Reply-To: "ADSM: Dist Stor Manager" To:
>ADSM-L AT VM.MARIST DOT EDU Subject: Can't backup MSCS shared disk using 
>schedule
>Date: Thu, 19 Apr 2001 11:44:01 -0400
>
>Server: AIX v3.7.3.8 Client: v4.1.2.12
>
>
>The MSCS client is unable to backup his shared disks using the schedule (he
>can back them up manually). It seems that when he starts up the schedule
>service the nodename and password are being deleted from the registry. On
>the NT event log the error message says to use the dsmcutil utility to
>update the node as there's no password. When you check the registry the
>node and password are deleted although they were there before attempting to
>start the service. It shows up on the client as both an authorization and a
>TCPIP problem. When he first installed the client and the schedule services
>his client was experiencing connectivity problems due to a new routing
>configuration. As he couldn't install the clients without connectivity to
>the server, he decided to use the dsmcutil to create the schedules and the
>services. When he experienced the problems that I mentioned, he did a
>complete unistall of the schedule, the services, and the client. He then
>re-booted and re-installed everything, but the results were the same.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com