• I don't see this as something that can be easily managed by simple GUI tools. There's so many different ways you can store data, backup data, and restore data that it starts to look like something that a DBA should be intimately involved in. It's not needlessly complicated - unlike many MS products (BizTalk /shudder). It is complicated to the point it actually needs to be to provide us with the level of security we want or need.

    I mostly agree with this. There are a lot of situations, most in fact, where DR is not the primary use case for backup/restore. It's really hard to script/gui/wizard all the various restore situations while allowing for outages and disk space shortages and poorly trained users. ("Put that Sept 22 copy of INT customer test data on the DEV box again." "Dude, that should have said Not In." "I don't care about the Test backups. We need the Prod backups to fit on the stupid SAN.")

    That said, there are *lots* of smaller, simple, vanilla installations out there that would benefit tremendously from a backup/restore wizard with options for DR and simple point in time restoration. Smaller places can be the most vulnerable when bad things happen, and they're the ones most likely to be doing without a trained DBA.

    [font="Arial"]Are you lost daddy? I asked tenderly.
    Shut up he explained.
    [/font]
    - Ring Lardner