Loading...

Automatic Subclient Creation and Configuration for Oracle Multi-Instance Snap Optimization

Once the instances are created or discovered, execute the following QScript to create and configure the subclients:

qoperation execscript -sn OraMultiDBCGSnapConfig -si <ClientComputerGroup> -si <hourly/snap schedule policy> -si <daily/clone schedule policy> -si <y/n>(FullScan)

Arguments

Client Computer Group

Create one client group and add all the clients for which snap/clone jobs will be performed

Hourly/snap schedule policy

Create hourly schedule policy which will be used to run snap jobs for every hour

Daily/clone schedule policy

Create daily schedule policy which will be used to run clone jobs once for daily.

FullScan (Y/N)

If the value is "n", then it is incremental scan and as part of incremental scan it will check only newly created/discovered instances. subclients will be created for them only. Otherwise it will check all the instances in that client group and create subclients if any instance do not have the required subclients.

When you execute the script, the system will check all the instances in that client group and perform the following steps:

  1. If the subclients are not already created, it will create the following two subclients for snap and clone correspondingly:

    <instancename>_snap

    <instancename>_clone

  2. It will assign EMC TimeFinder Snap Snap Engine to <instancename>_snap subclient and EMC TimeFInder Clone to <Instancename>_clone subclient. See Modify Snap Engine for a subclient section to change the Snap Engine.
  3. By default, the system will perform a File System backup copy. Use RMAN for backup copy is also selected for these subclients.

    If you are using NoArchiveLog mode Database, disable Use RMAN for backup copy.

  4. It will add all the snap subclients(<instancename>_snap) to hourly schedule policy and all clone subclients(<instancename>_clone) to daily schedule policy.

    If you want to exclude instances from creating subclients and associating them to shared schedule policy, update the instance description with exclude with cvsnap schedule. Then the above script will not create subclients for those instances. See Update instance description to change the instance description using command line.

Once you execute the script, assign the storage policy and proxy client to all the subclients using the CommCell Console or command line.

Example:

Executing configuration script:

[root@brahmani64 Base]# ./qoperation execscript -sn OraMultiDBCGSnapConfig -si CVLT -si hourly -si daily -si n
QScript[OraMultiDBCGSnapConfig] CS[commserve] DB[CommServ] Source[SQL File]

Qscript Output:

Changed database context to 'CommServ'.
Created snap subclients for:
Client [client1] Instance [par1]
Client [client1] Instance [par2]
OraMultiDBCGSnapConfig completed at Aug 8 2012 11:48PM. ErrorCode (0).
Qscript Execution Succeeded!

Modify Subclient Using Command Line

Download the update_subclient_template.xml file and save it on the computer from where the command will be executed.

Assign a Storage Policy to a Subclient

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes.

qoperation execute -af update_subclient_template.xml -clientName client1 -instanceName par1 -subclientName par1_snap -storagePolicyName snapSP

Assign a Proxy to a Subclient

Make sure that the proxy is configured correctly before assigning a proxy to a subclient.

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes.

qoperation execute -af update_subclient_template.xml -clientName client1 -instanceName par1 -subclientName par1_snap -storagePolicyName snapSP -snapToTapeProxyToUse/clientName dbcs

Disable RMAN for Backup Copy

You must disable RMAN for backup copyfor NOARCHIVELOG databases.

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes.

qoperation execute -af update_subclient_template.xml -clientName client1 -instanceName par1 -subclientName par1_snap -storagePolicyName snapSP -snapToTapeProxyToUse/clientName dbcs -isRMANEnableForTapeMovement false

Modify the Snapshot Engine for a Subclient

Download the update_subclient_template.xml file and save it on the computer from where the command will be executed.

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes.

qoperation execute -af update_subclient_template.xml -clientName client1 -instanceName par1 -subclientName par1_snap -storagePolicyName snapSP – snapShotEngineName “EMC CLARiiON Snapview Snap”

Update the Instance Description

Execute the following command to change the instance description after substituting the parameters and attributes:

[root@brahmani64 Base]#./qoperation execscript -sn SetOracleInstanceProperties.sql -si client1 -si 'Q_ORACLE' -si par1 -si 'User Description' -si 'exclude from cvsnap schedule' -si 1

Configure the Proxy for RMAN Backup Copy

When you configure a proxy for RMAN backup copy, make sure to satisfy the following requirements:

  • Make sure that the data, log, diag, FRA and all the dump directories on the proxy are identical to the source.
  • Oracle gid and uid should match the source computer's oracle user.
  • Oracle instances on the proxy should be configured similar to those at source and should be in started mode. You need to configure the instances on the CommCell console.
  • You can also use sRMANDATAFILECOPY additional setting for RMAN backup copy. See RMAN Backup Copy Operations for more information.

Last modified: 12/26/2018 7:12:34 PM