Re: Hot Backup - D3/Linux
- From: "Mark Brown" <Mark_Brown@xxxxxxxxxxxxx>
- Date: Mon, 31 Mar 2008 13:39:47 -0700
"JJCSR" <JCronin@xxxxxxx> wrote in message news:190f7226-0670-459f-8e79-8cd3ac7675d1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Is anyone out there experienced with "hot-backup", using D3/Linux?
If so, can you report pros and cons? Has anyone who might be using
hot-backup found any reason to use transaction-logger in conjunction
with hot-backup?
Thanks,
Jim Cronin
Director MIS
Kittery Trading Post
Jim,
Hot backup IS transaction logger. In a nutshell, here's what happens.
You do a full save of your system. You start logging transactions.
You take your filesave to a second machine, one with at least as much disk and i/o speed.
You do a full restore on this backup machine. You define a slave master relationship between the two boxes via the software provided. Then start hot-backup.
Hot backup takes the transaction log from the master machine and distributes it to the slave machine(s), keeping the critical files updated.
With reasonably fast lan speeds and reasonably fast hardware, the two boxes are almost virtual twins. Which is what you want. If the master box goes down, you switch over to box two and your back up and running. The only data it is possible to lose is whatever is in the transaction logger pipeline, so the idea is to keep it to a minimum by "tuning" system parameters.
Some fairly large players use hot backup. Auto Trader Magazine pops to mind.
It can take hours to restore a large system and additional hours to restore the transaction logs.
If it is reasonably monitored (slave and/or master phantoms die sometimes) and don't let the logger queue get too big, I've never heard of anyone with a better solution.
--
Mark Brown
Sr. Software Engineer
Drexel Management Svc Inc.
484-716-6154 (cell)
.
- References:
- Hot Backup - D3/Linux
- From: JJCSR
- Hot Backup - D3/Linux
- Prev by Date: Hot Backup - D3/Linux
- Previous by thread: Hot Backup - D3/Linux
- Index(es):
Relevant Pages
|