When you change the recovery log size, you must delete the recovery log file. Changing the recovery log size removes the Business Continuity Manager object state information. After the sequencers are started, all systems exist in an Unrecoverable state.
Important: All objects managed by Business Continuity Manager remain in an unsynced state after this process is completed.
- From bcmadmin, change the RecoveryLogSize parameter value to the new size in gigabytes:CONFIG UPDATE SEQUENCER RecoveryLogSize <newSize> REASON 'Increasing recovery log size';
- Retrieve the recovery log file name and path.The default location is /data/recovery.log. The recovery log path is stored in the configuration variable, RecoveryLogPath, and the filename is stored in the configuration key RecoveryLogName.Run the bcmadmin commands config list key RecoveryLogPath and config list key RecoveryLogName to query the current setting for these parameters.
- Run the following commands to resize the recovery log.Resizing the recovery log involves the deletion of the current recovery log file. Make sure all systems and objects are fully recovered and in the active state before running the following commands.
- Stop both sequencer processes:/etc/init.d/bcm stop
- Remove the old recovery log file on both Business Continuity Manager servers:rm /data/recovery.log
- Restart the sequencer processes on both Business Continuity Manager servers:/etc/init.d/bcm start
- Stop both sequencer processes:
- Reactivate the cluster.