Dear Bareos Community, I'm in the process of transitioning from Bacula to Bareos for obvious reasons - nothing gets fixed anymore in Bacula. I have a few questions which I could not answer going through the Bareos release notes - so maybe one of you guys can help me out here - or point me to the right documentation:
[1] Windows Backups & VSS I am using Bacula file daemon (Windows x64) version 5.2.10 (the last version available for free) and Bacula director version 5.2.6 (Linux x86) . This version has a nasty bug when backups using VSS are made. There is a miscount of "+1" between the files backed up and the number of files being reported as backed up. For example: if a job consists of 50 files, Bacula director ends up with 51 files in the catalog. If you run a VolumeToCatalog after that, the system ends up with an error (checked 50 files, expected 51) which leads either to a "verify failed" status or a director lockup. Has this problem been reported / resolved in Bareos? [2] Verify and Restore Performance My "backup server" (the machine holding the tape drive and running the director) is an older system (Pentium III) which is equipped with an Adaptec 39320 SCSI controller (Ultra 320 SCSI LVD), a DLT-1 Quantum Tape Drive (Ultra 160 SCSI LVD) and a Seagate Ultra 320 / 10000rpm harddisk. This configuration has no problem whatsoever backing up data from the harddisk to the tape. During restores and verifies, however, I experience a lot of shoe shining. I do understand that data spooling is not implemented for restores and verifies. However, as the system is perfectly capable of doing backups from the local harddisk to tape (without data spooling), I would think restores to the local harddisk should work as well - not to mention verifies (VolumeToCatalog) where the only job is reading the data from tape and calculating MD5 checksums. Can somebody provide some information if Bareos is different in that matter or what I might have to change in my configuration to make at least VolumeToCatalog verifies work without shoe shining? [3] Verify Jobs and File Daemons For a "VolumeToCatalog" verify job, can someone please explain why I need a file daemon? Can I define the job without a file daemon? I am asking because I would like to be able to run verify jobs without the need to have the file daemon available which created the backup in the first place. Thanks for your help, Markus -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
