I cannot believe how badly I messed up this post.  (My excuse is that my local baseball team (Go Tigers!) played a late game last night...)  Let me see if I can straighten it out a bit.

Timothy J Massey/OBSCorp wrote on 10/11/2013 04:51:50 PM:

> David Williams <dwilliams AT dtw-consulting DOT com> wrote on 10/11/2013 04:41:09 PM:
>
> > Ok,
> >
> > Tried the following and still not working.  I'd expect the following
> > to just back up Users/dwilliams/My Photos, but still everything is
> > getting backed up.  I guess I am just not understanding how this is
> > supposed to work.
>
> You very well may not.  But take solace:  this may be one of the
> very highest FAQ issues.  (Next to how to archive an entire BackupPCserver...)
>
> There are two parts to the exclude.  The first part is the share
> name.  That's the part that's labelled "key" in the gui.  In the
> case you included, it is set to "users".  Is "users" the name of the
> (SMB?) share you are using?

Looking more closely at your message, I see that it certainly seems to.

Notice how I'm talking about excludes and you're talking about *includes*?  Totally missed that!  Fortunately, the two work exactly the same:  only the parameter name is different...

> Here's a concrete example from one of my servers (that does *not*
> use a "*" for the key):
>


> Key = D
> Path = /Shares/Excluded

Also notice that when I wrote the text version, I *removed* the trailing slash.  I don't know for certain, but that very well may be your issue.  *Your* include did not have it, my exclude *does*.  Give that a shot, too.

Also, your path includes spaces.  Spaces are the devil.  I know you didn't pick the path, but that may have something to do with it as well.  Pick a folder in dwilliams that does *NOT* have a space and see if you can get that one to back up.  If that works, then you know that you have to figure out how to escape the space.  You may not, but definitely something to test.

> Also, GUI's are nice, but learn to love the configuration files
> themselves.  It's a *LOT* easier to make sure you have everything
> correct that way, and moving exclusions to a new host is a very
> simple cut and paste away.
>
> Here's the relevant part from the above example:
>
> $Conf{BackupFilesExclude} = {
>   'D' => [
>     '/Shares/Excluded/'
>   ]
> };

I can't stress this part enough, though.  GUI's are great and all, but they can hide things like extra spaces in a parameter.  Looking at the *actual* parameter in the *actual* config file is really, really a good place to start.

> Also, check the XferLog that's generated for that host.  Here's an
> example of the first few lines of the above host:

I've actually never used BackupFilesInclude, but I certainly imagine that the path gets logged just like the Exclude example I gave you.

> I hope that helps!

Along with this addendum!  :)

Tim Massey

Out of the Box Solutions, Inc. Creative IT Solutions Made Simple! http://www.OutOfTheBoxSolutions.com tmassey AT obscorp DOT com		22108 Harper Ave. St. Clair Shores, MI 48080 Office: (800)750-4OBS (4627) Cell: (586)945-8796

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk

_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/