Unsolved
This post is more than 5 years old
1 Rookie
•
20.4K Posts
1
7770
Using proxycp.jar to retire VMs
Trying to figure out how to use proxycp.jar to retire VMs. What format does --file filename should be ? I just put VM name in the file and get this:
COMMAND : java -jar proxycp.jar --retirevms --filename filename
VDP/Nemo Detected : false
------------------------------------------------------------------------------------
Jan 21, 2016 8:35:22 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
Error : McsFaultMsgException
Thanks
Amol
207 Posts
0
January 22nd, 2016 07:00
You need to provide complete path of the VM in the file.
Note : Make sure to use the latest version from the FTP
Regards
Amol Powar
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
January 22nd, 2016 13:00
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
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
January 22nd, 2016 14:00
Amol,
thank for your help but for some reason retirevms does not actually retire the VM, it's still listed in vCenter.
Amol
207 Posts
0
January 22nd, 2016 14:00
That's an easy fix, please download the new version from FTP
Regards
Amol Powar
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
January 25th, 2016 10:00
Hi Amol,
any chance you could see why it's not deleting VMs, does it work in your environment ?
Thank you
Amol
207 Posts
0
January 26th, 2016 05:00
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
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
January 26th, 2016 06:00
Amol,
Thank you for your continued assistance.
I actually do these options:
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.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 23rd, 2016 10:00
Hi Amol,
have you had an opportunity to look into this ?
Thank you
Amol
207 Posts
0
February 23rd, 2016 10:00
Thanks for the reminder I almost forgot about this, let me work on it now. I'll update the thread in next few hours.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 23rd, 2016 10:00
i really appreciate it.
Amol
207 Posts
0
February 24th, 2016 06:00
It will take some more time than anticipated due to some new issues that were encountered for retiring ContainerClient VM, I'll keep you posted.
Amol
207 Posts
1
March 14th, 2016 10:00
Proxycp is using a very old endpoint for communication with MCS and it will be hard to implement this fix (It may break other options). I am going to retire proxycp.jar going forward and add all the new options into av2ool. I'll try to copy useful features from proxycp and add them into av2ool ( May take some time) .Please download a new tool av2ool.jar and use the following option and let me know it it works
Note : --expires is an optional parameter, if you don't specify,it will use the default expiration for the backups
Regards
Amol Powar
jeff_easter1
5 Posts
0
March 14th, 2016 12:00
retire.lst:
/msvXXXX5.XXXXX.com/ContainerClients/xxx07
/msvXXXX5.XXXXX.com/ContainerClients/xxx02
/msvXXXX5.XXXXX.com/ContainerClients/xxx03
/msvXXXX5.XXXXX.com/ContainerClients/xxx04
--------------------------------------------------
A V 2 O O L v0.03
--------------------------------------------------
March 14, 2016 3:28:28 PM EDT
--------------------------------------------------
CMD : java -jar av2ool.jar client retire --filename retire.lst
--------------------------------------------------
--expires option not specified, using default expiration
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
Error : The server did not recognise the action which it received:
admin@XXXXavamar1:~/>:
Amol
207 Posts
0
March 14th, 2016 14:00
What is the version of Avamar ?
jeff_easter1
5 Posts
0
March 15th, 2016 05:00
7.1.0-370_HF241893_25