Hello, after Windows client upgrade from public 5.2.10 to developers' gift 7.0.5, I have noticed that incremental jobs started to be too big and too slow. Before upgrade with 5.2.10:
Elapsed time: 4 hours 28 mins 43 secs FD Files Written: 180,897 FD Bytes Written: 18,411,348,578 (18.41 GB) After upgrade with 7.0.5: Elapsed time: 1 day 8 hours 31 mins 19 secs FD Files Written: 10,770,656 FD Bytes Written: 24,493,173,950 (24.49 GB) The difference is in ~ 10,000,000 entries. Full job has ~ 33,000,000 entries, where there are ~ 10,000,000 directories and ~ 23,000,000 files (strange itself). Job listing confirmed, that 7.0.5 Windows client includes all directory entries on the server in the incremental backup. Please, is there a configuration possibility to work around this problem? I have tried 7.4.0 for personal use also, and it works like 5.2.10, so maybe just 7.0.5 has this bug? Meantmime, I had to return to 5.2.10. Thank you. -- Rudolf Cejka <cejkar at fit.vutbr.cz> http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
