Bareos Bug Tracker
Bareos Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000963bareos-core[All Projects] file daemonpublic2018-06-12 20:442018-06-12 20:44
Reporterassafin 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOSFreebsd OS Version11.0
Product Version16.2.4 
Target VersionFixed in Version 
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):

diskshadow
add volume f:
begin backup
create
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.
bareos-master: impact
bareos-master: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2018-06-12 20:44 assafin New Issue


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker