Unsolved
This post is more than 5 years old
1 Rookie
•
20.4K Posts
1
7785
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
March 15th, 2016 07:00
I have uploaded a new version to the same location, please try again and let me know the result.
jeff_easter1
5 Posts
0
March 15th, 2016 08:00
Now it moves them into the MC_RETIRED folder, but as soon as a sync with vcenter is run, they pop back into the Avamar ready to try backups again. Is this temporarily disabling dynamic containers before retiring?
EDIT:
I tried it the way described below, and have the same issue. There seems to be no way to retire VM's you don't want to backup.
"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."
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
March 15th, 2016 10:00
Jeff,
you simply do not want to backup this VM or this VM will be retired but have yet to be deleted out of vCenter ? I would like to switch to folder based backup and trying to work through the different scenarios with my VMware guys.
jeff_easter1
5 Posts
0
March 15th, 2016 10:00
Some vm's in both scenarios. Some we cannot backup as a snapshot causes the application on the vm to fail, some we are told are going to be decomm'd before they are deleted from the vcenter. Are you asking me to switch to folder based backup?
Amol
207 Posts
0
March 15th, 2016 12:00
If you are using the ContainerClient feature there is no way to "exclude" particular VM from a given container. Only option you have is to either make "container" static (You will loose dynamic properties like auto import etc.)
Regards
Amol Powar
philorme
1 Message
0
May 24th, 2017 08:00
I also am having a problem with the proxycp.jar (latest version) , but in my case I am trying to use the --deleteclientswithnobackups option also from a VMcontainer (have tried setting the folder to static, makes no difference), now it will list the VM's with no backups (--listclientswithnobackups) okay, and it looks like it is deleting when running with the deleteclientswithnobackups option, you get the following output.
COMMAND : java -jar proxycp.jar --deleteclientswithnobackups --domain /ukwkmh-vira001/ContainerClients
VDP/Nemo Detected : false
-------------------------------------------------------------------------------------------------------------------
No Backups /ukwkmh-vira001/ContainerClients/Red Hat Enterprise Linux 6.6 Template
Deleted true
No Backups /ukwkmh-vira001/ContainerClients/Red Hat Enterprise Linux 6.x Template
Deleted true
but it has not deleted them, is there a log I can switch on/ look at to find out what is happening.b.t.w. this works fine in a non VMware folder (domain)