The other thing, and I do this with MySQL, is that you can probably dump
the database or something like that. My expectation is that you have a
good reason for not doing that, but maybe not.
Frank Sweetser wrote:
On Mon, Mar 06, 2006 at 12:12:58PM -0600, Jason Balicki wrote:
I have a client trying to backup a MS SQL database. We
use RunBefore and RunAfter commands to stop and start the
DB. Usually this works fine, but if we run out of space
on a tape then Bacula can't get any farther until someone
mounts another tape. However, because the application
is critical, someone usually will manually start the
services before the job can finish. I can't fix this
behavior.
If you have enough space disk space on the clients being backed up, one
alternative is to have the RunBefore script stop the database, copy it to a
staging area, restart the database, and then let the staging area get backed
up. The RunAfter script would then clean up the staging area.
--
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | | Ryan Novosielski - User Support Spec. III
|$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630
begin:vcard
fn:Ryan Novosielski
n:Novosielski;Ryan
org:UMDNJ;IST/Academic Systems and Technologies
adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103-2757
email;internet:[EMAIL PROTECTED]
title:185 South Orange Avenue
tel;work:(973) 972-0922
tel;fax:(973) 485-2612
x-mozilla-html:FALSE
version:2.1
end:vcard
