#FBACKUP SHUTDOWN AFTER BACKUP ARCHIVE#
All archive logfiles necessary would be applied to the database once it is restored from the cold backup. If the database is in ARCHIVELOG mode, the cold backup would be the starting point for a point-in-time recovery.
This image copy can be used to move the database to another computer provided the same operating system is being used. The database is consistent and restorable. These views can be queried even when the database is mounted and not open.Ī cold backup of the database is an image copy of the database at a point in time. The location of all database files can be found in the data dictionary views, DBA_DATA_FILES, V$DATAFILE, V$LOGFILE and V$CONTROLFILE. The init.ora file (can be recreated manually).To have a complete cold backup the following files must be backed up. For example, in Unix you could use cpio, tar, dd, fbackup or some third party utility. An operating system utility is used to perform the backup. If the database is shutdown with the IMMEDIATE or ABORT option, it should be restarted in RESTRICT mode and then shutdown with the NORMAL option.
#FBACKUP SHUTDOWN AFTER BACKUP OFFLINE#
In order to use the hot backup methodology, the database must be in archivelog mode.Īn offline cold backup is a physical backup of the database after it has been shutdown using the SHUTDOWN NORMAL command.
All data in the Oracle or system buffers and all non-committed changes may be lost unless a redo log switch is forced, the resulting archive log and a control file copy taken along with the hot file backup. A Cold backup, that is, one done with the database in a shutdown state, provides a complete copy of the database which can be restored exactly.Ī Hot backup, or one taken while the database is active, can only give a read consistent copy, but doesn't handle active transactions. Normal system backups, referred to as either Hot or Cold backups, are used to protect from media failure.
0 kommentar(er)
