Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Article Number: 000060149


Avamar: How to use capacity.sh script to manage capacity on an Avamar system

Summary: This article explains how to use the capacity.sh script to manage capacity on an Avamar system.

Article Content


Symptoms

The purpose of this article is to describe the use of the Avamar capacity.sh script. An understanding of how to use the script helps the user to understand which Avamar clients are adding the most data. This can provide valuable information when managing capacity on an Avamar system.


Cause

Not applicable

Resolution

The Avamar capacity.sh script is a tool that helps users understand the daily change in capacity on an Avamar system.  
 
How to run the script:
  1. Log in to the Avamar Utility Node as the admin user.
  2. Run capacity.sh.
Sample output of capacity.sh when run with no extra options.
 
DATE     AVAMAR NEW     #BU    DDR NEW     #BU    SCANNED       REMOVED     MINS PASS AVAMAR NET      CHG RATE
========== ============= ==== ============= ==== ============= =============  ==== ==== ============= ==========
2015-02-22      42116 mb   20          0 mb    0    1632430 mb         -2 mb     1    9      42113 mb      2.58%
2015-02-23       9244 mb   37         87 mb    1    2007496 mb         -2 mb     1    8       9241 mb      0.46%
2015-02-24     251437 mb   44          0 mb    0    3320302 mb         -5 mb     1    7     251431 mb      7.57%
2015-02-25     128836 mb   29          0 mb    0    2984357 mb        -18 mb     1    8     128817 mb      4.32%
2015-02-26       5972 mb   28          0 mb    0    3236844 mb       -120 mb     2    9       5852 mb      0.18%
2015-02-27      10400 mb   28          0 mb    0    1698648 mb       -207 mb     1    8      10193 mb      0.61%
2015-02-28        517 mb   20          0 mb    0    1639704 mb        -25 mb     1    8        492 mb      0.03%
2015-03-01        232 mb   17          0 mb    0    1670693 mb         -2 mb     1   10        230 mb      0.01%
2015-03-02       1795 mb   21          0 mb    0    1683217 mb      -1391 mb     1   13        403 mb      0.11%
2015-03-03      61734 mb   31          0 mb    0    3310735 mb        -80 mb     1   15      61653 mb      1.86%
2015-03-04      63130 mb   32          0 mb    0    3238318 mb     -56945 mb     3   24       6184 mb      1.95%
2015-03-05       3824 mb   33          0 mb    0    3296444 mb       -123 mb     2    8       3700 mb      0.12%
2015-03-06      66523 mb   31          0 mb    0    3334139 mb          0 mb     1    5      66522 mb      2.00%
2015-03-07       8831 mb   24          0 mb    0    3003236 mb       -456 mb     4   17       8375 mb      0.29%
2015-03-08       1051 mb    8          0 mb    0    1475912 mb        -92 mb     1    9        959 mb      0.07%
================================================================================================================
 14 DAY AVG     43709 mb   26          5 mb    0    2502165 mb      -3965 mb     1   10      39744 mb      1.75%
 30 DAY AVG     34940 mb   24          2 mb    0    2098185 mb      -2798 mb     1   13      32141 mb      1.67%
 60 DAY AVG     23373 mb   19          1 mb    0    1575990 mb     -10646 mb     1   10      12727 mb      1.48%

Top Change Rate Clients.  Total Data Added 655735mb

     NEW DATA % OF TOTAL CHGRATE TYPE CLIENT
============= ========== ======= ====
    272838 mb     41.61   1.44%  AVA /MC_SYSTEM/avamar-1361485148
    244332 mb     37.26   2.22%  AVA /domain1/clientZ.customer.com
    114913 mb     17.52  29.74%  AVA /domain2/clientF.customer.com
      4238 mb      0.65   9.71%  AVA /REPLICATE/AvamarServer50/clients/replicatedclient.customer.com
      3772 mb      0.58  14.41%  AVA /domain1/clientD.customer.com

Starting with the above part of the script, we see a row of data for each day being reported on. The default reporting time frame is 14 days.

For each day, the above section reports the following information:    

AVAMAR NEW - The amount of new, modified data added to the Avamar Server
BU# - The number of Avamar server backups which took place
DDR NEW - The amount of new, modified data added to any attached Data Domain systems 
BU# - The number of Data Domain directed backups which took place
SCANNED - The amount of source data scanned on the clients
REMOVED - The amount of data removed from the Avamar Server by garbage collection
MINS - The amount of time for which garbage collection ran.
PASS - The number of passes achieved by garbage collection
AVAMAR NET - The net data change on the Avamar system (AVAMAR NEW less REMOVED)
CHG RATE - The percentage increase or decrease of data that is stored in the Avamar Server due to the net data change. 

