[Amit Bansal]

OCR and Voting Disk are critical components for Oracle RAC. There are scenario’s where it can be lost. e.g Volume containing them is overwritten or somebody accidently deletes the file. Fortunately there are steps to restore them. Starting 11gR2, Oracle automatically takes backup of Voting disk too in OCR backups. Below steps list down the exact procedure for performing the restore

Step 1: Identify the OCR backup location. ocrconfig -showbackup would provide the location of the backup. Depending on what is the master node, you should find the backup on one of the nodes on cluster. Default location is grid_home/cdata/cluster_name

Step 2: Identify which backup to restore. There is weekly backup, daily backup and 3 hourly backup’s which are preserved. You should identify the file which contain’s the latest ocr changes i.e if you modified db service,instance using srvctl or added a node. We are using weekly backup as no changes were made to the system

Step 3: Ensure that CRS is stopped on all nodes and restore the backup

[root@proddb-001 ]# ocrconfig -restore week.ocr 

Step 4: Start the CRS in exclusive mode

[root@proddb-001 ]#  crsctl start crs -excl
CRS-4123: Oracle High Availability Services has been started.
CRS-2672: Attempting to start 'ora.mdnsd' on 'proddb-001'
CRS-2676: Start of 'ora.mdnsd' on 'proddb-001' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'proddb-001'
CRS-2676: Start of 'ora.gpnpd' on 'proddb-001' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'proddb-001'
CRS-2672: Attempting to start 'ora.gipcd' on 'proddb-001'
CRS-2676: Start of 'ora.cssdmonitor' on 'proddb-001' succeeded
CRS-2676: Start of 'ora.gipcd' on 'proddb-001' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'proddb-001'
CRS-2672: Attempting to start 'ora.diskmon' on 'proddb-001'
CRS-2676: Start of 'ora.diskmon' on 'proddb-001' succeeded
CRS-2676: Start of 'ora.cssd' on 'proddb-001' succeeded
CRS-2672: Attempting to start 'ora.ctssd' on 'proddb-001'
CRS-2676: Start of 'ora.ctssd' on 'proddb-001' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'proddb-001'
CRS-2676: Start of 'ora.crsd' on 'proddb-001' succeeded

We can verify that no votingdisk is present

[root@proddb-001 ]# crsctl query css votedisk
Located 0 voting disk(s).

Step 5: Add the voting disk and provide the location

[root@proddb-001 cludata]# crsctl add css votedisk /u05/cludata/cssfile
Now formatting voting disk: /u05/cludata/cssfile.
CRS-4603: Successful addition of voting disk /u05/cludata/cssfile.
[root@proddb-001 cludata]# crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   77de89dc89fe4fb3bfb87e5a33237312 (/u05/cludata/cssfile) []
Located 1 voting disk(s).

Step 6: Stop the crs using -f option

[root@proddb-001 cludata]# crsctl stop crs -f
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'proddb-001'
CRS-2673: Attempting to stop 'ora.crsd' on 'proddb-001'
CRS-2677: Stop of 'ora.crsd' on 'proddb-001' succeeded
CRS-2673: Attempting to stop 'ora.mdnsd' on 'proddb-001'
CRS-2673: Attempting to stop 'ora.ctssd' on 'proddb-001'
CRS-2677: Stop of 'ora.mdnsd' on 'proddb-001' succeeded
CRS-2677: Stop of 'ora.ctssd' on 'proddb-001' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'proddb-001'
CRS-2677: Stop of 'ora.cssd' on 'proddb-001' succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'proddb-001'
CRS-2677: Stop of 'ora.gipcd' on 'proddb-001' succeeded
CRS-2673: Attempting to stop 'ora.gpnpd' on 'proddb-001'
CRS-2677: Stop of 'ora.gpnpd' on 'proddb-001' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'proddb-001' has completed
CRS-4133: Oracle High Availability Services has been stopped.

Step 7: Start the crs normally on all nodes.

crsctl start crs >/pre>

[Author]

Posts