Say I have a current standalone SQL 2005 node that is SAN attached.
How can I get it clustered by adding a passive secondary node to it ? Can I
do so ? Or do I have to setup an entirely 2 new clustered set of servers and
move the database from the standalone server to it ?
I am trying to avoid buying 2 new servers and move the database across but
would like to just add another node to the existing standalone server and
get it clustered. If this is possible, how can I do it ?
Clusters have built from the ground up. You can't make it a cluster after
the install of SQL. Migrate to a new cluster, built from the ground up, that
is the best option.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Hassan" <Hassan@.hotmail.com> wrote in message
news:%23PKJjfJHHHA.3872@.TK2MSFTNGP06.phx.gbl...
> Say I have a current standalone SQL 2005 node that is SAN attached.
> How can I get it clustered by adding a passive secondary node to it ? Can
> I do so ? Or do I have to setup an entirely 2 new clustered set of servers
> and move the database from the standalone server to it ?
> I am trying to avoid buying 2 new servers and move the database across but
> would like to just add another node to the existing standalone server and
> get it clustered. If this is possible, how can I do it ?
>
>
|||Just to expand on what Rodney said, it is possible to create a cluster from
existing equipment, but it is neither desirable nor supported. The
potential disruption during the install and migration process will likely
cause some unplanned downtime, which defeats the entire purpose of a
cluster. It is best to start from a clean slate and migrate the data into
the new system.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:ODTKVxJHHHA.4804@.TK2MSFTNGP03.phx.gbl...
> Clusters have built from the ground up. You can't make it a cluster after
> the install of SQL. Migrate to a new cluster, built from the ground up,
> that is the best option.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://www.msmvps.com/clustering - Blog
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:%23PKJjfJHHHA.3872@.TK2MSFTNGP06.phx.gbl...
>
|||What you can do, however, if you are willing to live with a new network
name, is to build a new single-node cluster and install SQL Server on it.
After migrating the databases to this new host, you can then rebuild the
original server and then have it joined to the new cluster as a new cluster
node.
This last bit has very specific steps. Look them up in Books Online or
TechNet. I even think I have a detailed list lying around this new group
somewhere. If I find it, I'll shoot it out to you.
Anyway, this should save you the cost of buying a third server.
Sincerely,
Anthony Thomas
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23WajdlSHHHA.960@.TK2MSFTNGP04.phx.gbl...
> Just to expand on what Rodney said, it is possible to create a cluster
from[vbcol=seagreen]
> existing equipment, but it is neither desirable nor supported. The
> potential disruption during the install and migration process will likely
> cause some unplanned downtime, which defeats the entire purpose of a
> cluster. It is best to start from a clean slate and migrate the data into
> the new system.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:ODTKVxJHHHA.4804@.TK2MSFTNGP03.phx.gbl...
after[vbcol=seagreen]
Can[vbcol=seagreen]
server
>
Showing posts with label standalone. Show all posts
Showing posts with label standalone. Show all posts
Friday, February 24, 2012
Sunday, February 19, 2012
Clustering a standalone SQL server + storage array
Hi all, i'm wondering whether any of you clustering experts could help.
Our apps team look after a trading system that uses an HP DL360 server
running SQL 2000 SP3a with a few small databases on it. This is a critical
server as it stores trading system information, market orders etc.
A requirement has now arisen to cluster this machine with another similar
server and connect each to an HP Smart Array, with the SQL databases being
installed on that.
Is this possible? What will happen to SQL or the OSs when the systems are
clustered and the storage array attached and configured? I assume i'll have
to back up the databases, cluster then attach the storage, then restore the
databases to the array.
Any information would be greatly appreciated!
Thanks
Andoni
Andoni
I think the easiest and safest way to accomplish this will be to reinstall
the SQL Server once the cluster is complete. Once the server is complete you
can attach your datafiles or to restore them from a valid backup. If your
application makes changes to the master database you should consider to name
your virtual server as the current production server (after renaming the
current server of course) this way you may be able to reuse your master
database.
Have in mind that all datafiles MUST be on the shared disk(s) so consider to
have enough space on the Shared storage, because the cluster Can't use local
disk for sql server datafiles, only for binaries.
Hope this helps.
Regards
Fernando Rivas
|||Hello Andoni,
You can do this it’s quite straight forward follow the steps bellow, but
make sure you read about and peice that is not clear on books on line.
1.Install clustering on new machine we’ll call it svr1.
2.Install clustering on old server we’ll call it svr2 and the sql on it sql1.
3.Once you have clustering working and failover of the resource groups is
working as expected with out error your ready to install sql server. Now if
you installed a default instance first time around on svr2 so that sql1 is
default and your apps need to connect to a default instance then this will
not work. In that case you let me know.
4.Install sql as a clustered resource we’ll call it sqlcluster
5.Apply service pack.
6.At this point you have your clustered instance and your non-clustered
instance running at the same time.
7.Make sure the cluster instance is on svr2 so that server has control over
the shared disk.
8.Then backup your sql1 instance.
9.Move the logons from sql1 to sqlcluster.
10.Detach the first database your interested in and then copy the data and
log files to the data and log shared drives you setup as part of the cluster.
11.Then attatch the same files to the sqlcluster instance the fix any
orphaned logins.
12.The run dbcc checkdb(databasename) on the database.
13.Rebuild indexes and update stats on the database.
14.Test that the application can connect to the new instance sqlinstance.
15.If so then repeat steps 10-14 for each database.
16.Once the migration is done I would disable the old server and not
de-install quite yet.
I made a lot of assumptions about your level of knowledge so it’s a part is
to vague then let me know.
Hope this helps
John Vandervliet MCSE, MCTS
"Andoni" wrote:
> Hi all, i'm wondering whether any of you clustering experts could help.
> Our apps team look after a trading system that uses an HP DL360 server
> running SQL 2000 SP3a with a few small databases on it. This is a critical
> server as it stores trading system information, market orders etc.
> A requirement has now arisen to cluster this machine with another similar
> server and connect each to an HP Smart Array, with the SQL databases being
> installed on that.
> Is this possible? What will happen to SQL or the OSs when the systems are
> clustered and the storage array attached and configured? I assume i'll have
> to back up the databases, cluster then attach the storage, then restore the
> databases to the array.
> Any information would be greatly appreciated!
> Thanks
> Andoni
Our apps team look after a trading system that uses an HP DL360 server
running SQL 2000 SP3a with a few small databases on it. This is a critical
server as it stores trading system information, market orders etc.
A requirement has now arisen to cluster this machine with another similar
server and connect each to an HP Smart Array, with the SQL databases being
installed on that.
Is this possible? What will happen to SQL or the OSs when the systems are
clustered and the storage array attached and configured? I assume i'll have
to back up the databases, cluster then attach the storage, then restore the
databases to the array.
Any information would be greatly appreciated!
Thanks
Andoni
Andoni
I think the easiest and safest way to accomplish this will be to reinstall
the SQL Server once the cluster is complete. Once the server is complete you
can attach your datafiles or to restore them from a valid backup. If your
application makes changes to the master database you should consider to name
your virtual server as the current production server (after renaming the
current server of course) this way you may be able to reuse your master
database.
Have in mind that all datafiles MUST be on the shared disk(s) so consider to
have enough space on the Shared storage, because the cluster Can't use local
disk for sql server datafiles, only for binaries.
Hope this helps.
Regards
Fernando Rivas
|||Hello Andoni,
You can do this it’s quite straight forward follow the steps bellow, but
make sure you read about and peice that is not clear on books on line.
1.Install clustering on new machine we’ll call it svr1.
2.Install clustering on old server we’ll call it svr2 and the sql on it sql1.
3.Once you have clustering working and failover of the resource groups is
working as expected with out error your ready to install sql server. Now if
you installed a default instance first time around on svr2 so that sql1 is
default and your apps need to connect to a default instance then this will
not work. In that case you let me know.
4.Install sql as a clustered resource we’ll call it sqlcluster
5.Apply service pack.
6.At this point you have your clustered instance and your non-clustered
instance running at the same time.
7.Make sure the cluster instance is on svr2 so that server has control over
the shared disk.
8.Then backup your sql1 instance.
9.Move the logons from sql1 to sqlcluster.
10.Detach the first database your interested in and then copy the data and
log files to the data and log shared drives you setup as part of the cluster.
11.Then attatch the same files to the sqlcluster instance the fix any
orphaned logins.
12.The run dbcc checkdb(databasename) on the database.
13.Rebuild indexes and update stats on the database.
14.Test that the application can connect to the new instance sqlinstance.
15.If so then repeat steps 10-14 for each database.
16.Once the migration is done I would disable the old server and not
de-install quite yet.
I made a lot of assumptions about your level of knowledge so it’s a part is
to vague then let me know.
Hope this helps
John Vandervliet MCSE, MCTS
"Andoni" wrote:
> Hi all, i'm wondering whether any of you clustering experts could help.
> Our apps team look after a trading system that uses an HP DL360 server
> running SQL 2000 SP3a with a few small databases on it. This is a critical
> server as it stores trading system information, market orders etc.
> A requirement has now arisen to cluster this machine with another similar
> server and connect each to an HP Smart Array, with the SQL databases being
> installed on that.
> Is this possible? What will happen to SQL or the OSs when the systems are
> clustered and the storage array attached and configured? I assume i'll have
> to back up the databases, cluster then attach the storage, then restore the
> databases to the array.
> Any information would be greatly appreciated!
> Thanks
> Andoni
Subscribe to:
Posts (Atom)