Topics | Advanced Backup Options | Support | Related Topics
Once you have selected your backup type, you can choose to apply Advanced Backup Options to your operation. These provide media management tools at the operation level, as well as tools to optimize your backups for specific circumstances. The advanced options are listed below.
When selected (default) for Macintosh File System, Unix File System, or Windows File System, specifies that the backup will include both the mount point and the data pointed to from that mount point. For Windows File System, this data is backed up even if it is included in another subclient; therefore, data for this file system can be duplicated in the backup. For all supported file systems, clearing the Follow Mount Points option in the Advanced Backup Options dialog box causes the configuration (i.e., the mount point) to be backed up without backing up the data on the mounted volume.
For Windows File System, mount points, which point from the directory to the target data, allow you to add new volumes to the existing file system without using new drive letters. Backups follow mount points by default, backing up both the configuration and the data on the mounted volume. For Windows File System, these backups will not duplicate data in any of the following situations:
However, for Windows File System, a backup that follows a mount point will duplicate data if the mount point points to a volume with an existing drive letter. In this case, data is backed up via the mount point and by any subclient that scans the existing drive letter. To avoid this duplication, filter the mount point or volume letter, or clear the Follow Mount Points option.
If you schedule a backup job for a default subclient with this option cleared and subsequently initiate another backup, the first job will back up all the data, including the mount point data.
| Follow Mount Point restore will not restore the mount point if Follow Mount Point option was selected during backup. In such a case it will recover the data pointed to from the mount point in a defined folder and create a duplicate copy of the data. |
For Windows file systems, specifies that the backup include the data pointed to in remote storage. By default, the system backs up only the reparse points — pointers to the remotely stored data — and not the data itself. You must select the Backup data in remote storage option in the Advanced Backup Options dialog box in order to back up the actual remote storage data.
The Windows 2000 or Windows Server 2003 Remote Storage feature conserves disk space by moving infrequently used data from the hard disk to directly-attached remote storage; it recalls the data when needed. You specify criteria for moving files to remote storage during Windows installation.
Remotely stored data should not be included in every full backup for the following reasons:
Even if this option is not selected, reparse points can be restored if the local disk becomes corrupted. But data is not restored in the event of a disaster to the remote storage device.
It is not recommended that you include remotely stored data in every backup; however, you should deploy a backup scheme that includes some backups of remotely stored data, in accordance with your deployment of the Remote Storage Service. Before instructing the system to back up this data, ensure that the media in the remote storage device will be available at the times of backup and restore.
HotFix InformationFor Windows file systems, specifies that information will be collected about all hot fixes for the operating system configuration. This is useful in situations where knowledge of the operating system configuration is vital to successfully restoring a system. It is also useful in disaster recovery scenarios.
For step by step procedures, see Start a Backup with HotFix Information.
Back up Files Protected by System File Protection
Specifies the backup is to include those files that are protected by the Windows System File Protection feature. This feature protects shared files that may be overwritten by application installations, such as dynamic link libraries (DLLs). This option is available for any subclient that backs up the System State.
Stop DHCP Service when Backing up System State Data
For Windows file systems, specifies the system stop DHCP services on the client computer when System State data is backed up. This option is provided for cases where you cannot use VSS to back up the System State.
For more information, see VSS for Windows File System iDataAgents.
Stop WINS Service when Backing up System State Data
For Windows file systems, specifies the system stop WINS services on the client computer when System State data is backed up. This option is provided for cases where VSS cannot be used to back up the System State.
See VSS for Windows File System iDataAgents for more information.
Start Log Backup after Successful BackupSpecifies that a Transaction Log backup will start automatically after a successful Full or Differential backup operation is completed. This is useful when you want to back up logs immediately after a data backup, and allows you to do so without creating two scheduled jobs.
For more information, see SQL - Automatically Start a Transaction Log Backup after a Successful Backup or Sybase - Transaction Log Backups.
For SQL Server 2008 Enterprise or later, specifies that the backup will be compressed by SQL Server before being backed up. The size of the backup will be smaller than an uncompressed backup of the same data. Typically, compressing a backup will require less device I/O which should increase backup speed significantly. However, CPU usage may increase for compressed backups and you may want to evaluate performance counters. Scheduling the backup during off-peak hours or compressing only low-priority backups may be desirable. When using the SQL Native Backup Compression option, there is no need for deduplication as the data will be compressed with this option and deduplication will not consequently save any more space.
|
|
VSS-enabled and SnapProtect backups are not supported backup types for compression. |
For more information, see Start a Backup with SQL Native Compression.
A copy-only backup is an independent backup and does not affect the usual chaining involved in traditional backups. This type of backup can be performed for a special purpose and does not affect the overall backup and restore procedures. It applies to full backups, full Volume Shadow Services (VSS)-enabled backups, and full SnapProtect Backups.
At least one regular full backup must exist within our software in order to run differential and transaction log backups, otherwise, the first non-full backup will be converted to full. Subsequent non-full jobs after copy-only backup should run as the backup type specified without any conversion.
Specifies the system will create a new index with a full or On Demand data protection operation, and for archive operations. Selecting this option will cause the following to occur for this job only:
Still, a new index can always be created on-demand for an individual job at any time. This is possible by selecting the Create New Index option in the Advanced Backup Options of a backup or schedule policy dialog box.
This option is selected by default for all full backup operations, except On Demand Data Protection Operations. For scheduled backups, disable this option only if you need full backup transparent browse capabilities.
For more information about the Index and its use, see Index.
Create Backup Copy immediately
Specifies a backup copy will be created immediately after the completion of the SnapProtect backup job. This option enables you to perform a backup copy operation during the SnapProtect backup job and is referred to as inline backup copy. This option applies to SnapProtect backup only and the backup copy creation is based on the backup copy rules specified for the snapshot copy.
For step-by-step instructions on creating an inline backup copy, see Inline Backup Copy.
Partial (Excludes read-only Filegroups)
A partial backup resembles a full database backup, but does not contain all the filegroups. Instead, it contains all the data in the primary filegroup, every read/write filegroup, and any optionally-specified read-only files. Partial backups are useful whenever you want to exclude read-only filegroups. A partial backup of a read-only database contains only the primary filegroup.
Tail-log Backup (database is left in restoring state)
This advanced backup option is only available if the Transaction Log option was selected in the Backup Option dialog box. Specifies to back up the tail of the log and to leave the database in the RESTORING state.
Optimize Backups for Novell Storage Management Services (SMS)
The NetWare File System, OES File System and Novell Directory Services iDataAgents provide the capability to utilize Novell's Storage Management Services (SMS) when backing up data.
When the Optimize for Novell SMS option is selected from the Data tab of the Advanced Backup Options dialog box (for Novell Directory Services iDataAgent, see Configuring Novell Directory Services iDataAgent for Backup Optimization), Novell's SMS will query the configured subclient content to determine what data will be backed up. Once the data has been queried, SMS then determines the order and conduct of backing up the data. This negates the need for the iDataAgents to generate a collect file during the scan phase, which significantly reduces the amount of time taken for the scan phase to complete.
Note the following before optimizing backups using Novell's Storage Management Services (SMS):
Configuring Novell Directory Services iDataAgent for Backup Optimization
Use the following steps to configure Novell Directory Services iDataAgent for backup optimization utilizing Novell's Storage Management Services:
|
 |
