NetWorker Blog

Commentary from a long term NetWorker consultant and Backup Theorist

  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Enterprise Systems Backup and Recovery

    If you find this blog interesting, and either have an interest in or work in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system rather than just a bunch of copies made by unrelated software, hardware and processes.
  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Twitter

    Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Client side compression and saveset sizes

Posted by Preston on 2009-09-30

Hi!

The text of this article can now be read at the NetWorker Information Hub. Click here to read it.

Advertisements

One Response to “Client side compression and saveset sizes”

  1. Hi Preston,

    it is indeed the size of the compressed data transfered from the client. I use compression in conjunction with staging when:
    – there is no de-duplication
    – the client has fast cpus
    – the data is “good” (> 1.5 :1 ratio) compressable (text files, database dumps, and so on but NO mp3, mpg, avi, already compressed files)
    – or the bandwidth between client and storage node i small

Sorry, the comment form is closed at this time.

 
%d bloggers like this: