Author: Myrtle taylor
-
Recovery Catalog Versions – RMAN Backups and Reporting
Read More: Recovery Catalog Versions – RMAN Backups and ReportingI recommend that you create a recovery catalog for each version of the target databases that you are backing up. Doing so will save you some headaches with compatibility issues and upgrades. I have found it easier to use a recovery catalog when the database version of the rman client is the same version used…
-
Registering a Target Database – RMAN Backups and Reporting
Read More: Registering a Target Database – RMAN Backups and ReportingNow, you can register a target database with the recovery catalog. Log in to the target database server. Ensure that you can establish connectivity to the recovery catalog database. For instance, one approach is to populate the TNS_ADMIN/tnsnames.ora file with an entry that points to the remote database. On the target database server, register the…
-
Creating a Recovery Catalog – RMAN Backups and Reporting
Read More: Creating a Recovery Catalog – RMAN Backups and ReportingWhen I use a recovery catalog, I prefer to have a dedicated database that is used only for the recovery catalog. This ensures that the recovery catalog is not affected by any maintenance or downtime required by another application (and vice versa). Listed next are the steps for creating a recovery catalog: 1. Create a…
-
Using BACKUP … VALIDATE – RMAN Backups and Reporting
Read More: Using BACKUP … VALIDATE – RMAN Backups and ReportingThe BACKUP … VALIDATE command is very similar to the VALIDATE command, in that it can check to see if data files are available and if the data files contain any corrupt blocks, for example: RMAN> backup validate database; This command does not actually create any backup files, it only reads the data files and…
-
Put It Together in a Script – RMAN Backups and Reporting
Read More: Put It Together in a Script – RMAN Backups and ReportingAn RMAN script can pull of these configurations together and automate the backup job. The following is an instructional script that shows how these components work together. This gives a basic script for a starting point to understanding the RMAN recommendations and be able to implement them. There is also a good chance that a…
-
Use Incremental Backups – RMAN Backups and Reporting
Read More: Use Incremental Backups – RMAN Backups and ReportingIncremental backup strategies are appropriate for large databases in which only a small portion of the database blocks change from one backup to the next. If you are in a data warehouse environment, you may want to consider an incremental backup strategy, because it can greatly reduce the size of your backups. For example, you…
-
Delete Backups, Based on Retention Policy – RMAN Backups and Reporting
Read More: Delete Backups, Based on Retention Policy – RMAN Backups and ReportingYou can report on backups that RMAN has determined to be obsolete per the retention policy, as follows: RMAN> report obsolete; To delete obsolete backups, run the DELETE OBSOLETE command: RMAN> delete obsolete; You are prompted with this: Do you really want to delete the above objects (enter YES or NO)? If you are scripting…
-
Set the Autobackup of the Control File – RMAN Backups and Reporting
Read More: Set the Autobackup of the Control File – RMAN Backups and ReportingYou should always configure RMAN to back up the control file automatically after running any RMAN BACKUP or COPY command or after you make physical changes to the database that result in updates to the control file (such as adding/removing a data file). Use the SHOW command to display the current setting of the control…
-
Determine the Location for the Snapshot Control File – RMAN Backups and Reporting
Read More: Determine the Location for the Snapshot Control File – RMAN Backups and ReportingRMAN requires a read-consistent view of the control file for the following tasks: • Synchronizing with the recovery catalog • Backing up the current control file RMAN creates a snapshot copy of the current control file that it uses as a read-consistent copy while it is performing these tasks. This ensures that RMAN is working…
-
Use Online Backups – RMAN Backups and Reporting
Read More: Use Online Backups – RMAN Backups and ReportingMost production databases have 24/7 availability requirements. Therefore, you need to take online RMAN backups. Your database must be in archivelog mode for online backups and to be able to recover to a point in time. You need to consider carefully how to place archivelogs, how to format them, how often to back them up,…
Search
Popular Posts
-
Recovery Catalog Versions – RMAN Backups and Reporting
I recommend that you create a recovery catalog for each version of the target databases that you are backing up. Doing so will save you some headaches with compatibility issues and upgrades. I have found it easier to use a recovery catalog when the database version of the rman client is the same version used…
-
Registering a Target Database – RMAN Backups and Reporting
Now, you can register a target database with the recovery catalog. Log in to the target database server. Ensure that you can establish connectivity to the recovery catalog database. For instance, one approach is to populate the TNS_ADMIN/tnsnames.ora file with an entry that points to the remote database. On the target database server, register the…
-
Creating a Recovery Catalog – RMAN Backups and Reporting
When I use a recovery catalog, I prefer to have a dedicated database that is used only for the recovery catalog. This ensures that the recovery catalog is not affected by any maintenance or downtime required by another application (and vice versa). Listed next are the steps for creating a recovery catalog: 1. Create a…