On 10/03 09:17 , Toni Van Remortel wrote: Just some grammatical and clarity suggestions. It's already a very good piece. I'm sure others will have some suggestions as well. I don't know POD; so I can't really give much formatting advice.
> =head1 Importing data in backups > > If you want to import a backup snapshot into BackupPC before starting any > backups. replace with: This is a technique for importing data from a host you wish to backup with rsync in the future. Doing this will allow you to load your backup with much of the data you will need, thus avoiding transferring it over slow links with rsync. > =head2 Examle 1 : simulating with SSH and rsync, and backing up non default > paths s/Examle/Example/ > I use an address that is bound to 'lo', so you have a simple check on the > import speed (just watch 'lo' with eg 'bmon'). I use an address that is bound to 'lo', so there is a simple check on the import speed (just watch 'lo' with 'bmon' or 'iftop'). > =item Step 2: set up passwordless SSH login =item Step 2: Set up a passwordless SSH login > In normal situations, the backuppc user has no home directory. It is > advised to create one, because that will hold the users pre-shared ssh > keys. To keep it secure, we will only allow the backuppc user to use them. > > usermod -d /home/backuppc backuppc # As a point of interest, the debian package sets up the backuppc user's # home directory to be /var/lib/backuppc, which is the root under which the # data pool is stored. I much prefer this placement, because it means the # stored keys are on the same disk as the data pool, if you put your # backuppc data pool on a separate partition or disk mounted on # /var/lib/backuppc. > mkdir .ssh > cd .ssh > ssh-keygen -t rsa -f simulation_host # As another point of interest, I would suggest chmod'ing .ssh to # permissions 600. > On the client, we like to backup /mnt/samba/data. So we will set that up on > our simulation_host. On the client, we would like to backup /mnt/samba/data. So we will set that up on our simulation_host. > =item Step 4: configuration of the client in BackupPC =item Step 4: Configuration of the client in BackupPC > Configure the client in BackupPC. Fill in every configuration detail like you > would use it for the rest of the backup servers life. Make sure you use the > clients FQDN as 'host' name. Configure the client in BackupPC. Fill in every configuration detail like it will be for the rest of the backup servers life. Make sure you use the clients FQDN as the 'host' name. > =item Step 5: run a full backup =item Step 5: Run a full backup > You can monitor the progress by watching the LOG file, and in a console on > the backup server with eg bmon (bandwidth monitor) on the 'lo' interface. You can monitor the progress by watching the LOG file, and a bandwith monitor (such as 'bmon' or 'iftop') in a console on the backup server. > =head2 Examle 2 : simulating with SSH and rsync, and backing up system paths =head2 Example 2 : Simulating with SSH and rsync, and backing up system paths -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
