Обсуждение: Syncing Databases Weekly
Hi,
I am familiar with applications like slony for replications, I am looking for a technique for syncing a very large database every week for backup and redundancy purposes. More specifically, I do all my writes to a main server once a week, at the end of the updates I would like to automatically copy all of the data to a second server as a live backup in case the main system ever goes down.
My initial thought involved streaming a pg_dump from main server to the backup server every week and doing the pg_restore on the receiving side. I initially tried using slony but it just took too long for slony to catch up and there is no real need to do replication during the update. Does that seem like the best option?
Benjamin Arai
Benjamin Arai wrote: > Hi, > > I am familiar with applications like slony for replications, I am looking > for a technique for syncing a very large database every week for backup and > redundancy purposes. More specifically, I do all my writes to a main server > once a week, at the end of the updates I would like to automatically copy > all of the data to a second server as a live backup in case the main system > ever goes down. PITR (Point In Time Recovery) - details in the manuals and recently discussed on one of the lists. -- Richard Huxton Archonet Ltd
Benjamin Arai wrote: > Hi, > > I am familiar with applications like slony for replications, I am > looking for a technique for syncing a very large database every week > for backup and redundancy purposes. More specifically, I do all my > writes to a main server once a week, at the end of the updates I would > like to automatically copy all of the data to a second server as a > live backup in case the main system ever goes down. You could use batch replication via Mammoth Replicator or PITR. Joshua D. Drake > > My initial thought involved streaming a pg_dump from main server to > the backup server every week and doing the pg_restore on the receiving > side. I initially tried using slony but it just took too long for > slony to catch up and there is no real need to do replication during > the update. Does that seem like the best option? > > *Benjamin Arai* > barai@cs.ucr.edu <mailto:barai@cs.ucr.edu> > http://www.benjaminarai.com <http://www.benjaminarai.com/> > > **
Joshua D. Drake wrote: > Benjamin Arai wrote: > >> Hi, >> >> I am familiar with applications like slony for replications, I am >> looking for a technique for syncing a very large database every week >> for backup and redundancy purposes. More specifically, I do all my >> writes to a main server once a week, at the end of the updates I >> would like to automatically copy all of the data to a second server >> as a live backup in case the main system ever goes down. > > > You could use batch replication via Mammoth Replicator or PITR. > Slony's log shipping is another option. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.
Brad Nicholson wrote: > Joshua D. Drake wrote: > >> Benjamin Arai wrote: >> >>> Hi, >>> >>> I am familiar with applications like slony for replications, I am >>> looking for a technique for syncing a very large database every week >>> for backup and redundancy purposes. More specifically, I do all my >>> writes to a main server once a week, at the end of the updates I >>> would like to automatically copy all of the data to a second server >>> as a live backup in case the main system ever goes down. >> >> >> >> You could use batch replication via Mammoth Replicator or PITR. >> > Slony's log shipping is another option. Oh cool... I didn't know Slony could do that. Glad to hear it. > >
On Feb 7, 2006, at 1:34 PM, Brad Nicholson wrote: > Slony's log shipping is another option. But that requires at least one regular replica to exist as well.