I have several gigabytes of data for archiving, and want to use QuickPar to protect my data. I'd really appreciate some guidance in this effort, as the data is very important to me.
QuickPar has a number of very technical looking options, enough to make me wonder how I should configure it for my usage. I'm a little reluctant to do it wrong and risk loosing data.
The data to be archived is in sets, where a set consists of either thousands of small files in various folder structures, or a few large
files typically hundreds of megabytes in size. The data sets currently exist as:
- Existing data CDs
- ISO images of other data CDs on my computer
- Files organized into folder structures on my computer
The basic plan I have in mind goes something like this:
1. Use 7-Zip to create a single compressed archive of each data set, placing each archive into it's own folder, accompanied by documentation describing the archive contents
2. Use QuickPar to create recovery files for the contents of each folder
3. Place copies of QuickPar, 7-zip, and an MD5SUM program (probably Slavasoft FSUM) into a "utils" folder
4. Use the MD5SUM program to recursively generate a single master checksum file which contains checksums of all files in all folders
5. Burn the entire group of folders, including "utils" and the master checksum file, to a DVD-R
6. Burn a backup copy of the DVD-R
7. Verify the master checksum file of the backup DVD-R
8. Store the backup DVD-R offsite
9. Feel very confident that my data is safe <!-- s
--><img src="{SMILIES_PATH}/icon_smile.gif" alt="
" title="Smile" /><!-- s
-->
Please tell me if my plan is flawed in some way. Your advice about proper configuration for the recovery files will also be appreciated. I really want my data to be protected.
TIA
Offline
Why not try this
pards
<!-- m --><a class="postlink" href="http://www.quickpar.org.uk/forum/viewtopic.php4?t=819">http://www.quickpar.org.uk/forum/viewtopic.php4?t=819</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.quickpar.org.uk/forum/viewtopic.php4?t=810">http://www.quickpar.org.uk/forum/viewtopic.php4?t=810</a><!-- m -->
since its base on commandline tools there is an intrisic limit to the number of files in a tree (or lengths of the path) that kan be parsed.
try and you will find out
Offline
Hello par2ds,
"par2ds":1p4atj22 wrote:
Why not try this
pards
<!-- m --><a class="postlink" href="http://www.quickpar.org.uk/forum/viewtopic.php4?t=819">http://www.quickpar.org.uk/forum/viewtopic.php4?t=819</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.quickpar.org.uk/forum/viewtopic.php4?t=810">http://www.quickpar.org.uk/forum/viewtopic.php4?t=810</a><!-- m -->
since its base on commandline tools there is an intrisic limit to the number of files in a tree (or lengths of the path) that kan be parsed.
try and you will find out[/quote:1p4atj22]
It's good to know this add-on exists, in cases where creating a single bulk archive is undesireable. For my own reasons, I've found it necessary to create the single bulk archive for each data set. Yes, it takes some time, but it's worthwhile for me anyway.
I hoped my post would generate replies about whether I was using QuickPar in the best way possible, for my particular application. The process of using QuickPar to create recovery data, and to recover corrupted data, is somewhat complex.
I'm currently proceeding with the project, using my plan posted above. Still, I'm not quite sure whether my data is getting the best protection QuickPar can offer. In this regard I can only say that my own test show that QuickPar is capable of recovering corrupted/missing data, at least until the amount of missing/corrupted data gets too large.
I thank you for your polite, and relevant reply. Any others?
Offline