Re: newbie backup script question
From: <jl34778_at_corp02.d51.lilly.com>
Date: 25 Mar 94 22:49:37 EST
Message-ID: <1994Mar25.224937.1_at_corp02.d51.lilly.com>
Date: 25 Mar 94 22:49:37 EST
Message-ID: <1994Mar25.224937.1_at_corp02.d51.lilly.com>
In article <1994Mar24.224555.14553_at_govonca.gov.on.ca>, plattd_at_govonca.gov.on.ca (Dave Platt) writes:
> The following is a backup script, which we plan to run
rest of original message deleted
I have a couple of comments.
- I think that it is not a good idea to hardcode passwords into script files. I'd recommend setting up an OPS$ORACLE6 account that has DBA privilege. Then, you can run exp with a /.
- The tablespace names are also hardcoded, which means that if you add a tablespace, you have to remember to modify the backup procedure. It is not very difficult to write a sql script that actually builds the backup script using the tablespace names found in the data dictionary. Since the script gets rebuilt every time you run the backup, new tablespaces are automatically backed up.
- Backing up to disk is OK, but at some point, you need to get the stuff to tape and get it off site to protect from a massive loss.
- When you backup to tape, don't forget to backup any archive logs created during the backup and by the alter system switch logfile at the end. You will need those archive log files if you ever intend to recover from the stuff on tape.
- My experience is that you can't afford to keep 7 days of archive logs around. They fill up the disk too quickly. You do need to keep any archive logs created between backups.
Bob Received on Sat Mar 26 1994 - 04:49:37 CET