Joseph Gishera
asked on
MICROSOFT WINDOWS CLUSTER SHUTDOWN FOR MAINTENANCE - WINDOWS SERVER 2008 R2
Hi,
we have a planned maintenance for our production environment (WINDOWS SERVER 2008 R2) scheduled in a weeks time from the time of this post. Windows cluster is configured for two nodes on an ACTIVE/PASSIVE basis. Going by the company planned maintenance policies all nodes are expected to be shutdown . Oracle database 11gR2 is running on the primary node. Kindly advise on the best procedure to shutdown and startup the cluster after maintenance is completed.
Also do i shutdown the database manually through the 'SHUTDOWN IMMEDIATE' command?
Kind regards.
we have a planned maintenance for our production environment (WINDOWS SERVER 2008 R2) scheduled in a weeks time from the time of this post. Windows cluster is configured for two nodes on an ACTIVE/PASSIVE basis. Going by the company planned maintenance policies all nodes are expected to be shutdown . Oracle database 11gR2 is running on the primary node. Kindly advise on the best procedure to shutdown and startup the cluster after maintenance is completed.
Also do i shutdown the database manually through the 'SHUTDOWN IMMEDIATE' command?
Kind regards.
ASKER
Hi Arnold,
Thank you for the timely response. I was however thinking of using the approach listed below,
1). Open Failover Cluster Manager (CluAdmin.msc)
2). Right-click on the cluster name, select ‘More Actions’, then “Shut Down Cluster…”
3). When prompted if i want to shut down the cluster, i click “Yes”
to shutdown the entire cluster then proceed to shutting down the respective node (I got this idea after more reading) . Also, will this method shutdown down the oracle database services running in the ACTIVE NODE? Kindly advice if this approach is viable for my case of shutting down the entire cluster.
Also please give directions on the right procedure to follow when starting the cluster and database service after the maintenance exercise is completed.
The maintenance is meant for server RAM upgrade and dust blowing as the servers are extremely dusty putting them at risk of failing.
Kind regards.
Thank you for the timely response. I was however thinking of using the approach listed below,
1). Open Failover Cluster Manager (CluAdmin.msc)
2). Right-click on the cluster name, select ‘More Actions’, then “Shut Down Cluster…”
3). When prompted if i want to shut down the cluster, i click “Yes”
to shutdown the entire cluster then proceed to shutting down the respective node (I got this idea after more reading) . Also, will this method shutdown down the oracle database services running in the ACTIVE NODE? Kindly advice if this approach is viable for my case of shutting down the entire cluster.
Also please give directions on the right procedure to follow when starting the cluster and database service after the maintenance exercise is completed.
The maintenance is meant for server RAM upgrade and dust blowing as the servers are extremely dusty putting them at risk of failing.
Kind regards.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hello Arnold,
Cleaning will be done out of place.
I will go for with this - "Option to avoid down time is power off the passive mode, do what needs to be done. Power it back up, failover the cluster, poweroff the new passive node, do what needs to be done, bring backtrack the node, and either failover the cluster back, or let it run as is without actually having any down time. " Its more viable with minimal downtime.
Thanks for coming to my rescue.
Cleaning will be done out of place.
I will go for with this - "Option to avoid down time is power off the passive mode, do what needs to be done. Power it back up, failover the cluster, poweroff the new passive node, do what needs to be done, bring backtrack the node, and either failover the cluster back, or let it run as is without actually having any down time. " Its more viable with minimal downtime.
Thanks for coming to my rescue.
ASKER
Thanks experts. This worked!
No special direction to db shutdown is needed. Deals with if you shutdown the active node,the cluster will failover.
Maintenance window is that to address an issue with the SAN?
Or you are combining the maintenance window with installing updates?