View Issue Details

IDProjectCategoryView StatusLast Update
0000963bareos-corefile daemonpublic2024-05-15 15:47
Reporterassafin Assigned Toarogge  
Status closedResolutionreopened 
OSFreebsd OS Version11.0 
Product Version16.2.4 
Summary0000963: Windows Backup using VSS
DescriptionWe have a Baros-Server running on FreeBSD. We are trying to make a backup of a Windows Server on which an Exchange Server is installed.

Everything is running OK. But after some time we noticed that the Exchange Server transactions logs are not being rolled and that the backup size increases substantially.

After digging around on the Windows Server we saw that the volume shadow copies are not being deleted (yes, we are using Enable VSS = yes ). We think that this may result in the growth of the transaction logs.

Here is an example (on the Windows Server via CMD):

add volume f:
begin backup
end backup

The "end backup" will delete the shadow copy. And we assume that this will also lead to a truncation of the transaction log.

So, the question is: Does Bareos (the Windows Client) ends the WindowsVSS in a correct way, so that the shadow copy is being deleted?

If you need more infos, we can gladly help.

-- Alaa
TagsNo tags attached.




2019-08-01 10:18

manager   ~0003548

Sorry, but Bareos is not able to backup an Exchange database using VSS at this time.
As it doesn't handle Exchange correctly the Logs are not truncated and you'll expierience a growth in transaction logs.


2021-07-26 00:03

reporter   ~0004193

Is there any progress towards backing up Exchange 2016/2019 and have it commit the logs? Windows Server Backup has two options for the VSS, Full and Copy. The Full method will truncate the logs. Is there any way to pass the Full method for VSS with Bareos?


2024-05-15 15:47

manager   ~0005942

This was reported for an end-of-life (EOL) version of Bareos.

If you can reproduce this bug against a currently maintained version of
Bareos please feel free to open a new issue against that version at

Thank you for reporting this bug and we are sorry it could not be fixed.

Issue History

Date Modified Username Field Change
2018-06-12 20:44 assafin New Issue
2019-08-01 10:18 arogge Assigned To => arogge
2019-08-01 10:18 arogge Status new => resolved
2019-08-01 10:18 arogge Resolution open => won't fix
2019-08-01 10:18 arogge Note Added: 0003548
2019-08-01 10:18 arogge Status resolved => closed
2021-07-26 00:03 Ryushin Status closed => new
2021-07-26 00:03 Ryushin Resolution won't fix => reopened
2021-07-26 00:03 Ryushin Note Added: 0004193
2024-05-15 15:47 arogge Status new => closed
2024-05-15 15:47 arogge Note Added: 0005942