SnapProtect – Configuration – Oracle RAC
If you plan to use SnapVault or SnapMirror, use the appropriate storage policy based on the type of snapshot, such as NetApp 7-Mode and Cluster-Mode snapshots. For NetApp 7-Mode snapshots, use storage policies associated with OnCommand Unified Manager 5.0, 5.1, or 5.2. For NetApp Cluster-Mode snapshots, use storage policies associated with OnCommand Unified Manager 6.0, 6.1, 6.2 6.3P1, 6.4P1, or 7.0.
Most capabilities of data ONTAP 7-Mode apply, however cascaded replication of primary to snapvault to snapmirror on a single policy is not supported.
- First, you should create a Storage Policy for a successful RAC client configuration and backup.
- From the CommCell Browser, navigate to Policies.
- Right-click the Storage Policies and click New Storage Policy.
- Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:
- Select the Storage Policy type as Data Protection and Archiving and click Next.
- Enter the name in the Storage Policy Name box and click Next.
- Select No to use an existing global Deduplication policy.
- From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.
Ensure that you select a library attached to a MediaAgent operating in the current release.
- From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.
- For the device streams and the retention criteria information, click Next to accept default values.
- Select Yes to enable deduplication for the primary copy.
- From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication database.
In the Location box, type the name of the folder in which the DDB must be located or click the Browse to select the folder, and then click Next.
- Review the details and click Finish to create the Storage Policy.
- From the CommCell Browser, right-click the Client Computers, point to New Client | Application, and then click RAC.
- In the Pseudo-client Name box, type a name for the RAC client.
In the Database Name box, type the name of the Oracle RAC database to which you are assigning this client.
From the Storage Policy list, select the storage policy with a snap copy used for the data of the default subclient. See Create a Snap copy for more information.
Click the Details tab.
Click Add to add an instance for RAC client.
From the Instance Physical Client list, select an instance client containing the Oracle iDataAgent instances that you want to include in the Oracle RAC node.
In the Instance (ORACLE SID) box, type the name of the instance that you want to include in the Oracle RAC node.
Click Change User Account. In the User Name box, type the user name, and then click OK.
In the ORACLE HOME box, type or click Browse to locate the Oracle application install path.
In the Connect String box, type the credentials to access the Oracle RAC database. Use SYS login i.e., sys/password@Service for Oracle RAC client. For example, sys/pwd12@orcl4.
In the TNS_ADMIN Folder, type or click Browse to specify the path for TNS_Admin directory. Note that the TNS_admin path is automatically appended to the path of the $ORACLE_HOME directory even if you do not specify the path.
Repeat this step for each Oracle iDataAgent instance that you want to include.
In the Details tab, select Use Catalog Connect and type the user name to connect to the Recovery Catalog database.
Click the grayed box in Use Catalog Connect.
In the Password field, type the password for the user to connect to the Recovery Catalog database.
In the Confirm Password box, re-type the password for the user.
- Click the Storage Device tab.
- In the Storage Policy used for user command backup of data box, select a storage policy name.
- Click the Logs Backup tab.
- In the Storage Policy used for all Archive Log backups box, select a storage policy name.
- Click OK.
- From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the client and select Properties.
- From the CommCell Browser, navigate to <RAC Client>.
Right-click the <Instance> and click All Tasks | New Subclient.
In the Subclient Name box, type a name.
Click the Log Backup tab.
Click the Backup Archive Log checkbox. If you want the archive log files to be deleted after they are backed up, click the Archive Delete checkbox.
If you have multiple log locations, do the following:
- Click Select ArchiveLog Destinations for Backup and click Add.
- Type the path to the log files to be backed up.
- Click Select ArchiveLog Destinations for Delete and click Add.
- Type the path to the log files to be deleted
If Oracle log destinations are not shared across nodes, then you should select Use Rman for Log Backup.
- Click the Storage Device tab.
In the Data Storage Policy box, select a storage policy name. The Data threshold streams should be at least 1.
Configuring ASM Instance on the Physical Node
If Oracle home of ASM instance and RAC instance are different, then make sure to separately configure an ASM instance on the physical RAC client.
Assuming that you are using the first node for SnapProtect and hence using the first instance (+ASM1), use the following steps to configure the ASM instance:
- Make sure that the kfed utility resides under <Oracle ASM Home>/bin location. If the kfed utility do not exist, then build the kfed utility as shown in the following example:
cd <Oracle ASM Home>/rdbms/lib
make –f ins_rdbms.mk ikfed
Create an ASM instance on the node on which you perform an SnapProtect operation. The kfed utility needs to be configured on all the nodes.
- Ensure that the ASM disk string is not empty.
- From the CommCell Browser, navigate to Client Computers | <RAC Physical Client>.
Right-click the <Oracle Agent>, point to All Tasks and then click New Instance (Oracle SID).
In the Instance (ORACLE SID) box, type the Instance name (Ex:+ASM1).
In the ORACLE USER box, type the user account name for ASM Instance.
In the ORACLE HOME box, type the Oracle home path for ASM instance. Alternatively, you can click Browse to select the location.
Select the Storage Policy for the data of a default subclient from the list.
- Click the Details Tab.
In the Connect String box, type the Connect String. Use / as connect string.
In the TNS_ADMIN Folder box, type the TNS ADMIN folder name. Alternatively, click Browse to select the location.
- Click the Storage Device tab.
In the Storage Policy used for user command backup of data box, select a storage policy.
- Click the Log Backup tab.
In the Storage Policy used for all Archive Log backups box, select a storage policy name.
Skip the following section if you already created a snapshot copy.
The following section provides step-by-step instructions for creating a Snapshot Copy for a Storage Policy.
- From the CommCell Browser, navigate to Policies | Storage Policies.
Right-click the <Storage_Policy> and click All Tasks | Create New Snapshot Copy.
- Specify the following to create a Snapshot Copy:
- Type the Copy Name in the Copy Name box.
- From the Library list, select the name of Library.
- From the MediaAgent list, select the name of a MediaAgent.
- From the Drive Pool list, select the name of a Drive Pool.
- From the Scratch Pool list, select the name of the Scratch Pool.
Drive Pool and Scratch Pool are not applicable for disk libraries.
- Click OK.
The newly created Snapshot Copy can be associated with the subclient from which the snap backup is performed. In this case, the Snapshot Copy acts as the primary copy and therefore will contain only the metadata information associated with the snapshot Backup.
A backup copy operation provides the capability to copy snapshots of the data to any media. It is useful for creating additional standby copies of data and can be performed during the SnapProtect backup or at a later time.
Follow the steps given below to configure Backup Copy for moving snapshots to media.