is it just me or is the Disaster Recovery System of the 5.X and 6.X versions a real disaster?!?<br><br>just skipped through the bugs and found some disturbing stuff like:<br><br><span style="font-weight: bold;">
CSCsh32064</span><br style="font-weight: bold;"><span style="font-weight: bold;">drs restore of CCMDB fails</span><br style="font-weight: bold;"><br>Symptom:<br>CCMDB restore fails when run DRS restore.<br><br>Condition:
<br>Error in DRF MA log:<br>command failed -- Enterprise Replication not active (62)<br>Database selected.<br>425: Database is currently opened by another user.<br>107: ISAM error: record is locked.<br><br>Workaround:<br>
Possibly stop dbmon on all servers before attempting restore.<br><br>=> this bug seems not to be fixed for the 5.1(2) Versions?!?<br><br>or<br><br><span style="font-weight: bold;">CSCsj90196</span><br style="font-weight: bold;">
<span style="font-weight: bold;">Change DRS process to not require sub rebuild/restore</span><br><br>Symptom:<br>CM5.x and 6.x disaster recovery currently requires subscriber reinstall. CM3.x and 4.x did not require subscriber reinstall after BARS restore.
<br><br>Conditions:<br>Perform DRS restore on CM cluster.<br><br>Workaround:<br>After DRS restore on publisher reinstall each subscriber in the cluster.<br><br>=> nice if you have a couple of subs in your cluster...<br>
<br>You can also chose to restore only a certain subscriber in the cluster!? What kind of data will be restored? In 4.X Versions you just could restore the pub and a reboot of the subs would get them back to the version of restored data on the pub...
<br><br>Can someone shed some light on this topics? Any field experience, best practice, dos and don'ts for disaster recovery on 5.X and 6.X versions?<br><br>Regards<br>Patrick<br>