How to calculate FETB: frontend protected capacity by terabyte

frontend protected capacity that DPA can show with one of its default reports (per whole server or individually per client) is the same data that also the Networker nsrcapinfo command would report on the backup server itself.

However be ware what that actually reports. It is the largest backup for said client in the last 60 days. It does not say anything directly about how much data you actually protect nor about how much backup media capacity you would need to actually store that data, as for tape that would be completely different than for a Data Domain deduplication appliance. For NW you can create a mminfo query to calculate and add up per pool all savesets that have not yet expired per pool. Ideally that also should more or less match "mminfo -am - q <POOL>" output for each pool wrg to the amount of data in each pool.

https://www.dell.com/support/kbdoc/en-us/000029555/esg118514-networker-source-capacity-licensing-how-to-calculate-source-capacity?lang=en "NetWorker Source Capacity Licensing - How to calculate source capacity."

for NW vproxy based image level backups of vmware vm's https://www.dell.com/support/kbdoc/en-us/000228905/nvp-vproxy-nsrcapinfo-is-reporting-the-provisioned-size-of-vms?lang=en "NVP vProxy: nsrcapinfo is Reporting the Provisioned Size of VMs".

For DPA, did you read https://www.dell.com/support/manuals/en-us/data-protection-advisor/dpa_19.9_rrg/data-protection-suite-estimated-protected-capacity?guid=guid-5c7f249a-74b0-4dc1-a85e-7fc3c352fdf4&lang=en-us about "Data Protection Suite Estimated Protected Capacity"?

you can use a simple script like this mminfo_capacity_check.sh :

# define function
nsr_func(){
/usr/sbin/nsradmin -i - <<EOF
. type:nsr pool
show name
print
EOF
}

nsr_func|grep -iv query|cut -d':' -f2|cut -s -d';' -f1|sort > all_pools.log

cat all_pools.log| while read POOL
do
echo amount of data in GB for pool $POOL:
mminfo -q pool="${POOL},!ssrecycle" -oRt -r "totalsize,ssid" 2>/dev/null |sort -u| \
#/usr/xpg4/bin/awk 'BEGIN \
awk 'BEGIN \
                        { total_bytes = 0; total_gb = 0 } \
                        { total_bytes += $1 } \
                    END { \
                        if (total_bytes > 0) { total_gb = (total_bytes / (1024*1024*1024)) }
                        if (total_gb > 0) {  \
                            printf "%8d", total_gb "bytes"
                        } else { \
                            printf "No information for this query\n" \
                        }
                    }'

echo
echo total amount of data in pool, also stating expired data
mminfo -am -q pool=${POOL}
echo "******************************************************"
done

It calculates all savesets per pool, but also shows info about the pool itself. if that does not match more or less, then it might be an indication that data is not properly expired, which can occur as NW will not perform expiration if the device is being read from when it runs the index maintenance.

Setting the NW debug option /nsr/debug/recover_space_anytime (simply touch an empty file with that name) makes NW always perform the expiration of a device regardless if it is being read from.

PPDM is lacking on that end. For proper billing Dell is creating a separate tool to collect that data and report about it. So - weirdly - they don't even use DPA for that unlike is the case with Networker and Avamar.