You need to provide complete path of the VM in the file.

Note : Make sure to use the latest version from the FTP

root@aegrid1:~/#: cat /tmp/retirevmlist.txt
/aevc1.asl.lab.emc.com/VirtualMachines/Backmeup3
/aevc1.asl.lab.emc.com/VirtualMachines/Backmeup5
/aevc1.asl.lab.emc.com/VirtualMachines/Backmeup7
/aevc1.asl.lab.emc.com/VirtualMachines/Backmeup4
root@aegrid1:~/#: java -jar /usr/local/avamar/bin/proxycp.jar --retirevms --filename /tmp/retirevmlist.txt
======================= Starting ProxyCP ==========================
Proxycp : v2.64
Date    : January 22, 2016 7:12:15 AM PST

COMMAND : java -jar proxycp.jar --retirevms --filename /tmp/retirevmlist.txt

VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Jan 22, 2016 7:12:18 AM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider "JsafeJCE version 5.0" is registered at position 1
Current Backup Expiry date will be preserved
/aevc1.asl.lab.emc.com/VirtualMachines/Backmeup3                      Retired ? /MC_RETIRED/Backmeup32016.01.22.07.12.21
/aevc1.asl.lab.emc.com/VirtualMachines/BackMeUp5                      Retired ? /MC_RETIRED/BackMeUp52016.01.22.07.12.22
/aevc1.asl.lab.emc.com/VirtualMachines/BackmeUp7                      Retired ? /MC_RETIRED/BackmeUp72016.01.22.07.12.22
/aevc1.asl.lab.emc.com/VirtualMachines/Backmeup4                      Retired ? /MC_RETIRED/Backmeup42016.01.22.07.12.22
-------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : January 22, 2016 7:12:23 AM PST

Regards

Amol Powar

Amol,

My goal is to be able to get a list of deleted VMs

java -jar proxycp.jar --listdeletedvms --vc vcenter.mycompany.com

and then use that as an input file for

java -jar proxycp.jar --retirevms --filename filename

unfortunately when i list deleted VMs it does not provide the path, is it possible to add a flag to provide that information and not just the name of the VM ?

Thank you

Amol,

thank for your help but for some reason retirevms does not actually retire the VM, it's still listed in vCenter.

root@avepoc:/home/admin/#: java -jar proxycp.jar --listdeletedvms --vc vcepocw.mycompany.com
======================= Starting ProxyCP ==========================


Proxycp : v2.65
Date    : January 22, 2016 5:31:28 PM EST


COMMAND : java -jar proxycp.jar --listdeletedvms --vc vcepocw.mycompany.com


VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Jan 22, 2016 5:31:31 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider "JsafeJCE version 5.0" is registered at position 1
========================== vcepocw.mycompany.com ==========================
Please wait...creating cache for VM->UUID
---------------------------------------------------------------------------------
/vcepocw.mycompany.com/ContainerClients/sanback2_clone_Windows
-------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : January 22, 2016 5:31:35 PM EST






root@avepoc:/home/admin/#: cat file.out
/vcepocw.mycompany.com/ContainerClients/sanback2_clone_Windows




root@avepoc:/home/admin/#: java -jar proxycp.jar --retirevms --filename file.out
======================= Starting ProxyCP ==========================


Proxycp : v2.65
Date    : January 22, 2016 5:32:44 PM EST


COMMAND : java -jar proxycp.jar --retirevms --filename file.out


VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Jan 22, 2016 5:32:47 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider "JsafeJCE version 5.0" is registered at position 1
Current Backup Expiry date will be preserved
/vcepocw.mycompany.com/ContainerClients/sanback2_clone_Windows          Retired ? /vcepocw.mycompany.com/ContainerClients/sanback2_clone_Windows
-------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : January 22, 2016 5:32:51 PM EST

That's an easy fix, please download the new version from FTP

admin@aegrid1:~/>: sudo java -jar /usr/local/avamar/bin/proxycp.jar --listdeletedvms
======================= Starting ProxyCP ==========================
Proxycp : v2.65
Date    : January 22, 2016 2:01:12 PM PST

COMMAND : java -jar proxycp.jar --listdeletedvms 

VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Jan 22, 2016 2:01:15 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider "JsafeJCE version 5.0" is registered at position 1
========================== aevc1.asl.lab.emc.com ========================== 
Please wait...creating cache for VM->UUID
---------------------------------------------------------------------------------
/aevc1.asl.lab.emc.com/VirtualMachines/VM With Spaces in the name
-------------------------------------------------------------------------------------------------------------------
Closing Connection Pool : January 22, 2016 2:01:20 PM PST

Regards

Amol Powar

Hi Amol,

any chance you could see why it's not deleting VMs, does it work in your environment ?

Thank you

I think it is not working because the VM is dynamically added via Container client mechanism and the property is set as "dynamic".I am sure if you open the MC-GUI and right click on this VM from the "Administration" window all the options will be grayed out.Please edit the property of "parent" container (VMFolder/ResourcePool/ESX) of this VM from "policy->client" window and change it from "dynamic" to "static" and try to run proxycp again and it should retire the client properly. Once the client is retired change the property back to "dynamic".

I am tied up this week with other activity and wont be able to make any changes to proxycp, but next week I'll add intelligence to deal with this condition and automatically edit "parent" property if VM belongs to container client.

regards

Amol Powar

Amol,

Thank you for your continued assistance.

Amol Powar wrote: I think it is not working because the VM is dynamically added via Container client mechanism and the property is set as "dynamic".I am sure if you open the MC-GUI and right click on this VM from the "Administration" window all the options will be grayed out.

I actually do these options:

Amol Powar wrote: .Please edit the property of "parent" container (VMFolder/ResourcePool/ESX) of this VM from "policy->client" window and change it from "dynamic" to "static" and try to run proxycp again and it should retire the client properly. Once the client is retired change the property back to "dynamic".

This VM is located under multiple subfolders in vCenter so i disabled "Dynamic Mode" on every parent folder (VM is in the root of L2 subfolder) , still no luck.

Thank you very much for your time.

Hi Amol,

have you had an opportunity to look into this ?

Thank you

Thanks for the reminder I almost forgot about this, let me work on it now. I'll update the thread in next few hours.

i really appreciate it.