As a concept, an incremental stores the differences between the actual
status and the last full backup, so a full must exist first, yes.
You select what to backup defining at least a share. How you do it depends
on what method you use ("the underlying transport program").
The following examples defines multiples shares:
$Conf{SmbShareName} = ['c', 'd']; # backup 'c' and 'd' shares
$Conf{TarShareName} = ['/home', '/src']; # backup /home and /src
$Conf{RsyncShareName} = ['/', '/var', '/data', '/boot'];
Only one share could be, for samba, just $Conf{SmbShareName} = 'c';
Then you may refine your choice with $Conf{BackUpFilesOnly} or
$Conf{BackupFilesExclude} directives (but not both at the same time, at
least for samba). See
http://backuppc.sourceforge.net/faq/BackupPC.html#item__conf_backupfilesonly_
.
Something like a share '/my_test_dir' and $Conf{BackupFilesOnly} =
'my_test_file.txt' could be what you are looking for.
Luis A. Paulo
On Sat, Jan 23, 2010 at 3:40 AM, three_jeeps <
[email protected]> wrote:
>
> >From my reading of the backup pc documentation, and looking at the web
> interface, it seems that the initial backup will always be a 'full' backup
> True?...(it seems that is the only option presented on the web interface).
> If not true, please tell me how to get around this.
>
> Assuming that the first backup is 'full' I want, as a test, to specify one
> file in one directory to be backed up. Where do I specify how to do this?
> In the 'my_machine.pl' configuration file? Using the
> $Conf{BackupFilesOnly} = '/my_test_dir/my_test_file.txt' I assume?
>
> I guess the real question is, anytime backup is run, it ALWAYS uses the
> $Conf{BackUpFilesOnly} directive and the $Conf{BackupFilesExclude} directive
> to dictate what gets backed up or not?
> Thanks for the clarification
> -J
>
> +----------------------------------------------------------------------
> |This was sent by [email protected] via Backup Central.
> |Forward SPAM to [email protected].
> +----------------------------------------------------------------------
>
>
>
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> BackupPC-users mailing list
> [email protected]
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
