i have a problem with my VSC-Configuration. I will backup my virtual maschines with vsc. I have installed the plugin, and it works, i can connect to the netapp filer.
But when i start a backup, comes the errormessage:
I hope, someone can help me
I've a workarround
open taskmanager on VC
select both java processes responsible for VSC an kill them
the java processes restart automaticly an rebuild the entrys in
wait 1 minute and restart vcClient
1. If vCenter is open close it.
2. Stop your two NetApp VSC services (should say something like "NetApp for vSpher.....")
3. Locate the \crash directory and delete it.
4. Restart your VSC services
5. Open vCenter and you should be able to get to your console.
I had the exact same issue with VSC 4.1 (vSphere 5.1) after I already configured and completed a successful test backup.
I stopped the services as described (Netapp SnapManager for Virtual Infrastructure and Virtual Storage Console for Vmware vSphere Server) and deleted the crash folder from C:\Program Files\NetApp\Virtual Storage Console\smvi\server\ and restarted the services.
Once I restarted.... the Backup and Recovery tab worked fine and showed my previous backup job properties.
We get same error message in ESXi 5.0 environment. VSC works fine to enable "recommended values" on ESXi hosts.
Every time "NetApp vSphere Plugin Framework" tries to connect to "NetApp SnapManager for Virtual Infrastructure" service over port 8043 for backup/restore purpose, we get the error above.
We tried to change SMVI port by following the instructions in the following KB. But there is no information about configuring the VSC plug-in to connect SMVI over newly defined port.
Vcenter system configuration is below:
HP DL 380 G7, Microsoft windows server 2008 R2 enterprise, Vmware vcenter 5.0,VSC 2.1.2 x64.
The problem has been started after reinstalling the "VMware Vsphere Converter" to vCenter server.
We have removed "converter" and reinstalled VSC many times but result was not successful.
If VSC is installed to any other server, it works fine.
We have an open case about the issue but there is no resolution until now.