Re: Moving a SQL 2005 2-node, single-instance cluster to new SAN hardware
- From: "Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx>
- Date: Sat, 6 Oct 2007 22:20:13 -0400
Yep. Russ looks like he has the right steps. As he correctly noted, SQL only cares about drive letters when resolving file paths. I have done data moves like this in the past and it works as advertised.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Jeff Swearingen" <jeffvswearingen@xxxxxxxxx> wrote in message news:1191615753.522674.247760@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I have seen various posts on how to move SQL databases files on an
existing SAN to a new SAN. Geoff, Rod, Russ and others have provided
valuable suggestions.
I need help clarifying something -- although the files can be moved by
following some steps very carefully, do the SQL instances need to be
re-installed or re-configured in any way?
Environment:
- Two-node, single-instance running SQL Server 2005 Enterprise
- Existing SAN (older IBM DS400)
- New SAN (newer IBM DS4700)
- The SQL program files are installed to the local C: drives of each
node and the log/data files are on partitions residing on the SAN.
Also on the SAN are the Quorum and other application-specific cluster
resources.
I plan to follow the steps outlined in Russ' blog post:
http://msmvps.com/blogs/clusterhelp/archive/2005/08/05/61741.aspx
Any suggestions are welcome.
Thanks,
Jeff
.
- References:
- Moving a SQL 2005 2-node, single-instance cluster to new SAN hardware
- From: Jeff Swearingen
- Moving a SQL 2005 2-node, single-instance cluster to new SAN hardware
- Prev by Date: Re: sql 2005 cluster setup questions
- Next by Date: Re: sql 2005 cluster setup questions
- Previous by thread: Re: Moving a SQL 2005 2-node, single-instance cluster to new SAN hardware
- Next by thread: Re: Add an SQL2000 Note to a cluster
- Index(es):
Relevant Pages
|
