Has anyone managed to completely recover a 2008 / 2008 R2 Failover Cluster.
I'm talking about a whole environment recovery as in, a truck has just crashed through your computer room wall and taken out your cluster nodes (it's not personally happened to me, but , hey, you never know).
A lot of docs focus on recovery of a single node which is fine but I am having trouble recovering a 2-node cluster.
My process is as follows:
- On new node hardware, install vanilla operating system, service pack, etc.
- Create any local storage
- Install correct TSM BA Client (6.2.3.1)
- When all OK, restore system drive (C:\) and local storage (D:\)
So far, so good.....
The problem comes with the whole SystemState restore in that it won’t proceed unless the Cluster Service has started.
I have not joined my vanilla nodes to the domain or installed Failover Cluster (I never needed to do this on 2000/2003 clusters)
I can restore SystemState Bootable to get the OS back but the cluster service will not start because the CLUSDB file (part of SystemState Cluster Database) has not been restored and therefore not present.
Does anyone have any experience of this and is there a workaround.
Many Thanx
P.S. The only workaround I have is to shut down the Cluster Service on the inactive node, copy the CLUSDB file to an empty C:\ drive folder and restart the cluster service. This file can be successfully backed up during the data backup and restored during the data restore. This can then be used once the SystemState bootable restore has completed.
The only problem with this solution is that I don’t want to take my cluster service offline especially if it’s an Active-Active cluster.
I'm talking about a whole environment recovery as in, a truck has just crashed through your computer room wall and taken out your cluster nodes (it's not personally happened to me, but , hey, you never know).
A lot of docs focus on recovery of a single node which is fine but I am having trouble recovering a 2-node cluster.
My process is as follows:
- On new node hardware, install vanilla operating system, service pack, etc.
- Create any local storage
- Install correct TSM BA Client (6.2.3.1)
- When all OK, restore system drive (C:\) and local storage (D:\)
So far, so good.....
The problem comes with the whole SystemState restore in that it won’t proceed unless the Cluster Service has started.
I have not joined my vanilla nodes to the domain or installed Failover Cluster (I never needed to do this on 2000/2003 clusters)
I can restore SystemState Bootable to get the OS back but the cluster service will not start because the CLUSDB file (part of SystemState Cluster Database) has not been restored and therefore not present.
Does anyone have any experience of this and is there a workaround.
Many Thanx
P.S. The only workaround I have is to shut down the Cluster Service on the inactive node, copy the CLUSDB file to an empty C:\ drive folder and restart the cluster service. This file can be successfully backed up during the data backup and restored during the data restore. This can then be used once the SystemState bootable restore has completed.
The only problem with this solution is that I don’t want to take my cluster service offline especially if it’s an Active-Active cluster.