Re: Backing up large databases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Apr 28, 2006, at 10:34 AM, Andy Shellam wrote:
My future plan for when my database grows larger, is with the use of WAL logging – have a base backup taken on a Sunday morning (our quietest time), ship this to the hot-standby once a week, and start it off in a recovery mode (using my rolling-WAL script I’m testing now.) Then throughout the week, send the WAL logs from the live box as they become available down to the standby, which then get processed on arrival – these files are 16MB in size (I believe this can be changed).
Theoretically the size of WAL files can be changed, but in practice no one ever does this. In other words, it's probably not a great idea.
This is coming from an 8.1 server, I believe it’d be okay for 7.4 but don’t quote me on it.
PITR was introduced in 8.0. There's a number of other reasons to upgrade as well. In the meantime, Slony might be a viable alternative.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@xxxxxxxxxxxxx
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux