> Hi everyone, > > I am using Bacula 3.02 client and server to backup several machines on my home > network. It has been working great. Recently, I added my first Vista machine > which also happens to be 64-bit and now, although the backups complete, it > takes hours and the statistics are nonsense. I can only guess that sparse > files are at the root cause here, but cannot figure out how to track this > down. >
A backup of a Windows computer uses the BackupRead API to generate the data to go to the SD. BackupRead reads a single stream of data that includes the file attributes, ownership, acls, data, Alternate Data Streams, and sparse information. Bacula shouldn't need to know or care if the file is sparse or not, it just backs up the data that BackupRead returns. I wouldn't expect that 'sparse=yes' would have any useful impact unless there is a bug in which case it will probably break things. Can you restore the job somewhere else (another windows machine) and see if the restored files match up with the backed up files? Look out for any restore errors that say that the file sizes don't match. James ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
