Setting up a Debian archive mirror

Whether to mirror

While we appreciate all new mirrors, every prospective mirror maintainer should make sure that they can answer these questions before trying to start their own mirror:

What to mirror

The main mirror page lists the archives available for mirroring.

Please see the mirror size page for more precise information about mirror sizes.

The debian-security/ archives contain the security updates released by the Debian security team. It sounds interesting to everyone, but since the security updates are sporadic, one would have to mirror it very often to be up to date (or use push mirroring) so we do not recommend it. Debian makes every effort to maintain the high availability of instead.

NB: the debian-non-US/ archive is deprecated since the 3.1 (sarge) release in June 2005.

Where to mirror from

Many people seem to think that is the canonical location of Debian packages and that it will be best for them to mirror from that site. This is not true. is merely one of several servers that get updated from an internal Debian server. That address is presently located on a single server, and it still exists mainly for backwards compatibility.

The official mirrors are meant to be a good place to mirror from. Any of the servers in the full list of mirrors that have the tags Type: Push-Primary or Type: Push-Secondary should be good to mirror from. Please use one that is close to you both network-wise and geographically.

There is no real difference between different Push-Primary mirror servers as far as mirroring is concerned. On the other hand, if many people use (and unfortunately, they do), this needlessly wastes the donated bandwidth.

Mirror administrators in the United States should mirror from (the official mirror address from the US, which is a Push-Primary mirror). But, since that address is also a round-robin alias for several machines, it usually makes sense to determine which of the components is the best and then mirror from that particular one.
The upside of doing that is that it avoids the risk of failures when performing a two-stage rsync (different stages might end up on different machines during time windows where they have different data, causing a race condition). The downside is that it concentrates on a single site the performance of which may vary, but that is currently inherent to our mirror network in general.

How to mirror

The recommended method of mirroring is with the so called ftpsync scriptset, available in two forms:

The mirroring protocol which we strongly recommend is rsync.

Please do not mirror Debian using wget and other tools based on FTP. They may seem to work well, but will have numerous issues (they can't detect hard links, it's harder to make partial mirrors, etc).

rsync setup

We recommend to use the ftpsync scriptset to mirror the archive. Follow the README file included to set up mirroring.

If you do use your own scripts, the minimal functionality that must be supported is as follows:

Partial mirroring

Considering the already large size of Debian archive, some people prefer to mirror only parts of it they need. If you want to exclude something, you should exclude architectures.

With the recommended ftpsync, this can be done by editing the ARCH_EXCLUDE variable.

We strongly advise against excluding the project/, doc/ and other subdirectories. Usually these are minor in size and yet useful to users. Especially project/trace helps very much if there are any mirror issues.

It is possible to use other specially written scripts, but they are usually not necessary, and not recommended for official mirrors.

When to mirror

The main archive gets updated four times a day. The mirrors commonly start updating around 3:00, 9:00, 15:00 and 21:00 (all times UTC), but these are never fixed times and you should not fixate your mirror on them.

Your mirror should update a few hours after one of the main archive mirror pulses. You should check if the site you're mirroring from leaves a time stamp file in their project/trace/ subdirectory. The time stamp file will be named like that site, and it will contain the completion time of their last mirror update. Add a couple of hours to that time (to be safe) and mirror then.

It is essential that your mirror is in sync with the main archive. A minimum of 4 updates per 24 hours will ensure that your mirror is a true reflection of the archive. Please understand that mirrors that are not in sync with the main archive will not be listed in the official mirrors listing.

The easiest way to automatically have the mirror run every day is to use cron. See man crontab for details.

Note that if your site is being triggered with a push mechanism, then you don't need to worry about any of this.

Push-triggered mirroring

Push mirroring is a form of mirroring that we have developed to minimize the time it takes for changes to the archive to reach mirrors. An upstream mirror uses an SSH trigger to tell the downstream mirror to update itself. The pushing is usually limited to a secure trigger that takes no variable data, so the rest of the mirroring process is simply pull like with a cron job.

Push mirroring is necessary to keep multiple servers in synchronization (such as servers in DNS round-robin aliases like, and we use it for our first and second tier mirrors. But as this method requires a bit more effort to set it up, it isn't commonly done for private mirrors.

For a more detailed description of how this works, why it is secure, and how to set a push mirror, please see the complete explanation.

Recommended additional settings

If you are going to make the Debian mirror available through HTTP, please add the following settings to your Apache configuration (presuming, of course, you will use Apache), within the <Directory /path/to/your/debian/mirror> block, where /path/to/your/debian/mirror should be the actual name of the directory where you keep the mirror:

   Options +Indexes +SymlinksIfOwnerMatch
   IndexOptions NameWidth=* +SuppressDescription

This enables the directory indices and makes sure that following symlinks will work. The file names in the directory indices won't be truncated, and (mostly nonexistent) descriptions won't be shown.

In Apache 1.3.x, the following option may also be added:

   DirectoryIndex .

Do not add that option in Apache 2.x.

How to add a mirror to the mirror list

Once a mirror is set up, it should be registered with Debian in order to get included in the mirror list. Submissions can be done using our simple web form.

Any problems or enquiries can be sent to