BACKUPPC DOCUMENTATION PDF
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.
|Published (Last):||4 October 2012|
|PDF File Size:||2.92 Mb|
|ePub File Size:||8.78 Mb|
|Price:||Free* [*Free Regsitration Required]|
You will need to fill in the correct paths for ssh2 on the local host server and GNU tar on the client. The matching blocks and new data is sent back, allowing the client file to be reassembled. The information included will probably change. When you install V4, no changes are made to any V3 backups. The default setting of 3 days means that a partial older than 3 days is ignored when the next full backup is done.
Full path for tar on the client. This means the 1st and 4th incrementals level 1 go all the way back to the full. Download Zip archive With this option a zip file containing the selected files and directories is downloaded. For example, one week later, a new full is completed and the oldest is deleted, giving:.
If you find a solution to your problem that could help other users please add it to the Wiki at https: BackupPC does not consider downloading a zip file as an actual restore operation, so the details are not saved for later browsing as in the first case.
A failed full backup is saved as a partial backup. Storage layout BackupPC resides in several directories: The CGI script uses this value to serve up image files. BackupPC can be configured to keep a certain number of full backups.
The example above specifies keeping 4 of the most recent full backups 1 week interval two full backups at 2 week intervals, and 3 full backups at 4 week intervals, eg:. In certain cases you might want several distinct clients to refer to the same physical machine.
This number per client will be kept around before the oldest ones are pruned. Maximum number of log files we keep around in each PC’s directory ie: Which host directories to backup when using tar transport. Alternatively, backup files can be restored using manual commands. Filling is no longer useful, since file mangling and compression doesn’t make a filled backup very useful.
Command to run tar on the client. The combination of pooling common files and compression can yield a factor of 8 or more overall saving in backup storage. False for all backups prior to v1. Compressed file format The compressed file format is docjmentation generated by Compress:: The host-specific configuration can be edited from the host summary page using the link in the left navigation bar.
A full backup with rsync sets the –ignore-times option, which causes every file docummentation be examined independent of attributes. Config and Log Directories In this installation the configuration and log directories are located in the following locations: Depending upon your mail handler this is either a plain name eg: Several users have reported significantly better performance using reiserfs compared to ext3 for the BackupPC data file system.
Administrator Guide: BMS 2.0
The best way to copy a pool file system, if possible, is by copying the raw device at the block level eg: 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. 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.
For unix machines you can run nmbd the NetBios name server from the Samba distribution so that the machine responds to a NetBios name request. The permissions should look like this:. Your browser should prompt you with the filename and ask you whether to open the file or save it to disk.
See the zlib documentation for more information about compression levels. Optional commands to run before and after dumps and restores, and also before and after each share of a dump. Changing compression on or off after backups have already been done will require both compressed and uncompressed pool files to be stored.