Re: [BackupPC-users] BackupFilesExcludes for Linux

2008-12-08 Thread Mark Adams
I think I spotted a mistake in my own speculative config.  See below.

Mark Adams wrote:
 Greetings.  Me again.

 I upgraded my backup server and configured two hard drives into a single 
 logical volume with LVM for my TopDir, and successfully configured 
 BackupPC to backup a share on one of my host machines.  Rejoicing was 
 heard throughout the LAN.

 Now, I am faced with the necessity of backing up my /etc and some of my 
 user's home directory on that machine.

 I want to exclude several directories under my user's home directory, 
 but the information I've seen is all about configuring BackupPC for a 
 Windows host. I am assuming I need to change this:


 $Conf{BackupFilesOnly} = {
   '*' = [
 'images',
 'Photos'
   ]
 };
 $Conf{RsyncShareName} = [
   '/mnt/share'
 ];
 $Conf{ClientNameAlias} = '192.168.1.106';



 To this:


 $Conf{BackupFilesOnly} = {
   '/mnt/share' = [
 'images',
 'Photos'
   ]
  '/' = [
'etc'
   ]
  '/home' = [
   'madams'
   ]
 };
 $Conf{BackupFilesExclude} = {
  '/home/madams' = ['/torrent', '/Download'],
  };
 $Conf{RsyncShareName} = [
   '/mnt/share', '/home/madams', '/etc'
 ];
 $Conf{ClientNameAlias} = '192.168.1.106';


 Is this right, or do I misunderstand this configuration?

 Thanks.

   
I believe the $Conf{RsyncShareName} statement should involve '/' rather 
than '/etc'. The directory I want to backup is /etc which is a 
subdirectory of /.  I also believe the /home/madams directory should be 
/home.  Am I right?

-- 
Mark E. Adams

Random Musing: 
And do you think (fop that I am) that I could be the Scarlet Pumpernickel?



--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BackupFilesExcludes for Linux

2008-12-08 Thread Matthias Meyer
Mark Adams wrote:
   
 I believe the $Conf{RsyncShareName} statement should involve '/' rather
 than '/etc'. The directory I want to backup is /etc which is a
 subdirectory of /.  I also believe the /home/madams directory should be
 /home.  Am I right?
 

$Conf{RsyncShareName} should contain the directories which should backuped.
If it contain '/' than all subdirectories, including /etc will be backuped,
if it is not on another filesystem and you use --one-file-system.
If it contain '/etc' than only /etc and all subdirectories of /etc will be
backuped.

br
Matthias
-- 
Don't panic


--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BackupFilesExcludes for Linux

2008-12-08 Thread Holger Parplies
Hi,

Mark Adams wrote on 2008-12-08 14:37:54 -0700 [Re: [BackupPC-users] 
BackupFilesExcludes for Linux]:
 I think I spotted a mistake in my own speculative config.  See below.

right, and there's a second one along the same line ...

 [...]
  $Conf{BackupFilesOnly} = {
'/mnt/share' = [
  'images',
  'Photos'
]
   '/' = [
 'etc'
]
   '/home' = [
'madams'
]
  };
  $Conf{BackupFilesExclude} = {
   '/home/madams' = ['/torrent', '/Download'],

This should be

 '/home' = [ '/maddams/torrent', '/maddams/Download' ],
 
   };
  $Conf{RsyncShareName} = [
'/mnt/share', '/home', '/'
[edited to match your correction]
  ];
  $Conf{ClientNameAlias} = '192.168.1.106';

As Matthias probably meant to point out, you can achieve the same with

$Conf {RsyncShareName} = [ '/etc', '/home/maddams', '/mnt/share/images',
   '/mnt/share/Photos' ];
$Conf {BackupFilesExclude} = { '/home/maddams' = [ '/torrent',
'/Download'] };

or even

$Conf {RsyncShareName} = [ '/' ];
$Conf {BackupFilesOnly} = {
'/' = [ '/etc', '/home/maddams', '/mnt/share/images',
 '/mnt/share/Photos' ],
};
$Conf {BackupFilesExclude} = {
'/' = [ '/home/maddams/torrent', '/home/maddams/Download' ],
};

This is, of course, just as speculative as your config, but I believe it
*should* work that way :-).

The important part is that the hash keys in BackupFilesOnly and
BackupFilesExclude need to match your {RsyncShareName}s exactly, else they
will simply be ignored (there is no magic that determines that '/home/maddams'
lies within the '/home' share). Aside from that, *with rsync and tar* (not
rsyncd and smb) you are rather free to split your paths into share names and
BackupFilesOnly entries any way you like. Less shares probably means less
overhead and a backup definition that is easier to understand. If you use
'--one-file-system', you will need extra shares for anything on different file
systems (probably '/home' and '/mnt/share' in your case).

Regards,
Holger

--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] BackupFilesExcludes for Linux

2008-12-08 Thread Jeffrey J. Kosowsky
Holger Parplies wrote at about 00:24:56 +0100 on Tuesday, December 9, 2008:
  Hi,
  
  Mark Adams wrote on 2008-12-08 14:37:54 -0700 [Re: [BackupPC-users] 
  BackupFilesExcludes for Linux]:
   I think I spotted a mistake in my own speculative config.  See below.
  
  right, and there's a second one along the same line ...
  
   [...]
$Conf{BackupFilesOnly} = {
  '/mnt/share' = [
'images',
'Photos'
  ]
 '/' = [
   'etc'
  ]
 '/home' = [
  'madams'
  ]
};
$Conf{BackupFilesExclude} = {
 '/home/madams' = ['/torrent', '/Download'],
  
  This should be
  
   '/home' = [ '/maddams/torrent', '/maddams/Download' ],
   
 };
$Conf{RsyncShareName} = [
  '/mnt/share', '/home', '/'
  [edited to match your correction]
];
$Conf{ClientNameAlias} = '192.168.1.106';
  
  As Matthias probably meant to point out, you can achieve the same with
  
  $Conf {RsyncShareName} = [ '/etc', '/home/maddams', '/mnt/share/images',
  '/mnt/share/Photos' ];
  $Conf {BackupFilesExclude} = { '/home/maddams' = [ '/torrent',
   '/Download'] };
  
  or even
  
  $Conf {RsyncShareName} = [ '/' ];
  $Conf {BackupFilesOnly} = {
   '/' = [ '/etc', '/home/maddams', '/mnt/share/images',
'/mnt/share/Photos' ],
  };
  $Conf {BackupFilesExclude} = {
   '/' = [ '/home/maddams/torrent', '/home/maddams/Download' ],
  };
  
  This is, of course, just as speculative as your config, but I believe it
  *should* work that way :-).
  
  The important part is that the hash keys in BackupFilesOnly and
  BackupFilesExclude need to match your {RsyncShareName}s exactly, else they
  will simply be ignored (there is no magic that determines that 
  '/home/maddams'
  lies within the '/home' share). Aside from that, *with rsync and tar* (not
  rsyncd and smb) you are rather free to split your paths into share names and
  BackupFilesOnly entries any way you like. Less shares probably means less
  overhead and a backup definition that is easier to understand. If you use
  '--one-file-system', you will need extra shares for anything on different 
  file
  systems (probably '/home' and '/mnt/share' in your case).
  

Also (I believe that) using multiple share names on the same
filesystem will not preserve hard links that are split across the
share names. So, if you are backing up your linux partitions and want
to preserve hard links then you should probably keep all the key root
partitions on the same share (please correct me if I am wrong but I
don't see how rsync would otherwise know about the hard links since
each share is done independently).

--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/