On Sun, May 20, 2007 at 07:44:38PM +1000, Pascal Hakim wrote:
> On Sun, May 20, 2007 at 05:04:29AM -0400, Roberto C. Sánchez wrote:
> > On Sun, May 20, 2007 at 06:56:45PM +1000, Pascal Hakim wrote:
> > >
> > > I realise the original poster uses MySQL, but if you want to keep a
> > > postgresql DB
On Sun, May 20, 2007 at 05:04:29AM -0400, Roberto C. Sánchez wrote:
> On Sun, May 20, 2007 at 06:56:45PM +1000, Pascal Hakim wrote:
> >
> > I realise the original poster uses MySQL, but if you want to keep a
> > postgresql DB in sync like that, a great way to do it is by using
> > PITR/WAL shippin
On Sun, May 20, 2007 at 06:56:45PM +1000, Pascal Hakim wrote:
>
> I realise the original poster uses MySQL, but if you want to keep a
> postgresql DB in sync like that, a great way to do it is by using
> PITR/WAL shipping[1]. This will work pretty well if what you're worried
> about is hardware fa
On Fri, May 18, 2007 at 08:34:22PM -0400, Roberto C. Sánchez wrote:
> On Fri, May 18, 2007 at 02:21:50PM -1000, Kar-Hai Chu wrote:
> >
> > Due to a tight budget, we do not have a live redundant backup to our
> > production server (other than its RAID 1). One thing we *do* have is
> > hard drive sp
On Fri, May 18, 2007 at 02:21:50PM -1000, Kar-Hai Chu wrote:
>
> Due to a tight budget, we do not have a live redundant backup to our
> production server (other than its RAID 1). One thing we *do* have is
> hard drive space - so we've been trying to setup a process where live
> production data (my
I have 2 identical machines running a few medium size websites. One is
a production machine, the other is an identically (or 99% so) setup
machine used for development. Currently, when features on the
development server are adequately tested, they are pushed into
production.
Due to a tight budget
6 matches
Mail list logo
