Proxycp.jar
java -jar proxycp.jar –listdatastoremap
To correct a mismapped datastore, run the following command to refresh all known datastores.:
# java -jar proxycp.jar –selectalldatastore
Your additional command which I was not aware of is very useful
#java -jar proxycp.jar –selecthotaddstore
java -jar proxycp.jar –help will give you additional commands.
LISTVM
This option allows to List all the Virtual Machine protected by Avamar
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --listvm
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 8:44:10 AM PST
COMMAND : java -jar proxycp.jar --listvm
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
========================== Vms ==========================
AEESX-Proxy /aevc1.asl.lab.emc.com/ContainerClients/AEESX-Proxy
aevm41-Amol-DDVE /aevc1.asl.lab.emc.com/ContainerClients/aevm41-Amol-DDVE
aevm9xx-Amol-BC-W2k8R2 /aevc1.asl.lab.emc.com/VirtualMachines/aevm9xx-Amol-BC-W2k8R2
CloneBackupMeUp /aevc1.asl.lab.emc.com/ContainerClients/CloneBackupMeUp
HWproxy /aevc1.asl.lab.emc.com/ContainerClients/HWproxy
========================== Done =============================
LISTPROXY
This option allows you to List all the Proxies, By default it will list Single instance, use –all to list all the proxy instances
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --listproxy
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 9:34:27 AM PST
COMMAND : java -jar proxycp.jar --listproxy
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Listing single instace of a Proxy, use --all to list all the instances
========================== Proxies ==========================
/clients/aevm37-proxy-1 8 instance(s)
========================== Done =============================
GETLOGS
This option allows to collect Logs from the Proxy, By default the logs will be stored in/home/admin/proxycp/[proxyname]/[proxyname].YYYY-MM-DD.tar.gz
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --getlogs --proxy aevm37-proxy-1
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 9:37:38 AM PST
COMMAND : java -jar proxycp.jar --getlogs --proxy aevm37-proxy-1
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
================== aevm37-proxy-1 ====================nslookup
Executing : aevm37-proxy-1
tar -vczf ~/aevm37-proxy-1.2014-02-14.tar.gz --directory '/usr/local/avamarclient/' var-proxy-1 bin/MountPoint/mount/ bin/MountPoint/logs/ bin/MountPoint/results bin/logs/ var/ --exclude='*.gz' --exclude='*.dat'
var-proxy-1/
var-proxy-1/avagent_8.log
var-proxy-1/avagent_5.log
var-proxy-1/avagent.lck
var-proxy-1/avagent_1.log
var-proxy-1/vddkconfig.ini
var-proxy-1/vmware/
var-proxy-1/vmware/metadata/
var-proxy-1/vmware/metadata/VMFiles/
var-proxy-1/vmware/metadata/VMFiles/4/
var-proxy-1/vmware/metadata/VMFiles/4/attributes.xml
var-proxy-1/vmware/metadata/VMFiles/2/
var-proxy-1/vmware/metadata/VMFiles/2/attributes.xml
var-proxy-1/vmware/metadata/VMFiles/3/
var-proxy-1/vmware/metadata/VMFiles/3/attributes.xml
var-proxy-1/vmware/metadata/VMFiles/1/
var-proxy-1/vmware/metadata/VMFiles/1/attributes.xml
var-proxy-1/vmware/metadata/VMConfiguration/
var-proxy-1/vmware/metadata/VMConfiguration/vm.nvram
var-proxy-1/vmware/metadata/VMConfiguration/vm.vmx
var-proxy-1/vmware/temp/
var-proxy-1/avagent_0.log
var-proxy-1/avagent_7.log
var-proxy-1/avagent.log
var-proxy-1/cid.bin
var-proxy-1/avagent.cmd
var-proxy-1/clientlogs/
var-proxy-1/avagent_6.log
var-proxy-1/MOD-1392064051303-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
var-proxy-1/avvcbimage.cmd
var-proxy-1/MOD-1392064051303-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
var-proxy-1/avvmwfile.cmd
var-proxy-1/avagent_4.log
var-proxy-1/avagent_10.log
var-proxy-1/avagent_3.log
var-proxy-1/avagent_9.log
var-proxy-1/avagent.cfg
tar: bin/MountPoint/mount: Cannot stat: No such file or directory
tar: bin/MountPoint/logs: Cannot stat: No such file or directory
tar: bin/MountPoint/results: Cannot stat: No such file or directory
bin/logs/
bin/logs/VSphereVersion.log
bin/logs/VmwareFlr.log.78
bin/logs/VmwareFlr.log
bin/logs/VmwareFlrWs.log.19
bin/logs/VmwareFlr.log.77
bin/logs/VSphereWebService.log
bin/logs/VmMgr.log
bin/logs/VixInterface.log
bin/logs/VmwareFlrWs.log.20
bin/logs/MountMgr.log
bin/logs/VmwareFlrWs.log
var/
var/avagentAll.cmd
var/flag-registered
var/vddkconfig.ini
var/vmware/
var/avvcbimageAll.cmd
var/avvcbimage.cmd
var/avvmwfile.cmd
var/avvmwfileAll.cmd
tar: Error exit delayed from previous errors
Error while executing remote command....
================== aevm37-proxy-1 ====================
Local File name : /home/admin/proxycp/aevm37-proxy-1/aevm37-proxy-1.2014-02-14.tar.gz
Remote File Name : /root/aevm37-proxy-1.2014-02-14.tar.gz
Getting File....
Checking MD5Sum on remote file : /root/aevm37-proxy-1.2014-02-14.tar.gz
MD5Sum : 80239a7a3a684ef784ded50d9ba278b5
Tranfer in Progress, please wait
Checking MD5SUM on local file :/home/admin/proxycp/aevm37-proxy-1/aevm37-proxy-1.2014-02-14.tar.gz
MD5SUM : 80239a7a3a684ef784ded50d9ba278b5
MD5Sum check succeeded
Tranfer Completed
Recieved : Successful
Executing : rm -rf /root/aevm37-proxy-1.2014-02-14.tar.gz
Deleted :true
--------------------------------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : February 14, 2014 9:38:17 AM PST
GETVCLOGS
This option allows to Fetch the Logs from Vcenter
By default vpxd logs are fetched from the vcenter
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --getvclogs
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 9:42:14 AM PST
COMMAND : java -jar proxycp.jar --getvclogs
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Please wait fetching aevc1.asl.lab.emc.com-vpxd-2857.log from vCenter
Log file saved ==> "/usr/local/avamar/var/log/aevc1.asl.lab.emc.com-vpxd-2857.log"
Please wait fetching aevc1.asl.lab.emc.com-vpxd-2858.log from vCenter
Log file saved ==> "/usr/local/avamar/var/log/aevc1.asl.lab.emc.com-vpxd-2858.log"
To Fetch the HostD & Vmkernel log, please specify –vm VMNAME
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --getvclogs --vm CloneBackupMeUp
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 9:44:05 AM PST
COMMAND : java -jar proxycp.jar --getvclogs --vm CloneBackupMeUp
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Please wait fetching CloneBackupMeUp-hostd.log from vCenter
Log file saved ==> "/usr/local/avamar/var/log/CloneBackupMeUp-hostd.log"
Please wait fetching CloneBackupMeUp-vmkernel from vCenter
Log file saved ==> "/usr/local/avamar/var/log/CloneBackupMeUp-vmkernel"
GETVMLOGS
Virtual Machine backup/restore logs are stored on different proxies, This option allows to fetch logs for a particular VM from all the proxies
–days [Number_of_days] days worth of log can be fetches , Maximum 15 days can be specified
Logs are stored in /home/admin/proxycp/[VMNAME]
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --getvmlogs --vm aevm9xx-Amol-BC-W2k8R2
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 9:52:09 AM PST
COMMAND : java -jar proxycp.jar --getvmlogs --vm aevm9xx-Amol-BC-W2k8R2
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
VM Name :aevm9xx-Amol-BC-W2k8R2
Log Days :15
================== aevm37-proxy-6 ====================
Tranfer in Progress, please wait
scp: /usr/local/avamarclient/var-proxy-6/MOD-1392164899429-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log: No such file or directory
Got : /usr/local/avamarclient/var-proxy-6/MOD-1392164899429-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log
Got : /usr/local/avamarclient/var-proxy-6/MOD-1392164899429-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
Got : /usr/local/avamarclient/var-proxy-6/MOD-1392164899429-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
scp: /usr/local/avamarclient/var-proxy-6/MOD-1392164587492-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log: No such file or directory
Got : /usr/local/avamarclient/var-proxy-6/MOD-1392164587492-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log
Got : /usr/local/avamarclient/var-proxy-6/MOD-1392164587492-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
Got : /usr/local/avamarclient/var-proxy-6/MOD-1392164587492-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
Got All the Files from "aevm37-proxy-6" in "/home/admin/proxycp/aevm9xx-Amol-BC-W2k8R2"
================== aevm37-proxy-1 ====================
Tranfer in Progress, please wait
scp: /usr/local/avamarclient/var-proxy-1/MOD-1392064051303-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log: No such file or directory
Got : /usr/local/avamarclient/var-proxy-1/MOD-1392064051303-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log
Got : /usr/local/avamarclient/var-proxy-1/MOD-1392064051303-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
Got : /usr/local/avamarclient/var-proxy-1/MOD-1392064051303-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
Got All the Files from "aevm37-proxy-1" in "/home/admin/proxycp/aevm9xx-Amol-BC-W2k8R2"
================== aevm37-proxy-2 ====================
Tranfer in Progress, please wait
scp: /usr/local/avamarclient/var-proxy-2/MOD-1391799894464-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log: No such file or directory
Got : /usr/local/avamarclient/var-proxy-2/MOD-1391799894464-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log
Got : /usr/local/avamarclient/var-proxy-2/MOD-1391799894464-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
Got : /usr/local/avamarclient/var-proxy-2/MOD-1391799894464-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
scp: /usr/local/avamarclient/var-proxy-2/MOD-1391799928493-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log: No such file or directory
Got : /usr/local/avamarclient/var-proxy-2/MOD-1391799928493-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log
Got : /usr/local/avamarclient/var-proxy-2/MOD-1391799928493-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
Got : /usr/local/avamarclient/var-proxy-2/MOD-1391799928493-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
Got All the Files from "aevm37-proxy-2" in "/home/admin/proxycp/aevm9xx-Amol-BC-W2k8R2"
================== aevm37-proxy-7 ====================
Tranfer in Progress, please wait
Got : /usr/local/avamarclient/var-proxy-7/MOD-1391799239945-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log
Got : /usr/local/avamarclient/var-proxy-7/MOD-1391799239945-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
Got : /usr/local/avamarclient/var-proxy-7/MOD-1391799239945-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
Got : /usr/local/avamarclient/var-proxy-7/MOD-1391799508985-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew_avtar.log
Got : /usr/local/avamarclient/var-proxy-7/MOD-1391799508985-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.log
Got : /usr/local/avamarclient/var-proxy-7/MOD-1391799508985-40c40ca1859a96c084dffb442b68c9077e1185c0-3016-vmimagew.alg
Got All the Files from "aevm37-proxy-7" in "/home/admin/proxycp/aevm9xx-Amol-BC-W2k8R2"
--------------------------------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : February 14, 2014 9:52:17 AM PST
PORTCHECK
This option will test all the available port requirement for Vmware Backups
Following requirement will be tested
Proxy --> MCS : 28001
Proxy --> DATA Nodes : 27000,29000
Proxy --> Vcenter : 443
Proxy --> ESX HOST(S) : 902
Proxy --> Data Domain : 2049,2052
Proxy --> All above can be Resolved or Not
Following example shows that the sample report
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --portcheck
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 9:56:46 AM PST
COMMAND : java -jar proxycp.jar --portcheck
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Fetching Avamar Name/IPAddress of Utility Node & Data Nodes
--------------------------------------------------------------------------------------------------------------
Aavamar Node(s) : aevm40.asl.lab.emc.com
Total Node(s) : 1
--------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------
Data Domain : aedd2.asl.lab.emc.com
Total DD(s) : 1
--------------------------------------------------------------------------------------------------------------
Vcenter : aevc1.asl.lab.emc.com
--------------------------------------------------------------------------------------------------------------
ESX Host : aeesxg.asl.lab.emc.com
ESX Host : aeesxh.asl.lab.emc.com
ESX Host : aeesxe.asl.lab.emc.com
ESX Host : aeesxd.asl.lab.emc.com
ESX Host : aeesxi.asl.lab.emc.com
ESX Host : aeesx9.asl.lab.emc.com
ESX Host : aeesxb.asl.lab.emc.com
ESX Host : aeesx7.asl.lab.emc.com
ESX Host : aeesx8.asl.lab.emc.com
--------------------------------------------------------------------------------------------------------------
Proxy : /clients/aevm37-proxy-3 (aevm37.asl.lab.emc.com)
Proxy : /clients/aevm37-proxy-5 (aevm37.asl.lab.emc.com)
Proxy : /clients/aevm37-proxy-8 (aevm37.asl.lab.emc.com)
Proxy : /clients/aevm37-proxy-7 (aevm37.asl.lab.emc.com)
Proxy : /clients/aevm37-proxy-6 (aevm37.asl.lab.emc.com)
Proxy : /clients/aevm37-proxy-1 (aevm37.asl.lab.emc.com)
Proxy : /clients/aevm37-proxy-4 (aevm37.asl.lab.emc.com)
Proxy : /clients/aevm37-proxy-2 (aevm37.asl.lab.emc.com)
--------------------------------------------------------------------------------------------------------------
================== /clients/aevm37-proxy-2 ====================
Sending File, Please wait...
========================= /clients/aevm37-proxy-2===========================
MD5Sum :2e23a033b9d2f7f34814dbe46a1807b7
Remote MD5Sum :2e23a033b9d2f7f34814dbe46a1807b7
MD5Sum check succeeded
Successful
================== /clients/aevm37-proxy-2 ====================
Processing, Please wait...
-----------------------------------------------------------------------------------------
R E S U L T S
-----------------------------------------------------------------------------------------
Proxy Destination Blocked Resolvable
-----------------------------------------------------------------------------------------
/clients/aevm37-proxy-2 aevm40.asl.lab.emc.com [29000] true
--------------------------------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : February 14, 2014 9:57:01 AM PST
LISTVCSESSIONS
This option allows to List all the Session of Vcenter
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --listvcsessions
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 10:50:25 AM PST
COMMAND : java -jar proxycp.jar --listvcsessions
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
====================== aevc1.asl.lab.emc.com ============================
Product Name : VMware VirtualCenter Server
Product Version : 5.0
Build Number : 1378903
Active Session(s) : 53
IP UserName Count Last Active
------------------------------------------------------------------------------------
10.6.240.43 Administrator 0 37 Day(s) 22 hr(s) 48 min(s) 40 s
10.6.240.43 Administrator 0 37 Day(s) 22 hr(s) 48 min(s) 39 s
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 46 min(s) 42 s
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 46 min(s) 42 s
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 46 min(s) 41 s
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 46 min(s) 40 s
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 46 min(s) 39 s
10.6.240.43 Administrator 10 37 Day(s) 22 hr(s) 41 min(s) 34 s
10.6.254.217 Administrator 1 29 Day(s) 32 min(s) 48 s
10.6.254.217 Administrator 0 22 Day(s) 23 hr(s) 20 min(s) 26 s
10.64.18.165 Administrator 0 18 Day(s) 4 hr(s) 58 min(s) 56 s
10.64.18.165 Administrator 0 18 Day(s) 4 hr(s) 58 min(s) 54 s
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 7 min(s) 31 s
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 7 min(s) 30 s
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 7 min(s) 29 s
10.6.240.191 Administrator 1 16 Day(s) 1 hr(s) 6 min(s) 54 s
10.6.240.240 Administrator 7 6 Day(s) 23 hr(s) 58 min(s) 10 s
10.6.240.191 Administrator 86 1 Day(s) 22 hr(s) 9 min(s) 59 s
10.6.240.43 Administrator 31 1 Day(s) 19 hr(s) 23 min(s) 7 s
10.6.240.240 Administrator 153 1 Day(s) 15 hr(s) 45 min(s) 56 s
128.222.234.73 Administrator 2653 1 Day(s) 2 hr(s) 47 min(s) 53 s
10.6.240.43 Administrator 259 23 hr(s) 49 min(s) 57 s
10.6.240.250 Administrator 11375 15 hr(s) 52 min(s) Active Session
10.6.240.240 Administrator 354 15 hr(s) 44 min(s) 36 s
10.6.240.240 Administrator 580 15 hr(s) 44 min(s) 35 s
10.64.18.165 Administrator 55 14 hr(s) 51 min(s) 44 s
10.6.240.43 Administrator 388 12 hr(s) 9 min(s) 3 s
10.64.18.165 Administrator 29 7 hr(s) 34 min(s) 45 s
10.64.18.165 Administrator 5 7 hr(s) 34 min(s) 45 s
10.6.254.217 Administrator 1044 5 hr(s) 9 min(s) 14 s
10.6.240.250 Administrator 266 1 hr(s) 47 min(s) 37 s
10.6.242.111 Administrator 0 15 min(s) 32 s
10.6.242.111 Administrator 0 14 min(s) 7 s
10.6.240.250 Administrator 20 14 min(s) 7 s
10.6.242.111 Administrator 0 13 min(s) 3 s
10.6.254.216 Administrator 0 5 min(s) 10 s
10.6.240.250 Administrator 1342 3 min(s) 25 s
10.6.240.250 Administrator 1 21 s
10.6.240.250 Administrator 1 17 s
10.6.240.250 Administrator 1 15 s
10.6.240.43 Administrator 16 Active Session
10.6.254.216 Administrator 2 Active Session
10.6.240.240 Administrator 2433 Active Session
10.6.240.250 Administrator 109362 Active Session
10.6.240.43 Administrator 636256 Active Session
10.6.240.250 Administrator 54400 Active Session
10.6.240.250 Administrator 21977 Active Session
10.6.240.43 Administrator 109301 Active Session
10.6.240.43 Administrator 32 Active Session
10.6.240.250 Administrator 34 Active Session
10.6.240.250 Administrator 629432 Active Session
10.6.254.217 Administrator 19881 Active Session
10.6.240.240 Administrator ( Current ) 0 Active Session
KILLVCSESSIONS
This option allows to terminate oldest sessions from the Vcenter
–maxactive [Number] allows to keep the number of session alive, By Default Active Sessions are not killed
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --killvcsessions --maxactive 15
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 10:55:15 AM PST
COMMAND : java -jar proxycp.jar --killvcsessions --maxactive 15
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
====================== aevc1.asl.lab.emc.com ============================
Product Name : VMware VirtualCenter Server
Product Version : 5.0
Build Number : 1378903
Active Session(s) : 53
IP UserName Count Last Active
------------------------------------------------------------------------------------
10.6.240.43 Administrator 0 37 Day(s) 22 hr(s) 53 min(s) 29 s<--- Kill
10.6.240.43 Administrator 0 37 Day(s) 22 hr(s) 53 min(s) 29 s<--- Kill
10.6.240.43 Administrator 0 37 Day(s) 22 hr(s) 53 min(s) 29 s<--- Kill
10.6.240.43 Administrator 0 37 Day(s) 22 hr(s) 53 min(s) 29 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 32 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 32 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 31 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 31 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 31 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 31 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 30 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 30 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 29 s<--- Kill
10.6.240.8 Administrator 0 37 Day(s) 22 hr(s) 51 min(s) 29 s<--- Kill
10.6.240.43 Administrator 10 37 Day(s) 22 hr(s) 46 min(s) 23 s<--- Kill
10.6.240.43 Administrator 10 37 Day(s) 22 hr(s) 46 min(s) 23 s<--- Kill
10.6.254.217 Administrator 1 29 Day(s) 37 min(s) 38 s <--- Kill
10.6.254.217 Administrator 1 29 Day(s) 37 min(s) 38 s <--- Kill
10.6.254.217 Administrator 0 22 Day(s) 23 hr(s) 25 min(s) 16 s<--- Kill
10.6.254.217 Administrator 0 22 Day(s) 23 hr(s) 25 min(s) 16 s<--- Kill
10.64.18.165 Administrator 0 18 Day(s) 5 hr(s) 3 min(s) 46 s<--- Kill
10.64.18.165 Administrator 0 18 Day(s) 5 hr(s) 3 min(s) 46 s<--- Kill
10.64.18.165 Administrator 0 18 Day(s) 5 hr(s) 3 min(s) 44 s<--- Kill
10.64.18.165 Administrator 0 18 Day(s) 5 hr(s) 3 min(s) 44 s<--- Kill
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 12 min(s) 20 s<--- Kill
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 12 min(s) 20 s<--- Kill
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 12 min(s) 20 s<--- Kill
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 12 min(s) 20 s<--- Kill
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 12 min(s) 19 s<--- Kill
10.6.240.191 Administrator 0 16 Day(s) 1 hr(s) 12 min(s) 19 s<--- Kill
10.6.240.191 Administrator 1 16 Day(s) 1 hr(s) 11 min(s) 44 s<--- Kill
10.6.240.191 Administrator 1 16 Day(s) 1 hr(s) 11 min(s) 44 s<--- Kill
10.6.240.240 Administrator 7 7 Day(s) 3 min(s) Active Session<--- Kill
10.6.240.240 Administrator 7 7 Day(s) 3 min(s) Active Session<--- Skip (Active)
10.6.240.191 Administrator 86 1 Day(s) 22 hr(s) 14 min(s) 49 s<--- Kill
10.6.240.191 Administrator 86 1 Day(s) 22 hr(s) 14 min(s) 49 s<--- Kill
10.6.240.43 Administrator 31 1 Day(s) 19 hr(s) 27 min(s) 57 s<--- Kill
10.6.240.43 Administrator 31 1 Day(s) 19 hr(s) 27 min(s) 57 s<--- Kill
10.6.240.240 Administrator 153 1 Day(s) 15 hr(s) 50 min(s) 45 s<--- Kill
10.6.240.240 Administrator 153 1 Day(s) 15 hr(s) 50 min(s) 45 s<--- Kill
128.222.234.73 Administrator 2653 1 Day(s) 2 hr(s) 52 min(s) 43 s<--- Kill
128.222.234.73 Administrator 2653 1 Day(s) 2 hr(s) 52 min(s) 43 s<--- Kill
10.6.240.250 Administrator 11375 15 hr(s) 56 min(s) 50 s <--- Kill
10.6.240.250 Administrator 11375 15 hr(s) 56 min(s) 50 s <--- Kill
10.6.240.240 Administrator 354 15 hr(s) 49 min(s) 25 s <--- Kill
10.6.240.240 Administrator 354 15 hr(s) 49 min(s) 25 s <--- Kill
10.6.240.240 Administrator 580 15 hr(s) 49 min(s) 25 s <--- Kill
10.6.240.240 Administrator 580 15 hr(s) 49 min(s) 25 s <--- Kill
10.64.18.165 Administrator 55 14 hr(s) 56 min(s) 34 s <--- Kill
10.64.18.165 Administrator 55 14 hr(s) 56 min(s) 34 s <--- Kill
10.6.240.43 Administrator 388 12 hr(s) 13 min(s) 53 s <--- Kill
10.6.240.43 Administrator 388 12 hr(s) 13 min(s) 53 s <--- Kill
10.64.18.165 Administrator 29 7 hr(s) 39 min(s) 35 s <--- Kill
10.64.18.165 Administrator 29 7 hr(s) 39 min(s) 35 s <--- Kill
10.64.18.165 Administrator 5 7 hr(s) 39 min(s) 35 s <--- Kill
10.64.18.165 Administrator 5 7 hr(s) 39 min(s) 35 s <--- Kill
10.6.254.217 Administrator 1044 5 hr(s) 14 min(s) 4 s <--- Kill
10.6.254.217 Administrator 1044 5 hr(s) 14 min(s) 4 s <--- Kill
10.6.240.250 Administrator 266 1 hr(s) 52 min(s) 27 s <--- Kill
10.6.240.250 Administrator 266 1 hr(s) 52 min(s) 27 s <--- Kill
10.6.242.111 Administrator 0 20 min(s) 22 s <--- Kill
10.6.242.111 Administrator 0 20 min(s) 22 s <--- Kill
10.6.242.111 Administrator 0 18 min(s) 57 s <--- Kill
10.6.242.111 Administrator 0 18 min(s) 57 s <--- Kill
10.6.240.250 Administrator 20 18 min(s) 57 s <--- Kill
10.6.240.250 Administrator 20 18 min(s) 57 s <--- Kill
10.6.242.111 Administrator 0 17 min(s) 53 s <--- Kill
10.6.242.111 Administrator 0 17 min(s) 53 s <--- Kill
10.6.254.216 Administrator 0 9 min(s) 59 s <--- Kill
10.6.254.216 Administrator 0 9 min(s) 59 s <--- Kill
10.6.240.250 Administrator 1342 8 min(s) 15 s <--- Kill
10.6.240.250 Administrator 1342 8 min(s) 15 s <--- Kill
10.6.240.250 Administrator 1 5 min(s) 11 s <--- Kill
10.6.240.250 Administrator 1 5 min(s) 11 s <--- Kill
10.6.240.250 Administrator 1 5 min(s) 7 s <--- Kill
10.6.240.250 Administrator 1 5 min(s) 7 s <--- Kill
10.6.240.250 Administrator 1 5 min(s) 4 s <--- Kill
10.6.240.250 Administrator 1 5 min(s) 4 s <--- Kill
10.6.254.216 Administrator 2 2 min(s) 59 s <--- Skip
10.6.254.217 Administrator 19881 Active Session <--- Skip
10.6.240.43 Administrator 265 Active Session <--- Skip
10.6.240.43 Administrator 3 Active Session <--- Skip
10.6.240.240 Administrator 2434 Active Session <--- Skip
10.6.240.43 Administrator 109310 Active Session <--- Skip
10.6.240.250 Administrator 629477 Active Session <--- Skip
10.6.240.250 Administrator 109372 Active Session <--- Skip
10.6.240.43 Administrator 636309 Active Session <--- Skip
10.6.240.250 Administrator 54404 Active Session <--- Skip
10.6.240.250 Administrator 21981 Active Session <--- Skip
10.6.240.43 Administrator 52 Active Session <--- Skip
10.6.240.250 Administrator 42 Active Session <--- Skip
10.6.240.240 Administrator ( Current ) 0 Active Session <--- Skip
Terminating 38 session(s)
TESTCONN
This option allows to test Connectivity for Vcenter
–thread [Number] Concurrent Connections to Vcenter, Default value is 5
–sleep [Number] Amount of time to wait after connection , Default value is 1 Minute
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --testconn
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 10:56:50 AM PST
COMMAND : java -jar proxycp.jar --testconn
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Thread Parameter Not specified, Setting default thread value to 5
Sleep Parameter Not specified, Setting default Sleep value to 1 min
Using Default Vcenter Added to this Avamar Grid
Thread 2 Connected to aevc1.asl.lab.emc.com
Time Taken for Connection : 1 seconds 122 milliseconds
Active Session on VC : 22
Thread 4 Connected to aevc1.asl.lab.emc.com
Time Taken for Connection : 1 seconds 244 milliseconds
Active Session on VC : 23
Thread 1 Connected to aevc1.asl.lab.emc.com
Time Taken for Connection : 1 seconds 371 milliseconds
Active Session on VC : 24
Thread 5 Connected to aevc1.asl.lab.emc.com
Time Taken for Connection : 1 seconds 493 milliseconds
Active Session on VC : 25
Thread 3 Connected to aevc1.asl.lab.emc.com
Time Taken for Connection : 3 seconds 770 milliseconds
Active Session on VC : 26
Time Up... Disconnecting Thread 2
Time Up... Disconnecting Thread 4
Time Up... Disconnecting Thread 1
Time Up... Disconnecting Thread 5
Time Up... Disconnecting Thread 3
HOTADD
This option allows to check if Virtual Machine can use HotAdd transport mode during backup
root@aegrid1:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --hotadd --vm aevm9xx-Win2k3-32 --proxy aevm64-proxy-1
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 11:12:22 AM PST
COMMAND : java -jar proxycp.jar --hotadd --vm aevm9xx-Win2k3-32 --proxy aevm64-proxy-1
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Checking HotAdd Requirement for VM "aevm9xx-Win2k3-32" against Proxy "aevm64-proxy-1"
Please wait...gathering Information
======================== License Information =========================
vCenter Operations Manager-10.6.254.216: Unlicensed
aeesxe.asl.lab.emc.com : esxEnterprisePlus
aeesxg.asl.lab.emc.com : esxEnterprisePlus.vram
vCenter Operations Manager-10.6.196.111: Unlicensed
aeesxi.asl.lab.emc.com : esxEnterprisePlus.vram
aeesx8.asl.lab.emc.com : esxEnterprisePlus
aeesxh.asl.lab.emc.com : esxEnterprisePlus.vram
AEVC1 : vc
aeesx7.asl.lab.emc.com : esxEnterprisePlus
aeesx9.asl.lab.emc.com : esxEnterprisePlus
aeesxb.asl.lab.emc.com : esxEnterprisePlus
aeesxd.asl.lab.emc.com : esxEnterprisePlus
=========================== VM ===========================
Virtual Machine : aevm9xx-Win2k3-32
VM Datacenter : APPENG
ESX Host : aeesx8.asl.lab.emc.com
DataStore Name : Lun04
Free Space : 517 GB
Datastore URL : ds:///vmfs/volumes/50230e06-a6bd0c6c-90ec-0024e87ba3bb/
VMFS Version : 3
Max Block : 256 GB
Block Size : 1
Hardware Version : 7
Disk Type : persistent
File Name : [Lun04] aevm9xx-Win2k3-32/aevm9xx-Win2k3-32.vmdk
Thin Provisioned : false
Total Size (GB) : 8
Disk Size : 8 GB
=========================== Proxy ===========================
UUID : 422bacc6-1eec-bf25-dec3-6b3a4e66d39d
Proxy VM : aevm64.asl.lab.emc.com
Proxy Datacenter : APPENG
Proxy VM ESX Host : aeesx7.asl.lab.emc.com
Host hot Pluggable : true
Proxy VM Datastore Name : Lun04
Proxy VM Free Space : 517 GB
VMFS Version : 3
Max Block : 256 GB
Block Size : 1
Proxy VM DS URL : ds:///vmfs/volumes/50230e06-a6bd0c6c-90ec-0024e87ba3bb/
Hardware Version : 7
Disk Type : persistent
File Name : [Lun04] aevm64.asl.lab.emc.com/aevm64.asl.lab.emc.com-000002.vmdk
Thin Provisioned : false
Disk Type : persistent
File Name : [Lun04] aevm64.asl.lab.emc.com/aevm64.asl.lab.emc.com_1-000002.vmdk
Thin Provisioned : false
Total Size (GB) : 17
=========================== Result ===========================
License Check : P A S S E D
Datacenter Check : P A S S E D
Paravirtual SCSI : P A S S E D
IDE Disk Check : P A S S E D
Hard Disk Count : P A S S E D
Blocksize Check : P A S S E D
VM Hw version Check : P A S S E D
Datastore Selected : P A S S E D
Independent Disk : P A S S E D
Datastore Sharing : P A S S E D
--------------------------------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : February 14, 2014 11:12:28 AM PST
GETVCTASK
This option allows to see the Task Operation from Vcenter
–days [NUM] Days of task info to fetch, Default is 2 days
–current This will show the task visible in Vsphere Client
–cancel [Entity Name] This will cancel the hung activity from Vsphere Client
root@aevm40:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --getvctask
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : February 14, 2014 11:10:16 AM PST
COMMAND : java -jar proxycp.jar --getvctask
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
====================== aevc1.asl.lab.emc.com ============================
Entity Name Task Desc Start Time End Time State Cause
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
vDP com.vmware.vdp.integritycheck Fri Feb 14 10:58:31 PST 2014 Fri Feb 14 11:00:30 PST 2014 success NA
aevm50-Amol-Nemo com.vmware.vdp.integritycheck Fri Feb 14 08:59:53 PST 2014 Fri Feb 14 09:02:53 PST 2014 success NA
aevm85 Drm.ExecuteVMotionLRO Fri Feb 14 08:21:13 PST 2014 Fri Feb 14 08:21:31 PST 2014 success NA
vDP com.vmware.vdp.integritycheck Thu Feb 13 10:59:33 PST 2014 Thu Feb 13 11:00:33 PST 2014 success NA
aevm50-Amol-Nemo com.vmware.vdp.integritycheck Thu Feb 13 08:59:25 PST 2014 Thu Feb 13 09:01:25 PST 2014 success NA
avamarproxy5u Drm.ExecuteVMotionLRO Thu Feb 13 03:56:10 PST 2014 Thu Feb 13 03:56:29 PST 2014 success NA
aevm85 Drm.ExecuteVMotionLRO Thu Feb 13 03:51:10 PST 2014 Thu Feb 13 03:51:34 PST 2014 success NA
aevm83 Drm.ExecuteVMotionLRO Thu Feb 13 03:41:10 PST 2014 Thu Feb 13 03:41:31 PST 2014 success NA
aevm90-Amol-DC Drm.ExecuteVMotionLRO Wed Feb 12 12:40:10 PST 2014 Wed Feb 12 12:40:24 PST 2014 success NA
vDP com.vmware.vdp.integritycheck Fri Feb 14 10:58:31 PST 2014 Fri Feb 14 11:00:30 PST 2014 success NA
aevm50-Amol-Nemo com.vmware.vdp.integritycheck Fri Feb 14 08:59:53 PST 2014 Fri Feb 14 09:02:53 PST 2014 success NA
aevm85 Drm.ExecuteVMotionLRO Fri Feb 14 08:21:13 PST 2014 Fri Feb 14 08:21:31 PST 2014 success NA
vDP com.vmware.vdp.integritycheck Thu Feb 13 10:59:33 PST 2014 Thu Feb 13 11:00:33 PST 2014 success NA
aevm50-Amol-Nemo com.vmware.vdp.integritycheck Thu Feb 13 08:59:25 PST 2014 Thu Feb 13 09:01:25 PST 2014 success NA
avamarproxy5u Drm.ExecuteVMotionLRO Thu Feb 13 03:56:10 PST 2014 Thu Feb 13 03:56:29 PST 2014 success NA
aevm85 Drm.ExecuteVMotionLRO Thu Feb 13 03:51:10 PST 2014 Thu Feb 13 03:51:34 PST 2014 success NA
aevm83 Drm.ExecuteVMotionLRO Thu Feb 13 03:41:10 PST 2014 Thu Feb 13 03:41:31 PST 2014 success NA
aevm90-Amol-DC Drm.ExecuteVMotionLRO Wed Feb 12 12:40:10 PST 2014 Wed Feb 12 12:40:24 PST 2014 success NA
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : February 14, 2014 11:10:21 AM PST
CBTSTATUS
This option allows lets you review Vmware CBT status
Specifying no option will display every vm cbt status
--enablecbt --vm [vmnAme]
--disablecbt --vm
--enablecbt --Filename VM_List_File
The following show an example of enabling CBT on a vm
root@ave70SP1DA:~/#: java -jar proxycp.jar --cbtstatus --enablecbt --vm "Windows 2008 R2 64"
======================= Starting ProxyCP ==========================
Proxycp : v1.85
Date : February 14, 2014 3:36:21 PM EST
COMMAND : java -jar proxycp.jar --cbtstatus --enablecbt --vm Windows 2008 R2 64
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
VM Name(Avamar) : Windows 2008 R2 64
VM Name(Vmware) : Windows 2008 R2 64
CBT Enabled : false
Hardware Version : 7
Disk Type : persistent
File Name : [Avamar VMFS1] Windows 2008 R2 64 /Windows 2008 R2 64 .vmdk
Thin Provisioned : true
Total Size (GB) : 40
Enabling CBT for : Windows 2008 R2 64
------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : February 14, 2014 3:36:28 PM EST
proxycp.jar –cbtstatus –disablecbt –vm
Consolidate Snapshots
This option is is used for Consolidating the Snapshots for a Virtual Machine, ProxyCP will not consolidate snapshot of “Customer Create” snapshots are found
It is recommended to run –listproxydisk –cleanup option before running consolidation, this option will detach the snapshot from the proxy if found attached.
–vm [VM_Name] option can be specified to consolidate snapshot for a given Virtual Machine
–force By Default ProxyCP will skip the consolidation if no-hidden snapshots are found, using this option it will forcefully perform consolidation
–deleteexistingsnapshots [In order to consolidate snapshot, all the snapshot need to be removed. If customer created snapshots are found ProxyCP will skip the VM, by providing this option it will delete customer created snapshots
======================= Starting ProxyCP ==========================
Proxycp : v1.86
Date : April 7, 2014 11:14:04 AM PDT
COMMAND : java -jar proxycp.jar --consolidatesnapshots --vm aevm9xx-Win2k3-32 --force
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
It is recommended that you run '--listproxydisk --cleanup' option before consolildation, Please 'CTRL C' to exit, waiting 10 seconds
VM Name(Avamar) : aevm9xx-Win2k3-32
VM Name(Vmware) : aevm9xx-Win2k3-32
Snapshot Name : No Snapshots
Consolidating Snaphot by "Taking new Snapshot & Deleting All Snapshot" !!
Please be patient, It might take a while !!!
--force
101% ################################################## /
Snapshot "Avamar-Proxycp" was created.
Removing All the snapshots, Please wait !!
101% ################################################## /
Removed All Snapshots : Time taken : 6 Sec 114 ms
Categories
paulsbestscriptlets 