https://rivendellaudio.wiki/index.php?action=history&feed=atom&title=Setup_of_Hot_Standby_rdcatchd_eventsSetup of Hot Standby rdcatchd events - Revision history2026-04-23T14:47:26ZRevision history for this page on the wikiMediaWiki 1.45.3https://rivendellaudio.wiki/index.php?title=Setup_of_Hot_Standby_rdcatchd_events&diff=28900&oldid=previmported>WaybackImport: Imported from Wayback via edit2020-09-19T02:48:47Z<p>Imported from Wayback via edit</p>
<p><b>New page</b></p><div><pre><br />
On Friday 27 July 2007 12:57, Andrew (1550 AM) wrote:<br />
> What happens when a system which is setup for Hot-standby (as prescribed<br />
> in the appnote) is swapped in for a failed "master" which has a lot of<br />
> RDCatch events? My understanding that those events are specific to a<br />
> certain host. Is there a way to quickly copy those events to the standby<br />
> host?<br />
<br />
The CLI command is 'rdcatch_copy'.<br />
<br />
Here's the nomenclature:<br />
<br />
rdcatch_copy -h <src-mysql-host> -s <src-rd-host> -H <dest-mysql-host> -S <dest-rd-host><br />
<br />
Using this, you can copy all the events from one RDCatch machine to run<br />
on another RDCatch machine. It was created in response to a situation<br />
just like yours where thousands of events live on one machine yet need to<br />
move (in case of crash, temporary move, etc.) to another machine.<br />
--<br />
<br />
Sherrod Munday<br />
</pre><br />
</div>imported>WaybackImport