adding the list of reference wim to an xml
adding the list of reference wim to an xml
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 would be appreciated as the backup itself is being backed up and transferring the tens of terabyte every time is too much and delta wims are the perfect solution.
-
- Site Admin
- Posts: 474
- Joined: Sun Aug 02, 2015 10:31 pm
Re: adding the list of reference wim to an xml
Do you mean the XML document inside the WIM file? That might make sense, although it gets a little complicated if you try to work through the details of how a referenced WIM file would be identified and then found again automatically later (by path? by name? by GUID?). Then there are the questions of whether it would be enabled by default and would be secure.
Did you consider just using a wildcard pattern with --ref? For example:
Also, note that it is safe to reference files that aren't actually needed.
Did you consider just using a wildcard pattern with --ref? For example:
Code: Select all
wimapply test.wim --ref=*.wim
Re: adding the list of reference wim to an xml
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 (kind of dependencies list) would be great to check wich one is missing in case something goes wrong (and it could be printed to the console output with full path. In those cases, it's better to store more information than not enough. Compared to the TB of data, even a hundreds of path and GUID compressed with LZX will be nothing but a good help.
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 (kind of dependencies list) would be great to check wich one is missing in case something goes wrong (and it could be printed to the console output with full path. In those cases, it's better to store more information than not enough. Compared to the TB of data, even a hundreds of path and GUID compressed with LZX will be nothing but a good help.