NetApp Ontap 9.x Storage Snapshot Support and Issues

[bacon_strips]

I just updated my NetApp to 9.1P1 and my Veeam (9.5 U1) backup from snapshots does not work.

Probably should have checked compatibility before doing that one.

Any ETA for a fix?

[Gostev]

Do you have a support case open? If yes, please post it here and we will escalate it to the corresponding dev team for review. Thanks!

[marco.horstmann]

Ontap 9.1P1 fixed some issues, not sure if the one Marco talks about is one of them.
Has anyone heard anything regarding this?

https://mysupport.netapp.com/NOW/downlo ... tap/9.1P1/

Hi, I've no new update from NetApp regarding this issue.

I will try tomorrow to get a new status

[bacon_strips]

I opened case 02090268.

Thank you.

[marco.horstmann]

Ontap 9.1P1 fixed some issues, not sure if the one Marco talks about is one of them.
Has anyone heard anything regarding this?

https://mysupport.netapp.com/NOW/downlo ... tap/9.1P1/

Hi,

I've talked to the engineer from NetApp. Fix is planned in 9.1P3, which will be
probably available in April.

Regards
Marco

[flowe]

I just updated my NetApp to 9.1P1 and my Veeam (9.5 U1) backup from snapshots does not work.

Probably should have checked compatibility before doing that one.

Any ETA for a fix?

Hi,

I have a problem at a customer of me, too. They upgraded to ONTAP 9.1RC2 before they bought veeam.
I think veeam don't recognize the LUNs (iSCSI and FibreChannel).

If I want to perform a backup from storage-snapshot, I get the following error-message:
"VM does not meet the requirements for storage snapshot based jobs"

NFS-Shares works well.

Do you have the same problem?

[DerOest]

Hi flowe,
i've had a problem that Veeam could not properly scan the Ontap9.1 System.
Always gave an error with ISCSI - we only use NFS for VMware! We have a dedicated SVM only serving NFS data, and this is where Veeam failed with ISCSI, which did not make sense to me at all.

But you've got NFS working? Guess I'll have to try again!

/edit: just checked again, we've updated to 9.1P1 in the meantime. Still the same error.
I rechecked the FAS-System in Veeam, Access options are "NFS" only. Yet, when i scan the storage, it says:

10.03.2017 08:09:48 Successfully determined NFS exports supported for backup from storage snapshots on storage FAS2650 using NFS client from proxy ...
10.03.2017 08:10:04 NFS share xxx from volumexxx corresponding VMware host is not registered with Veeam
10.03.2017 08:13:58 Failed to obtain list of VMs on NFS share xxx from snapshot yyy of volume xxx Error: There is no initiators available.


Not sure if i should open a case while 9.1 is not officially supported?

[marco.horstmann]

With 9.5 you can select in the Storage System Settings which Protocol should be scanned. Maybe this helps you.

[DerOest]

Hi Marco, you were too fast I was just editing my above post, but for better visibility, i'll put it here again:

just checked again, we've updated to 9.1P1 in the meantime. Still the same error.
I rechecked the FAS-System in Veeam, Access options are "NFS" only. Yet, when i scan the storage, it says:

10.03.2017 08:09:48 Successfully determined NFS exports supported for backup from storage snapshots on storage FAS2650 using NFS client from proxy ...
10.03.2017 08:10:04 NFS share xxx from volumexxx corresponding VMware host is not registered with Veeam
10.03.2017 08:13:58 Failed to obtain list of VMs on NFS share xxx from snapshot yyy of volume xxx Error: There is no initiators available.


Not sure if i should open a case while 9.1 is not officially supported?

[foggy]

Yes, please open a case for this and provide your case ID here. Thanks.

[DerOest]

Case #02096314 was created.
-> I've uploaded the logs and screenshots, hope it helps!

[bacon_strips]

Marco, might you have a NetApp bug ID so I can track their progress on a fix?

Cheers

[marco.horstmann]

Hi,

sorry I have no Bug ID.

Regards
Marco

[DerOest]

Hello everyone,

