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: Kazranris Magal
Country: Norway
Language: English (Spanish)
Genre: Environment
Published (Last): 11 May 2005
Pages: 485
PDF File Size: 12.68 Mb
ePub File Size: 18.33 Mb
ISBN: 577-8-11590-527-1
Downloads: 52686
Price: Free* [*Free Regsitration Required]
Uploader: Kagagar

BackupPC is highly configurable and easy to install backhppc 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 docuumentation disk or network storage. For some sites this might be the complete backup solution. For other sites additional permanent archives could backuppd 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. 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 Documenttation 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: Configuration parameters can be set system-wide or also on a per-PC basis.

Email content, timing and policies are configurable. Backup basics Full Backup A full backup is a complete backup of a share. BackupPC can be configured documenntation 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. Incremental Backup 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 Dpcumentation 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.

  DBM - 21S PDF


BackupPC “fills-in” incremental documentatioj 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: Partial Backup When a full backup fails or is canceled, and some files have already been backed up, BackupPC keeps docu,entation partial backup containing just the files that were backed up successfully.

The partial backup is removed when the next successful backup completes, or if backupcp 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 method the partial backup is used to resume the next full backup, avoiding the need to retransfer the file data already in the partial backup.

Identical Files 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.

Backup Policy 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 can 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 doucmentation a fresh file system, and create new backups from the clients. The chance of the server disk failing can be made very docjmentation 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 server and the clients it is backing up if they are physically nearby.

This backup can be done perhaps weekly using the archive function of BackupPC. Other users have reported success with removable disks to rotate backuppcc BackupPC data drives, or using rsync to mirror the BackupPC data pool offsite. The home page can be found at: SourceForge project The SourceForge project page is at: Everyone is encouraged to contribute to the Wiki. Anyone with a SourceForge account can edit the Wiki.

Mailing lists 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.

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. To post a message to the backuppc-users list, send an email to backuppc-users lists. 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.


BackupPC Documentation

These packages can be used as complete solutions, documentationn also as back ends to BackupPC to backup the BackupPC server data to tape. Various programs and scripts use rsync to provide hardlinked backups.

Unison is a utility that can do two-way, interactive, synchronization. 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. But these other programs provide simple, effective and fast solutions and are definitely worthy of consideration.

Comments and suggestions are welcome. You can help BackupPC is free. BackupPC already has documentwtion than enough features for my own needs. The main compensation for continuing to work on BackupPC is knowing that documenntation and more documentatioon find it useful.

So feedback is certainly appreciated, both positive and negative. 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! Also, everyone is encouraged to contribute patches, bug reports, feature and design suggestions, new code, Wiki additions you can do those directly and documentation corrections or improvements.

Answering questions on the mailing list is a big help too. The CPU and disk documenration 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.

BackupPC Documentation

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 be 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. Zlib” and “perldoc Archive:: Zip” to see if you have these modules.

You’ll need to install the File:: RsyncP module if you want to use Rsync as a transport method. It’s pretty easy to fetch and compile samba, and just grab smbclient and nmblookup, without doing the installation. Use “tar –version” to check your version.

Use “rsync –version” to check your version. What type of storage space do I need? BackupPC uses hardlinks to pool files common to different backups. You can of course use any kind of RAID system or logical volume manager that combines the capacity of multiple disks into a single, larger, file system. Such approaches have the advantage that the file system can be expanded without having to copy it. Any standard linux or unix file system supports hardlinks. NFS mounted file systems work too provided the underlying file system supports hardlinks.