On Backups
"In all honesty, if you were looking after a 3rd party application that had a database, you would probably do the same as the schemas arent often published."
100% agree with you there. There are many applications that use some obscure DB system, or worse yet, use a common DB but don't tell you the password(s) to manage it. All in the name of database integrity and proprietary systems of course. This will prevent BackupExec and the like from sinking its hooks in.
"lots of perfectly acceptable ways of getting a consistent backup, from using an applications backup API to using a snapshot system that is application aware (such as VSS on Windows)."
I doubt VSS is Sybase-aware. Sorry. And as for backup APIs in the software, you neglected to read the author's next sentence. He mentions using the software's internal backup functions as an option.
"AIMstor will give CDP combined with snapshot instances so you've got the frequent crash consistent images (ie every minutes) combined with less frequent recovery point which are fully consistent"
Such CDP systems would only benefit DBs if they grab the transaction log. Then you can have the DB roll back the log to a consistant state. The CDP system isn't, in itself, magical enough to do this on its own.
""that is why an RTO of zero is science fiction."
Really? Isnt this what mirroring is for? Or there are some products that do real time replication."
Such a fail comment. In the event of a database foobar, that corruption is automagically replicated to your mirror. Same goes for corrupting (modifying/deleting) files. The only time mirroring to a hotsite is useful is for system failure. Server bursts into flames? No problem, we have a hotsite. Directory tree got deleted? You lose your zero RTO due to having to restore files.