Avamar VMware stuck snapshots

1. Log in as admin to the utility node
2.  Disable the firewall
• /usr/local/avamar/lib/admin/security/avfirewall stop
3. Download proxycp.jar

• cd /tmp ;   curl -O ftp://avamar_ftp:anonymous@ftp.avamar.com/software/scripts/proxycp.jar 

Using proxycp.jar

To see a list of commands, run the following from the Avamar Utility Node:            
java -jar proxycp.jar


To view VM’s with hidden Snapshot Files, run this command:
java -jar proxycp.jar –listsnapshots 2>/dev/null | grep Snapshot

To remove original disk from the proxy that they were still mounted to, use this command.
java -jar proxycp.jar –listproxydisk –cleanup

Next clean up Avamar only snapshots with this command if any are present
java -jar proxycp.jar –listsnapshots –cleanup

Using the above list you may proceed using the command below to attempt to consolidate the vm’s that are failing.  Warning, proceed with caution.
java -jar proxycp.jar –consolidatesnapshots –vm REPLACEWITHVMNAME



** Thank you Hugh Griffin for the above content. I'm only duplicating content in case EMC decide it is too dangerous for our frail little hands. **

Avamar GEN4 Visio stencil

Looking for Gen4 hardware stencils ?

Just use DELL's stencils.
The utility node is a Dell R710 server , and the storage nodes are R510 servers.

Symmetrix V-Max head / track / cylinder conversion

Symmetrix V-Max
Enginuity Code: 5874
Includes EMC Symmetrix V-Max and various different configurations within this model.
GB = Cylinders * 15 * 128 * 512 / 1024 / 1024 / 1024
Eg: 262668 Cylinder device equates to 240.47 GB of usable data
262668 * 15 * 128 * 512 / 1024 / 1024 / 1024 = 240.47 GB

Cylinders = GB / 15 / 128 / 512 * 1024 * 1024 * 1024
15 = tracks per cylinder
128 = blocks per track
512 = bytes per block
8 bytes = 520-512 used for T10-DIF
1024 = conversions of bytes to kb to mb to gb
Drive format on a V-Max is 520 bytes, out of which 8 bytes are used for T10-DIF ( A post on DMX-4 and V-Max differences).


(Thank you storagenerve.com)

Avamar 7.0.1 - Disabled groups are being reported as failed

Since the last version of Avamar, any clients located within a disabled backup group are now
being reported as "Failed" in the daily  summary. This is good if for some reason you forgot to re-enable a group after a temporary exclusion, but very annoying if you have groups disabled for some good reasons.

This behavior can be change in the mcserver.xml file ( Please be careful ):

1. Make a backup of mcserver.xml just in case.

cp -p /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml /usr/local/avamar/var/mc/server_data/prefs/x-mcserver.bak20140923

2. Edit the mcserver.xml file

vi /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml

3. Change this key from true to false

<entry key="report_disabled_client_job_as_fail" value="false" />

4. Restart MCS and the backup scheduler

dpnctl stop mcs; dpnctl start mcs; dpnctl start sched

Avamar error - Error writing 32-byte header to cache file

You most likely have "avtar.exe" process stucks. This seem to be happenning the most often on MSSQL clients.

Kill them, and restarts Avamar services.

Avamar - MCCLI - 1,22801,User login failure.

After running /usr/local/avamar/7.0.1-61/bin/avsetup_mccli for the first time, if you make an error in your setup, it will never go back and update files in your home ~/.avamardata/* correctly.


Fix:

1. delete ~/.avamardata/* OR:
2. manually update ~/.avamardata/7.0.1-61/var/mc/cli_data/prefs/mcclimcs.xml with the correct information.

How to suppress errors and backup exceptions in Avamar Activity and enterprise manager

So you don't want to know about a certain error, or the administrator of that system is not helping you solve this backup problem ?

No problem, just do the following so it will not appear in your "failed" list:

Go to the AVAMAR_INSTALL_PATH\avs\var directory 
Create a file named avtar.cmd

Append the following in it (replace 30901 with the error code you want to suppress):

--downgrade-error-codes="30901"