I have a few older servers still using SnapManager rather than SnapCenter, and the critical security update that Microsoft released a few days ago (KB5001779) completely breaks SnapManager compatibility - backup jobs no longer run, and console reports "Unable to determine Exchange virtual server group status before SnapManager operation" straight upon opening. This is happening both in Exchange 2013 and Exchange 2019, same error. I have opened a case with support, but while I'm waiting for a response, has anyone else run into this, and is there a workaround?
Solved! See The Solution
A new version of SME is posted that fixes the issue
Bugs fixed in SME 7.2.1P1:
SME unable to enumerate DBs after Microsoft security update KB500177
We are also experiencing the same issues following the installation of this patch, We have logged this with Netapp and are currently awaiting a response.
I am not aware of any work around at this time and from similar issues posted to Microsoft here :
It does not appear that Microsoft have a workaround at this time.
I will try to post here if and when we get any more info or a fix.
Same issue here. After updating the security Updates (April 2021) SnapManager breakes and right now I have now workaround.
Will also create an support ticket. Can you please share your Case IDs?
It appears that we have all logged calls with Netapp for this issue, our case number is: 2008734252
As this is clearly a problem affecting multiple customers is it possible for any updates with the progress regarding a solution to be added to this thread?
This issue is new and it will need to be investigated by NetApp engineering, once we have a solution from them this forum will be updated with a BUG number or a KB article
Upon reviewing further
[04/16 12:59:23 754] Getting dash board info...
[04/16 12:59:23 754] Calling PowerShell to get current exchange server...
[12:59:23.754] [PowerShell Cmdlet]: get-exchangeserver -status -identity <Exchange server name>
[04/16 12:59:23 754] [PowerShell Cmdlet]: get-exchangeserver -status -identity <Exchange server name>
[12:59:23.911] [Remote PowerShell Cmdlet Error]:The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
[04/16 12:59:23 912] [Remote PowerShell Cmdlet Error]:The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
Please verify if you are seeing the same errors in your environment , it is an indication that Exchange Powershell cmdlets are failing.
We are getting an error 0 event with the following message when attempting to run a snapmanager backup.
There are no Storage Groups/Databases that are configured to be backed up by SnapManager
Where is the log extract from (wich logfile?)
Normal powerhsell comands (in Exchange Shell) like get-exchangeserver -status -identity run as expected.
In my case: The Windows schedule job runs but actually nothing happens and there is no log created under C:\Program Files\NetApp\SnapManager for Exchange\Report\Backup.
For what it's worth, I've been advised by support to uninstall the security update. Since that would open the servers up to severety 9.8 remote code execution vulnerabilities, I'd rather forgo backups for a while, or even look for an alternative solution in general.
Here ist the NetApp KB article: SME unable to see database after Exchange Security update KB5001779 - NetApp Knowledge Base
For me it is not an option to uninstall critical security updates. However, Exchange Server 2016 is only supported up to CU11. Any newer CU is not supported and therefore I would not expect an solution by NetApp.
I have migrated to SnapCenter 4.4. (which was already runnig for SQL, VMWare and HANA). This is documented here
Please note that you can not restore an SnapManager Snapshot with SnapCenter.
Backup and restore works fine with SnapCenter and the Exchange Scurity updates.
We're using Snapmgr in 7mode. Snapcenter is not supported so we can 1. uninstall that KB, which is not an option or 2. look at another backup software. Thats not a "solution" netapp...
A Bug has been opened to address this issue . NetApp Engineering is actively working to get a workaround/solution
Please subscribe to this bug
Until a workaround/ solution is identified, only if you are able to (after assessing the security needs of your systems) , we recommend you to roll back the patch.
Here is the kb that documents
Is there currently an issue with that bug page?, I am unable to load it here, it just shows loading...
We have reviewed our environment and we are unable to roll back the latest patch for security reasons.
We also have big issues with SnapManager 7.2.0
Can't roll back the patch either for the same reason (security).
Will need a solution pretty soon, otherwise we will go for another vendors product.
We had exactly the same situation - no SME backups were possible since the security patch was installed.
Deinstallation of KB5001779 was possible (Exchange 2016 CU20) AND a solution for this issue: SME backups now are running fine again!
Of course running Exchange without this security patch is risky and thereford not a good solution - but running without backup is not aceptable at all.
We will migrate to SnapCenter as soon as possible.
NetApp Wins One Silver and One Bronze Stevie® Award in 2022 Stevie Awards for Sales and Customer Service