Netapp snapshot is created on wrong volume

[dries.vergote]

Hi
First of all Case #04961089

We upgraded recently from v9.5.4b to V11 and after the upgrade everything seem to work fine except 2 jobs.
Those jobs have snapshot transfer issue. After some investigation I saw that the snapshot are created under another datastore.

case:
We have 3 jobs:
- datastoreA_001
- datastoreA_002
- datastoreA

Snapshot backup job taken from datastoreA_001 & datastoreA_002 are located in DATASTOREA.
In the veeam job GUI I see the correct vm's are being processed. In the snapshot I see the vm's of datastoreA.

In a test backup job of datastoreA_001 with no secundary location (we are snapmirror for the other 3) name Datastore1_001_test we see the snapshot again under datastoreA.

Any ideas?
I have enabled the old jobs from my veeam V9.5.4b and those are running just fine.

Regards
Dries Vergote

[PetrM]

Hi Dries,

I see that the case has just been created so let's wait for the conclusion from our support team. I'm sure our engineers will be able to figure out the cause of the problem.

Thanks!

[foggy]

Hi Dries, this looks like a known issue that has already been addressed in the upcoming v11a update. Thanks for opening a case - our engineers will be able to verify whether it is the same problem or something different.

[dries.vergote]

Hi Foggy

I saw one of your comments in a tread about Qtree that the scanning is changed for the storage device in V11.
So it might still in there.

The enigeer just ask me to rescan.
I gave them output of the logs:

Code: Select all

[11.08.2021 15:22:45] <01> Info         [ViVmStorageIntegrationChecker] Datastore 'datastore_A_001' is storage snapshot compatible.
[11.08.2021 15:22:45] <01> Info         [ViVmStorageIntegrationChecker] All datastores on 'xxxx' VM is storage snapshot compatible.
[11.08.2021 15:22:45] <01> Info         [San] Choosing best source volume LUN: 
[11.08.2021 15:22:45] <01> Info                 Volume LUN: 'Name 'datastore_A'
[11.08.2021 15:22:45] <01> Info                 Volume LUN: 'Name 'datastore_A_001'

[11.08.2021 15:22:45] <01> Info         [NetApp] Choosing best volumes from: [2]
[11.08.2021 15:22:45] <01> Info                 Volume LUN: 'sel_datastore_A', '/vol/datastore_A', Host: Name 'netapp-cls001',  Id 'a2030f5c-ce84-4952-bd5d-42b93fd4dc83', Mode 'NaCluster', IsMetroClusterEnabled 'False', MetroClusterPartner '', IsMetroClusterAlive 'False'
[11.08.2021 15:22:45] <01> Info                 Volume LUN: 'sel_datastore_A_001', '/vol/datastore_A_001', Host: Name 'netapp-cls001',  Id 'a2030f5c-ce84-4952-bd5d-42b93fd4dc83', Mode 'NaCluster', IsMetroClusterEnabled 'False', MetroClusterPartner '', IsMetroClusterAlive 'False'

[11.08.2021 15:22:45] <01> Info         [NetApp] Connection was successfully established.
[11.08.2021 15:22:45] <01> Info         [San] Choosed LUN: 'Name 'datastore_A',

It choses the first one and not the correct one.

[foggy]

That one is a bit different - according to QA, you're seeing exactly the issue that is addressed in v11a. So please wait a bit until it is released.

[dries.vergote]

When will it be relaesed? This is a production system. Is there a workaround?
Renaming the datastore on netapp?

[foggy]

As an experimental workaround, our support can change some stored procedure in Veeam B&R database to address that - it helped a couple of customers with the similar issue.

[dries.vergote]

thanks for the reply.
Any idea on release date for V11a?