BackupPC acts as a server and is installed on a Linux system, and from there . Documentation contains the whole BackupPC documentation. Adding a CGI Administrator to BackupPC; Modifying the etc. can be found in the BackupPC Documentation: Step 9 CGI Interface. As BackupPC operates on services running on a remote host, I will call Please read BackupPC documentation: step 5 of client setup for a full.

Author: Fektilar Mojinn
Country: Barbados
Language: English (Spanish)
Genre: Photos
Published (Last): 20 September 2015
Pages: 408
PDF File Size: 12.71 Mb
ePub File Size: 2.82 Mb
ISBN: 496-2-31674-239-6
Downloads: 70018
Price: Free* [*Free Regsitration Required]
Uploader: Tern

Administrator Guide: BMS 2.0

BackupPC is highly configurable and easy to install and maintain. Given the ever decreasing cost of disks and raid systems, it is now practical and cost effective to backup a large number of machines onto a server’s local disk or network storage. For some sites this might be the complete backup solution.

For other sites additional permanent archives could be created by periodically backing up the server to tape. Identical files across multiple backups of the same or different PC are stored only once using hard linksresulting in substantial savings in disk storage and disk writes. The CPU impact of compression is low since only new files those not already in the pool need to be compressed.

BackupPC Documentation

No client-side software is needed. On WinXX the standard smb protocol is used to extract backup data. Alternatively, rsync can also be used on WinXX using cygwinand Samba could be installed on the linux or unix client to provide smb shares.

Single files can be downloaded from any backup directly from the CGI interface. Zip or Tar archives for selected files or directories from any backup can also be downloaded from the CGI interface. Finally, direct restore to the client machine using smb or tar for selected files or directories is also supported from the CGI interface. Configuration settings allow machines connected via slower WAN connections eg: Flexible configuration parameters allow multiple backups to be performed in parallel, specification of which shares to backup, which directories to backup or not backup, various schedules for full and incremental backups, schedules for email reminders to users and so on.

Configuration parameters can be set system-wide or also on a per-PC basis. Users are sent periodic email reminders if their PC has not recently been backed up.

Email content, timing and policies are configurable.

A full backup is a complete backup of a share. BackupPC can documentatuon configured to do a full backup at a regular interval typically weekly.

BackupPC can be configured to keep a certain number of full backups. Exponential expiry is also supported, allowing full backups with various vintages to be kept for example, a settable number of most recent weekly fulls, plus a settable number of older fulls that are 2, 4, 8, or 16 weeks apart. An incremental backup is a backup of files that have changed since the last successful full or incremental backup.

Starting in BackupPC 3. A full backup has level 0. A new incremental of level N will backup all files that have changed since the most recent backup of a lower level.

The default value is all level 1, which makes the behavior the same as earlier versions of BackupPC: For SMB and tar, BackupPC uses the modification time mtime to determine which files have changed since the last lower-level backup. That means SMB and tar incrementals are not able to detect deleted files, renamed files or new files whose modification time is prior to the last lower-level backup.


Rsync is more clever: Deleted, new files and renamed files are detected by Rsync incrementals. BackupPC can also be configured to keep a certain number of incremental backups, and to keep a smaller number of very old incremental backups. If multi-level incrementals are specified then it is likely that more incrementals will need to be kept since lower-level incrementals and the full backup are needed to reconstruct a higher-level incremental. BackupPC “fills-in” incremental backups when browsing or restoring, based on the levels of each backup, giving every backup a “full” appearance.

This makes browsing and restoring backups much easier: When a full backup fails or is canceled, and some files have already been backed up, BackupPC keeps a partial backup containing just the files that were backed up successfully. The partial backup is removed when the next successful backup completes, or if another full backup fails resulting in a newer partial backup.

A failed full backup that has not backed up any files, or any failed incremental backup, is removed; no partial backup is saved in these cases.


The partial backup may be browsed or used to restore files just like a successful full or incremental backup. With the rsync transfer documejtation the partial backup is used to resume the next full backup, avoiding the need to retransfer the file data already in the partial backup.

BackupPC pools identical files using hardlinks. By “identical files” we mean files with identical contents, not necessary the same permissions, ownership or modification time. Two files might have different permissions, ownership, or modification time but will still be pooled whenever the contents are identical.

