Search the Community
Showing results for tags 'archive'.
I created an archive of a large photo directory (mostly consisting of ~20-30MB raw files) and find that, while the on-disk size is just under 1.2TB (where 1TB = 10244) the resulting backup is about 1.7TB. Is this to be expected? I have software compression enabled based on the fact that gzip can still compress the raw files a few percent. Is it possible Retrospect's compression is causing that much expansion?
For the life of me I can't figure out how to exclude certain file types (in my case, specifically, .DS_Store files) from restores from a tape media set. Any suggestions / solutions? I'm using Retrospect 9.0.2 Mac on Mac OSX Server 10.6.8 Cheers C
I have wanted to upgrade my servers to retro 9 for a long time, and now that I am doing so, am really pleased that in my long-term back operations, Retro is doing exactly what I want. I have always wanted to "distill" my periodic backup sets to a smaller number of larger sets over time, as the backups aged. I wanted to keep all my snapshots, though. For reliability, I start new sets every month or quarter, and this results in duplication of data. Retro 9 will distill that duplication out, and leave me with just what I need when I copy the data off to archive sets. Grooming looks like it will do what I want even on existing sets without copying them. Nice work, guys.