On Tue, 2009-12-01 at 10:47 -0500, John Drescher wrote:
> On Tue, Dec 1, 2009 at 10:43 AM, Shawn wrote:
>
> I didn't see what you meant, but you were right, in the
> Exclude section was:
>
> Wild = "[A-Z]:/Users/*/AppData/*"
>
> Albeit that is
On Tue, Dec 1, 2009 at 10:43 AM, Shawn wrote:
> I didn't see what you meant, but you were right, in the Exclude section
> was:
>
> Wild = "[A-Z]:/Users/*/AppData/*"
>
> Albeit that is certainly a mulligan - even if I have No excludes at all
> against the AppData directory - strangely, Bacula wil
I didn't see what you meant, but you were right, in the Exclude section
was:
Wild = "[A-Z]:/Users/*/AppData/*"
Albeit that is certainly a mulligan - even if I have No excludes at all
against the AppData directory - strangely, Bacula will just not back
anything up but folder names within that AppD
What I will do, is abolish the Exclude statements and touch up the
Include statements so it's no-holds-bar against that directory, will
update in a little while after a new backup job. I'm just concerned
because - by all appearances, it should be backing up the AppData
directory without a hitch...
2009/11/30 Shawn
>
> Hello everyone,
>
> It's been a long time since I've posted here, I originally gave out a
> hashed up version of a Vista/Windows Server 2008 file set that was being most
> optimal, however, I'm recognizing late that the "C:\Users\username\AppData"
> folder isn't exactly
Hello everyone,
It's been a long time since I've posted here, I originally gave out
a hashed up version of a Vista/Windows Server 2008 file set that was
being most optimal, however, I'm recognizing late that the "C:\Users
\username\AppData" folder isn't exactly being backed up...
I'm cons
