The Oracle RAC iDataAgent
uses the following logical entities to manage backup and restore
operations from the CommCell Console.AgentFacilitates Oracle instance discovery. InstanceDefines the Oracle database to be backed up. SubclientDefines the Oracle database objects to be backed up. |
Oracle RAC instances are created as part of the procedure to create a RAC pseudo-client. Multiple Oracle iDataAgent instances can be configured using a RAC pseudo-client. You can create one Oracle RAC instance per Oracle RAC node. See Creating a RAC Client for more information.
At least one Oracle iDataAgent instance must be configured within each Oracle RAC instance, and you cannot remove an Oracle iDataAgent instance from an Oracle RAC instance unless more than one Oracle iDataAgent instance is configured therein. Removing an Oracle iDataAgent instance from an Oracle RAC instance does not delete the backup data; this data is still available for restore by another eligible client. The Oracle User should have DBA and SYSDBA privileges for creating an Oracle RAC instance.
You can add a new instance to the existing RAC client. While adding a new instance make sure to use SYS login as connect string to connect to the database. Make sure that the Connect String value does not include "/" when used with the Use SQL Connect option as RAC will have multiple nodes.
If you want to use a SCAN connect string for an instance, use connect string as: sys/sys@nodename:1521/service name of the database where, service name is the database name.
For Example: sys/sys@devrac11gr2-1.xyzcompany.com:1521/DEVRAC11.xyzcompany.com
Use the following steps to add an instance to the existing RAC client.
In RAC one node configuration, a single instance of Oracle RAC database runs on one node of the cluster while the second instance is in a cold standby mode. If there is a failure or fault in the first node and the instance cannot be restarted on the same node, then RAC One Node detects it and relocates the instance to the second node. The benefit of this feature is that it automates the instance relocation without any downtime and manual intervention. In this configuration, you must use unique instance names while configuring instances on nodes. See Creating a RAC Client for more information. For example, if you have two RAC nodes and a database that is not relocated to node2, configure instance on node1 and node2. If instance is running on node1, instances on node1 must be instance_1. If a database is relocated to node2, then the instances on node2 will be instance_2.
For example:
If the RAC database name is testracdb.
Instances are testracdb_1 and testracdb_2.
If the node1 is active, the instances will be testracdb_1 on both nodes. If the database is relocated to node2, then the instances will be testracdb_2 on both nodes.
Use the following steps to configure the RAC on one node:
See Can you restore from a RAC One Node in a multiple node configuration for important considerations that you need to follow while restoring from a RAC One Node.
The Oracle RAC iDataAgent is designed to back up and restore an Oracle RAC database (*.dbf) along with control files (*.ctl) and archived redo log files. After you create an Oracle RAC pseudo-client, a default subclient is created by the system only after you first configure an Oracle RAC database instance from the CommCell Console. Since an Oracle RAC instance references a RAC database, the default subclient includes the entire database associated with that instance. However, you can use the CommCell Console to create user-defined subclients to include only some of the database content by configuring the Subclient Properties (Content) tab. Any content that is not included in the user-defined subclients will remain in the default subclient.
You can create user-defined subclients to backup the specific components or conditions, such as the following:
If a new database object is added to the database, and if none of the subclients contain that database object , then that object is automatically assigned to the content of the default subclient.
During an offline backup, the database is shutdown and is not available for use. Since incremental backups require access to various tablespaces and datafiles, it is always recommended that you perform a full backup of the database when it is offline. The full backup includes all the datafiles, tablespaces, and control file of the Oracle database. Note that, offline backups do not include the archived log files.
Offline backups can be performed when the database is in offline or online mode. If the database is online, it shuts down the database, performs the backup and then brings up the database back.
In order to backup the Oracle database when it is offline, you need to create a separate user-defined subclient for offline backup. Make sure that the database is in the MOUNT mode during the backup.
Use the following steps to create a subclient for offline backups:
In some environments, it may not be possible to bring down the entire database to perform an offline backup. In such situations, you can choose online backups, where the database will be up and running during the backup.
You can perform either a full backup or incremental backup of the Oracle database when it is online. Since full backups includes all the datafiles, tablespaces and logs, it is very time consuming, hence you can plan for a full online backup less frequently (say, on weekly basis). On the other hand, incremental backups includes the data and logs that have been changed after the last full backup, they are faster and can be performed more frequently (say, on a daily basis).
If a new database object is added to the database, and if none of the subclients contain that database object , then that object is assigned to the content of the default subclient
Use the following steps to create a subclient for online backups:
You can also create subclients to backup specific datafiles and tablespaces, which undergo frequent changes in the Oracle database.
Use the following steps to create a subclient to backup individual datafiles and tablespaces:
Archive logs are required to recover database transactions that have been lost due to an operating system or disk failure. You can apply these archive logs to an online backup in order to recover a database.
Though online full backups can include both data and logs, because of their importance in recovering data, it is recommended that you create separate subclients to backup archive log files.
You can selectively copy full backup to a selective copy during an auxiliary copy operation. The advantage of this type of backup is that both data and logs use the same storage policy, which means that they reside together on the same media. They are completely self-contained for restore and long term archiving purposes. Also, the data aging rules for selective online full backups are different from regular full backups, as both data and logs are aged together under the same storage policy
It is recommended to create a different storage policy during the creation of this subclient.
When performing the selective online full backup, note the following:
As the Control file stores the status of the physical structure of the database. It is required when you want to recover the database to the current state. Hence it is important to include control files in your backups. By default, control files are included in the subclient for selective online full backups. You can also include/exclude control files for online or offline backups. The following sections describe the methods by which you can backup control files.
You can configure the instance to automatically backup Control Files whenever you a backup the subclient in that instance.
Use the following steps to enable automatic backup of control files for all the subclients in the instance.
If the control file backup is enabled at the instance level, you can also include/exclude control files for backups from a specific subclient. Use the following steps to enable control file backups for a specific subclient.
You can enable autobackup from RMAN command line to automatically backup the control file in every backup job operation.
Enter the following commands/parameters at the RMAN prompt (the catalog connect string is optional):
$rman target <connect string for target> catalog <connect string for catalog>RMAN>configure controlfile autobackup on;
For Example:$rman target systemuser/systempass@rman92 RMAN>configure controlfile autobackup on;
By default, all data is backed up which includes tablespaces. If you want to restore individual tables, you need to enable table level backup.
In order to backup and restore database tables, you need to enable table level backups for the subclient. Use the following steps to enable backups at table level.
By default, when you restore database tables to a target instance, the system automatically duplicates the source database to an auxiliary instance in a temporary staging location specified during the restore operation. The database will be automatically imported from this auxiliary instance after the restore.
Use the following steps to set up a specific database as an auxiliary instance. This is useful when you want to restore a table to a specific failure point.
1. | Copy the init<SID>.ora file from the source database to the auxiliary database instance. | |
2. | Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance. | |
3. | Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance. |
Windows
Clients: DB_FILE_NAME_CONVERT=('source_of_df_path/','dup_of_df_path/', 'source_of_temp_path/','dup_of_temp_path/',...) LOG_FILE_NAME_CONVERT=('source_of_log_path/ redo','dup_of_log_path/redo') Unix Clients: DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/ ,source_of_temp_path/,dup_of_temp_path/,...) LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo) |
4. | Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance. | |
5. | Restart the Oracle Services, if using Windows clients. | |
6. | Add the destination instance name in the Listener.ora and Tnsnames.ora files. If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host. |
DUPDB = (DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dupdb) (UR=A) ) ) |
7. | Restart the Listener. | $lsnrctl reload |
8. | Ensure that the auxiliary instance is in NOMOUNT mode. | sql> startup nomount; |
When you backup archive logs, you can specify the locations from where the log backups should be performed. This capability enables you to schedule backup operations from different log destinations on the same subclient. If necessary, you can also delete the logs after the backup.
Ensure that the logs in the specified location are backed up. This may cause data loss if those archive logs are not backed up. |
When performing archive log backups, the current redo log file is closed (even if it is not filled up completely) and the next redo log file is used for writing using a log switch. The closed redo log file is then archived during the log phase. Use the following steps to disable the log switch:
When backing up archive logs, by default the logs are not deleted after the backup operation. Use the following steps to enable deletion of logs soon after the backup.
See Deleting Archive Logs After a Specific Backup for more information.
Oracle HOME directory refers to the location where the Oracle application resides. When instances are discovered, the home path is automatically assigned to the instance. However, you can modify the home path location for an instance at any point of time. Use the following steps to configure the Oracle HOME directory:
When an instance is configured, by default, the TNS_Admin directory is created in the Oracle HOME\network\admin path. Use the following steps to change the path for the TNS_ADMIN directory:
In order to perform offline backups of the Oracle database, all users must be logged out of the database and it must be completely shut down. When the database is online, you can enable a graceful shutdown of the database using lights out script that will notify the users about the shutdown and set a specific wait time for the users to logout of the database. Use the following steps to configure lights out script for offline backups:
The Server Parameter file (SPFile) contains the database startup information. By default, the backups do not include the SPFile.
Use the following steps to include SPFile during backups:
Flash Recovery Area is a specific area in the disk storage that exclusively holds a copy of all backup-related components, such as image copies, redo logs, and control file auto backups. This facilitates faster restores of backup data and minimizes restores from tapes during restore operations. Use the following steps to enable backup of flash recovery area:
In order to perform backup and restore operations, you need to create and configure the following user accounts on the Oracle client:
On Unix clients, the user should be part of the user group assigned during the iDataAgent install. You can also use the operating system user account to verify the rights to perform all backup and restore operations for the associated Oracle instance.
On Windows clients, the user should be part of local administrator group and also part of the ora_dba group with read/write permissions on Calypso folder. You can use the Impersonate user account to verify the rights to perform all backup and restore operations for the associated Oracle instance.
The user account for standard database should have the following privileges:
Alternatively, instead of using administrator user account with SELECT ANY TABLE privilege, you can also create user accounts with lesser privileges for accessing specific objects:
For example:
The Recovery Catalog database user account must have recovery catalog owner privileges.
Additional accounts (except Impersonate User) should be established by Oracle database administrator.
Use the following steps to configure the user account to access the Oracle application:
Use the following steps to configure the user account privileges to access the Oracle database:
By default, recovery catalog is not used for backup and restore. As the recovery catalog contains metadata about RMAN operations for each registered database, it is recommended to include recovery catalog in backups. The metadata information is useful when you want to restore and recover the database after a crash. Use the following steps to use the Recovery Catalog for backups:
It is a good practice to synchronize the recovery catalog with the control file, as the control file contains the latest backup information, which is need to perform restores.
Use the following steps to synchronize the control file with the recovery catalog:
The Oracle RAC iDataAgent allows you to perform parallel backups across multiple RAC nodes as a matter of design. Unlike other agents, this agent requires just one subclient and one storage policy per type used (i.e., data, log) along with the requisite number of allocated streams to perform parallel backups. As such, you can load-balance your backups across all or selected nodes of your RAC database and thereby take advantage of the strengths of each node.
Keep in mind that the same number of streams used for performing a backup will be needed to restore the data.
Several options are available for enhancing backup performance and reduce the network bandwidth used for performing backups. These options include:
In addition to the above configurations, you can also enable distribution of data across disks during backup operations. See Enhancing Backup Performance for more details
Use the following steps to enhance the backup performance:
You can assign unique identification tags for all backup operations from a specific subclient. These tags can be used during a restore operation to easily identify a particular backup. Use the following steps to assign unique identification tag for backups.
You can configure a subclient to skip the following data during backup operations:
Use the following steps to exclude data during backup operations:
Prior to running backup operations, you can check datafiles for physical and logical corruption.
Prior to running backup operations, you can validate a backup job, which will cause RMAN to simulate the backup for the purpose of determining whether the backup can be successfully restored. Once a validate job is completed, you can view the log files of the job to identify and correct any validation issues.
During validation, the backup jobs are simulated without the media, you can view the log files of the job to identify and correct any validation issues.
Use the following steps to enable validation of backup jobs:
Prior to running a backup, you can check the following:
By default, during a data aging operation, an Oracle CROSSCHECK is performed by the system to synchronize the entries in the CommServe database with the RMAN catalog. Use the following steps to disable the cross check operation:
You can take multiple copies of the data or log backups using RMAN command line. During restores, even if one of the copies is missing or corrupted, the restore operation will automatically failover to the other copy and restore the data.
1. | To utilize the PARALLELISM option, you need to set the initial parameter in pfile or spfile. | Example: BACKUP_TAPE_IO_SLAVES=TRUE |
2. | Configure device type. | Example: RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET; |
3. | Specify two copies of data. | Example: RMAN> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2; |
4. | Specify two copies of log backups. | Example: RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2; |
5. | Add the environmental variables for the client and instance on which the iDataAgent is installed. | Example: allocate channel ch1 type 'sbt_tape' PARMS="<software_install_path>/Base/libobk.so, ENV=(CvClientName=<client_name>, CvInstanceName=<instance_name>)" |
6. | Once you set the parameters, restart the Oracle database and perform backup operations from the CommCell Console. | Example: To restart the database,
|
You can add, modify, or delete several configurable properties for the Oracle RAC iDataAgent from the command line interface.
Command line configuration enables you to:
The following sections describe the available command line configurations:
Parameter | Description of Parameter Values |
appName | Name of the application. In this case it would be 'Oracle RAC' |
clientName | Name of the RAC pseudo client as displayed in the CommCell Browser (eg., RACPseudoClient) |
instancePhysicalClient/clientName | Name of RAC client node (eg., racnode1) |
instanceName | Name of the Oracle instance (eg., dbname) |
userAccount/userName | Name of the user that has local administrator rights to administer the Oracle application. This is the account used by the user to log in to and use the application to run jobs. (eg., oracle) |
oracleRACInstance/connectString/userName | Name of the Oracle recovery catalog database (eg., cataloguser) |
oracleRACInstance/connectString/password | Password for the catalog connect user (eg., catalogpasswd) |
oracleRACInstance/connectString/serviceName | Name of the Oracle recovery catalog database (eg., catalogdb) |
racDBInstance/connectString/userName | Name of the user with dba privileges (eg., sys) |
racDBInstance/connectString/password | Password for the user with dba privileges |
instanceOracleSID | Name of the RAC node database. (eg., dbname1 for racnode1 and dbname2 for racnode2) |
oracleHome | Path for the Oracle application software (eg., /oracle/oraclehome/) |
tnsAdminFolder | Path to the TNS Admin directory (eg., /oracle/oraclehome/network/admin/) |
dataBackupStoragePolicy/storagePolicyName | Name of the data storage policy (eg., data_sp) |
logBackupStoragePolicy/storagePolicyName | Name of the log storage policy (eg., log_sp) |
blockSize | Block size value for backup and restore operations on the selected instance (eg., 163840) |
enableDeduplication | Option to enable or disable deduplication. Valid values are True/False. |
networkAgents | Number of Network Agents (eg., 2) |
useCatalogConnect | Option to choose whether RMAN will use recovery
catalog database at the time of backup.
Valid values are True/False. If recovery catalog database need to be used choose true else false. |
softwareCompression | Option to enable compression on the Client or
MediaAgent computer. Valid values are:
|
To run command line operations you must first login to the CommServe as follows:
qlogin -cs <commserve name> -u <user name>
qlogin -cs server1 -u user1
qoperation execute -af <xml_path>\CreateRACClient.xml -clientInfo/clientType 'RAC' -entity/clientName '<RACpseudoclientname>'
qoperation execute -af <xml_path>\CreateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName '<RACpseudoclientname>' -instance/instanceName '<RACinstancename>' -useCatalogConnect true -oracleRACInstance/connectString/userName '<catalog_db_user_name>' -oracleRACInstance/connectString/password '<catalog_db_password>' -oracleRACInstance/connectString/domainName '<catalog_db_name>' -ctrlFileAutoBackupType NOT_CONFIGURED -blockSize 163840 -disableRMAN true -networkAgents 2 -softwareCompression OFF -dataBackupStoragePolicy/storagePolicyName '<data_storage_policy>' -logBackupStoragePolicy/storagePolicyName '<log_storage_policy>' -enableDeduplication true -generateSignature ON_CLIENT -racDBOperationType ADD -instancePhysicalClient/clientName '<RACnode1name>' -instanceOracleSID <node1instancename> -userAccount/userName '<oracleusername>' -oracleHome '<oracle_home_path>' -racDBInstance/connectString/userName '<racdb_username>' -racDBInstance/connectString/password '<racdb_password>' -racDBInstance/connectString/serviceName '<racdbname>' -tnsAdminFolder '<tnsadmin_path>'
qoperation execute -af <xml_path>\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName '<RACpseudoclientname>' -instance/instanceName '<RACinstancename>' -racDBOperationType ADD -instancePhysicalClient/clientName '<RACnode2name>' -instanceOracleSID <node2instancename> -userAccount/userName '<oracleusername>' -oracleHome '<oracle_home_path>' -racDBInstance/connectString/userName '<racdb_username>' -racDBInstance/connectString/password '<racdb_password>' -racDBInstance/connectString/ServiceName '<racdbname>' -tnsAdminFolder '<tnsadmin_path>'
qoperation execute -af <xml_path>/GetRACInstance.xml -appName 'Oracle RAC' -clientName '<RACpseudoclientname>' -instanceName '<RACinstancename>'
qoperation execute -af <xml_path>\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName '<RACpseudoclientname>' -instance/instanceName '<RACinstancename>' -racDBOperationType OVERWRITE -instancePhysicalClient/clientName '<RACnodename>' -instanceOracleSID <instancename_for_node> -userAccount/userName <username> -oracleHome '<homepath>' -racDBInstance/connectString/userName '<connect_string_username>' -racDBInstance/connectString/password '<connect_string_password>' -racDBInstance/connectString/ServiceName '<connect_string_name>' -tnsAdminFolder '<tnsadmin_path>'
qoperation execute -af <xml_path>DeleteRACInstance.xml -appName 'Oracle RAC' -clientName '<RACpseudoclientname>' -instanceName '<RACinstancename>'
Creating a RAC Client |
qoperation execute -af C:\XML\CreateRACClient.xml -clientInfo/clientType 'RAC' -entity/clientName 'RacPseudoClient' |
Adding First RAC Node |
qoperation execute -af C:\XML\CreateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -useCatalogConnect true -oracleRACInstance/connectString/userName 'cataloguser' -oracleRACInstance/connectString/password 'catalogpasswd' -oracleRACInstance/connectString/domainName 'catalogdb' -ctrlFileAutoBackupType NOT_CONFIGURED -blockSize 163840 -disableCATALOGUSER true -networkAgents 2 -softwareCompression OFF -dataBackupStoragePolicy/storagePolicyName 'data_sp' -logBackupStoragePolicy/storagePolicyName 'log_sp' -enableDeduplication true -generateSignature ON_CLIENT -racDBOperationType ADD -instancePhysicalClient/clientName 'racnode1' -instanceOracleSID dbname1 -userAccount/userName 'oracle' -oracleHome '/oracle/oraclehome/' -racDBInstance/connectString/userName 'sys' -racDBInstance/connectString/password 'syspasswd' -racDBInstance/connectString/serviceName 'dbname1' -tnsAdminFolder '/oracle/oraclehome/network/admin/' |
Adding First RAC Node without Catalog Connect |
qoperation execute -af C:\XML\CreateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -useCatalogConnect false -ctrlFileAutoBackupType NOT_CONFIGURED -blockSize 163840 -disableCATALOGUSER true -networkAgents 2 -softwareCompression OFF -dataBackupStoragePolicy/storagePolicyName 'data_sp' -logBackupStoragePolicy/storagePolicyName 'log_sp' -enableDeduplication true -generateSignature ON_CLIENT -racDBOperationType ADD -instancePhysicalClient/clientName 'racnode1' -instanceOracleSID dbname1 -userAccount/userName 'oracle' -oracleHome '/oracle/oraclehome/' -racDBInstance/connectString/userName 'sys' -racDBInstance/connectString/password 'oracle' -racDBInstance/connectString/serviceName 'dbname1' -tnsAdminFolder '/u01/app/oracle/product/11.2.0.3/db_1/network/admin/' |
Adding Second RAC Node |
qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -racDBOperationType ADD -instancePhysicalClient/clientName 'racnode2' -instanceOracleSID dbname2 -userAccount/userName oracle -oracleHome '/oracle/oraclehome/' -racDBInstance/connectString/userName 'sys' -racDBInstance/connectString/password 'passwd' -racDBInstance/connectString/ServiceName 'dbname2' -tnsAdminFolder '/oracle/oraclehome/network/admin/' |
Configure Control File Auto Backup |
qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -ctrlFileAutoBackupType CONFIGURE_ON |
Set the Block Size |
qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -blockSize 163840 |
Modify Log Storage Policy and Disable Catalog User |
qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -logBackupStoragePolicy/storagePolicyName 'log_sp' -disableCATALOGUSER true |
Change Network Agents |
qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -networkAgents 2 |
Change Software Compression and Network Agents |
qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -softwareCompression OFF -networkAgents 1 |
Enable Deduplication |
qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -enableDeduplication true -generateSignature ON_MEDIAAGENT |
Delete RAC Database Instance |
Use the following command to delete the instance dbname1: qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -racDBOperationType DELETE -instancePhysicalClient/clientName 'racnode1' -instanceOracleSID 'dbname1' |
Delete RAC Instance |
qoperation execute -af <xml_path>DeleteRACInstance.xml -appName 'Oracle RAC' -clientName 'RacPseudoClient' -instanceName 'dbname' |
There are several configurable properties available for your agent that can be modified from the agent, instance, or subclient level as per need.
It is recommended that you do not modify the properties of a subclient when a job is in progress for that specific subclient. If a job is in progress, either wait for the job to complete or kill the job from the Job Controller.
The following table describes the properties that can configured from the agent, instance, and subclient levels.
Option | Description | Related Topics |
Change Storage Policies |
You can modify the
storage policies in any of the following situations:
You can change the storage policies from the subclient level.
|
Refer to Storage Policies. |
Rename a Subclient |
You can rename a subclient:
|
|
Data Transfer Options |
You can efficiently configure the available resources for transferring data secured
by data protection operations from the subclient level. This includes the following:
You can configure the data transfer options.
|
Refer to Data Compression and Network Bandwidth Throttling. |
View Data Paths |
You can view the data paths associated with the primary
storage policy copy of the selected storage policy or incremental storage
policy. You can also modify the data paths including their priority from
the subclient level.
|
|
Configure a Subclient for Pre/Post Processing of Data Protection |
You can add, modify or view Pre/Post processes for the
subclient. These are batch files or shell scripts that you can run before
or after certain job phases.
|
Refer to Pre/Post Processes. |
Configure Activity Control |
You can enable backup and restore operations from the agent and subclient level.
However, you can enable restore operations only from the agent level.
|
Refer to Activity Control. |
Configure User Security |
You can configure user security from the agent or subclient
level.
You can perform the following functions:
|
Refer to User Administration and Security. |
Enable/Disable Data Encryption |
You can enable data encryption from the suclient level.Encryption must be enabled at the client level prior to configuring any
instances residing on that client.
|
Refer to Data Encryption. |
View Software Version and Installed Updates |
The Version tab, at the Agent level displays the
software version of
the component.
|
|
CommCell Configuration Report |
The CommCell Configuration Report provides the properties of the
CommServe, MediaAgents, clients, agents, SRM agents, subclients, and
storage policies within the CommCell based on the selected filter
criteria.
|
Refer to CommCell Configuration. |
The following sections describe the steps involved in deleting an agent, instance, or subclient.
When you delete an instance or backupset, the associated data is logically deleted and you can no longer access the corresponding data from CommCell Console for recovery purposes. Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity. |
You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.
This operation will permanently delete the data backed up from this level and it cannot be restored.
Data that is backed up for any Oracle instance configured on the Oracle RAC node is lost if the configured Oracle instance is hard-deleted. |
Consider the following before deleting an instance:
Consider the following before deleting a subclient:
Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.