[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference chefs::ms-exchange

Title:Microsoft Exchange Server
Notice:
Moderator:FLASK2::SYSTEM
Created:Fri Feb 17 1995
Last Modified:Thu Jun 05 1997
Last Successful Update:Thu Jun 05 1997
Number of topics:1099
Total number of notes:5174

1085.0. "Cluster - Services do not start" by MUDIS3::FISCAL (A VAX, A VAX, my kingdom for a VAX) Wed May 28 1997 13:00

    Hi
    despite warnings not to start another Cluster note (607.1)
    I do as my previous note (in 689) remained unanswered. So here I go again:
     
    okay we are in a situation where the customer has non-cluster-aware
    Exchange installed on his cluster BDC node.
    After restart the services do not start automatically - they have
    to be started manually.
    What has to be done to make automatic start permanent?
    regards
    Artur
                                        
T.RTitleUserPersonal
Name
DateLines
1085.1BUSY::SLABAudiophiles do it 'til it hertz!Wed May 28 1997 21:084
    
    	Well, would it have been possible to use the handy yet seldom-used
    	REPLY command instead of the ever-popular WRITE COMMAND?
    
1085.2Exchange - Starting It on a ClusterNQOS01::16.81.32.132::ATKINSatkinss@mail.dec.comFri May 30 1997 20:3619
I have not tested this with Exchange but I think what you are seeing is the 
disks are not online when Exchange tries to start the services. You should 
create a script that starts the services and put that in the failover group 
that the exchange database and files live on.  Set your services to Manual.

For example 

NET START <Servicename>

Thanks,
Steve

P.S. This by no means addresses the real issue of being able to fail over 
Exchange on a Cluster.  MS says 24x7 availibilty on their WEB page. Meaning 
you don't have to stop the Exchange server to do backups. This thinking and 
marketing hype concerns me and I wonder if they understand what 24X7 really 
means.