nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Exchange KB5001779 breaks SnapManager for Exchange

borismekler

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?

Find more posts tagged with

Accepted answers

NTAp-AVS

A new version of SME is posted that fixes the issue

https://mysupport.netapp.com/site/products/all/details/snapmanager_e2k/downloads-tab/download/30034/7.2.1P1/downloads

Bugs fixed in SME 7.2.1P1:
Bug ID	Title
1393644	SME unable to enumerate DBs after Microsoft security update KB500177

All comments

DAR

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 :

https://techcommunity.microsoft.com/t5/exchange-team-blog/released-april-2021-exchange-server-security-updates/ba-p/2254617/page/3#comments

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?

borismekler

Case number 2008734372 here.

Since this appears to be an easily reproducible issue, I'm hoping for a speedy resolution.

harness

As yet we do not have a workaround for this issue. Please open a support ticket in order to get this issue addressed.

DAR

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?

NTAp-AVS

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

Thanks

NTAp-AVS

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.

borismekler

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.

ADVUNIBN1

Is this only a SnapManager issue or is SnapCenter with this Exchange Patch also affected?

borismekler

SnapCenter (at least version 4.4P1) seems fine.

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

http://docs.netapp.com/ocsc-44/index.jsp?topic=%2Fcom.netapp.doc.ocsc-isg%2FGUID-C3F798B8-5C60-4828-B0C5-48A666251066.html

Please note that you can not restore an SnapManager Snapshot with SnapCenter.

Backup and restore works fine with SnapCenter and the Exchange Scurity updates.