"James Harper" <[EMAIL PROTECTED]> wrote: > > 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.
I'm not an expert on MSSQL, but I'm not aware of any system that _ever_ allows you to back up the _files_ that make up the database safely. That's not to say that it couldn't be developed, I'm just not aware of it. I do know that the last time I researched the documents, the deal was that the only way to ensure a reliable backup was to use the MSSQL backup tools. Of course, this could be coded up by other vendors to make it integrate with their system more transparently. > > 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. I suppose. It would end-run the problem of having enough disk space to store the text file temporarily. How do you backup your transaction logs? -- Bill Moran Potential Technologies http://www.potentialtech.com ------------------------------------------------------- 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&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
