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

Here is a mail in /var/mail/root which I received in my server logs I see same packages downloaded many times again and again. The servers which are upgrading are total 5 (4 virtual machines and one host) so is there a way I can save bandwidth on this sort of setup.

share|improve this question
Hi many thanks to you all for the suggestions.I have found a cool solution mentioning here so that if some one comes by chance should help them… Ya I am micro optimizing the thing.This is a pilot project which in my work place if successful would be used to convert a large scale deployment of servers to Linux. – Bond Nov 18 '10 at 5:31

Create apt-cacher on one of the boxes and then point sources.list to your caching proxy. Apt-cacher only downloads requested packages, so no disk space of bandwidth is wasted.

share|improve this answer

As the packages are picked up via HTTP you could setup a caching proxy like Squid and have the servers set to update via that by setting the relevant option in your apt.conf.

You could also use services that specifically optimized for caching packages for apt, but be careful with these if you might have a mix of Debian and Ubuntu machines working through the same proxy. A general HTTP proxy may help you reduce the bandwidth footprint of other incoming services too without having several different proxy services running (I believe Yum uses HTTP too, as do many other service update procedures like clamav's pattern data updates and so forth.

Though really the amount of bandwidth used by regular apt/yum updates isn't all that high by modern standards unless you have a very slow (or very expensive) connection. The only time you would really notice a big difference is installing a fresh machine, when there might be a large backlog of package updates to download from between now and when the CD (or ISO image) you are installing from was created. The extra hassle of running a proxy and making sure the machines use it might cost you more in admin time than it will ever be worth in terms of savings due to reduced bandwidth use and download time. If your concerned is that all the machines could try updating at the same time and so saturate your incoming connection for a time, just make sure such admin tasks (and/or cron jobs) are staggered so one machine finishes before the next starts.

share|improve this answer

You could set up your own mirror I suppose, or find some way to pre-populate the packages into the staging area.

The real question is, do you pay for bandwidth or are you just micro-optimizing?

share|improve this answer
A local mirror could work. If there's no easy way of setting one up then a caching proxy might do the trick as a 'cheat's' way of achieving the same result. – RobM Nov 16 '10 at 10:18

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.