I'd be getting nervous too! As you may already know, a solid, tested backup and recovery solution is one of the DBAs paramount activities. And backup/recovery principals become even more complicated with Very Large Databases (VLDB). I can't solve your problem about your backup failing since I am unfamiliar with the Veritas backup solution. But I can provide some hints.
- Make sure you use RMAN for your backups. Backups of this size can become quite a large task to manage. RMAN really helps with this problem.
- The downtime window can become too large to backup a VLDB. This will most likely mean hot backups, with the database running. RMAN doesn't care wether the backup is hot or cold.
- Hopefully, you can separate the data that doesn't change into their own tablespace(s). This way, you can back up these tablespaces once, set them to READ ONLY, and not back them up again. Then, have your weekly, or monthly, backup cover the tablespaces that are still in READ WRITE mode.
- Instead of FULL backups, look at backing up a portion one week and then another portion next week. This way, you spread your backups out over time. This is where RMAN really comes into play, managing all of those backups for a quick and easy recovery.
For More Information
- Dozens more answers to tough Oracle questions from Brian Peasland are available.
- The Best Oracle Web Links: tips, tutorials, scripts, and more.
- Have an Oracle or SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical Oracle and SQL questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.