January 31, 2006 at 8:57 am
I want to use Symantec's LiveState 6.0 to make real-time, incremental, copies of our sql databases. That software uses the Microsoft Volume Shadow Copy services to attempt the copy. Symantec says I need to STOP sql server before making a copy to avoid any possible corruption. (Apparently, they claim, that if sql 200\2005 is running a heavy workload that it can ignore the VSS request to quiesce).
Question: is pausing the sql service good enough to allow for a, non-corrupted copy? (I don't really udnerstand the difference between pausing and stopping sql. The later is clear to me; the former is not)
TIA,
Bill
February 1, 2006 at 1:25 am
I believe that PAUSE only prevents new connections being made - any existing connections may still be running. Files are still open, buffers may not have been written to disk etc.
I doubt you can get a clean copy this way if your are copying the underlying open database files at the Disk/OS level.
February 1, 2006 at 8:56 am
You might want to look at DoubleTake, it claim to do real time syncronization.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply