Date: Tue, 15 Jan 2013 11:54:00 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: freebsd-questions@freebsd.org Subject: databases/postgresql: simple mirroring of a database or a whole server Message-ID: <50F53548.9010004@zedat.fu-berlin.de>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig61E681626FD1C5A6C183F872 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello list. First, please set me CC, i do not subscribe this list. I'd like to ask for a mirroring solution of an important databse on my installations across at least three boxes. The setup is as follows. Operating system is FreeBSD 10.0/amd and 9.1-STABLE/amd64. A top of the OS there is on all machines in question port databases/postgresql92-server|client running. I have a database that needs to be synchronized/mirrored. A data consistency in a narrow timeframe isn't necessary. The database in question is a very important literature reference db which is maintained via a web interface and this is done mostly from a private box at home, which changes the local database set. This database is also used at the lab. Usually, I have to dump the db, send it via ssh/scp over the net to the target machine and restore it - and this at least three times. Since network connectivity isn't available for some technical reasons when I maintain the local db at home, this task is a pain, if I forget to dump/restore the database. The task maintaining the databases like that isn't appreciable. So, I looked out for a mirroring solution. I came across SLONY I/II, but I feel not very comfortable with the complicated setup. Although having had a howto, it dind't work properly. So I'm looking for something more simple. The data consistency within short timeframes isn't so important, so a mission critical mirroring isn't necessary. But I would be feel better having something more "automatic" that is synchronizing more than two or three machines automatically when network connectivity is available. Is there a solution - easy task - to handle such a scenario? Thanks in advance, Oliver --------------enig61E681626FD1C5A6C183F872 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJQ9TVTAAoJEOgBcD7A/5N8NNkH+wQdo1z/9aWPIwheq6pEvpbH iijez09wTQD1S6SF1x8MI7mo02jZtc01qph+cUeSHEBGAj8uCRTel9PtPRrhlUjs AWKn+c8wyTXoq+sxmToLE2cczOkmMEVDNZ4mY5QAcnJcityT5y/8L23NdJ5+FXvn dYCZeEJthn7eD5WjrK8lAEmdh/GFfhqwZRcyvmMFLQr08djFA6J+k/TBz0jOWThx 5QbpZH5BDTNmdys+++B427K5tsJptdxwTgqF3guuGJzJvp2bRHe1GiV2v0RbvBQp tvYT+bGdD0dTpTiFKg4xS4F4/v89+SIyKZIf5hcorweZwazdb2HPbEG2TzxYi+E= =sm1V -----END PGP SIGNATURE----- --------------enig61E681626FD1C5A6C183F872--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50F53548.9010004>