Hi,
Is there any way in which I could manage VM snapshots using vMA? I'm using the command "vmware-cmd" but I see no option to LIST the snapshots and revert to a specific one.
I can only get the command to show me in a boolean fashion if the VM has snapshots, remove them or revert to the last one.
Thanks in advance!
elgreco81
Is there any way in which I could manage VM snapshots using vMA? I'm using the command "vmware-cmd" but I see no option to LIST the snapshots and revert to a specific one.
I can only get the command to show me in a boolean fashion if the VM has snapshots, remove them or revert to the last one.
I'm afraid that's the best you can do with what the vMA offers of builtin tools, unless you write custom perl scripts making use of the viperltoolkit (comes with the vMA).
The vMA was always intended as a kind of centralized local ESX(i) CLI to manage hosts and not VMs through supported commands (esxcfg-*/vicfg-*, esxcli etc), which are also available on a local ESX(i) host; with the advantage that it is centralized and you don't have to enable SSH on your hosts each time.
More advanced things like management of VMs (apart from basic stop/start etc) should be performed through the standard API applications like the vSphere (Web) Client (with vCenter), PowerCLI scripts or other programming interfaces such as the viperltoolkit.
Is there any way in which I could manage VM snapshots using vMA? I'm using the command "vmware-cmd" but I see no option to LIST the snapshots and revert to a specific one.
I can only get the command to show me in a boolean fashion if the VM has snapshots, remove them or revert to the last one.
I'm afraid that's the best you can do with what the vMA offers of builtin tools, unless you write custom perl scripts making use of the viperltoolkit (comes with the vMA).
The vMA was always intended as a kind of centralized local ESX(i) CLI to manage hosts and not VMs through supported commands (esxcfg-*/vicfg-*, esxcli etc), which are also available on a local ESX(i) host; with the advantage that it is centralized and you don't have to enable SSH on your hosts each time.
More advanced things like management of VMs (apart from basic stop/start etc) should be performed through the standard API applications like the vSphere (Web) Client (with vCenter), PowerCLI scripts or other programming interfaces such as the viperltoolkit.
Ok. Good to know that so I don't waste any more time trying to do it using VMA commands
I'm no great expert scripting in perl, so I guess this is going to be one of the things that make me open the web client.
Thank you very much for your help!
elgreco81
PS: Perl for Zimbra/vMA - JavaScript for vCO, Powershell for serveral vsphere solutions...plus all of the native commands in every new appliance...ruby for puppet, java for hyperic, bash for "regular scripting" in linux, eclipse for VMware studio, python because it's cool :smileysilly:. My head is just going to explode sooner or later!!! LOL