Avamar: How to disable SnapshotManager on the Avamar proxy
Summary: This article describes how to disable the SnapshotManager feature on the Avamar proxy
Symptoms
Avamar Image backup or restore jobs are failing/slow due to SnapShotManager operations.
Cause
-
The SnapshotManager is a web service that operates on the Avamar server.
-
During backup or restore operations, when the Avamar proxy performs a snapshot operation (create, delete, or consolidate), it uses SnapshotManager service.
-
This approach centralizes snapshot operations, allowing them to be queued on the Avamar server instead of vCenter.
To check the SnapshotManager status, follow these steps:
If SnapshotManager is enabled, the image backup log displays the following information:
avvcbimage Info <42215>: SnapshotManager: initializing at Avamarserver:443, vCenter vc6-avamar.example.com(root), datacenter(/Burlington), httpsTimeout_ms(3600000), maxDeleteRetries(-1)
avvcbimage Info <42191>: GET: curl_easy_getinfo succeeded with httpcode(200)
avvcbimage Info <44033>: AvSnapMgr::getData Succeeded httpCode: 200
If SnapshotManager is disabled, the image backup log shows:
avvcbimage Info <40643>: NOT using SnapShot Manager - using proxy method of calling vSphere API functions.
avvcbimage Info <18648>: The snapshot '' could not be removed.
Resolution
Long-term Solution:
This issue will be addressed in a future Avamar release. In future versions of Avamar, the Avamar proxy will not use SnapshotManager service.
How to Disable Snapshot Manager in Current Release:
To disable the SnapshotManager service, modify the proxy's avvcbimageAll.cmd using one of these two methods:
Automated method using goav:
1. Install goav using Avamar: GoAV Product Tool for Management and Troubleshooting
2. Run this GoAV command to comment snapshotmanager lines on all proxies:
admin@ave197:~/>: ./goav proxy snapshotmanager disable
===========================================================
GoAv : 1.47
Avamar : 19.7
Date : 26 Jan 2023 09:50 EST
===========================================================
COMMAND : ./goav proxy snapshotmanager disable
NOTE: This is not an official tool
===========================================================
Disable SnapshotManager on proxies[==================> ] Proxy:194proxy-cloud.burlington.lab is not accessible.
Disable SnapshotManager on proxies[========> ] Proxy:av194proxy-phil is not accessible.
Disable SnapshotManager on proxies[===================>] Proxy:192proxy.burlington.lab is not accessible.
Disable SnapshotManager on proxies[==============> ] ============== av193proxy-phil=========================
Executing sed -i 's/--snapshotManager/#--snapshotManager/' /usr/local/avamarclient/{etc,var}/{initproxyappliance.sh,avvcbimageAll.cmd} /etc/rc.d/initproxyappliance 2>/dev/null on av193proxy-phil
Disable SnapshotManager on proxies[===> ] ============== 197proxyga.burlington.lab=========================
Executing sed -i 's/--snapshotManager/#--snapshotManager/' /usr/local/avamarclient/{etc,var}/{initproxyappliance.sh,avvcbimageAll.cmd} /etc/rc.d/initproxyappliance 2>/dev/null on 197proxyga.burlington.lab
Disable SnapshotManager on proxies[============> ] ============== 194proxyga.burlington.lab=========================
Executing sed -i 's/--snapshotManager/#--snapshotManager/' /usr/local/avamarclient/{etc,var}/{initproxyappliance.sh,avvcbimageAll.cmd} /etc/rc.d/initproxyappliance 2>/dev/null on 194proxyga.burlington.lab
Disable SnapshotManager on proxies[=> ] ============== 197proxy.burlington.lab=========================
Executing sed -i 's/--snapshotManager/#--snapshotManager/' /usr/local/avamarclient/{etc,var}/{initproxyappliance.sh,avvcbimageAll.cmd} /etc/rc.d/initproxyappliance 2>/dev/null on 197proxy.burlington.lab
Manual method:
1. SSH into the Avamar proxy
2. Run the following command to comment out the snapshotmanager lines in avvcbimageAll.cmd files:
sed -i 's/--snapshotManager/#--snapshotManager/' /usr/local/avamarclient/{etc,var}/{initproxyappliance.sh,avvcbimageAll.cmd} /etc/rc.d/initproxyappliance 2>/dev/null