MS Exchange 2013 VSS writer error while backup. No log files were truncated

[le-sky]

Hi I'm trying to migrate from Windows Backup Server to PBS as an alternative on the Windows Server client, but facing with error from MS Exchange.

Guest os: Windows Server 2012R2
App: MS Exchange 2013 CU23 standalone
Backup service: on PVE to PBS with installed and launched qemu-ga on client machine

When I've initiated a backup procedure by PVE, first I get warning and info like these (e.g. db Spam for other DBs is the same):

Warning    31.07.2022 22:32:33    MSExchangeRepl    2038    Exchange VSS Writer  Microsoft Exchange VSS Writer backup failed. No log files were truncated. Instance <generated uuid>. Database <db uuid>.
Information    31.07.2022 22:32:33    ESE    2006    ShadowCopy    "Information Store - Spam (7744) Shadow copy instance 2 completed successfully.

Then 1 error and 1 information::

Error    31.07.2022 22:32:33    MSExchangeRepl    2034    The Microsoft Exchange Replication service VSS Writer (Instance <same inst. uuid>) failed with error FFFFFFFC when processing the backup completion event.
Information    31.07.2022 22:32:33    MSExchangeRepl    2037    The Microsoft Exchange Replication service VSS Writer (Instance <same inst. uuid>) backup has been successfully shut down.

after some minutes I get info that VSS Provider was stopped:

The VSS service is shutting down due to idle timeout.

Also I've repaired data by DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow says everything is ok, but the problem with logs keeps staying.

Please help what could be wrong here?

 

[1liminal1]

Did you ever find a solution to this? I've just migrated my Hypervisor to ProxMox and need a new solution to backup Exchange 2016.

 

[le-sky]

Did you ever find a solution to this? I've just migrated my Hypervisor to ProxMox and need a new solution to backup Exchange 2016.

Unfortunately not
Once in two week doing full backup by WBS turncates the logs. Maybe I will install the PS-script as workaround for this but it is not a solution ofc
Maybe moving to DAG solves the problem

 

[1liminal1]

Ahh ok, thanks.
Im actually going to try Veeam community edition, see how that goes

 

[ITT]

You have already the related COM-Security "fixed"?

First Reply:
Com Security VSS

 

[le-sky]

You have already the related COM-Security "fixed"?

First Reply:
Com Security VSS

Yes, Network Service is added to Access Permissions with allowed Local and Remote Accesses

 

[ITT]

Ah, i think this is related to 2012R2, i had this Problem too in the past!
Try googling around and you will find it.

 

[le-sky]

Ah, i think this is related to 2012R2, i had this Problem too in the past!
Try googling around and you will find it.

oh no.. guess i've shovelled entire Internet over, twice
ok I keep trying)