When verifying synthetic full backups, disparities between actual files on the client computer and the Index are collected. Internally, a flag is set when the synthetic full backup completes successfully. This flag adds functionality to the next incremental/differential backup to detect any items that the previous synthetic full backup did not include, and include any such items in that incremental/differential backup. The pending flag is cleared when the incremental/differential backup completes successfully, or when a conventional full backup completes, whichever occurs first.
See Verify Synthetic Full Backups for more information.
Ignore Error in Synthetic Full
Errors encountered in synthetic full backups can now be ignored if the Ignore Error in Synthetic Full advanced backup option is enabled. This is useful when running full backups is not possible and when synthetic full backups are continuously run, even is backup media is partially corrupted. Errors such as inability to read data (bad tape, files missing on disk media, etc.) will be ignored when this option is enabled.
See Ignore Error in Synthetic Full Backups for more information.
Catalog section provides options for job restartability using transaction logging and index cache sharing using Catalog Server:
Select this option if you wish to use the shared index cache profile (Catalog Server) of the MediaAgent (if configured) to save a copy of the job's index cache for index cache sharing along with transaction logging feature for granular job restartbility.
Index Cache Server with transaction logging provides the facility to automatically continue data protection operations when there are job failures due to loss of connectivity to the index, in the following situations:
When the Index Cache Server is used with transaction logging feature, the transaction log of the job is relayed to the Index Cache Server. So if a job has to be restarted in a failover scenario, the transaction logs are downloaded from the Index Cache Server to the local MediaAgent and replayed. This enables the job to be restarted from the point of failure.
To enable this feature, in the Advanced Backup Options dialog Data tab, select Use shared profile if present with transaction logging.
This option is recommended on clustered MediaAgents (MediaAgents installed in a cluster group) so that the data protection jobs on the MediaAgent can continue when there is a cluster failover. This feature is supported by all index-based agents. See Advanced Backup/Archive Options Support for a list of Agents that support this feature.
Select this option if you wish to use the shared index cache profile of the MediaAgent (if configured) to save a copy of the index cache for index cache sharing without using transaction logging feature for granular job restartbility. This is not a recommended configuration.
Select this option to use transaction logging feature to provide granular job restartbility for job failures due to index issues. When this option is enabled for a job, the transactions of the job are recorded in a log. If the job has to be restarted, the transaction log is replayed and the job is resumed from the last execution point.
Select this option to use neither shared profile nor transaction logging.
See Catalog Server for more information.
Priority
If selected, the default priority for this type of job will be used in determining how the Job Manager will allocate resources for this job.
Use this option to manually specify the priority for the job, between 0 (highest priority) and 999 (lowest priority). The Job Manager will use the priority setting when allocating the required resources. This is useful if you have jobs that are very important and must complete, or jobs that can be moved to a lower priority.
Specifies that this job will start in the Job Controller in a suspended state and cannot run until the job is manually resumed using the Resume option. This option can be used to add a level of manual control when a job is started. For example, you could schedule jobs to start in the suspended state and then choose which scheduled jobs complete by resuming the operation started in the suspended state.
Enable Total Running Time
The maximum elapsed time, in hours and minutes, from the time that the job is created. When the specified maximum elapsed time is reached, as long as the job is in the "Running" state, it will continue; if the job is not in the "Running" state when the specified time is reached, Job Manager will kill the job.
For more information, see Job Running Time.
Enable Number of Retries
The number of times that Job Manager will attempt to restart the job. Once the maximum number of retry attempts has been reached, if the job has still not restarted successfully, Job Manager will kill the job. Note that this job-based setting will not be valid if restartability has been turned off in the Job Management Control Panel.
For more information, see Restarting Jobs.
Kill Running Jobs When Total Running Time ExpiresOption to kill the job when the specified Total Running Time has elapsed, even if its state is "Running". This option is available only if you have specified a Total Running Time.
For more information, see Job Running Time.
This option starts the backup/archive operation on a new media, which causes the following to occur:
If cleared, the operation automatically uses the current active media or volume.
This media management feature provides a degree of control over where the data physically resides, for example helping you to meet security or performance goals. This feature is useful in situations where you would like the data to reside on a new media, not appended to a media already containing backup/archive data.
Another form of the Start New Media option is available from the library properties. See Library Properties - Start New Media for more information.
For related information, see Creating an Exportable Media Set.
Mark Media Full after Successful Operation
This option marks media full, 2 minutes after the completion of the backup/archive operation. If any jobs are initiated within the 2 minutes, they are allowed to write to the media. If the job was associated with the prior media, new media (such as a new tape) will be used for subsequent jobs. (Applies to all backup/archive types.)
This media management feature provides a degree of control over where the data physically resides, for example helping you to meet security or performance goals. This feature prevents any other data from being written to the media. If the job was associated with the prior media, new media (such as a new tape) will be used for subsequent jobs. (Applies to all backup/archive types.)
For related information, see Creating an Exportable Media Set.
Allow other Schedule to use Media Set
This option allows jobs that are part of a schedule policy or schedule and using a specific storage policy to start a new media and also prevent other jobs from writing to the set of media. It is available only when the Start New Media and Mark Media Full options are enabled, and can be used in the following situations:
For related information, see Creating an Exportable Media Set.
The Image Level iDataAgents can restore at both the file and volume level. However, if you do not need the file level restore capability, then you can increase performance by skipping metafile creation. This disables the file level restore, and is most useful in situations where the file system is already backed up by the File System iDataAgent.
If selected:
If cleared, a metafile will be created, and the data can be restored using either File Level restore or Volume Level restore.
If File Level restores will never be used for this client, instead of manually selecting the Skip Metafile Creation option for each job, edit the SkipMetaFileCreation registry key to automatically skip metafile creation for all backup jobs.
Release Resources during meta-data collection phase
For the Image Level iDataAgents, specifies that reserved media will be released while the system is collecting the metadata for the data protection operation. This is useful in cases where the system is collecting data on a large volume and you want the resources available for other jobs.
Reserve Resources Before Scan
Normally, media is reserved for a job before the operation phase (backup or archive). When selected, this option will reserve the media before the scan phase. This reserves the media earlier because the scan phase precedes the operation phase.
Job should wait for Inline Copy Resources
If you are performing a data protection/archive operation on a subclient with a storage policy that has the Inline Copy option enabled, then this option specifies that the operation should wait until resources are available for both the data protection/archive operation and the Inline Copy. (This option is available only if an Inline Copy is created on the storage policy that is being used for this data protection operation).
If cleared, the data protection operation will create the Primary copy even if there are not enough resources to create the Inline Copy.
For more information, see Inline Copy.
Data path options enable you to execute the data protection operations to a specific data path. You can select the following data path options in this tab.
See Change the Data Path for a Backup/Backup Schedule for more information.
Several Vault Tracking options are available to export and track media. These options are available only when a Vault Tracker license is available in the CommServe, and are only applicable for data protection operations using a storage policy associated with a library containing removable media (e.g., tape, optical or stand-alone.)
For additional information, see the following:
Specifies that the NAS NDMP file server is to create a snapshot and perform the backup from the snapshot, rather than backing up the live file system.
Specifies that the user quota information and group quota information, registered in the node to monitor and control disk usage, is to be backed up.
Specifies that the original files, not stub files, are copied during the backup job. This allows you to back up data that has been archived, rather than just the stub left by the NAS NDMP file server's data archiving software. Refer to the hardware vendor's documentation for more information about such archived data.
Specifies the number of read-ahead processes to use during backup operations of BlueArc file servers. To configure read-ahead processing, select a number from 1 to 10. If left blank or nothing is specified, the file server default setting is used. A value of 0 disables read-ahead processing, which may be used when file sizes are large. If file sizes are small (16 KB or less), it may be useful to select 10 read-ahead processes. Read-ahead processing consumes resources, so you may want to limit the number of additional processes unless it makes a significant difference in performance. See the BlueArc documentation for more information.
Specifies that the NAS NDMP file server is to create a snapshot and perform the backup from the snapshot, rather than backing up the live file system.
Selecting this option enables the Celerra "Use the Backup-with-Integrated-Checkpoints" feature, which automatically creates, mounts (as read-only), and uses the new checkpoint of the file system for the backup, and then deletes the checkpoint when the backup completes (and even if it fails).
Specifies a data block level backup of an entire specified volume, rather than a file-by-file backup.
When this option is selected:
Using this option is incompatible with NDMP Restore Enabler. If selected, you can restore only to an EMC Celerra file server.
If needed, a VBB Full Destructive Restore can be run when this option is selected.
Specifies that the original files, not stub files, are copied during the backup job. This allows you to back up data that has been archived, rather than just the stub left by the NAS NDMP file server's data archiving software. Refer to the hardware vendor's documentation for more information about such archived data.
Specifies that the user quota information and group quota information, registered in the node to monitor and control disk usage, is to be backed up.
Specifies that the NAS NDMP file server is to create a snapshot and perform the backup from the snapshot, rather than backing up the live file system.
Choices = select "Yes", "No", "Snap" or "Sync"
Prevents the concurrent execution of multiple backup or restore operations on the same file system.
Specifies that when enabled, the files on a Hitachi file server are backed up in the order in which they appear on disk rather than the order they appear in the directory tree. This can improve the performance of the backup; however the directory restore operations will be slower since the data in the directory is not saved with the backup image. Also, Direct Access Restore (DAR) operations are not possible when this feature is enabled. Version 06-01 supports this feature. See the Hitachi documentation for more information.
Specifies that the NAS NDMP file server is to create a snapshot and perform the backup from the snapshot, rather than backing up the live file system.
Choices = select "Yes", "No", "Snap" or "Sync"
Specifies that backup operations will be blocked.
Backup ArchiveLog
This option specifies whether the archive logs will be backed up. When selected, the archive logs get backed up based on the criteria set below.
This option allows you to back up the archive logs older than the specified number of days. Use the space provided to enter the number of days.
This option allows you to back up the archive logs that are not older than the specified number of days. Use the space provided to enter the number of days.
This option allows you to back up the archive logs based on the time they were created. Use the Start Time and End Time fields to specify the time range when the logs were created. This time range will be used as the criteria for archive logs to be backed up.
This option allows you to back up the archive logs based on the specified range of Log Sequence Numbers (LSN). Use the Start LSN and/or End LSN fields to specify the range of LSNs used as the criteria for archive logs to be backed up.
This option allows you to back up the archive logs based on the specified range of System Change Numbers (SCN). Use the Start SCN and/or End SCN fields to specify the range of SCNs used as the criteria for archive logs to be backed up.
This option allows you to back up archive logs that match the specified string pattern, or partial string pattern. Use the space provided to enter the string pattern. Note that when you select this option and leave the field blank, all the archive logs from the selected destinations get backed up. Refer RMAN documentation for information on how to enter a pattern.
For Example:
To back up the log file DB1_1_2355.arch, you can specify the pattern as %2355% with or without the destination selected. The log file DB1_1_2355.arch will be backed up from the default or selected destination.
This options allows you to back up one copy of all the archive logs, from any of the available destinations randomly, regardless of any criteria.
Select ArchiveLog destinations
This option allows you to select the location from where the archive logs will be backed up. Note that, this option is disabled when you select the All criteria. Use the Add button to select an archive log destination from the Select ArchiveLog destinations drop-down list. Similarly, use the Delete button to remove an archive log destination from the previously selected list of archive log destinations. If you select the LIKE option with no string to be matched and do not select any destination, one copy of all the archive logs will be backed up from any of the available destinations randomly.
The Select ArchiveLog destinations drop-down box lists all the destination paths configured for the instance (including USE_DB_RECOVERY_DEST path). However, if you need to use the database recovery file destination, you need to manually type in the exact path in the space provided instead of choosing the USE_DB_RECOVERY_DEST path from the list.
While defining the destination path in the Oracle SPFile, if you do not end the destination path with a slash symbol, the last name in the destination path will get added to the archive log file name. Therefore, in the Select ArchiveLog destinations option, if you select the destination path that includes part of the file name and also specify a pattern for the file name using the LIKE option, the operation will fail. However, if you select the LIKE option without specifying the pattern, the operation will succeed.
| The value in this field will overwrite the value in the Select ArchiveLog Destinations for Backup field the Subclient Properties (Log Destinations) tab. |
This option allows you to back up the archive logs that have not been backed up for at least n number of times.
For related information, see Start an Archive Log Backup for Oracle and Oracle RAC iDataAgents.
Delete ArchiveLog
This option specifies whether the archive logs will get deleted. When selected, the archive logs get deleted based on the criteria set below
This option allows you to delete the archive logs that are older than the specified number of days. Use the space provided to enter the number of days.
This option allows you to delete the archive logs that are not older than the specified number of days. Use the space provided to enter the number of days.
This option allows you to delete the archive logs based on the time they were created. Use the Start Time and End Time fields to specify the time range when the logs were created. This time range will be used as the criteria for deleting the archive logs.
This option allows you to delete the archive logs based on the specified range of Log Sequence Numbers (LSN). Use the Start LSN and/or End LSN fields to specify the range of LSNs used as the criteria for deleting the archive logs.
This option allows you to delete the archive logs based on the specified range of System Change Numbers (SCN). Use the Start SCN and/or End SCN fields to specify the range of SCNs used as the criteria for deleting the archive logs.
This option allows you to delete archive logs that match the specified string pattern, or partial string pattern. Use the space provided to enter the string pattern. Note that when you select this option and leave the field blank, all the archive logs from the selected destinations get deleted. Refer RMAN documentation for information on how to enter a pattern.
For Example:
To delete the log file DB1_1_2355.arch, you can specify the pattern as %2355% with or without the destination selected. The log file DB1_1_2355.arch will be deleted from the default or selected destination.
This option allows you to delete one copy of all the archive logs, from any of the available destinations randomly, regardless of any criteria.
Delete Instance Archive Log
This option allows you to delete the archive logs of the selected instance in the Oracle RAC node. You can delete the instance archive logs based on the Log Time, Log Sequence Number, or System Change Number. You will also require to provide the archive log destination location from where the logs will be deleted.
Select ArchiveLog destinations
This option allows you to specify the location from where the archive logs will get deleted. Note that, this option is disabled when you select the All criteria. Use the Add button to select an archive log destination from the Select ArchiveLog destinations drop-down list. Similarly, use the Delete button to remove an archive log destination from the previously selected list of archive log destinations. If you select the LIKE option with no string to be matched and do not select any destination, one copy of all the archive logs will be deleted from any of the available destinations randomly.
The Select ArchiveLog destinations drop-down box lists all the destination paths configured for the instance (including USE_DB_RECOVERY_DEST path). However, if you need to use the database recovery file destination, you need to manually type in the exact path in the space provided instead of choosing the USE_DB_RECOVERY_DEST path from the list.
While defining the destination path in the Oracle SPFile, if you do not end the destination path with a slash symbol, the last name in the destination path will get added to the archive log file name. Therefore, in the Select ArchiveLog destinations option, if you select the destination path that includes part of the file name and also specify a pattern for the file name using the LIKE option, the operation will fail. However, if you select the LIKE option without specifying the pattern, the operation will succeed.
| The value in this field will overwrite the value in the Select ArchiveLog Destinations for Delete field on the Subclient Properties (Log Destinations) tab. |
This option allows you to delete the archive logs that have been backed up for at least n number of times.
For related information. see Delete Archive Logs for Oracle and Oracle RAC iDataAgents.
| Always ensure that the archive logs are backed up prior to deleting them. |
Enter Maximum number of database block corruptions
Specifies the maximum number of database block corruptions a backup process can encounter before stopping. A database block is a logical unit of database space. RMAN ignores the specified number of database block corruptions before terminating a backup process. Once the specified threshold value is reached, RMAN abruptly stops the backup process with an error message.
For example:
LISTING 2: r_20030520213618.log
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on d1 channel at 05/20/2003 21:36:26
ORA-19566: exceeded limit of 0 corrupt blocks for file
/u01/app/Oracle/oradata/MRP/sales_data_01.dbf
It is recommended that you set this number to match the number of corrupted database blocks identified by RMAN for the database file being backed up. By default, the maximum number of allowed database block corruption value is 0. In this case, even one corrupted database block will terminate the backup process. For more information on detecting the number of corrupted database blocks, see the Oracle documentation.
Enable RMAN Disk Ratio
When this option is selected, RMAN reads data files across disks and groups them in a backup set. This way, the backup load is distributed across disks thus increasing the backup performance. By default, this option is disabled in the Advanced Backup Options (Oracle Options) tab. Once you have enabled this option, you must also specify a disk ratio value greater than zero in order for RMAN to utilize this option. The disk ratio option is applicable only when you are backing up data files or control files.
Specifies the number of disks from which data files are included in each backup set. For example, consider data files distributed across 10 disks that supply data at 10 bytes/second and a tape drive that needs 40 bytes/second to keep streaming. In this case, you can set the disk ratio value to 4, which will direct RMAN to include data files from 4 disks in each backup set. RMAN compares the disk ratio value with the number of disks available for backup and uses the lowest value. For example, if the disk ratio value is set to 4 and the data files are available in 3 disks, RMAN attempts to include data files from 3 disks in each backup set. If you set the option to 0, disk ratio will be disabled. When the disk ratio option is disabled, RMAN reads the files as specified in Data Files per BFS option in the Subclient Properties (Backup Arguments) tab.
You can configure the Oracle Tag for backups to uniquely identify a particular backup copy. The Oracle Tag specified for a backup can be used during a restore operation to tell the system which particular backup to restore the data from. Use of the Oracle Tag backup argument provides an alternative to point-in-time restores. See Configure Backup Arguments for step-by-step instructions.
You can assign tags for a specific backup job tag from the Advanced Backup Options (Options) tab. In addition, you can also assign an Oracle tag to all the backup jobs of a subclient from the Subclient Properties (Backup Arguments) tab. However, the tag defined at the backup job level will override the tag defined at the subclient level.
Customize Script
When this option is selected, you can view the RMAN scripts for the selected data/log backup options and edit them as required from the CommCell Console.
Oracle RMAN scripts for backup operations can also be viewed and modified when creating/editing a Data Protection Schedule Policy from the CommCell Console. However, you will have to manually enter the default RMAN script in the provided text box for data or log backups and then edit the script to suit your requirements. Also note that, for data and log backups, ensure that the RMAN scripts are available in the Custom rman script tab. For step-by-step instructions, see Customize RMAN Script from Schedule Policy.
This option is extremely useful when you want to include RMAN commands in the script that are not supported by the software.
For more information, see Customized RMAN Scripts.