While the database is shut down, each of the files actively used by the database is
backed up. These files provide a complete image of the database as it existed at the moment it
was shut down.
NOTE
You should not rely on an offline backup performed following a
shutdown abort, because it may be inconsistent. If you must perform
a shutdown abort, you should restart the database and perform
a normal shutdown or a shutdown immediate or a shutdown
transactional prior to beginning your offline backup.
The following files should be backed up during a cold backup:
All datafiles
All controlfiles
All archived redo log files
Initialization parameter file or server parameter file (SPFILE)
Password file
If you are using raw devices for database storage, with or without ASM, you??™ll have to back
up these devices as well using operating system commands such as dd in combination with a
compression utility, as in this example:
dd if=/dev/sdb | gzip > /mnt/bkup/dw_sdb_backup.img.gz
During a recovery, an offline backup can restore the database to the point in time at which
the database was shut down. Offline backups commonly play a part in disaster recovery planning,
because they are self-contained and may be simpler to restore on a disaster recovery server than
other types of backups. If the database is running in ARCHIVELOG mode, you can apply more
recent archived redo logs to the restored offline backup to bring the database back to the point
in time of a media failure or a complete loss of the database.
Pages:
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640