I have another issue with Win 2016 and SMHV.
I've upgraded our 3-node Hyper-V cluster from Win 2012R2 to Win2016.
After upgrade of the last node in the cluster, the backup is stopped working at all.
As I can see in the logs, SMHV is created : "{GIUD}" snapshot, but doesn't create "{GUID}_backup" snapshot.
Backup failed because this snapshot is not existing and SnapDrive can't rename these snapshots to normal SMHV name.
Wed Jul 4 23:34:53 [hq-str3-a:wafl.snap.delete:info]: Snapshot copy {7196c57a-52a7-426d-9775-14cf7c0d2ae4} on volume hv10_vhd NetApp was deleted by the Data ONTAP function zapi_snapshot_delete. The unique ID for this Snapshot copy is (77, 8605171).
Wed Jul 4 23:41:04 [hq-str3-a:api_mpool_01:notice]: Multicreation of snapshot named {cf161a21-6224-4105-8ba6-8638122d93b0} successful. It took 2 milli seconds from start to finish in ZAPI.
Wed Jul 4 23:41:12 [hq-str3-a:lun.offline:warning]: LUN /vol/hv10_vhd/{b8bcd75a-22a1-4ab6-a78b-e75190cbc4f3}.aux has been taken offline
Wed Jul 4 23:41:14 [hq-str3-a:lun.destroy:info]: LUN /vol/hv10_vhd/{b8bcd75a-22a1-4ab6-a78b-e75190cbc4f3}.aux destroyed
Wed Jul 4 23:43:04 [hq-str3-a:app.log.err:error]: HQ-HV13: SnapDrive 7. 1. 5. 7043: (135) Snapshot Copy event: For the description of this event please check the application event log on the host system.
Wed Jul 4 23:43:54 [hq-str3-a:app.log.err:error]: HQ-HV13: SnapMgrServiceHost SMHV version: 2.1.3.2730: (106) Backup Category: Backup of the Dataset Name: hv10 Backup id: cc37f935-43df-4a4b-91bd-a5e9c7bca748 failed to execute Error :An error occured while renaming snapshots after backup operation.
Thu Jul 5 00:00:00 [hq-str3-a:kern.uptime.filer:info]: 12:00am up 751 days, 9:02 192673871 NFS ops, 100479298 CIFS ops, 0 HTTP ops, 0 FCP ops, 15330353377 iSCSI ops
GetTargetLunInfo succeeded.
Storage System Name = hq-str3-a
lunPath = /vol/hv10_vhd/hv10_vhd.lun
Snapshot copy Name = {cf161a21-6224-4105-8ba6-8638122d93b0}
Failed to rename the Snapshot copy ({CF161A21-6224-4105-8BA6-8638122D93B0}_backup) of the LUN to the new Snapshot copy name (hv10_hq-hv10_HQ-HV13_07-04-2018_23.34.23_backup).
LUN Name = hv10_vhd.lun
Storage Path = /vol/hv10_vhd
Protocol Type =
Storage System Name = hq-str3-a
Error code : An attempt to rename Snapshot copy from '{CF161A21-6224-4105-8BA6-8638122D93B0}_backup' to 'hv10_hq-hv10_HQ-HV13_07-04-2018_23.34.23_backup' on volume 'hv10_vhd' failed on the storage system 'hq-str3-a'. Error code: 13021. Error description: The current snapshot does not exist.
SnapManager for Hyper-V backup failed to complete
Backup of the Dataset Name: hv10
Backup id: cc37f935-43df-4a4b-91bd-a5e9c7bca748 failed to execute
Error :An error occured while renaming snapshots after backup operation..
hq-str3-a> snap list hv10_vhd
Volume hv10_vhd
working...
%/used %/total date name
---------- ---------- ------------ --------
0% ( 0%) 0% ( 0%) Jul 04 23:41 {cf161a21-6224-4105-8ba6-8638122d93b0}
6% ( 5%) 2% ( 2%) Jul 01 23:07 hv10_hq-hv10_HQ-HV11_07-01-2018_22.50.00_backup
6% ( 0%) 2% ( 0%) Jul 01 23:03 hv10_hq-hv10_HQ-HV11_07-01-2018_22.50.00
10% ( 4%) 3% ( 1%) Jun 30 23:45 hv10_hq-hv10_HQ-HV11_06-30-2018_23.30.01_backup
10% ( 0%) 4% ( 0%) Jun 30 23:41 hv10_hq-hv10_HQ-HV11_06-30-2018_23.30.01
I can't open a support case at this moment, because the support contract is expired.
HGS is not installed. We don't have shielded VMs. It's a crazy to install HGS/ADDS/etc on the cluster. NetApp, are you kidding ?
!!! WARNING !!!
If you are going to upgrade your cluster from Win 2012R2 to Win 2016, keep one server with Win 2012R2 in the cluster.
DON'T upgrade all nodes.