S
Simon L. Prinsloo
Guest
Hi It turns out that there may have been another backup running while they were busy with they setup of this target. It seems that the repl.recovery files are constantly update while normal processing is active. We can not afford to loose the primary target while we are creating the secondary target, thus the question is if it is safe to delete the .recovery file on the source, or would that break replication to the primary target? Should it be deleted on the primary target as well? Some background on the steps being followed: 1. The primary target database is shut down. As a consequence of this, the replication server on the source dies as well. 2. Confirm that the replication server on the source is gone. 3. probkup online -REPLTargetCreation -com 4. rsync the backup to the new server. 5. prorest the backup on the new server. 6. proutil -C enableSiteRelication targer (On the new server) 7. Replace the .repl.properties on the source with a version containing both targets. 8. Start both the target databases. 9. Restart the replication server on the source database.
Continue reading...
Continue reading...
