Subject | Re: Transaction log or alternative |
---|---|
Author | agarzotto |
Post date | 2004-06-22T13:19:51Z |
--- In firebird-support@yahoogroups.com, Lester Caine <lester@l...>
wrote:
[...]
know accidentally deleted a production database when trying to create
a backup using gbak and messed up with the parameters so that the
database was overwritten 8-]
But what would you do so that a database can be recovered if there is
a nightly backup, the database is on a RAID and suddenly you find out
that the RAID-controller has gone wild and all copies on all mirrored
disks are the same mess? Is there a way to cope with that other than
losing everything since last night (e.g. we lose the information that
we charged your credit card this morning and will thus charge it again
;-) ? A DB replicator would replicate the mess, wouldn't it?
Regards,
Andreas
wrote:
[...]
> But since we are professionals, we would have disabled those actionson
> the production database, and would be working to produce an upgradeon
> backup of the live data ;)So let's assume we are all professionals [one such professional that I
> With a view to pumping live data into the new database once all the
> off-line testing had been completed.
know accidentally deleted a production database when trying to create
a backup using gbak and messed up with the parameters so that the
database was overwritten 8-]
But what would you do so that a database can be recovered if there is
a nightly backup, the database is on a RAID and suddenly you find out
that the RAID-controller has gone wild and all copies on all mirrored
disks are the same mess? Is there a way to cope with that other than
losing everything since last night (e.g. we lose the information that
we charged your credit card this morning and will thus charge it again
;-) ? A DB replicator would replicate the mess, wouldn't it?
Regards,
Andreas