New answers tagged replication
rsync is a great tool for keeping files in sync. I would use it in combination with SSH (and public keys), like this: rsync -az -e ssh --delete /var/www otherserver:/var/www For multiple servers multiple uses of rsync might be the best option. Another option is pdcp -r, but that requires copying all the files every time instead of doing delta-transfers. ...
First of all, let's have a reference for OpenLDAP replication in this page, section 18.3.3. Your configuration looks more like the one for MirrorMode replication than the one for N-Way multimaster replication. I think the most likely cause is that you didn't assign a uniqueserverID the the two servers, they both have a value of 1 and the replication overlay ...
I ran into the a similar set of errors recently when my primary DC's system volume filled up (I'd just taken the job, and the DC was previously sitting at less than a gig of HD space and I hadn't gotten around to freeing space). When it happened, the nt file replication system (ntfrs) on the PDC got corrupted. Make sure that the structure of the sysvol ...
At least for version 9.4, an identical filesystem path needs to exist on the standby(s). From http://www.postgresql.org/docs/9.4/static/warm-standby.html#STANDBY-PLANNING: "In particular, the path names associated with tablespaces will be passed across unmodified, so both primary and standby servers must have the same mount paths for tablespaces if that ...
What do you want is a bidirectional, asynchronous replication/mirroring. The best tool at hand under Win2008+ (without buying special hardware/software) is DFSR. It was designed precisely with that WAN-routed replication in mind.
Have you used the same hostname and IP address for the secondary? If so you need to remove the secondary as a DC, remove all GUID/references in DNS/ADDS to the old name...or you can use a unique name.
Top 50 recent answers are included