Interpreting the data:    
This section gives you an idea of what is happening daily, and to understand trends and anomalies. Consider whether the data is showing any of the following: 
  • A large increase in "New Data."
  • Regularly missed garbage collection (Removed = 0).
  • Insufficient garbage collection (PASS < 2).
  • Persistently high change rates (CHG RATE > 1%).
  • Days where backup did not run.

Below the above section, are three rows which summarize the data over the previous 14, 30, and 60-day periods. This is useful for understanding the longer term trends.

The output above shows that new data that is added to the system is accelerating. The change rate is increasing from 1.48% to 1.67% to 1.75%.
 
The bottom section of the output shows the amount of data that was added during the reporting period. 

Here we learn that the total amount of data added by all the clients was 655,735 MB. The script then shows a (configurable) number of the top clients which contributed to this new data.  

Let us take our previous example:    

Top Change Rate Clients.  Total Data Added 655735mb

     NEW DATA % OF TOTAL CHGRATE TYPE CLIENT
============= ========== ======= ====
    272838 mb     41.61   1.44%  AVA /domain1/clientD.customer.com
    244332 mb     37.26   2.22%  AVA /domain1/clientZ.customer.com
    114913 mb     17.52  29.74%  AVA /domain2/clientF.customer.com
      4238 mb      0.65   9.71%  AVA /REPLICATE/AvamarServer50/clients/replicatedclient.customer.com
      3772 mb      0.58  14.41%  AVA /MC_SYSTEM/avamar-abcdef123456


Here we learn that clientD.customer.com added the most new data to the Avamar Server (272,838 MB) which was 41.61% of the total data added. The client's own change rate was 1.44%.

clientF.customer.com did not add a significant amount of data but has the highest change rate out of the top clients.

The Administrator would be well advised to monitor this client to understand why the change rate is so high.
From a capacity management perspective, the 'top' clients that are listed in this section are candidates for close inspection. This is because they have the greatest effect on the overall capacity.

If considering reducing retention policies, refining datasets, or migrating clients, the greatest capacity gains can be made by reviewing these clients.

To increase the number of clients reported in this section, append the capacity.sh with the 'top' flag. For example: 
capacity.sh --top=20
 

Additional Information

For more information about Avamar capacity management, see KB article 79977: Avamar - Capacity Management Concepts and Training  

To install or update the capacity.sh script:    
  1. Download the latest version of the script from the following link: ftp://avamar_ftp:anonymous@ftp.avamar.com/software/scripts/capacity.sh
  2. Upload the script to the Avamar Utility Node, and place in the /usr/local/avamar/bin directory.
  3. Change the permissions to allow the script to be run:   
chown root:root /usr/local/avamar/bin/capacity.sh
chmod 755 /usr/local/avamar/bin/capacity.sh
  1. Confirm that the permissions are as shown below:   
ls -l /usr/local/avamar/bin/capacity.sh
-rwxr-xr-x 1 root root 13696 Dec 3 08:26 /usr/local/avamar/bin/capacity.sh

Advanced options are found by appending "--help" when running the script. For example:    
capacity.sh --help.

This prints information about the new data added and the data that is removed by garbage collection.

If there are backups going to Data Domain, additional columns are added showing the amount of data is going to Data Domain and to Avamar.

The amount that is scanned and change rate includes both Avamar and Data Domain data. Removed and Net are always only Avamar data.

You can use the --avamar or -ddr flags so that the Scanned and Rate columns will only reflect Avamar or Data Domain information.
  • --version - Display the program version
  • --help - Display the help screen
  • --days=n - Limit data to backups in the past "n" days. Defaults to 14
  • --client=x-  Limit data to backups with clients that contain "x"
  • --domain=x - Limit data to backups in domains that contain "x" --avamar Limit data to backups with Avamar as the target
  • --ddr - Limit data to backups with Data Domain as the target
  • --norepl - Do not include replication backups
  • --gb - Report in GB instead of MB
  • --top=n - Limit large client list to "n." Default 5
  • --start=x - Start report from date mm/dd/yy
  • --end=x - End report on date mm/dd/yy

To obtain a list of all backups on an Avamar or Avamar-DataDomain system, see KB article 19732: Avamar: How to use the dump_root_hashes.rb script to generate a list of clients and backups comparing the content of two Avamar systems and other use cases     

Article Properties


Affected Product

Avamar

Product

Avamar

Last Published Date

10 Mar 2022

Version

5

Article Type

Solution