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 |
|
ewe1d@yahoo.de
Starting Member
17 Posts |
Posted - 2004-09-27 : 05:02:27
|
| Hi,I'm relatively new to SQLServer (worked with Oracle) so forgive me if there is an obvious answer....We're designing a new SQL Server 2000 setup involving a cluster with two nodes in active/passive mode with the database files on a storage area network, and a standby system to be set up at a differnt location. The standby system is fed data from the cluster via log shipping.My question is what happens to the standbyDB in a failover on the cluster? If a failover to node2 takes place am i right in thinking node2 "picks up" and continues to use the transaction log from Node1?... assuming the log is located on the SAN? This would also mean the transaction info is uninterrupted and we wouldn't need to rebuild the standbyDB, right?Thanks for your helpChidd |
|
|
ewe1d@yahoo.de
Starting Member
17 Posts |
Posted - 2004-09-27 : 05:12:06
|
| .... and what about changes in structure, e.g. new files added to database involved in log shipping?Would the standby database have to be completely rebuilt? |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-09-27 : 07:08:13
|
| if you have a cluster, the data and log files are actually on a shared drive, therefore if node1 fails then node2 picks up the loadin logshipping, tlogs are transferred from primary to secondary server. i haven't done logshipping but logically, yes changes will be carried over via tlogs. |
 |
|
|
|
|
|