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.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-03-19 : 08:27:48
|
| Em writes "SQL 2000 (sp3), windows 2000 (sp4).Just starting to learn more about the clustering etc. that we have in place and am a bit concerned / confused about something.We have 2 servers set up in an active / passive legato cluster (set up by an external company). ie 'server1' (primary), 'server2' (secondary), 'server' (virtual) (not their real names obviously but it keeps it simple for the example). When I register it on enterprise manager on my machine I register the virtual server i.e. 'server'. But when i look at the jobs that are scheduled etc. their source is showing as 'server1'. I'm concerned that it may mean I'm missing the cluster and am actually only hitting the primary server?? How will that affect the secondary server in the event of failover etc.?Any explanations gratefully received :)" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-19 : 12:23:22
|
| What does sysservers show for the name of the SQL Server? The virtual name should have been used during installation of the product.Tara |
 |
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2004-03-22 : 11:27:04
|
| It sounds like you may have a problem. All the SQL data/configuration should refer to the virtual server or virtual server and instance name if you have instances. In the event of a failover the virtual server moves to the active node. In your example the virtual server would move from primary to secondary if the primary server failed. You would still attach to the sql server using the virtual name.Lance Harra |
|
|
|
|
|
|
Virtual server in an active / passive legato cluster