It looks like that is how I had it already, was C:/bacula/*
Screenshot of server side
Screenshot of Windows client side:
Here is what the file set looks like directly in the /etc/bacula/bacula-dir.conf file on the server:
|
Client { Name = bnspflu1-ts01-fd Password = *********** Address = 10.100.101.203 FDPort = 9102 Catalog = MyCatalog AutoPrune = yes File Retention = 10 days Job Retention = 10 days } FileSet { Name = bnspflu1-ts01 Include { File = "C:/bacula/*" Options { } } } Job { Name = bnspflu1-ts01 Type = Backup Level = Full Client = bnspflu1-ts01-fd FileSet = bnspflu1-ts01 Schedule = Full-Every-Saturday Storage = File Pool = File Messages = Standard } |
Do you think I need to do a FileSet that looks like these:
C:/bacula/*.*
C:/bacula/*.doc
C:/bacula/*.docx
C:/bacula/*.xls
C:/bacula/*.xlsx
C:/bacula/*.txt
C:/bacula/*.ppt
I appreciate the help…..very excited to see this work.
LK
From: John Drescher [mailto:drescherjm AT gmail DOT com]
Sent: Tuesday, February 25, 2014 4:27 PM
To: Larry Kemp
Cc: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] Failure Backing Up Windows Client Machine
I am confident now my two remaining tasks are:
1. Get a valid working windows file-set built that Bacula will accept, backup and not give me errors on.
2. Then automate the startup of the File Daemon client on the Windows Server which I am confident I can do and then report back to the distro as to how I do it.
So since simply entering “C:\DIRECTORY\*” does not seem to jive….what do I need to do to define a valid file-set for my Windows machines that I need to backup?
