SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


vmware snapshot and database corruption?


vmware snapshot and database corruption?

Author
Message
CavyPrincess
CavyPrincess
Right there with Babe
Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)

Group: General Forum Members
Points: 767 Visits: 1644
Anyone heard that vmware snapshots can cause database corruption on SQL Server databases? The VMware is ESX 4 running Windows 2008 R2, and SQL Server 2008 (and R2)

I hadn't heard this before, but someone asked me about it. My "google research" found 5-year old posts that indicate this, but recent posts seem to say it's fine.

Thoughts or opinions?

Thanks,
Cindy
sql-lover
sql-lover
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1597 Visits: 1930
CavyPrincess (4/26/2012)
Anyone heard that vmware snapshots can cause database corruption on SQL Server databases? The VMware is ESX 4 running Windows 2008 R2, and SQL Server 2008 (and R2)

I hadn't heard this before, but someone asked me about it. My "google research" found 5-year old posts that indicate this, but recent posts seem to say it's fine.

Thoughts or opinions?

Thanks,
Cindy


It is not recommended.

Any snapshot functionality that does not use VSS may leave SQL Server in an inconsistent state. This is because any backup product or solution that uses VSS, allows the SQL server disk to pause briefly (or that's the concept behind) so any in memory transaction or database activity can be backed up accordingly. When VSS is not used, there is a chance that something that should have been written to the disk (mdf file), was not, or viceverse, ending with a database that is not in a consistent state. Then when you start MS-SQL or try to open the database, it won't open.

If you are running SQL on VMware or HyperV, run regular SQL backups, native or RedGate and save those on a different drive or backup device. You may also use SAN backups but you must ensure they integrate VSS on its solution, to avoid the issue I just mentioned.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search