Avamar Proxy Causing Disk Consolidation Errors
Versions used are: Avamar 19.2 vCenter 6.7
Issue:
Disk consolidation is needed on multiple VMs. When an attempt is made to consolidate, it fails with locked file. You investigate which file is locked.
Step 1:
User right click Name-O-Server
Step 2:
Left click “Snapshot” then “Consolidate”
Below, in the “Resent Tasks” you will get the following error:
- Step 3:
User left click on “Edit Settings…
Step 4:
User left click Hard Disks arrow and searches for the locked disk file.
Step 5:
Step 6:
Expand to find the locked file, it will end with several zeros and a number.
Step 7:
User right click PROXY-03
Step 8:
User left click on “Edit Settings…
Step 9:
User left click on “Yes (button)”
Step 10:
The first two hard drives are the proxy’s normal number of hard drives. This is the amount of disk when the proxy is not currently being used for backup. When the backup process starts the proxy snapshots the VM to be backed up and then mounts the snapshot to the proxy creating multiple hard drives. It can have multiple drives from multiple VMs mounted to the proxy. This locks the original VM’s disk that it is backing up. This disk can be identified by its name ending with leading zeros and a number as seen in Step 5.
In this case (below) I have already deleted the disc from the proxy before I thought to make this document, but the process below is the same.
Step 11:
Go through each hard drive an find the one you need to consolidate. Left click in the “X” next to the drive of the mounted hard disk of the VM that is locked by this proxy. You can see the name of the mounted VM to the right of “Disk File”.
WARNING: 1. Only click the “X”, do not delete from Datastore! This will delete it from the original VM and break the server! 2. Make sure that the disk chosen to delete is not currently running as a backup job in Avamar. You need to cancel the backup in Avamar first then you can delete from proxy.
Step 12:
User left click on “OK (button)”
Step 13:
Go back to step 2 and re-attempt to consolidate disk which will succeed now.
Step 14:
We now need to clean up the proxy to prevent this from happening the next day. Open a console connection to the proxy. Putty or in my case SecureCRT either way the results will be the same.
Step 15:
Unless you modified it, the default username is: admin password is: avam@r
Step 16:
Below is a copy of a session. The task is to delete any directory from the /tmp directory that starts with vmware-root_ and ends with random numbers.
admin@PROXY-03:~> su
Password: avam@r
PROXY-03:/home/admin # ls
.bash_history .bash_profile .bashrc .bashrc.avbkup .config .emacs .fonts .inputrc .local .muttrc .profile bin
PROXY-03:/home/admin # cd ..
PROXY-03:/home # cd ..
PROXY-03:/ # ls
.snapshots bin boot data01 dev etc extra home lib lib64 mnt opt proc root run sbin selinux space srv sys tmp usr var
PROXY-03:/ # cd tmp/
PROXY-03:/tmp # ls
.ICE-unix .XIM-unix .font-unix WEB-INF hostname.txt patch security_update.log vmware-config-21953.0 vmware-root_31401-3988572629
.Test-unix .cimple .tmp_avamar av_fstab.log hsperfdata_root patch.log sfcbLocalSocket vmware-root zypper-kernel-log
.X11-unix .cimplerc CIM.log avpkgkey.pub netconfig.log proxy-init.txt systemd-rollup-log vmware-root_1190-2697663874
PROXY-03:/tmp # rmdir vmware-root_1190-2697663874/
PROXY-03:/tmp # rmdir vmware-root_31401-3988572629/
PROXY-03:/tmp # ls
.ICE-unix .X11-unix .cimple .font-unix CIM.log av_fstab.log hostname.txt netconfig.log patch.log security_update.log systemd-rollup-log vmware-root
.Test-unix .XIM-unix .cimplerc .tmp_avamar WEB-INF avpkgkey.pub hsperfdata_root patch proxy-init.txt sfcbLocalSocket vmware-config-21953.0 zypper-kernel-log
