 | |
SQL Clustering - two clusters, same LAN
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
SQL Clustering - two clusters, same LAN -
09-08-2008
, 08:43 AM
#2
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#3
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#4
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#5
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#6
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#7
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#8
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#9
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
#10
| |||
| |||
|
|
Hi I'm new to SQL server so i'm hoping that some of you pros out there can help me out. We are looking to perform an upgrade on our SQL clusters. Fortunately enough we have two sets of hardware so this probably makes life a little easier in that the existing cluster will remain untouched. Spec:- Existing Cluster: SQL Server 2000/Win2k3 Ent New Cluster: SQL Server 2005/Win2K3 Ent **Both clusters are attached to two separate storage devices. We effectively want one cluster active, and second offline. We hope that this will give us the ability to switch back in the event if the new cluster causes problems. Both clusters will be connected to the same network but will remain in a active/passive state so to speak. To aid with the migration can we bring one cluster down and bring the new one up? Not sure if that’s possible and what potential problems this would cause hence why i'm here asking for advice. I'd be grateful if anybody can shed any light or advise on what the best approach would be in this case? Ideally if things don't go according to plan, we want to be in a position where we can revert back to the old (SQL 2000) cluster. The SQL named instances would need to remain the same on the new cluster due to external applications that rely on these named instances. Hope that makes sense...... |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.