2017-03-17 05:28 AM
i installed SnapManager for Hyper-V in the Version 2.1.2 on both 2- Node Cluster Server. (Windows Server 2016)
All works fine, but the scheduled task doesn't work!
I configured a Dataset with scheduler Policy - so the Task start and end within 20 seconds. Result: Succes - but no backups are created.
SnapManager for Hyper-V\Backup report:
[17.03.2017 11:30:35, (25)] The operation completed successfully.
[17.03.2017 11:30:35, (25)] AutoSupport is disabled, AutoSupport update will not be performed
[17.03.2017 11:30:35, (25)] Backup task: completed successfully
[17.03.2017 11:30:35, (25)] <?xml version="1.0" encoding="utf-16"?>
<VM Name="VM-01" Id="35a19b6f-a903-9687-bd8b-b053da809361" Result="OK" />
The Job-ID is Dataset_[job]cc_Dataset_Policy_01-01-0001_00.00.00 - i think there is an mistake? time? date?
Recovery Tab: The selected dataset or virtual machine has no backups.
SnapManager for Hyper-V backup failed to complete
An error occured while executing SnapManager backup job.
Job: new-backup -ds CORE_Dataset -pid Dataset_Policy -h Cluster1 -scid 2918e971-abb2-4a5b-ad31-5773a46887df
Details: An error occured while invoking the powershell cmdlet.
Input Not Valid, Specfied scheduled job is not found in the task list
When i run the job manually it works, but it won't run at the scheduled time.
Complete uninstall, try an older version from SMHV 2.1, delete files and reinstall with new configuration, still the same!
Has anyone seen this issue, og have any ideas what could be the reason?
SnapManager for Hyper-V 2.1.2
Windows Server 2016
2- Node Cluster
Thanks for your help!!
If you need more information - let me know!
2017-03-21 09:36 PM
It might be due to bug: http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1064148
2017-05-12 12:05 AM
I have the same problem/bug.
Anyone that has found a workaround?
I have created a case with Netapp on this.. but I really need this to get up and running.
Best regards, Pelle
2017-07-05 10:52 PM
Hello to everyone
I also have problem with SnapManager for Hyper-v on Windows Server 2016 but my problem is different.
My backups are running on schedule but the problem is that Application consistant backup are failing withe error that SnapManager cannot rename Snapshot.
We opened the case at NetApp and NetApp said that we have to install Host Guardian Service role on the Windows Server 2016 hosts.
We did this and SnapManager is now working but the problem is that installation of HGS role depends on AD DS and IIS role.
You cannot install HGS role, unless you install also AD DS and IIS role.
Now I have on my Hyper-V hosts HGS, AD DS and IIS role and on every host I have, in Server Manager is post deployment task waiting to promote this host to a domain controller.
I am not happy with this scenarion and I am asking you ... did you also had to instal HGS role in Windows Server 2016 Hyper-V host to make SnapManager work?
2017-07-20 05:27 AM - edited 2017-07-20 05:28 AM
That would interest me too! I refuse to install the HGS until i get an technical explanation why. In most Hyper-V scenarios HGS is not need.
Thanks for any reply.
2017-07-24 02:48 AM - edited 2017-07-24 02:49 AM
We have 2 Windows 2016 Hyper-V Clusters, and both with the task manager issue. After contact NetApp support, we managed to get one of the clusters working by invoking the powershell command created by SMHV in a manually created task (in task manager).
Short after that, we were informed that SMHV 2.1.2P1 should solve that issue, but on our main cluster, the issue remains. We've also been advised to install HGS role (without configuration)... we're in the middle of that... very annoying ...
2018-01-15 11:32 AM
It is a bug. I have the same problem here. I found a solution using Snap Manager for Hyper-v powershell Extension.
This is the code I used (You can customize as your needs)
New-Backup -Dataset 'Data_set_name' -RetainBackups 3 -CrashConsistentBackup -Host 'CLU_NAME' -Verbose
Save the code above in a .ps1 file and create a new schedule task using the script.