VSC 4.1 "Backup & Recovery" problem when I create a new Backup job: not all Datasotores elegible

[CESAR_ALONSO]

Dear All,

I have a NetApp FAS2020A (with 2 controllers). It is setup with a VIF in both controllers, and 2 IP directions in each VIF (principal one and an alias). This is running in a vSphere 5.1 environment, with VMware vCenter Server Appliance 5.1 (vCSA). I'm only using NFS protocol to export Datasotores to VMware. I have 4 NFS DataStores, and each Datastore is mounted in the ESXi servers using a different IP address (remember that I have 4 IPs: 1 for each VIF, and one alias for each VIF).

I have problem with VCS "Backup and Restore" Function. When I try to create a new Backup Job, in the "Virtual Entities" section, and I have to choose which will be in the backup, not all of them are shown. Only the ones that are mounted with the "principal" IP address of each VIF are eligible (check Storage Details - NAS.png attachment). But If I go to "Monitoring and Host Configuration > Storage Detail - NAS", I can see all of them (check New Backup.png attachmnet).

Also, In the past I did not have this problem. I think that it begun when I upgraded from VCS 4.0 to 4.1, but I'm not sure.

Best regards

    César

[kboyle]

All,

The VSC 4.1P1 release was published today (which includes the previously referenced D release and a few other fixes).

Please use the “Access a Specific Release” section on the bottom of the Software Download page (http://support.netapp.com/NOW/cgi-bin/software/). Select "Virtual Storage Console (VMware vSphere)," input the version 4.1P1, and hit “Go” to review the fixed bugs and to download the software.

Regards,

Kim

[sottich71 · Accepted solution]

Hello

please show here:

VSC 4.1 fails to enumerate NFS datastores mounted using alias IP addresses?

https://kb.netapp.com/support/index?page=content&id=2017360&actp=LIST_RECENT&viewlocale=en_US&searchid=1360229703160

Regards

Stefan

[CESAR_ALONSO]

Thank you for the tip. It's a known bug of VSC 4.1. Comming back to 4.0 fix it

[dburkland]

It looks like there is a bug fix for this issue that NetApp has released. See the most previous posts in this thread:

https://communities.netapp.com/thread/25188