This section describe the following types of backups: ❑ Registry file backups
❑ System backups
❑ Standby database backups ❑ Standard database backups
System administrators often perform the first two types of backups, and database administrators (DBAs) perform the last two types of backups.
The last three types of backups should include backing up the Agile server files located at \\Agile_dir\Agile9. These are the files needed to run Agile and the attachments to the Agile database. They should also include backing up the Oracle files located in the \\oracle\oradata\instance_name folder.
Third-party backup procedures, such as Cheyenne Software’s ArcServe, are not described in this chapter. However, if you are using one, see “Useful Information for Backup and Maintenance Tools” on page C-5 for the default username and other Oracle database information.
Performing System Backups
You typically perform a system backup on a small system. You bring down the entire system, including all the programs, data files, and log files. Typically, a system backup is run each night.
To perform a system backup, shut down the system, start it up again in single-user or maintenance mode, then copy system files to tape, as follows:
1 Shut down active applications. 2 Shut down the relational database. 3 Stop the Agile Application Server process.
4 Bring the system back in single-user (maintenance) mode. 5 Back up all disks to tape with a suitable utility.
6 Start the Agile Application Server process. 7 Start the system in multi-user mode. Table C-2: Oracle default field data
Oracle Field Default Data Custom Data
Oracle Sys account password oracle Oracle System account password manager Oracle Ctxsys account password ctxsys Oracle database Agile account username agile Oracle database Agile account password tartan
Oracle database host name Agile server hostname
8 Restart the database.
9 Restart applications as needed.
Using Standby Databases
Typically, a standby database is run on a large system. The standby database feature maintains a duplicate database of your primary online database at the same location or at a remote site. (Both the standby database and the primary database must be running on the same hardware platform, operating system, and Oracle patch release.) A standby database acts as a backup when it resides locally, and is implemented as part of a database disaster recovery strategy when it resides at a remote site. The standby database has the following features:
❑ It is copied from the primary or current production database onto a system residing locally or remotely. ❑ It is mounted, but not open, and is in constant recovery mode.
❑ Redo log files generated from the primary database can be transported to the standby database, and the standby database can apply these logs to recover the database.
❑ In the event of a disaster, a standby database can be activated and fully functional as a new production database. A standby database takes time to set up and configure. For more information, see the references suggested in “Exporting the Database” on page C-9.
Performing Database Backups
Typically, you run a standard database backup daily. Databases backups can be:
❑ Cold or offline, where the database is shut down before copying database-related files: control files, data files, redo log files, initial parameter file (initagile9.ora), spfileagile9.ora, and password file(pwdagile9.ora). A database running in ARCHIVELOG or NOARCHIVELOG mode can be backed up by a cold backup (NOARCHIVELOG mode permits only cold backups).
❑ Hot or online, where a backup is performed while the database is open and users are accessing it. To perform a hot backup, a database must be running in ARCHIVELOG mode. When performing a hot backup, the database tablespace must first be put in backup mode, then the datafile can be copied by the operating system. Once the datafile has been copied, the database tablespace can be placed online again. This allows the database to be backed up tablespace by tablespace.
❑ A logical backup creates logical copies of database objects in a binary export file. Logical backups use the agile9 database utilities, agile9exp and agile9imp. When performing logical backups, a database must be open and running.
Note Oracle EXP and IMP utilities do not export the ctxsys account. So, FTS objects will be recreated during an agile9 import.
For best results, you should timestamp backups and generate scripts to perform them automatically using the operating system task schedule command.
Performing Cold Backups
Cold backups should be done on all the database-related files, including data files, control files, redo log files, the initial parameter file (initagile9.ora),the password file (pwdagile9.ora), and the server parameter file
(spfileagile9.ora).
To perform a cold backup on all database-related files: 1 Shut down the database.
2 Use the operating system copy command to copy all of the database data files, the control file, the initial parameter file, the password file, and the archived redo log file (if the database is running in ARCHIVELOG mode) to the backup destination.
Appendix C Database Management
3 Restart the database.
For details, see the references suggested in “Exporting the Database” on page C-9.
Performing Hot Backups
Hot backups require a setup procedure, after which a backup is created every day. For instructions, see the references suggested in “Exporting the Database” on page C-9.