#Issues with MSSQL snapshots not beeing labeled for SnapVault...

1 messages · Page 1 of 1 (latest)

thick niche
#

We have recently upgraded to SC 6.1 (Windows) and we have several SQL Servers running without any issues at all.
But we also have an older Win2012R2 server which isn't supported anylonger, and so much that the installer failed while upgrading. So we had to manually install a verison 5.1 agent on the server.
So it is in a status of "Upgrade mandatory" which we cannot do... so a catch 22 kinda setup 🙂
Anyway it looks like we are able to start the existing backups OK from SnapCenter after we moved them from the Windows Task Scheduler to the SQL Server scheduler. (I think from 6.0 the Windows Task Scheduler isn't used)... We reuse the existing policies which this server has been running on for years, which include snapvault snapmirror-label of "Daily" etc.. yet as we run the backups now, it creates the SQL Server backup, and starts the "Replicating to Secondary", which fails after some time... and we get the message that it wasn't able to see any snapmirror retionships for a volume.. which it has... we can see that even though the primary snapshots have been created they are not snapmirror-labeled and therefore not replicated as the snapmirror update is run... I don't think we will get much luck asking NetApp Support about this, as the Windows Server is unsupported... but can anyone confirm if it is possible getting this working again, or are we wasting our time, and should we find another solution for this server? (this is of cause not a critical server, and will die within 6-12 months, but backups are always nive to have)...

thick niche
#

Somehow we managed to get this running again... it turned out to be the good old issue of REST-API... and because the upgrade process of the agent, just ended up breaking and didn't roll-back, we had to reinstall the agent manually.. but ofcause the .config file was then back to stock and it was then trying to talk REST to the storage controllers which still doesn't work.. after adding the infamous line in the file to disable REST, everything worked again... all hail ONTAPI 😉