SnapProtect Backup with hardware Snap Engines | SnapProtect Backup with Data Replicator
Use this tab to enable SnapProtect backup and to establish the options for SnapProtect backup operations, for the selected subclient. These options are available if you select Data Replicator as the Snap Engine. Note that all the options described in this help may not be available and only the options displayed in the dialog box are applicable to the agent for which the information is being displayed.
Specifies whether SnapProtect backup for the selected subclient is enabled or disabled.
Available Snap Engines
Lists the available snapshot engine vendors. To select a snapshot engine vendor, click the pull-down arrow and click the one that you want to use.
- Manage Array
Click to access the Array Management dialog box, which enables you to add or modify access information for a array.
Use this list to specify the name of the proxy server that will be used for performing the SnapProtect backup operations.
Use Separate proxy for Backup Copy
Select to use a separate proxy server for performing backup copy operations such as mounting the snapshot and copying the data to any media.
Use this list to specify the name of the proxy server for performing backup copy operations such as mounting the snapshot and copying the data to any media.
Use source if proxy is unreachable
If the proxy client is unreachable, use the source computer, which is typically the client computer or the MediaAgent used during snap backup of the job.
Use RMAN for backup copy
Select to use RMAN for copying the data to the media. When data is moved from snap to media, the RMAN backup interface is used for block level backup operations. Also, RMAN is required in the case of Automatic Storage Management (ASM) Oracle Databases, since ASM data is not available on the file system.
Enable Snap Integrity Check
You can configure to run integrity check of a hardware snap during an SnapProtect backup.
When the Snap Integrity Check is enabled, the following steps are performed automatically during an SnapProtect backup:
- The database is placed in a quiesced state.
- A snapshot is created for data volumes.
- The database is placed in a unquiesced state.
- The snapshot is mounted on source and cataloging of datafiles is performed from mounted snapshot. This verifies whether all the datafiles are properly captured during an SnapProtect backup.
- The snapshot is created for log volumes
- The snapshot is mounted on source and cataloging is performed for mounted log files.
The RMAN catalog datafilecopy will check the datafile header and verify its authenticity before cataloging it.
When using ASM databases, during snap integrity check, the snap mount path is appended to the ASM disk string to enable discovery of ASM disks. This does not have any impact on the Oracle database or clients. Also, the check ensures that the modified ASM disk string does not impact the discovery of asm disks belonging to already existing disk group.
Once the snap integrity check is completed, the appended snap mount path in the ASM disk string is retained and can be reused for other SnapProtect jobs.
When this is not enabled, you do not see the mount and catalog snap files happening in the Oracle RMAN.log.
The default is disabled.
Use Oracle VSS Writer
Select to initiate Oracle SnapProtect backup operation using the Microsoft Volume Shadow Copy service, Oracle VSS writer and VSS provider. The VSS provider and VSS writer service for the Oracle database need to be installed on the Oracle client machine and must be running in order to perform this type of backup.
Use RMAN for Tape Movement
Select to use RMAN for movement to media operations.
Allow multiple data readers within a drive or mount point
Specifies whether multiple data reads are allowed for a single physical drive or mount point during backups on this subclient. It is recommended that this option is selected for specialized hardware such as RAID, or possibly in the case of spanned volumes.
Number of Data Readers for Backup Copy
Use this space to specify the number of simultaneous backup data streams allowed for this subclient, during the movement to media operation. For best performance, this should be set no higher than the number of physical drives that hold this subclient's data, except for specialized hardware such as RAID.
This option enables the use of full data journaling necessary to preserve the consistency of the database during data replication.
Use snapshot on the source to replicate data
This option enables the use of the snapshot located on the source client to replicate data.
Minimum size of file using hash comparisons
The minimum size of the file (in KB) that would be picked up for hash comparisons during data replication. Files less than the minimum size would be replicated without comparison.
Block size to use for hashing
Block size (in KB) used in hash comparisons.