You do not need to create a separate catalog for every instance you want to backup. Note that multiple instances can use the same catalog. Note that “target /” refers to the local database: ~]$ rman target / catalog RMAN> register database Grant the RECOVERY_CATALOG_OWNER role to the schema owner you just created (“rman”): GRANT RECOVERY_CATALOG_OWNER TO rman Ĭreate the recovery catalog: ~]$ rman catalog RMAN> create catalog Better yet, just create a test instance and see what happens…Ĭonnect to the instance where you will create the recovery catalog as a user with SYS or SYSDBA privileges, and issue the following command to create the user/schema which will be used for the catalog: CREATE USER rman IDENTIFIED BY cat TEMPORARY TABLESPACE temp DEFAULT TABLESPACE tools QUOTA UNLIMITED ON tools Always read the documentation and/or talk to your DBA before copying and pasting things from the Internet. Please note that these instructions are for a single instance (RAC may be different). So, let’s not do that.Ĭreate the catalog on a separate Oracle database. Once you reach the limit…you loose reference to your database backups. Without a catalog, objects are tracked in the control files, which can only contain so many references. As you may have guessed, RMAN keeps track of objects in its own database, called a catalog in Oracle parlance. It then instructs TSM what to do with the files. Keeping track of which files are needed for restores, or are ready to be expired, is handled by RMAN. RMAN determines which files need to be backed up, and hands them to TSM. Rather than the TSM client managing the backups, the Oracle backup utility, RMAN, performs this function. However, when backing up a running (“hot”) Oracle database, the process changes. Expiration of these backups is handled by the TSM server, which compares its retention policies to its database. Any new or changed files and directories are added to the TSM database and copied to the appropriate storage pool managed by the TSM server. When backing up a typical filespace, the TSM backup-archive (BA) client compares what files and directories are on the node to what is in the TSM database.
Tsm database drape of the forgotten souls how to#
In this installment, we’ll look at how to keep TSM and Oracle in sync. In the first installment of this series, I discussed some of the basic concepts in using Tivoli Storage Manager for Databases to backup and recover Oracle databases. By tkyle on in Databases, Infrastructure, Oracle, TSM |
0 kommentar(er)
