agarzotto wrote:

>So let's assume we are all professionals [one such professional that I
>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?
>
>

Well, that depends what kind of 'mess' you mean. If it's something like
'delete * from table' done by mistake, then, obviously, it will be
replicated.
But a DB replicator prevents any kind of physical corruption: if the
database file is deleted, overwritten with gbak :-), corrupted due to a
bad RAID controller, and any other hardware factor, then the replicated
DBs will be totally unaffected. Of course, they will be unable to
replicate, but that will be the extent of it.

Jonathan Neve.