Found it. And it has NOTHING to do with my config - and EVERYTHING to do
with where the config is.
OLD VERSION:: in the per-PC configuration file,
//var/lib/BackupPC//pc/$host/config.pl.
NEW VERSION:: __CONFDIR__/pc/HOST.pl per-pc config file
I was putting the client config in pc/lamp.config.pl
but in the new version it is pc/lamp.pl
I found this out by essentially trying to force my config to be used by
hard coding my shares into the $Conf{RsyncClientCmd} and having the dump
command not change. I messed around some more and found out it was ignoring
my client level config entirely. I could only make it do my bidding by
changing the master config ... eventually I found the problem.
Thanks for talking to me!
On Wed, Jan 30, 2013 at 11:01 PM, Adam Goryachev <
mailingli...@websitemanagers.com.au> wrote:
> On 31/01/13 14:45, Ctdi Unix wrote:
>
> Thank you for helping me.
>
> You are correct I killed it very quickly. Because in the previous version,
> the dump command would show the actual shares I wanted on the command line
> { and not / } and I would not get any messages like
> *Remote[2]: file has vanished: "/proc/2/exe"
> *
> which indicates it is *really* looking at / and not *only* at the mounts
> I want.
>
> You said:
>
> *During this time, the target "lamp" is looking at every file on the
> disk, once finished, it will send the list across.*
>
> Really it looks at the whole disk when I don't want to backup the whole
> disk?
> Is it going to send the whole list across?
> Has this changed in this version then? Because I can run dump on my old
> version and it does not do that.
> *
> *
>
> *If that is not what you want, then you should change the configuration.
> If you only wish to backup /home/foo and /home/bar you have two options:
> 1) Setup the shares as /home/foo and /home/bar instead of /
> 2) Setup the share as /home and use the include or exclude option as
> needed.
>
> If you only need those two directories, then I would just use two shares
> to back them up. This also means you would probably not need the
> one-file-system option as you are unlikely to mount other FS under these
> directories, but I would use it anyway just in case.
> *
>
> FWIW boxes on same lan, no firewall, lamp just has one disk with
> everything in /
>
> OK, so the main thing that was not clear is that you cancelled immediately
> because it didn't do what you wanted, I assumed it had "hung". See above
> for the solution.
>
>
> Regards,
> Adam
>
> --
> Adam Goryachev
> Website Managerswww.websitemanagers.com.au
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_jan
> _______________________________________________
> 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/
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
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/
