I have gotten the agent to the point where backups of Microsoft SQL Server databases seem to work pretty reliably for me, and would be interested in some feedback from testing outside of my test environment.
What's tested and working: . Estimate . Backups of databases . Backups of logs . SQL Server 2000 . SQL Server 2005 What's untested but should be working: . Backups of filegroups . Backups of files What's missing/broken (by no means a complete list :): . Can't specify 'no_truncate' on log backup . Restores . GZIP compression, MD5, or any other options . Fileset excludes, and in fact almost all fileset options except for "File" . 'show client' reports (just gives some fixed test) . graceful bailing on errors Even though restores don't yet work, you can simply run a restore to a normal df instead of a sqlfd which will give you a file, and then restore from that. You'll get an error on restore that the file size doesn't match - ignore it. It does need .NET 2.0, but that shouldn't be a concern given the environment it is designed to run on. If anyone want's to test it, please download the binary (no source yet - too messy :) from http://www.meadowcourt.org/bacula-sqlfd.zip (it's only 24kb zipped). Just unzip it somewhere, modify the config file, and run 'test.exe' from a command prompt. It should immediately dump out the parsed config file and then start listening for connections. DISCLAIMER - I am not aware of any failure mode that could ever cause any damage to anything, but this is highly untested code so please don't run it in a production environment. With the default config it listens on port 9104, but set it to whatever you want, as long as you set the director to the same thing. My director fileset for testing looks like: FileSet { Name = "client-sql" Include { # Options { # signature = MD5 # } File = /default/databases/master } } Valid 'File' declarations are: /<instance>/databases /<instance>/databases/<dbname> /<instance>/logs /<instance>/logs/<dbname> /<instance>/filegroups/ /<instance>/filegroups/<dbname> /<instance>/filegroups/<dbname>/<filegroupname> /<instance>/files/ /<instance>/files/<dbname> /<instance>/files/<dbname>/<filename> <instance> should be 'default' for the default instance, or the name of a named instance of SQL server. Please note that if you do a log backup, your log files will be truncated! It will dump out heaps of crap to the command prompt screen as jobs run... just ignore that unless it is obviously telling you about an error (eg an Exception report or something) James ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
