Backup Terminology Whole Database Backup Whole database backup (also known as whole backup) refers to a backup of all datafiles and the control file of the database. Whole backups can be performed when the database is closed or open. This is the most common method of backup. The whole backup that is taken when the database is closed (after the database is shut down using the NORMAL, IMMEDIATE, or TRANSACTIONAL options) is called a consistent backup. In such a backup, all the database file headers are consistent with the control file, and when restored completely, the database can be opened without any recovery | User-Managed Backups Objectives After completing this lesson, you should be able to do the following: Describe user-managed backup and recovery operations Discuss backup issues associated with read-only tablespaces Perform closed database backups Perform open database backups Back up the control file Perform cleanup after a failed online backup Use the DBVERIFY utility to detect corruption Terminology Whole database backup Target database may be open or closed Backup of all datafiles and the control file Partial database backups Tablespace Data file Control file Consistent backups Inconsistent backups Backup Terminology Whole Database Backup Whole database backup (also known as whole backup) refers to a backup of all datafiles and the control file of the database. Whole backups can be performed when the database is closed or open. This is the most common method of backup. The whole backup that is taken when the database is closed (after the database is shut down using the NORMAL, . | User-Managed Backups Objectives After completing this lesson, you should be able to do the following: Describe user-managed backup and recovery operations Discuss backup issues associated with read-only tablespaces Perform closed database backups Perform open database backups Back up the control file Perform cleanup after a failed online backup Use the DBVERIFY utility to detect corruption Terminology Whole database backup Target database may be open or closed Backup of all datafiles and the control file Partial database backups Tablespace Data file Control file Consistent backups Inconsistent backups Backup Terminology Whole Database Backup Whole database backup (also known as whole backup) refers to a backup of all datafiles and the control file of the database. Whole backups can be performed when the database is closed or open. This is the most common method of backup. The whole backup that is taken when the database is closed (after the database is shut down using the NORMAL, IMMEDIATE, or TRANSACTIONAL options) is called a consistent backup. In such a backup, all the database file headers are consistent with the control file, and when restored completely, the database can be opened without any recovery. When the database is operated in NOARCHIVELOG mode, only a consistent whole database backup is valid for restore and recovery. When the database is open and operational, the datafile headers are not consistent with the control file unless the database is open in read-only mode. When the database is shut down with the ABORT option this inconsistency persists. Backups of the database in such a state are termed as an inconsistent backup. Inconsistent backups need recovery to bring the database into a consistent state. When databases need to be available 7 days a week, 24 hours a day, you have no option but to use an inconsistent backup, and this can be performed only on databases running in ARCHIVELOG mode. Backup Terminology (continued) Tablespace Backup A .
