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.
Some article numbers may have changed. If this isn't what you're looking for, try searching all articles. Search articles

How to identify Avamar clients which have breached the backup soft limit (soft_quota_exceeded)

Summary: This article describes how to identify Avamar clients which have breached the backup soft limit. The limit is also known as soft_quota_exceeded.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content


Instructions

Avamar v7 introduces the concept of client 'hard' and 'soft' quotas, 

When a client breaches a hard limit

The Avamar Management Console Service (MCS) cancels the backup. The client log reports:
avtar Info <5314>: Command failed (1 warning, exit code 10019: externally cancelled by Administrator)

The client has no concept of quotas, they are managed by the Avamar MCS.

The backup activity's hard_quota_exceeded flag in the MCDB activities table is tagged as true.

The Activity monitor reports 'Hard limit exceeded'.

The Activity monitor reports 'Hard limit exceeded'.

There is a report filter to allow effective reporting of clients whose hard limit has been exceeded.

filter to allow effective reporting of clients whose hard limit has been exceeded

When a client breaches a soft limit

The backup is allowed to continue running naturally.

There is no indication in the client logs of a quota breach.

The Activity monitor does not report that the soft limit has been exceeded.

The activity report contains a column for soft_quota_exceeded at the right-hand side. It is not possible to filter for this column, the report must be manually sorted.

The activity report contains a column for soft_quota_exceeded at the far right hand side, however it is not currently possible to filter for this column and can only be manually sorted.

To identify Avamar clients which have breached the backup soft limit,

Either:
  • Sort the activity reports using the soft_quota_exceeded column
  • OR connect to the Avamar Postgresql MCDB database and run an appropriate SELECT query.
Example:
1. Connect from the Avamar Utility Node command line:
psql mcdb -p 5555 -U admin

2. Run a query to show client activities which breached their soft quota.
mcdb=# select client_name, completed_ts, bytes_scanned, bytes_new,  bytes_modified_sent, hard_quota_exceeded, soft_quota_exceeded from activities where soft_quota_exceeded=true;
        client_name         |      completed_ts       | bytes_scanned | bytes_new  | bytes_modified_sent | hard_quota_exceeded | soft_quota_exceeded
----------------------------+-------------------------+---------------+------------+---------------------+---------------------+---------------------
 testclient.avamar.com | 2013-12-30 12:58:31.14  |    7094762974 |     242833 |              131489 | f                   | t
 testclient.avamar.com | 2013-12-30 14:52:42.995 |    7548942467 |    1245137 |              286313 | f                   | t
 testclient.avamar.com | 2013-12-30 14:12:49.359 |    7095146514 |    3664973 |              144530 | f                   | t
 testclient.avamar.com | 2013-12-30 14:13:46.753 |    7095023064 |    1601981 |               36150 | f                   | t
 testclient.avamar.com | 2013-12-30 14:18:47.076 |    7541705632 |     127051 |               19644 | f                   | t
 testclient.avamar.com | 2013-12-30 14:16:09.359 |    7541705836 |  435203276 |               62833 | f                   | t
 testclient.avamar.com | 2013-12-30 14:20:40.637 |    7548945327 |    2050805 |             1760101 | f                   | t
 testclient.avamar.com | 2013-12-30 15:11:52.415 |    8952385028 | 1180518706 |           165100707 | f                   | t

 
 

Additional Information

Article Properties


Affected Product

Avamar

Product

Avamar

Last Published Date

15 Aug 2023

Version

3

Article Type

How To