wimlib

wim capture d:\ some_network_path\backup.wim
so nothing fancy. We renamed the executable to "wim" to fasten typing on of commands. We are really busy at the moment so we didn't had time to further test wimlib for our use case. We will report as soon as we have done new tests.

If it's already implemented, the behavior I reported is strange. We archived a folder containing only one .7z file. So the low CPU usage phase is difficult to understand , because only a pure checksum phase without compression can lead to such a low CPU usage if I'm correct. In our test, even with 2...

Thank you for the very good explanation. In the case where the file being added has a unique size (no other files that has already been processed has the same size), it would be safe to compute the checksum and compress at the same time, because only files of the same size can have the same content ...

1) The read/write speed is about the same (40MB/sec in both ways) during the whole process. Only the cpu usage changes significantly when a .7z file is being processed (comparable to archiving without compression). What I mean with wim archive being recompressed is that an already compressed .wim ar...

Ok, Process Monitor revealed it's due to a big .7z file. Of course this file was the last one so it took more than a day to find it :D 1) It appears that compression stops when archiving 7z files (8%CPU used), which is a really good idea as it is not further compressible. But wim archives are being ...

Hi Synchronicity, By relative path would be the best I think. But if *.wim automatically sort wim files and ignores non-relevant ones, it can be a good solution. We can also create a dir for each backup, with all relevant delta wims to avoid time-consuming scans. Nonetheless, a list of required wims...

Would it be possible to add the wim given on the command line with --delta-from to an xml to be able to apply a wim without to much hassle. After a month of backup, we have to specify 30 refs. As it's not possible to append to a delta wim, it will grow to 360 at the end of the year. Any solution wou...

Yes the system has 16GB of memory. We will look into it more in depth.

On one of our folder (containing a 40GB partition dump made with dd, without compression and some small checksum files) wimlib was really fast until 99%. At this point, cpu usage dropped to 1% for wimlib, but the source and destination HDD continued to read and write for pretty long. We waited 5 min...

Regarding the memory usage, the overall memory usage (displayed in the task manager) is of 1.2GB on startup. It has nothing to do with wimlib (not started at that point). After Wimlib did backup the 3TB HDD and the process is not there anymore (job done) the memory usage (again nothing to do with wi...