I have both. In my case they are geographically separate. Production server at data center. Replicated "just in case," also at data center. At HQ, I replicate that for DR purposes. INTERNALLY (gigabit backend), I have another internal test server that
I refresh FROM THE REPLICATED SERVER AT HQ on a regular basis. I use the replicated server to query stuff (select) and dump databases to the interaction test server regularly for full testing.
-------- Original message --------
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: 02/23/2016 4:16 PM (GMT-06:00)
To: drum.lucas@xxxxxxxxx
Cc: pgsql-admin@xxxxxxxxxxxxxx
Subject: Re: Incremental Refresh - PostgreSQL 9.2
Hi all,
I've got a Master server and a Test Server.
Master server has a 1.7 TBTest server has a full copy from master - 1.7 TB.
The copy was made using pg_dump
I.E: /usr/pgsql-9.2/bin/pg_dump --exclude-table-data='' --format=custom geoop_live > bigdump.sql
Question:Now that the test server has a full copy from master, how could I just do a incremental refreshing once a month?
Instead copying all the DB (1.7GB), just copy what has been changed?Is that possible?
You cannot accomplish incremental updates if your choice of tool is pg_dump. The only way to do a true incremental would be to rely upon something like rsync on the data directory while the master server is offline.
So, assuming that is not an option, you should probably look at the various true replication solutions that are available and see which of those might serve as an alternative.
David J.
Journyx, Inc.
7600 Burnet Road #300
Austin, TX 78757
www.journyx.com
Austin, TX 78757
www.journyx.com
p 512.834.8888
f 512-834-8858
Do you receive our promotional emails? You can subscribe or unsubscribe to those emails at http://go.journyx.com/emailPreference/e/4932/714/
