SVMI Configuration oddness when using vfilers

[GARYWADAPT]

I'm having a few issues with VSC (SMVI). Bascially it's being a total pain.

First of all, we've got a bunch of vfilers configured on the vfiler0. smvi only sees a few of those vfilers. The credentials are correct and an update doesn't find the other vfilers. There are no hints as to why this is.

Secondly, A test backup gives me this error:

2012-04-18 09:44:23,754 PROGRESS - Starting backup request

2012-04-18 09:44:23,941 INFO - Generating backupName for the scheduleJob d62a2a5b-c4a6-4a92-8ebe-32f26a6aae16 is backup_VCenter Test Backup_20120418094423

2012-04-18 09:44:28,059 WARN - Unable to manage datastore NFS_02_MIR: Failed to find NFS export path /vol/UCS_Vmware_Vol4 for datastore NFS_02_MIR on storage system test01. NFS datastores must be exported from a Data ONTAP storage system.

2012-04-18 09:44:28,371 WARN - Unable to manage datastore NFS_02_MIR: Failed to find NFS export path /vol/UCS_Vmware_Vol4 for datastore NFS_02_MIR on storage system test01. NFS datastores must be exported from a Data ONTAP storage system.

2012-04-18 09:44:28,527 ERROR - Did not find any of the following datastores or virtual machines to backup: []. Storage system(s) may need to be added.

2012-04-18 09:44:28,543 ERROR - FLOW-11019: Failure in VmGetVirtualMachinesToBackup: Did not find any of the following datastores or virtual machines to backup: []. Storage system(s) may need to be added.

2012-04-18 09:44:28,558 ERROR - FLOW-11010: Operation transitioning to abort due to prior failure.

2012-04-18 09:44:28,761 PROGRESS - Sent status notification message to [deleted]

2012-04-18 09:44:28,777 PROGRESS - Storing logs for backup_VCenter Test Backup_20120418094423 in file C:\Program Files\NetApp\Virtual Storage Console\smvi\server\repository\logs\d62a2a5b-c4a6-4a92-8ebe-32f26a6aae16\backup_backup_VCenter Test Backup_20120418094423.xml

This backup has been configured by clicking on the virtual machine itself. The machine sits on one of the vfilers and so all the exports are handled from there yet the  VSC seems to expect the export to be on vfiler0?

Finally, Is there any plage where I can see an overview of all the backup jobs I have running?

Thanks.

[scottgelb]

does "vfiler run * options httpd.admin.enable" show on for all vfilers?

[GARYWADAPT]

Hi,

I've tried this on both a production system and on a simulator test box. Yes, httpd.admin.enable is on:

filerone> vfiler run * options httpd.admin.enable

===== vfiler0

httpd.admin.enable           on

===== vf_vfiler_one

httpd.admin.enable           on

The messages file shows this:

Wed Apr 18 20:55:13 BST [app.log.info:info]: Host Name: localhost. Os Version: Windows Server 2008 6.0. VC Version: 5.0.0: SMVI SnapManager for Virtual Infrastructure Server 3.0.4 (Build: 110819): (90501) Logging: A backup operation has started

Wed Apr 18 20:55:17 BST [app.log.err:error]: localhost: SMVI SnapManager for Virtual Infrastructure Server 3.0.4 (Build: 110819): (10102) Backup Failure, VC: Backup failure due to error in resolving the datastore or VM to backup. This could happen if the VMs or Datastores to be backed up could not be found.  Backup Name = backup_01810c6fa9b660bc1423dd11d3488d22  SMVI Server Error Messages = Did not find any of the following datastores or virtual machines to backup: []. Storage system(s) may need to be adde

Now the first line I'm guessing is the vcenter box where SMVI is installed as thats a windows 2008 box with vc 5. The next line just tells me that it can't find the datastores. The vCenter has several datastores on non-netapp hardware but this particular test machines IS on the filer.

[GARYWADAPT]

I think I have found a fix for this.

The vfilers are on seperate vlans to the physical filer and seperate to the vcenter box itself (where VSC is installed). It looks like VSC HAS to be able to communicate directly with whatever owns the volumes be it the phyiscal filer or a vfiler. As soon as I added a NIC to vcenter that could talk directly to the vfiler then added it in to the Backup and restore -> setup part of VSC it all started working.

[DEANMORETON]

We have the same situation.. any thoughts on how this is going to scale?  Considering vSphere 5 config maximums we will hit the limit of 10 virtual NICs per VM pretty soon.