Jump to content

Search the Community

Showing results for tags 'compression'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 7 results

  1. It is possible to obtain a technical detail of the compression capabilities of Retrospect for Software in hard drives ? Thanks
  2. Hi, I'm a bit confused as to what just happened, but in my last backup the Data Compression was switched on as in the screen shot attached. However it is turned off as an option in the script and neither has it ever before been 'on' looking at my previous logs for this script. Any ideas as to how it could have turned on? Thanks
  3. 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?
  4. Hi, Can someone tell me what the influence on backup file size will be when creating a backup with the option Software data compression on? Will the difference in file size of the compressed backup files compared to the original size differ according to the type of files? For example, text and office documents would probably give the best results in compression. How about graphics? Will they compress at all? thanks,
  5. i think i'm finally starting to get a handle on how Retrospect does its thing, but there is one thing i have noticed that has me baffled. When i set up my scripts, i decided to switch off compression as its going to slow things down, and backing up over 12TB a week is not quick! Once i get some extra hardware for speeding up the connections maybe i'll swicth it on... anyway, I have 5 separate scripts running each week, and then a second set of 5 running the next week. This lets me have a weekly rotation of LTO5 tapes that i can keep off site. For reasons i dont understand, In the Activities Window one of the scripts (and it just happens to be for the largest data set) is showing compression is ON. Yet if i check the script itself, its supposed to be OFF. All the scripts were written at the same time, and i checked that they all had compression off, so why is this one script behaving incorrectly?
  6. Retro 10.2.0 (221) engine on Mac OS X 10.8.4 on a Mac Mini. I have been having trouble with media set copies, and so have been very watchful of the operations that I do to ensure that the output is sound. I had a small media set, about 7.8 GB, we'll call it orig. I copied it to arch, with compression enabled in the script. The resultant media set was 2.2 GB, but had the requisite 203 files. I wanted to verify that the 2.2 GB was "enough" by running a script *without* compression enabled to "re-inflate" the data. I copied the copy to "zjunk" without compression, and the result had 203 files, and 2.2 GB. I then tried resetting zjunk, and copying orig to zjunk, which resulted in 7.8 GB and 203 files. I then tried copying arch (compressed) on top of the files already in zjunk, with options un-checked so that no duplicate elimination was done. The resulting zjunk was 406 files and 9.9 GB. It appears that "compression" is a one-way operation on media sets. un-checking the "compress" option in the script will NOT un-compress the resultant copy. It also appears that compressed, and un-compressed data can be "mixed" in a given media set. The media sets, therefore, have no "compress attribute". Is this as it should be? It would be nice to get more information on the compression. There are a few places where "amount saved" is put in the logs, but when estimating the amount of space/tape that will be required, that compression performance data can be really useful.
  7. I am copying rebuilt Retro 6 tapes to a disk media set, and have requested data compression in the "options" in the script doing the copy. The resultant copy works, but the resultant disk media set is larger than expected and the status window in "activities" says data compression is "OFF". It appears that Retro 9 ( is ignoring my request for data compression
  • Create New...