Computer Associates ARB6002700WF0. ..... Disaster Recovery Guide - Page 101

BrightStor ARCserve Backup., Method 2

Page 101 highlights

Method 2 Recovering from a Cluster Failure 6. Recreate and format the old partition layout according to your disaster recovery on a cluster checklist. Reassign old drive letters and volume labels according to your checklist. 7. Restore all shared disk partitions by performing a whole volume restore using BrightStor ARCserve Backup. 8. Run the caclurst.exe utility to load the cluster database from the following: %windir%\clusbkup caclurst.exe is available from the BrightStor ARCserve Backup home page. caclurst /s c:\winnt\clusbkup /q Q: 9. Stop the cluster service. 10. Reboot the primary server. 11. Verify that cluster services are now running properly on the primary node. 12. Start the secondary node. Your cluster should now be back online. 1. Stop cluster services on the secondary node. 2. Shut down the secondary node. 3. If the cluster quorum disk must be replaced with good disks, shut down primary node. Replace the bad disks. 4. Restart the primary node. 5. Have your checklist handy. At this point the cluster service startup fails. 6. To start the cluster service on primary node, enter: \windir%\cluster\clussvc -debug -noquorumlogging The cluster shared disk is accessible. 7. Write back the quorum disk signature by running dumpcfg.exe -s [disk signature] 8. Restore the lost shared disk using BrightStor ARCserve Backup. Note: You can run the following command to recreate the quorum log if no backup of quorum disk log is available: %windir%\cluster\clussvc -debug -resetquorumlog 9. Restart start the cluster service on the primary node using the Service Control Manager. 10. Start the secondary node. Your cluster should now be back online. Recovering a Cluster B-11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127

Recovering from a Cluster Failure
Recovering a Cluster
B–11
6.
Recreate and format the old partition layout according to your disaster
recovery on a cluster checklist. Reassign old drive letters and volume labels
according to your checklist.
7.
Restore all shared disk partitions by performing a whole volume restore using
BrightStor ARCserve Backup.
8.
Run the caclurst.exe utility to load the cluster database from the following:
%windir%\clusbkup
caclurst.exe is available from the BrightStor ARCserve Backup home page.
caclurst /s c:\winnt\clusbkup /q Q:
9.
Stop the cluster service.
10.
Reboot the primary server.
11.
Verify that cluster services are now running properly on the primary node.
12.
Start the secondary node. Your cluster should now be back online.
Method 2
1.
Stop cluster services on the secondary node.
2.
Shut down the secondary node.
3.
If the cluster quorum disk must be replaced with good disks, shut down
primary node. Replace the bad disks.
4.
Restart the primary node.
5.
Have your checklist handy. At this point the cluster service startup fails.
6.
To start the cluster service on primary node, enter:
\windir%\cluster\clussvc -debug -noquorumlogging
The cluster shared disk is accessible.
7.
Write back the quorum disk signature by running dumpcfg.exe –s [disk
signature]
8.
Restore the lost shared disk using BrightStor ARCserve Backup.
Note:
You can run the following command to recreate the quorum log if no
backup of quorum disk log is available:
%windir%\cluster\clussvc -debug -resetquorumlog
9.
Restart start the cluster service on the primary node using the Service Control
Manager.
10.
Start the secondary node. Your cluster should now be back online.