BackupPC

Source: Wikipedia, the free encyclopedia.
BackupPC
Initial releaseSeptember 21, 2001; 22 years ago (2001-09-21)
Stable release
4.4.0 / June 20, 2020; 3 years ago (2020-06-20)[1]
Repository
Written inPerl
Cross-platform
TypeBackup
LicenseGPL 3
Websitebackuppc.github.io/backuppc

BackupPC is a

UNIX-based server. No client is necessary, as the server is itself a client for several protocols that are handled by other services native to the client OS. In 2007, BackupPC was mentioned as one of the three most well known open-source backup software,[2] even though it is one of the tools that are "so amazing, but unfortunately, if no one ever talks about them, many folks never hear of them".[3]

D2D2T solution, if the archive function of BackupPC is used to back up the disk pool to tape. BackupPC is not a block-level backup system like Ghost4Linux but performs file-based backup and restore. Thus it is not suitable for backup of disk images or raw disk partitions.[4]

BackupPC incorporates a

DMZ
.

It is published under the GNU General Public License.

Protocols supported

BackupPC supports NFS, SSH, SMB and rsync.[5]

It can back up Unix-like systems with native ssh and tar or rsync support, such as Linux, BSD, and OS X, as well as Microsoft Windows shares with minimal configuration.[6]

On Windows, third party implementations of tar, rsync, and SSH (such as Cygwin) are required to utilize those protocols.[7]

Protocol choice

The choice between tar and rsync is dictated by the hardware and bandwidth available to the client. Clients backed up by rsync use considerably more CPU time than client machines using tar or SMB. Clients using SMB or tar use considerably more bandwidth than clients using rsync. These trade-offs are inherent in the differences between the protocols. Using tar or SMB transfers each file in its entirety, using little CPU but maximum bandwidth. The rsync method calculates checksums for each file on both the client and server machines in a way that enables a transfer of just the differences between the two files; this uses more CPU resources, but minimizes bandwidth.[8]

Data storage

Version 3.x

BackupPC uses a combination of hard links and compression to reduce the total disk space used for files. At the first full backup, all files are transferred to the backend, optionally compressed, and then compared. Files that are identical are hard linked, which uses only one additional directory entry. The upshot is that an astute system administrator could potentially back up ten Windows XP laptops with 10 GB of data each, and if 8 GB is repeated on each machine (Office and Windows binary files) would look like 100 GB is needed, but only 28 GB (10 × 2 GB + 8 GB) would be used.[9] Compression of the data on the back-end will further reduce that requirement.

When browsing the backups, incremental backups are automatically filled back to the previous full backup. So every backup appears to be a full and complete set of data.

Version 4.x

Version 4.x can still use V3.x repositories, but all new backups use a new format (seamless upgrade). The overall performance is higher than with the V3.x version.

See also

References

  1. ^ "Releases - backuppc/backuppc". Retrieved 2 November 2020 – via GitHub.
  2. ISBN 978-0-596-10246-3
  3. ^ Shawn Powers: Linux Journal: BackupPC Linux Journal, March 17, 2011.
  4. ^ Falko Timme: Back Up Linux And Windows Systems With BackupPC, January 2007. Retrieved July 30, 2010.
  5. ^ Shawn Powers: Linux Journal: BackupPC Linux Journal, March 17, 2011.
  6. ^ Don Harper: BackupPC – Backup Central Archived 2010-03-18 at the Wayback Machine, May 2008. Retrieved July 30, 2010.
  7. ^ Mike Petersen: Deploying BackupPC on SLES Archived 2011-12-17 at the Wayback Machine. February, 2008. Retrieved 30 Jul. 2010.
  8. ^ Andrew Tridgell: Efficient Algorithms for Sorting and Synchronization, February 1999. Retrieved September 29, 2009.
  9. ^ "BackupPC Documentation".

External links

Retrieved from "https://en.wikipedia.org/w/index.php?title=BackupPC&oldid=1176479381"