> In the case of MSSQL, you can _never_ safely back up the database
files.
> (Unless, of course, you shut down the database server).

Hmmm... I thought that MSSQL spoke VSS and could give a coherent copy of
the underlying files. But I was far from positive on that so I stand
corrected.

> Like most SQL servers, MSSQL has a function do dump the database to a
> text file.  You then back up the text file like any other.  This is
the
> correct way to do a database backup.

Actually, the really correct way is to have a backup 'agent' (MSSQL
specific fd) that sets up a named pipe and then tells the sql server to
back up to that named pipe. The agent reads the data from the pipe and
sends it (one way or another) to the backup media.

Would this functionality be useful to anyone?

> I can't speak to Exchange.

I believe it's more or less the same thing, but while I'm a whiz on most
things MSSQL related, the bowels of Exchange are thus far unexplored by
me :)

Thanks

James


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to