John Socks on Nostr: nprofile1q…4d5tr I used to work on a product that did this commercially, for ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqjc4xaefaljfgcqcleu6lnwzf5kyp2jw940kjsnv7zst8muuhcr9q04d5tr (nprofile…d5tr) I used to work on a product that did this commercially, for Oracle. Based on that experience I would say there are a lot of ways to approach it.
The big question is whether you want an occasional backup, or a fully replicated database ready for failover at any time.
Either way though, the first steps are generally to shut down the primary, and take a copy that is fully coherent. After that you can run a tool to run synchronization as an ongoing process.
I see a couple tools for that.
The big question is whether you want an occasional backup, or a fully replicated database ready for failover at any time.
Either way though, the first steps are generally to shut down the primary, and take a copy that is fully coherent. After that you can run a tool to run synchronization as an ongoing process.
I see a couple tools for that.