This is possible since BackupPC stores the file meta-data permissions, ownership, and modification time separately from the file contents. Based on your site’s requirements you need to decide what your backup policy is.

BackupPC is not designed to provide exact re-imaging of failed disks. See “Some Limitations” for more information. BackupPC saves backups onto disk.

Because of pooling you documeentation relatively economically keep several weeks of old backups. At some sites the disk-based backup will be adequate, without a secondary tape backup. This system is robust to any single failure: If the server disk fails, BackupPC can be restarted on documenattion fresh file system, and create new backups from the clients. The chance of the server disk failing can be made very small by spending more money on increasingly better RAID systems.

However, there is still the risk of catastrophic events like fires or earthquakes that can destroy both the BackupPC backupc and the clients it is backing up if they are physically nearby.

This backup can be done perhaps documentatin using the archive function of BackupPC. Other users have reported success with removable disks to rotate the BackupPC data drives, or using rsync to mirror the BackupPC data pool offsite. The project home page can be found at:.

This page has links to the current documentation, the Github and SourceForge project pages and general information.

BackupPC Documentation

Generally use of SourceForge has been deprecated in favor of Github. All source code and development has moved to Github starting in Releases will continue to be available on both Github and SourceForge.

BackupPC has a Wiki at https: Documentaion is encouraged to contribute to the Wiki. Three BackupPC mailing lists exist for announcements backuppc-announcedevelopers backuppc-develand a general user list for support, asking questions or any other topic relevant to BackupPC backuppc-users. The lists are archived on SourceForge and Gmane. The SourceForge lists are not always up to date and the searching is limited, so Gmane is a good alternative.


The backuppc-announce list is moderated and is used only for important announcements eg: It is low traffic. You only need to subscribe to one of backuppc-announce and backuppc-users: The backuppc-devel list is only for developers who are working on BackupPC. Do not post questions or support requests there. But detailed technical discussions should happen on this list.

If you want to mirror linux or unix files documenfation directories to a remote server you should use rsync, http: BackupPC uses rsync as a transport mechanism; if you are already an rsync user you can think of BackupPC as adding efficient storage compression and pooling and a convenient user interface to rsync. Two popular open source packages that bacuppc tape backup are Amanda http: These packages can be used as complete solutions, or also as back ends to BackupPC to backup the BackupPC server data to tape.

Various programs and scripts use rsync to provide hardlinked backups. See, for example, Mike Rubel’s site http: Unison is a utility that can do two-way, interactive, synchronization. An external wrapper around rsync that maintains transfer data to enable two-way synchronization is drsync; see http: BackupPC provides many additional features, such as compressed storage, hardlinking any matching files rather than just files with the same nameand storing special files without root privileges.

Backupc these other programs provide simple, effective and fast solutions and are definitely worthy of consideration.

The new features planned for future releases of BackupPC are on the Wiki at http: BackupPC already has more than enough features for my own needs. The main compensation for continuing to work on BackupPC is knowing that more and more people find it useful.

So feedback is certainly appreciated, both positive and negative. Beyond being a satisfied user and telling other people about it, everyone is encouraged to add links to http: Unlike the commercial products in this space, I have a zero budget in both time and money for marketing, PR and advertising, so it’s up to all of you!

Feel free to vote for BackupPC at http: Also, everyone is encouraged to contribute patches, bug reports, feature and design suggestions, new bacluppc, Wiki additions you can do those directly and documentation corrections or improvements. Answering questions on the mailing list is a big help too.

A linux, solaris, or unix based server with a substantial amount of free disk space see the next section for what that means. The CPU and disk performance on this server will determine how many simultaneous backups you can run. You should be able to run simultaneous backups on a moderately configured server. Several users have reported significantly better performance using reiserfs compared to ext3 for the BackupPC data file system. When BackupPC starts with an empty pool, all the backup data will be written to the pool on disk.

After more backups are done, a higher percentage of incoming files will already documentatikn in the pool. BackupPC is able to avoid writing to disk new files that are already in the pool. Disk reads from the pool are still needed to do file compares to verify files are an exact match.

If you don’t have perl, please see http: