Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 To be prepared for recovery

Author  Topic 

mikr33
Starting Member

5 Posts

Posted - 2012-03-15 : 15:34:30
Hi,

we have two identical standalone machines with MS Sql server2008 std. edition
with shared disk storage (no cluster, no mirroring, second one is standby).
In case of hw failure of first one is there some procedure to run second one like :
1. to have all dbs including system dbs on shared storage
2. map this storage to second machine
3. in config. manager set parameter for folder on shared storage
3. change server name, ip addr.
4. reboot
5. server is up and running

is it wrong idea ?

regards Miroslav

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-03-15 : 16:03:08
That's not how it works. You would need to do backup/restore, so be sure that the backups are available and restorable to the second machine.

How about you implement log shipping?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

mikr33
Starting Member

5 Posts

Posted - 2012-03-15 : 16:16:03
Yes, log shipping is an option. I am trying to find some solution without direct connection between servers.
There will be some backup but it means lost data.
So you mean, it is not possible at least attach dbs from shared storage ?

Miroslav
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-03-15 : 16:21:29
It's possible but not guaranteed. In order to attach database files to another server, the files need to be in a good state. If there was activity on the files at the time the first server went down, the files are probably in a bad state and therefore not attachable. I'm generalizing here, but you should never rely on a solution that would require you to try to attach files that were open by SQL Server on another server. There are no guarantees.

If you won't have a direct connection between the two servers and therefore mirroring can't be used, then implement log shipping or similar. Yes there will be data loss if you can't backup the tail of the log on the first server, but if you cared about data loss, you would architect your system better so that you could use mirroring or clustering.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2012-03-15 : 16:25:37
Just read that Log shipping is to be deprecated "in the near future"

SQL Server 2008R2 Unleashed Page 535





Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-03-15 : 16:26:33
quote:
Originally posted by X002548

Just read that Log shipping is to be deprecated "in the near future"




I'm using the term loosely. It doesn't need to be the Log Shipping feature, I just mean to ship the backups and restore them.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

mikr33
Starting Member

5 Posts

Posted - 2012-03-15 : 16:31:52
we can do consistent snapshot e.g every 10 minutes, so I suppose it can be used for restore. can be restored objects on instance level like
packages, logins ...?
Go to Top of Page

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2012-03-15 : 16:34:15
If you are going to the trouble of setting up shared storage - why are you not also looking at setting up a cluster? It seems to me you want the benefits of clustering and the ability to have your shared storage presented to both servers in case of failure.

That is exactly what clustering does for you.

For either mirroring or log shipping, you have to have additional storage available for the other system.
Go to Top of Page

mikr33
Starting Member

5 Posts

Posted - 2012-03-15 : 16:43:05
yes, you are right, sql server is already in production env. so we have to migrate data somewhere, setup cluster and migrate back ....
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2012-03-15 : 17:55:46
quote:
Originally posted by X002548

Just read that Log shipping is to be deprecated "in the near future"



No, log shipping's not deprecated in 2008 R2 nor in 2012.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

mikr33
Starting Member

5 Posts

Posted - 2012-03-16 : 01:05:23
ok, thanks, I have to leave first idea - only attach or map dbs from another server
(in case of abnormal end).
Go to Top of Page
   

- Advertisement -