Restore Cluster Config / Rollback



Hi,

I'm in a situation whereby a customer needs to rollback their Cluster config
to a previous known good date.

Basically what happened was upon some MS documentation the MS Exchange
System Attendant resource was deleted. Am now unable to reinstall it as a
new resource.

The drives are configured as per required and no other resources are affected.

I'd like to know the steps to restore a cluster. I only have a standard
system state backup (from Netbackup) to restore from.
Should this be ok?
How do I make the cluster restore authoritive for the whole cluster?

If you are unable to comment for Netbackup, please offer the standard
technique for NTBackup as they are probably similar.

TIA

Mark

.



Relevant Pages

  • Re: 2-node cluster wont stop sqlservr.exe during user-initiated failo
    ... Any clues in the cluster host nodes' application event logs? ... Senior Database Administrator ... >I have the following cluster config: ... But when we do a "move group" for the SQL Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: ServiceGuard Question
    ... configuration (it will leave your package cntl/conf files alone - ... cmapplyconf should give no problems. ... > We have just take a node out of cluster. ...
    (comp.sys.hp.hpux)
  • Re: Event ID 4522 After Installation of Exchange 2007 on Cluster N
    ... Cluster Config, Network; where we can specify that the Private NIC's role is ... this is a two node cluster, try starting cluster service on the other ... startup option to start cluster service. ...
    (microsoft.public.exchange.setup)
  • Re: Fulltext failure on a 2 node cluster
    ... No cluster resource for that cluster has shown as failed. ... There are NO error messages in SQL Server or the event log. ... Server full-text search resource online: ...
    (microsoft.public.sqlserver.clustering)
  • Re: How would you configure an N+1 cluster using MS Cluster Servic
    ... In case anyone else stumbles across this problem with the Generic Service ... It is possible to use both the Cluster Administrator and the APIs to ... The only way round this restriction seems to be to write a resource type DLL ... hence prevent multiple failovers to a passive node in an N+1 configuration. ...
    (microsoft.public.windows.server.clustering)