NFS with Ontap 9.1 works - my issues are resolved.

Cause: Despite all checklists being ticked off, on our FAS2650 no "public" LIFs for the NFS-SVM were created.
Only the "private"/non-routed/L2 internal Datastore-VLAN between Netapp and ESXi was created
-> While testing everything worked when i manually mapped the Datastores to the ESXi Hosts
-> But Veeam, coming from a "normal" routed L3 VLAN was not able to access, as the corresponding Netapp LIFs on this subnet were missing

So, it was a User error

But @Veeam: Please fix this behaviour, it is extremely misleading!
The Netapp SVM is NFS only, and in Veeam the Netapp is configured for NFS-access only. Yet, the error messages all point towards ISCSI/FC (Initiators, SAN, etc. all over the logs.)
In this case, Veeam should just scream "hey, i can not access this storage over NFS, fix it!" instead.

TLDR: No way for Veeam to access NFS Datastore, Veeam throws logs pointing towards ISCSI/FC, leading me to believe it's a Veeam-bug because 9.1 is not officially supported yet

[DerOest]

Hi,

sorry I have no Bug ID.

Regards
Marco

Hi Marco (et al),
Ontap 9.1P3 was released (I guess you already heard of this through other channels^^).
http://mysupport.netapp.com/NOW/downloa ... tap/9.1P3/

Just guessing, could this be the bug you mentioned?
1064560 Large file deletion or LUN unmap operations can stall on FlexClone volumes

Any news if Ontap 9.1(P3) will be supported by Veeam B&R 9.5 Update2?

Greetings from Germany!

[marco.horstmann]

Hi DerOest,

I asked my NetApp contact if this is the fix he talked about. No update yet.

I have no information about 9.1 Support and VBR 9.5 U2. Gostev and his team has not
given us engineers infos about this topic, yet.

Regards
Marco

[foggy]

NetApp ONTAP 9.1 is officially supported with the Update 2.

[marco.horstmann]

Hi,

I got just some minutes a mail from my NetApp contact. The fix is slipped to 9.1P4 and 9.2RC1.

Regards
Marco

[lightsout]

Just a question. I've been running Veeam 9.5U1 with cDOT 9.1 since early March without issue. I'm using NFS for VMware and storage snapshots for backups.

Everything seems to work, I am missing something that this update will now help me with? Or is it just official support & tested?

[foggy]

The latter.

[DerOest]

(quick edit as foggy was seconds faster)

But there's also this change:

• Performance improvements. The performance of Backup from Storage Snapshot with application-aware processing enabled has been noticeably improved.

[lightsout]

I saw that, and looking forward to testing it.

[foggy]

But there's also this change:

• Performance improvements. The performance of Backup from Storage Snapshot with application-aware processing enabled has been noticeably improved.

This is a general improvement that relates to all supported storages.

[Joje]

We have B&R 9.5 and Netapp ONTap 9.1P2. Just upgraded to Update 2 and we now have an issue.

The backups can't transfer snapshot to snapvault because it says the relationship cant be found for the snapvault.

I even reverted to update 1 and then it finds the relationship just fine. I do want the new features and bug fixes so I want to go to update 2. Anyone else seen this problem?

[marco.horstmann]

No as far as I know, please create a support case that our support can talk a look on this.

[advunibyte-ak2]

We have the same Issue with NetApp ONTAP 9.0GA!
The backups can't transfer snapshot to snapvault because it says the relationship cant be found for the snapvault.
@Joje: Have you an open Support Ticket for this Issue?

thanks and best regards,
Andreas

[Joje]

Yes, the customer logged a support ticket regarding this and veeam says its a bug in 9.5U2 with XDP (mirror-vault). I haven't been at the customers site since then but they have a patch for this issue if you raise a ticket with them.

A ticket with veeam that is.

[larry]

Was this issue fix with 9.5U2 ?

[Joje]

Was this issue fix with 9.5U2 ?

Not sure if you refer to my post or not. If you did then the problem was introduced in U2 so you need a fix after that.

[larry]

Joje do they have the fix? Was going to upgrade today.