Determining redo log recovery time

Hi

A 60 GB (of which 28 GB is data) Oracle7 Server V7.1 database is being deployed at my site. I'm being told that I must do a full backup of this database every night, in order to minimize the time to rebuild it, if a complete database restore is necessary. We have hardware redundancy up the wazoo, but I recognize that user/program error can still corrupt a database. We are creating redo logs and archiving those redo logs (in triplicate!) to tape.

In order to reduce the backup time and the backup volume, I really want to do a full backup at most weekly, and would prefer monthly. But (not being a DBA), I have little information to push back with.

So I'm focusing on the transaction volume, which (I believe) drives the archived redo logs size, which (I believe) drives the restore time. Any suggestion for how I can determine the amount of time it takes to apply arhived redo logs to a restored database? We're running on Digital AlphaServer 4000 systems. I don't expect anyone to know the answer, as I'm not providing enough information. But, what information should I provide to get at the answer? I read the last three chapters of the Oracle7 Server Concepts manual, but didn't see this information there.

Thanks!
Terry Lemons
Digital Semiconductor Received on Sat Apr 12 1997 - 00:00:00 CDT