Re: [Bacula-users] Backing up MS SQL server with Bacula?
Hi, thank you all for your ideas. @James The idea of your client sounds very good. Seems to be a great plugin for Exchange - perhaps sometime for MSSQL, too. At the moment I'm not able to you use VSS because the operating system is Windows 2000 Server an we are using MS SQL Server 2000, so there is no VSS available. So I have to use the builtin backup routine of SQL Server and backup these files with bacula as usual. What backup procedure do you use for your MS SQL databases? There are several options available - I use the SQL maintenance function with a Transact SQL script that does a full backup of all databases once a week (filextension *.BAK) and an everyday backup of the transaction logs (filextension *.TRN). Not the best method, I think... There is another way doing this with a virtual tape file - anyone using this? Matthias - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Backing up MS SQL server with Bacula?
Hi list, anyone backuped a MS SQL server with Bacula? Is this somehow possible - are there any plugins for that or do I have to use the built-in backup functionality of the MS SQL server and backup the database dumps / transaction logs later with Bacula? Matthias - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up MS SQL server with Bacula?
Le jeudi 11 octobre 2007 09:09, Matthias Kellermann a écrit : Hi list, anyone backuped a MS SQL server with Bacula? Is this somehow possible - are there any plugins for that or do I have to use the built-in backup functionality of the MS SQL server and backup the database dumps / transaction logs later with Bacula? Matthias - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users Hi, You can use ClientRunBeforeJob in Job definition : ... ClientRunBeforeJob = /etc/bacula/ClientRunBeforeJob.sh ... In /etc/bacula/ClientRunBeforeJob.sh you can use mysqldump to save your database. It works for me :-) -- Jean-Michel Caricand Tél: 03.81.66.20.63 E-mail: [EMAIL PROTECTED] Equipe systèmes Laboratoire d'Informatique de l'Université de Franche-Comté 16, route de Gray - 25030 BESANÇON CEDEX - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up MS SQL server with Bacula?
Hi, 11.10.2007 09:29,, Jean-Michel Caricand wrote:: Le jeudi 11 octobre 2007 09:09, Matthias Kellermann a écrit : Hi list, anyone backuped a MS SQL server with Bacula? Is this somehow possible - are there any plugins for that or do I have to use the built-in backup functionality of the MS SQL server and backup the database dumps / transaction logs later with Bacula? Matthias ... Hi, You can use ClientRunBeforeJob in Job definition : ... ClientRunBeforeJob = /etc/bacula/ClientRunBeforeJob.sh ... In /etc/bacula/ClientRunBeforeJob.sh you can use mysqldump to save your database. It works for me :-) Note that MS SQL != MySQL. Still, the basic idea can be used similarly. You use a Client Run Before Job script to trigger a dump of the information you need, and don't back up the actual database files. Using VSS, it *might* be possible to get usable database backups by simply storing the files, but there are people around knowing more about MS SQL than I do... lots of people, given I know almost nothing about it :-) Arno -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up MS SQL server with Bacula?
anyone backuped a MS SQL server with Bacula? Is this somehow possible - are there any plugins for that or do I have to use the built-in backup functionality of the MS SQL server and backup the database dumps / transaction logs later with Bacula? With MS SQL Server (2005 and 2000) I use the bultin commands to dump/restore the database. And then bacula is perfectly fine backing up a dump file. John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up MS SQL server with Bacula?
We put MS SQL in full recovery mode, then have a maintenance schedule in MS SQL that does a full back-up. We exclude the actual data files and include the log files (full and transaction). We have the schedule run about 15 min before bacula runs on the client. I think the RunBefore Client would be a better option though. Robert On 10/11/07 1:09 AM, Matthias Kellermann [EMAIL PROTECTED] wrote: Hi list, anyone backuped a MS SQL server with Bacula? Is this somehow possible - are there any plugins for that or do I have to use the built-in backup functionality of the MS SQL server and backup the database dumps / transaction logs later with Bacula? Matthias - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users Robert LeBlanc College of Life Sciences Computer Support Brigham Young University [EMAIL PROTECTED] (801)422-1882 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up MS SQL server with Bacula?
Robert LeBlanc wrote, sometime around 11/10/07 12:03: We put MS SQL in full recovery mode, then have a maintenance schedule in MS SQL that does a full back-up. We exclude the actual data files and include the log files (full and transaction). We have the schedule run about 15 min before bacula runs on the client. I think the RunBefore Client would be a better option though. I currently have a maintenance plan which does a consistency check and then database backup followed by log backup (the latter is needed if you don't want your log files to grow to infinite size when a database is in 'Full' recovery mode). This currently runs asynchronously w.r.t. bacula, so I just make sure that I schedule the bacula job to run at a time by which the database server will have dumped its backups. I also have a client run before job script (shell script executed with cygwin), which prunes backup dump files older than a week, and gzips the remainder (SQL Server backup files gzip rather well, I find). I think I trust gzip to do a better job than the tape drive's hardware compression. If you look at the maintenance plan, all it does is call a stored procedure with some arguments. It should be trivial to call this from the client run before job too, making the whole process synchronous. I also saw someone having some success running backups over named pipes and streaming them directly to tape, avoiding the middle step of dumping databases to files before backing up. I like having an online copy of the database backups though, as it makes restoring in the common case (something went wrong and we need last night's backup now!) much easier. Backups are handy for recreating test copies of databases too. I've posted the prune compress script here before, so it should be in the archives somewhere. It's nothing fancy. -- Russell Howe, IT Manager. [EMAIL PROTECTED] BMT Marine Offshore Surveys Ltd. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up MS SQL server with Bacula?
Robert LeBlanc wrote, sometime around 11/10/07 12:03: We put MS SQL in full recovery mode, then have a maintenance schedule in MS SQL that does a full back-up. We exclude the actual data files and include the log files (full and transaction). We have the schedule run about 15 min before bacula runs on the client. I think the RunBefore Client would be a better option though. I currently have a maintenance plan which does a consistency check and then database backup followed by log backup (the latter is needed if you don't want your log files to grow to infinite size when a database is in 'Full' recovery mode). This currently runs asynchronously w.r.t. bacula, so I just make sure that I schedule the bacula job to run at a time by which the database server will have dumped its backups. I also have a client run before job script (shell script executed with cygwin), which prunes backup dump files older than a week, and gzips the remainder (SQL Server backup files gzip rather well, I find). I think I trust gzip to do a better job than the tape drive's hardware compression. If you look at the maintenance plan, all it does is call a stored procedure with some arguments. It should be trivial to call this from the client run before job too, making the whole process synchronous. I also saw someone having some success running backups over named pipes and streaming them directly to tape, avoiding the middle step of dumping databases to files before backing up. I like having an online copy of the database backups though, as it makes restoring in the common case (something went wrong and we need last night's backup now!) much easier. Backups are handy for recreating test copies of databases too. I wrote an agent for MSSQL which worked quite well, although it's in a non-working state at the moment as I started working on the Exchange agent which involved a rewrite of the base class. The Exchange agent has been running in production use for over a month now, so I think it's pretty stable (see archive for more details). I hope to get back to the SQL agent for bacula in the next few months, but work suddenly got really busy :) Basically it's a program that pretends to be a Bacula FD, and creates a filesystem namespace out of MSSQL elements, eg /instance/database name/database /instance/database name/logs ... filegroups ... files Once backed up, you could also just restore the backup using the normal bacula fd, which would give you a file you could then restore with MSSQL, eg RESTORE DATABASE xyzzy FROM DISK='C:\tmp\whatever'. One of the things that has been added to Bacula since I first wrote the agent is much more flexible restore redirection, so I should now be able to get the 'restore to another database' option working in a sensible way. Not sure about 'point in time' restores though... not sure that Bacula has the flexibility to allow this... I think it would need some knowledge of MSSQL. Probably best just to restore everything to files and do it manually. I'm sure someone will correct me if I'm wrong though :) But for now, use VSS (which apparently has been documented to work), or do what everyone else does and just use MSSQL to back up to a file which in turn gets backed up by bacula. James - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up MS SQL server with Bacula?
Did you ever post the source to your exchange client? I'm very interested in an exchange plugin for bacula, as I back up over 25 windows servers and I am forced to use the windows backup agent to perform a backup of exchange. Sincerely, -Michael On 10/11/07, James Harper [EMAIL PROTECTED] wrote: I wrote an agent for MSSQL which worked quite well, although it's in a non-working state at the moment as I started working on the Exchange agent which involved a rewrite of the base class. The Exchange agent has been running in production use for over a month now, so I think it's pretty stable (see archive for more details). I hope to get back to the SQL agent for bacula in the next few months, but work suddenly got really busy :) Basically it's a program that pretends to be a Bacula FD, and creates a filesystem namespace out of MSSQL elements, eg /instance/database name/database /instance/database name/logs ... filegroups ... files Once backed up, you could also just restore the backup using the normal bacula fd, which would give you a file you could then restore with MSSQL, eg RESTORE DATABASE xyzzy FROM DISK='C:\tmp\whatever'. One of the things that has been added to Bacula since I first wrote the agent is much more flexible restore redirection, so I should now be able to get the 'restore to another database' option working in a sensible way. Not sure about 'point in time' restores though... not sure that Bacula has the flexibility to allow this... I think it would need some knowledge of MSSQL. Probably best just to restore everything to files and do it manually. I'm sure someone will correct me if I'm wrong though :) But for now, use VSS (which apparently has been documented to work), or do what everyone else does and just use MSSQL to back up to a file which in turn gets backed up by bacula. James - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
