Avamar: How a Backend Capacity Report is Generated for Backups Stored on a Data Domain
Summary: This article is to explain how Avamar implements the Backend Capacity Report for clients with backups stored on Data Domain.
Instructions
Backend capacity reporting for client backups stored on Data Domain is a new feature that was introduced with Avamar version 7.3.
The Backend Capacity Report for the GSAN, available since Avamar version 5.x, uses replication technology to calculate the size of backups after deduplication.
To report the client backups stored on Data Domain, DDOS uses the feature Physical Capacity Measurement (PCM) or Physical Capacity Reporting (PCR).
This allows the calculation of accurate disk usage by a directory tree, collection of directory trees, MTree, or a collection of MTrees.
The following article provides a detailed explanation: Data Domain: Physical Capacity Measurement or Physical Capacity Reporting Frequently Asked Questions
The steps below, using Management Console Server (MCS) logging, outline how Avamar uses the PCM feature to obtain Backend Capacity Report information for backups stored on Data Domain:
1. When a backend capacity report is launched, the MCS service spawns a thread to run the report:
03/31-13:17:01.00044 com.avamar.mc.rpt.job.ReportManager$1.run
INFO: Started: com.avamar.mc.rpt.job.BackendCapacityDDReportJob@a471a6aa (1 running, 0 waiting)
03/31-13:17:01.00045 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.run
FINE: Running report <REPORT_NAME>
2. MCS retrieves the backups for the client or domain selected in the report:
03/31-13:17:01.00045 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.publishStatus
FINE: Fetching backups
03/31-13:17:01.00119 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.fetchBackups
FINE: Including domain: /clients/
03/31-13:17:01.00203 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.getClientBackups
FINE: Including client: /clients/test.local.domain (23 backups)(test.local.domain)
3. Once all backups are collected, MC calls a REST API to Data Domain to create a Compression Measurement:
03/31-13:17:13.00602 com.avamar.mc.rpt.bcrdd.CompressionMeasurement.<init>
FINE: Creating URI: https://dd.local.domain:3009/rest/v1.0/dd-systems/d57a21caedf6d961%3Ac514d833dda5914e/stats/compression/measurements
03/31-13:17:13.00602 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.publishStatus
FINE: Created measurement for: dd.local.domain
The measurement includes backups of all clients:
03/31-13:17:13.00605 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.publishStatus
FINE: Submitting measurement 1 of 1
03/31-13:17:13.00606 com.avamar.mc.rpt.bcrdd.CompressionMeasurement.createMeasurement
FINE: Description: 1490959033606
Include Paths:
/data/col1/avamar-1445355479/cur/f513b4cb897b43b3ffe8e2d9cec7788b92ca4ce1/1D2A998DFA45A2E
/data/col1/avamar-1445355479/cur/f513b4cb897b43b3ffe8e2d9cec7788b92ca4ce1/1D2A8D1E01CBD2E
/data/col1/avamar-1445355479/cur/f513b4cb897b43b3ffe8e2d9cec7788b92ca4ce1/1D2A80883413D1A
03/31-13:17:19.00385 sun.net.www.protocol.http.HttpURLConnection.getInputStream0
FINE: sun.net.www.MessageHeader@7736bdf27 pairs: {null: HTTP/1.1 201 Created}{Content-Type: application/json}{Content-Length: 314}{X-DD-AUTH-TOKEN: c6cd873bdaf7c3861d60ba35e10eab189}{X-DD-UUID: d57a21caedf6d961:c514d833dda5914e}{Cache-Control: no-cache}{Server: Data Domain OS 5.7.2.10-541351} 03/31-13:17:19.00385 com.avamar.mc.rpt.bcrdd.CompressionMeasurement.createMeasurement
INFO: Measurement 120259084337 created
03/31-13:17:21.00423 sun.net.www.protocol.http.HttpURLConnection.getInputStream0
FINE: sun.net.www.MessageHeader@799be7fe7 pairs: {null: HTTP/1.1 200 OK}{Content-Type: application/json}{Content-Length: 314}{X-DD-AUTH-TOKEN: c6cd873bdaf7c3861d60ba35e10eab189}{X-DD-UUID: d57a21caedf6d961:c514d833dda5914e}{Cache-Control: no-cache}{Server: Data Domain OS 5.7.2.10-541351}
03/31-13:17:21.00423 com.avamar.mc.rpt.bcrdd.CompressionMeasurement.addExtraPaths
INFO: Paths added/excluded for measurement 120259084337
4. The report can take a few minutes to complete, during which time, MCS continues to monitor the measurement from Data Domain:
03/31-13:21:12.00658 sun.net.www.protocol.http.HttpURLConnection.getInputStream0
FINE: sun.net.www.MessageHeader@1017660a7 pairs: {null: HTTP/1.1 200 OK}{Content-Type: application/json}{Content-Length: 553}{X-DD-AUTH-TOKEN: c6cd873bdaf7c3861d60ba35e10eab189}{X-DD-UUID: d57a21caedf6d961:c514d833dda5914e}{Cache-Control: no-cache}{Server: Data Domain OS 5.7.2.10-541351}
03/31-13:21:12.00658 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.publishStatus FINE: Monitoring 1 measurements
5. Once the measurement is completed on Data Domain, MC receives gets the data:
03/31-13:22:18.00806 sun.net.www.protocol.http.HttpURLConnection.getInputStream0
FINE: sun.net.www.MessageHeader@6e4fa4fb7 pairs: {null: HTTP/1.1 200 OK}{Content-Type: application/json}{Content-Length: 984}{X-DD-AUTH-TOKEN: c6cd873bdaf7c3861d60ba35e10eab189}{X-DD-UUID: d57a21caedf6d961:c514d833dda5914e}{Cache-Control: no-cache}{Server: Data Domain OS 5.7.2.10-541351}
03/31-13:22:18.00807 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.monitor FINE: Finished measurement: dd.local.domain (dd.local.domain)
Error:
Backups: 191
measurement_id: 120259084337
finish_epoch: 1490959338
creation_epoch: 1490959033
link: [rel: self, href: /rest/v1.0/dd-systems/d57a21caedf6d961%3Ac514d833dda5914e/stats/compression/measurements/120259084337, rel: related, href: /rest/v1.0/dd-systems/d57a21caedf6d961%3Ac514d833dda5914e/stats/compression/measurements]
state: finished
paths_not_found_count: 0
snapshot_epoch: 1490959135
files_seen_count: 573
id: 120259084337
user_description: DDBoostUser
start_epoch: 1490959277
priority: normal
extended_retention_tier: total_comp_factor: 0.0, local_comp_factor: 0.0, pre_comp_bytes: 0, post_comp_bytes: 0, global_comp_factor: 0.0 measurement_description: 1490959033606
percent_done: 100
active_tier: total_comp_factor: 172.97872552006913, local_comp_factor: 1.386, pre_comp_bytes: 51388185187694, post_comp_bytes: 297078065717, global_comp_factor: 124.80427526700515
03/31-13:22:18.00807 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.publishStatus FINE: Monitoring 0 measurements
6. MCS finishes the job and inserts the report data into the report_history table of the MCS Database (MCDB). This allows the reports to be viewed from the Avamar UI:
03/31-13:22:18.00814 com.avamar.mc.rpt.job.BackendCapacityDDReportJob.run FINE: Finished (317769 ms)
03/31-13:22:18.00814 com.avamar.mc.rpt.job.ReportManager$1.run INFO: Finished: com.avamar.mc.rpt.job.BackendCapacityDDReportJob@a471a6aa
GSAN storage. Similarly, the Backend Capacity Report for GSAN does not include the backups on Data Domain.
Additional Information
- Avamar: Backend Capacity Report: Requirements for use with Data Domain
- Data Domain: Physical Capacity Measurement or Physical Capacity Reporting Frequently Asked Questions
- Avamar: Backend Capacity Report for Data Domain fails to run, reporting "Feature is not enabled." (Log in as a registered user to Dell Support may be required to view this article.)