Someone (who left the team) has setup my SQL Server 2000 Cluster1\Myinstance
It *was* setup to do log-shipping to a DR server and I thought he has setup
the instance to be 2+1 LAM Enabled before he left.
What tools/techniques can I use to see if the instance is 2+1 LAM enabled
and the nodes under the cluster, for I can see the log-shipping is still
enabled!
What does LAM mean?
Have you configured Log Shipping Monitor? It will show you how log shipping
is configured and give you statistics on how it is performing.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
news:8AB81107-4C6F-4CAC-B4B3-26286EC700D4@.microsoft.com...
> Someone (who left the team) has setup my SQL Server 2000
> Cluster1\Myinstance
> It *was* setup to do log-shipping to a DR server and I thought he has
> setup
> the instance to be 2+1 LAM Enabled before he left.
> What tools/techniques can I use to see if the instance is 2+1 LAM enabled
> and the nodes under the cluster, for I can see the log-shipping is still
> enabled!
|||Forget the LAM stuff
2+1 means I have 2 production nodes (I know what they are) and 1 DR node, I
believe. How/where would such DR setting be configured.
I know the log shipping is still enabled for log-shipping to disaster
recovery server (which would require connecting clients to change the host
name), but I want to find out if a DR node exist within the cluster (which
require AD reconfiguration, I believe) but connecting clients require no
changes to hostname.
Obviously I want to ensure a DR node exist before decomissioning the
log-shipping DR server.
But not sure how/where to check for SQL Server 2000.
"Hilary Cotter" wrote:
> What does LAM mean?
> Have you configured Log Shipping Monitor? It will show you how log shipping
> is configured and give you statistics on how it is performing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
> news:8AB81107-4C6F-4CAC-B4B3-26286EC700D4@.microsoft.com...
>
>
|||If I understand what you are doing correctly this is a M+1 single instance
configuration. Multiple nodes share a single failover node.
In this case your log shipping destination (called a secondary) should float
between nodes and it is transparent to log shipping which node is it
shipping to as it ships to a virtual server.
If your DR server is in a different location and not part of the cluster,
again it is transparent to the primary (the log shipping source) where you
are shipping to.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
news:EA513DEE-0616-4B41-BC5D-31EB42ACB792@.microsoft.com...[vbcol=seagreen]
> Forget the LAM stuff
> 2+1 means I have 2 production nodes (I know what they are) and 1 DR node,
> I
> believe. How/where would such DR setting be configured.
> I know the log shipping is still enabled for log-shipping to disaster
> recovery server (which would require connecting clients to change the host
> name), but I want to find out if a DR node exist within the cluster (which
> require AD reconfiguration, I believe) but connecting clients require no
> changes to hostname.
> Obviously I want to ensure a DR node exist before decomissioning the
> log-shipping DR server.
> But not sure how/where to check for SQL Server 2000.
> "Hilary Cotter" wrote:
|||Where are all these configured and how can I test how they are set up?
"Hilary Cotter" wrote:
> If I understand what you are doing correctly this is a M+1 single instance
> configuration. Multiple nodes share a single failover node.
> In this case your log shipping destination (called a secondary) should float
> between nodes and it is transparent to log shipping which node is it
> shipping to as it ships to a virtual server.
> If your DR server is in a different location and not part of the cluster,
> again it is transparent to the primary (the log shipping source) where you
> are shipping to.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
> news:EA513DEE-0616-4B41-BC5D-31EB42ACB792@.microsoft.com...
>
>
|||Use the log shipping wizard in EM on the Enterprise Edition of SQL Server.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
news:E60E85E3-01F2-4643-A629-1D33FB03CA7D@.microsoft.com...[vbcol=seagreen]
> Where are all these configured and how can I test how they are set up?
> "Hilary Cotter" wrote:
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment