SQLServer - disaster recovery
From: Griff (Howling_at_The.Moon)
Date: 09/09/04
- Next message: Aaron [SQL Server MVP]: "Re: Free Space Alert in Sql Server"
- Previous message: Tibor Karaszi: "Re: sp_spaceused compared Database Size"
- Next in thread: Bob Castleman: "Re: SQLServer - disaster recovery"
- Reply: Bob Castleman: "Re: SQLServer - disaster recovery"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 9 Sep 2004 15:17:47 +0100
I understand that if a machine running SQLServer crashes [Standard Edition]
then the data and log files may well be left in an open (attached) state.
This means that one couldn't stick the disks into a new machine and start
using the databases because they would need to be closed (detached) first
and one needs the now dead server to achieve this.
I'm wondering whether the following scenario may help solve this issue.
If I used a machine running some sort of virtual server technology (such as
VMWare's GSX server) then this could run a virtual GUEST server whose disk
image was stored on a SAN (or similar device). If the machine died, then I
could simply replace that machine with another that had (say) GSX server on
it and point it to the existing virtual image on the SAN. This virtual
image contains the SQLServer, so there's no problem having to
detach/reattach the databases.
Have you attempted something similar? If so, was it successful?
If you haven't attempted this, does it sound sensible?
I guess that I'd need to identify whether the virtual Guest could be left in
a similar "open" state, thus preventing another HOST from running it.
Griff
- Next message: Aaron [SQL Server MVP]: "Re: Free Space Alert in Sql Server"
- Previous message: Tibor Karaszi: "Re: sp_spaceused compared Database Size"
- Next in thread: Bob Castleman: "Re: SQLServer - disaster recovery"
- Reply: Bob Castleman: "Re: SQLServer - disaster recovery"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|