Configure a data domain server for file-level compression collection
In addition to the Names and Backup Type that were entered when an EMC Data Domain server was created, credentials are required to access and collect from the server. Also, if File-Level Compression collection from NetBackup systems is desired, MTree data must be listed.
File-Level Compression information can be instrumental in determining efficient storage strategies and identifying storage that can be reclaimed, thereby reducing archive storage expenses. This data can be used to identify clients with inefficient de-duplication ratios, highlighting where de-deduplication is not an effective approach for certain backed-up files. For example, some hosts may be running database applications that are constantly producing unique bits of data. These hosts can consume much of the expensive Data Domain storage. Data Domain collection now can identify the largest offenders, which can then be moved to less expensive storage to avoid paying premium rates for de-duplication. Use the following report templates to take advantage of this collected data: Data Domain NetBackup File Compression Summary and the Data Domain NetBackup File Compression Detail.
Enter the following details and click .
Field
Description
Data Domain Server Name*
In order for Data Domain Servers to be listed in the policy window, they must be configured with a of .
SSH User ID*
The command-line interface (CLI) via SSH is used to gather Data Domain system data. This requires the SSH Service to be enabled and a Data Domain user that has a management role of 'user'. This User ID must be the same for all addresses listed in the System Addresses entry field for the Data Domain systems.
Password*
The password associated with the User ID.
Repeat Password*
The password associated with the User ID.
File-Level Compression - MTrees Attached to Backup Systems*
This selection is relevant only when the File-Level Compression probe is selected in the EMC Data Domain Backup Policy.
Select the option to either include or exclude collection from the MTrees entered in the list. If the exclude option is selected with an empty MTree list, data from all MTrees will be collected. If the include option is selected with an empty MTree list, no file-level compression data will be collected.
Note:
Warning: Choosing to exclude file-level collection with an empty MTree list may cause collection to take several hours to complete.
Exclude from collection the MTrees entered below*
OR
Collect only from MTrees entered below
Enter one or more MTree names to be included in collection or to be excluded from collection, depending on the selected option. When compression information is collected from the MTree, an attempt is made to connect the file with a backup job that has previously been collected. A 'hint' must be specified to allow this to occur. Currently Oracle RMAN, Veritas NetBackup, and EMC Avamar are supported. For this probe to collect data, the RMAN / NetBackup / Avamar jobs must have been previously collected and all RMAN or NetBackup collection probes must have been run.
Note:
The Exclude from collection the MTrees entered below field will not collect for Avamar.
To specify an MTree to which RMAN is sending backup files to, enter:
RMAN:[MTree Name].
For NetBackup, enter:
NBU:[MTree Name].
For Avamar, enter:
AVM:[MTree Name].
Example of a comma-separated MTree list: RMAN:/data/col1/rman_su1, NBU:/data/col1/nbu_ddm1
AVM:/data/col1/avamar-1629802442
If you do not specify a hint, it is assumed that the Data Domain MTree contains files created by Veritas NetBackup.
To run File-Level compression across all Mtrees on a Data Domain system, with a 'hint' to specify that the database attempt to link files with Backup jobs, enter:
RMAN:*
or
NBU:*
or
AVM:*
depending on the Backup system using the MTree. Mixed use of wildcards is not supported.
Aggregated global and local compression rates for all NetBackup backup images are collected for all MTrees that are connected to the Active Data Domain servers via DDBOOST and where the NetBackup Data Collector is active and has successfully completed an initial data collection.
Warning:
Choosing to exclude collection with an empty MTree list may cause collection to take several hours to complete.
Click to save the policy.
On the Data Collector server, add entries to the local hosts file, both resolving to the Portal server IP address.