Reply to post:

Data trashed? When RPO 0 isn't enough

Mike Timbers

Much of what's being discussed here is for dealing with physical failure but it's good to see virtual failure scenarios also being discussed. I once was involved with an Oracle database that got a logical block corruption. Not only would it not re-start, we couldn't do a restore because we'd done bit-level backups so they contained the same logically-corrupted block. The block had been written four days earlier so to go back before that point would have meant losing four days worth of data.

It's not therefore a question of instantaneous data replication across n+1 sites at zero latency. True RPO-0 means being able to write the same raw data to two totally different storage (software AND hardware) solutions across multiple locations. No-one is going to pay for that.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon