Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a +150Gb FILESTREAM enabled database growing steadily +10Gb weekly, and am curious if anyone has any recommendations | familiarity regarding compression ratios for database backups.

I tried Hyperbac, as I have previously worked with this 3rd-party software, but was greatly disappointed in the compression ratio achieved for the FILESTREAM data. Most of the backup is consumed by the FILESTREAM data.

Sincerely, Sean Fitzgerald

share|improve this question

Compression ratios depend highly on the data contents. If you're storing things like compressed audio (mp3 or other), videos, or images, chances are they you'll get pretty poor compression ratios in your backups - the data is already compressed "natively".

"Normal" database backups often have relatively high compression ratios (comparing datafile size to backup file size) because the database's storage engine is optimized for speed rather than space. That means there's a lot of "wasted" space in the datafiles, so it compresses well.

If you had a database containing only blobs of already compressed data, the backup compression ration would also be very poor.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.