Single Oracle IBM Storage Protect Snapshot instance for multi-database protection

When you are configuring IBM® Storage Protect Snapshot for Oracle, you can configure the product for all Oracle databases on the same host in the same configuration process with a single user ID.

Configure and manage all Oracle databases in a single host that are administered by the same administrative user id. When the single instance is configured for one or more Oracle databases that run on that host, IBM Storage Protect Snapshot operations and commands can be run for all those databases. When you run IBM Storage Protect Snapshot backup or restore operations on a single database, the database and the location of the Oracle software are identified in the command line.

When you use a single Oracle user ID, the databases that are administered by that user ID require a single IBM Storage Protect Snapshot instance with one set of binaries, daemons, and one repository. This approach ensures that less disc space is required, and actions such as upgrading to a new version of the product can be run only once on that instance for all databases. Different operations on different databases can be run in parallel. Logging for all databases that are managed by an IBM Storage Protect Snapshot instance is done centrally by the single instance owner user.

Migration

Choose to migrate one or more existing IBM Storage Protect Snapshot instances to a multi-database instance. Run the Migration Tool to migrate a specific instance. When you are upgrading, the configuration is done once for each IBM Storage Protect Snapshot instance that protects one or more databases. For more information about migration, see the Migrating Oracle instances section.

Cloning

The same single userid must be available on all clone servers. That user ID must also have the same home directory, UID, and GID as on the production server.

Offloading

The same single user ID must be available on all backup servers to allow successful offload operations to the IBM Storage Protect server. That user ID must also have the same home directory, UID, and GID as on the production server.

ASM

In ASM environments, a specific Oracle grid user is still required for IBM Storage Protect Snapshot operations. This user must be a member of the group asmadmin. Each ASM node where IBM Storage Protect Snapshot is running requires its own CLIENT section where the appropriate ORACLE_SID is specified. If the database is cloned, there must be a CLONING section where the appropriate ORACLE_SID is specified.