On Jan 25, 2013, at 11:17 AM, Alan McKay wrote:

> Seems to make sense to me since the catalog backup is already
> happening, but maybe this is a bad idea for some reason?
> 
> If it is OK to do that, are there any others I should add?
> 
> FileSet {
>  Name = "Catalog"
>  Include {
>    Options {
>      signature = MD5
>    }
>    File = "/var/lib/bacula/bacula.sql"
>    File = "/etc/bacula/"
>  }
> }


In addition to that:

1 - my script doesn't delete the file.  It keeps it.  Just in case.
2 - another cronjob copies that file, and the bacula *.conf files to another 
server
3 - by another server, I mean another three servers.  That way, I always have a 
copy of my db and the conf files and they aren't on a backup

-- 
Dan Langille - http://langille.org


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users