VMs info in Nimble Snapshot is Not displayed

[Tos]

Hi

Our customer have trouble.
They want to do restore from Nimble Storage Snapshot.
So they run Snapshot-Only Jobs and it's successful.
https://helpcenter.veeam.com/docs/backu ... tml?ver=95

The created storage snapshot is displayed from Veeam console and Nimble console.
But, when clicking Storage Snapshot from Veeam Console, the VM info is not displayed. (VMs Count is "0" )

Manually created storage snapshot is also displayed from Veeam console and Nimble console.
https://helpcenter.veeam.com/docs/backu ... tml?ver=95

But VMs count is also displayed as "0" from Veeam console.

Storege Rescan is also successful, but VMs count is still "0". They can't restore from Storage Snapshot.

Do you know the cause and handling ?
They use the latest Veeam (update3a) and Nimble OS (ver5.x). Is it related ?

Regards
Toshi

[csydas]

Hey Toshihiro,

I had something similar with our Netapp setups, and we figured out in the end it was a permissions issue. The Account used to access our Netapp NFS exports was setup with granular permissions. After re-adding the account to have full permission for all exports, we were able to successfully restore from our shares.

Check the account used to add your Nimble to Veeam for permissions. Try giving it everything temporarily and see if the situation is resolve, then you can work with Nimble to narrow down the issue.

[Tos]

Hi
Thanks for your advice.
Although we confirmed, the user who used to register in nimble uses the admin user ("admin" user).
It seems that iSCSI connection of Veeam server and Nimble volume can also be configured.
Is there any other possible cause for it ?

[Tos]

Hi
Finally, I understood the cause of this event.
This issue occurs when a storage snapshot is created on a datastore larger than 16TB with VMFS5 later.
So we adjust the NImble volume so that it is divided and used. It's resolved.

[foggy]

Hi Toshihiro, could you please confirm you're on Veeam B&R 9.5 Update 3a, not just Update 3? We had this issue in U3, but it was addressed in U3a and if it still occurs on this version, we would like to investigate. Thanks!

[Tos]

Hi foggy
This issue still occur on Veeam B&R 9.5 Update 3a.
We checked with the support team and it seems to fix with the next update.

[foggy]

Could you please share your case ID? Thanks!

[DarrenToews]

Was this resolved? I'm seeing this same behaviour. We're on 9.5.4.2866 running a Nimble CS300 on NimbleOS version 5.0.7.200-612527-opt.

In addition when I try to rescan any of the Nimble Volumes through the Veeam console, I get the message that the volume is locked waiting for release. This happens no matter what volume I rescan.

[foggy]

Hi Darren, this topic doesn't contain a case ID we could track for a resolution, so please open your own case for investigation. Thanks!

[DarrenToews]

Thanks Foggy. Will do.

[kylecpcs]

Hi
Finally, I understood the cause of this event.
This issue occurs when a storage snapshot is created on a datastore larger than 16TB with VMFS5 later.
So we adjust the NImble volume so that it is divided and used. It's resolved.

This appears to still be an issue, even in the latest Veeam 11 release, fully patched.
This is in vSphere 7 with VMFS6 datastores on a Nimble HF40.
Nimble 15tb LUN shows all the available VMs for recovery.
Nimble 70tb LUN only shows a handful of the 70+ VMs...notably, it shows less than the 15tb LUN does.

Has there been any update to this issue? Or perhaps some kind of reg tweak?

[foggy]

Hi Kyle, we're not aware of any changes that could bring the mentioned behavior back after it was fixed back in v9.5u3a. May I ask you to open a support case for a closer investigation?

[kylecpcs]

Still having the issue. Opened a case through support. Patched v11 B&R with Nimble HF40.
Case # 05772580