X-Git-Url: http://git.rot13.org/?p=BackupPC.git;a=blobdiff_plain;f=doc-src%2FBackupPC.pod;h=c0b3b7db815308c97deaf4ef49d071a725af4432;hp=a780f9e3da13e583400cab50abcfe46ac032bd0e;hb=89175f12447774d75a0926230615bfa900bb62d9;hpb=e951f787a66c5bd9e9955c3f657a5b44289c0fe1 diff --git a/doc-src/BackupPC.pod b/doc-src/BackupPC.pod index a780f9e..c0b3b7d 100644 --- a/doc-src/BackupPC.pod +++ b/doc-src/BackupPC.pod @@ -269,8 +269,7 @@ BackupPC server data to tape. Various programs and scripts use rsync to provide hardlinked backups. See, for example, Mike Rubel's site (L), -JW Schultz's dirvish (L (although as of -June 2004 this link doesn't work)), +JW Schultz's dirvish (L), Ben Escoto's rdiff-backup (L), and John Bowman's rlbackup (L). @@ -300,7 +299,7 @@ appreciated, both positive and negative. Beyond being a satisfied user and telling other people about it, everyone is encouraged to add links to L -(I'll see then via Google) or otherwise publicize BackupPC. Unlike +(I'll see them via Google) or otherwise publicize BackupPC. 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 @@ -600,7 +599,7 @@ directory. =head2 Step 3: Setting up config.pl After running configure.pl, browse through the config file, -__INSTALLDIR__/conf/config.pl, and make sure all the default settings +__TOPDIR__/conf/config.pl, and make sure all the default settings are correct. In particular, you will need to decide whether to use smb, tar or rsync transport (or whether to set it on a per-PC basis) and set the relevant parameters for that transport method. @@ -746,12 +745,25 @@ L. This patch adds the --checksum-seed option for checksum caching, and also sends all errors to the client, which is important so BackupPC can log all file access errors. -Otherwise, to use SMB, you need to create shares for the data you want -to backup. Open "My Computer", right click on the drive (eg: C), and + +Otherwise, to use SMB, you can either create shares for the data you want +to backup or your can use the existing C$ share. To create a new +share, open "My Computer", right click on the drive (eg: C), and select "Sharing..." (or select "Properties" and select the "Sharing" tab). In this dialog box you can enable sharing, select the share name -and permissions. Many machines will be configured by default to share -the entire C drive as C$ using the administrator password. +and permissions. + +All Windows NT based OS (NT, 2000, XP Pro), are configured by default +to share the entire C drive as C$. This is a special share used for +various administration functions, one of which is to grant access to backup +operators. All you need to do is create a new domain user, specifically +for backup. Then add the new backup user to the built in "Backup +Operators" group. You now have backup capability for any directory on +any computer in the domain in one easy step. This avoids using +administrator accounts and only grants permission to do exactly what you +want for the given user, i.e.: backup. +Also, for additional security, you may wish to deny the ability for this +user to logon to computers in the default domain policy. If this machine uses DHCP you will also need to make sure the NetBios name is set. Go to Control Panel|System|Network Identification @@ -1543,7 +1555,7 @@ status files to keep. Note that for direct restore to work, the $Conf{XferMethod} must be able to write to the client. For example, that means an SMB share for smbclient needs to be writable, and the rsyncd module -needs "read only" set to "yes". This creates additional security +needs "read only" set to "false". This creates additional security risks. If you only create read-only SMB shares (which is a good idea), then the direct restore will fail. You can disable the direct restore option by setting $Conf{SmbClientRestoreCmd}, @@ -1984,7 +1996,10 @@ is only run when there are no BackupPC_dump or BackupPC_link processes running. Therefore, when it is time to run BackupPC_nightly, no new backups are started and BackupPC waits until all backups have finished. Then BackupPC_nightly is run, and until it finishes no new backups are -started. If BackupPC_nightly is slow, the settings +started. If BackupPC_nightly takes too long to run, the settings +$Conf{MaxBackupPCNightlyJobs} and $Conf{BackupPCNightlyPeriod} can +be used to run several BackupPC_nightly processes in parallel, and +to split its job over several nights. =back @@ -2729,7 +2744,7 @@ See L. =head1 Copyright -Copyright (C) 2001-2004 Craig Barratt +Copyright (C) 2001-2005 Craig Barratt =head1 Credits @@ -2762,6 +2777,9 @@ Lorenzo Cappelletti provided the Italian translation, it.pm for v2.1.0. Lieven Bridts provided the Dutch translation, nl.pm, for v2.1.0, with some tweaks from Guus Houtzager. +Reginaldo Ferreira provided the Portuguese Brazillian translation +pt_br.pm for v2.2.0. + Many people have reported bugs, made useful suggestions and helped with testing; see the ChangeLog and the mail lists.