SQL Server 2005: How to Suspend DB Transactions for a Split-Mirror Backup Strategy
Posted on 2006-05-11
In our environment, we use Sybase and SQL Server 2005. With our Sybase setup, we use a split-mirror backup strategy, utilizing our SAN, and it works very well. We don't use third party software to perform the split-mirror, but instead use command-line tools to do so. Before splitting the mirror, we run a "quiesce database" command on the necessary databases to suspend all transactions so the DBs are in a stable state when the split occurs (prevents torn pages, etc.). Being able to quiesce the databases is what helps us avoid having to use third-party tools to do the split (the third party tools would do something similar at a deeper level).
My question is how to recreate this setup in SQL Server 2005 without paying for a third-party software that utilizes VDI (Virtual Device Interface)? I'm looking for the SQL Server 2005 equivalent of "quiesce database" so I can suspend all transactions before performing the split of the mirror.
(P.S. I realize there are a number of different strategies available in '05 like mirroring, etc. However, in this question I would like to avoid discussing other methods and strictly discuss how this one would be implemented if it were chosen).
I look forward to learning from your expertise!