Professional Documents
Culture Documents
12v1 Database Backup PDF
12v1 Database Backup PDF
the DBA should be deleting old backups to create space for infrastructure has been damaged,
current backups. The data retention policy should be chosen but not destroyed. Before the
carefully, making sure that it complements the backup media Backups are of no event, the DBAs performed
subsystem retention policy and requirements for the backup backups to the backup media,
use if the IT team
recovery strategy. If not using a catalog, the DBA must ensure following all of the processes
that the control file record keep time instance parameter cannot restore the noted previously in this article,
matches the retention policy. data to the system and had these stored offsite.
at the time of need. In the enterprises most recent
Effective Backup Management IT audit, the auditor rated the
After making a solid backup plan and completing initial backup process as effective.
work, the DBA should properly manage backups, keeping the The backup media from the offsite storage is retrieved
following points in mind: and loaded. A message appears on-screen that states that the
Automating backupsFor Oracle, either set backups backup media are unreadable due to integrity issues. What
through OEM or use an OS scheduling tool, and Spool could have happened?
output to a log file that can be reviewed for any errors. In Many things could have happened. However, it is clear
SQL Server, use Maintenance Plans for scheduling backups. that a critical step did not happen. The restoration from
Monitoring backupsSet up monitoring using appropriate the backup media was never really tested. The control was
tools so that the DBA gets an e-mail or alert through a pager marked as effective because a backup process was in place
or cell phone for any failed backups, which should be rerun and being performed. In addition, no errors were ever
as soon as possible. received when the enterprise backed up to the backup media.
Backup logs and catalogsReview backup logs and backup Backups are of no use if the IT team cannot restore
catalog information periodically for any issues. Use RMAN the data to the system at the time of need. A DBA should
reporting to show backup status. For Oracle, back up the formulate a detailed strategy for this task:
RMAN catalog database by exporting all catalog schemas 1. D
atabases restore testingThere should be a requirement to
periodically as well as by doing an export backup of RMAN test database restores from disk as well as from tape backups.
catalog schema at the end of each backup. For SQL Server, 2. Validating restores where possibleThe DBA can validate
backup system databases, especially master and msdb. and verify backups without doing actual restores. Validating
Database catalog maintenanceWith Oracle databases, backups using the restore validate database command will
use delete obsolete to remove backups that are outside the do everything except actually restore the database. This is the
organizations retention policy. If obsolete backups are best method to determine if the backup is good and usable
not deleted, the catalog will continue to grow and before being in a situation in which it becomes critical.
performance will become an issue. Cross-checking 3. Refreshing nonproduction databases from production
(cross-check backup) will check that the catalog/control file backupsIt is good practice to periodically build
matches the physical backups. nonproduction databases from production backups
Validating backupsValidate and verify backups without using appropriate backup/restore utility commands as a
doing actual restores. restore practice.
Setting up dependenciesWhen backing up to disk, archive 4. Performing annual/biannual restore testing from tape as
these backups to tape as soon as backup to disk completes. part of auditThe DBA will have to explain the process