What bareos Version and what windows version are you using? Bareos supports volume mount points, they are detected and also snapshotted.
See http://doc.bareos.org/master/html/bareos-manual-main-reference.html#WindowsReparsePoints On 18.01.2016 13:33, Дмитрий Огородников wrote: > Hi All! > > I’ve found something nasty that looks like a bug to me. As we know, Bareos > supports VSS technology on Windows. When backing up a partition mounted as a > drive with a letter (let’s say “D:/”), VSS works fine. However, if the > partition is mounted in the folder (“C:/mnt/lun0” in my case), we got errors. > > Case 1. > FileSet { > Name = "03-fs" > Include { > Options { > Signature = MD5 # calculate md5 checksum per file > OneFS = no > } > File = C:/mnt > } > } > "File" picks the directory above the mountpoint, and we get this: > 12-янв 10:20 vld-ahvsrv03-fd JobId 830: Generate VSS snapshots. > Driver="Win64 VSS", Drive(s)="C" > 12-янв 10:21 vld-ahvsrv03-fd JobId 830: Fatal error: CreateSGenerate > VSS snapshots failed. ERR=The operation completed successfully. > 12-янв 10:21 vld-ahvsrv03-fd JobId 830: Error: VSS API failure calling > "BackupComplete". ERR=Object is not initialized; called during restore or not > called in correct sequence. > 12-янв 10:21 vld-ahvsrv03-fd JobId 830: Warning: VSS Writer "Shadow > Copy Optimization Writer" has invalid state. ERR=The writer vetoed the shadow > copy creation process during the freeze state. > 12-янв 10:21 vld-testbkp01-sd JobId 830: Elapsed time=00:01:18, > Transfer rate=0 Bytes/second > Doesn't work :( > Also, there are errors about VSS in the Windows log. > > Case 2. > Let’s change these two lines in config: > # OneFS = no > File = C:/mnt/lun0 > Now "File" picks the mountpoint exactly. We get this: > 12-янв 10:24 vld-ahvsrv03-fd JobId 831: Fatal error: No drive letters > found for generating VSS snapshots. > 12-янв 10:24 vld-ahvsrv03-fd JobId 831: Error: VSS API failure calling > "BackupComplete". ERR=Object is not initialized; called during restore or not > called in correct sequence. > 12-янв 10:24 vld-ahvsrv03-fd JobId 831: Warning: VSS Writer "Shadow > Copy Optimization Writer" has invalid state. ERR=The writer vetoed the shadow > copy creation process during the freeze state. > 12-янв 10:24 vld-testbkp01-sd JobId 831: Elapsed time=00:00:09, > Transfer rate=0 Bytes/second > This doesn’t work either, but there are no errors in the Windows log. > > Case 3. > Now "File" picks a folder under the mountpoint: > File = C:/mnt/lun0/test > The result is: > 12-янв 10:28 vld-ahvsrv03-fd JobId 832: Generate VSS snapshots. > Driver="Win64 VSS", Drive(s)="C" > 12-янв 10:28 vld-ahvsrv03-fd JobId 832: VolumeMountpoints are not > processed as onefs = yes. > 12-янв 10:28 vld-ahvsrv03-fd JobId 832: VSS Writer (BackupComplete): > "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE) > <…> > 12-янв 10:28 vld-ahvsrv03-fd JobId 832: VSS Writer (BackupComplete): > "Cluster Database", State: 0x1 (VSS_WS_STABLE) > 12-янв 10:28 vld-testbkp01-sd JobId 832: Elapsed time=00:00:18, > Transfer rate=90 Bytes/second > It works, but the log says «Driver="Win64 VSS", Drive(s)="C"». This is wrong > because “C:/” and “C:/mnt/lun0” are different partitions. So, I can’t be sure > that Bareos uses VSS on my partition (C:/mnt/lun0). Maybe it doesn’t. > > I'm guessing the problem is related to the “get_win32_driveletters” function. > This function presumes every partition is mounted as "driveletter". In fact, > partition can be mounted as "foldername". > > What do you think? Is it a bug, a feature, or normal by-design behavior? > -- Mit freundlichen Grüßen Philipp Storz [email protected] Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92 http://www.bareos.com Fax: +49 221 63 06 93-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- 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.
