Gurus,
Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
Cluster command line I can run which will stop my "SQL Agent Service"?
Spin
Hi
How about NET STOP?
John
"Spin" <Spin@.invalid.com> wrote in message
news:656t5iF2eq3dbU1@.mid.individual.net...
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>
|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:e2yjJedkIHA.5368@.TK2MSFTNGP04.phx.gbl...
> Hi
> How about NET STOP?
No can do John. NET STOP stops the service outside of the Cluster
environment. What will happen is the Windows Cluster service will detect
the service down then automatically restart it! What I need is a Cluster
service command line tool which gracefully stops the service per "knowledge"
if you will, of the Cluster service.
|||For the default instance:
cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
For a named instance (assuming that the instance name is SQL2):
cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
/offline
Linchi
"Spin" wrote:
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>
>
|||Thanks! I'll shout back on Monday if this works...
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...[vbcol=seagreen]
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
> "Spin" wrote:
|||"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
Worked!!!!! You are a Gentleman and a Scholar!
Spin
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Monday, March 26, 2012
Is there a Cluster command line I can run which will stop my "SQL Agent Service"?
Gurus,
Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
Cluster command line I can run which will stop my "SQL Agent Service"?
--
SpinHi
How about NET STOP?
John
"Spin" <Spin@.invalid.com> wrote in message
news:656t5iF2eq3dbU1@.mid.individual.net...
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:e2yjJedkIHA.5368@.TK2MSFTNGP04.phx.gbl...
> Hi
> How about NET STOP?
No can do John. NET STOP stops the service outside of the Cluster
environment. What will happen is the Windows Cluster service will detect
the service down then automatically restart it! What I need is a Cluster
service command line tool which gracefully stops the service per "knowledge"
if you will, of the Cluster service.|||For the default instance:
cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
For a named instance (assuming that the instance name is SQL2):
cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
/offline
Linchi
"Spin" wrote:
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>
>|||Thanks! I'll shout back on Monday if this works...
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
> "Spin" wrote:
>> Gurus,
>> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
>> Cluster command line I can run which will stop my "SQL Agent Service"?
>> --
>> Spin
>>|||"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
Worked!!!!! You are a Gentleman and a Scholar!
--
Spin
Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
Cluster command line I can run which will stop my "SQL Agent Service"?
--
SpinHi
How about NET STOP?
John
"Spin" <Spin@.invalid.com> wrote in message
news:656t5iF2eq3dbU1@.mid.individual.net...
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:e2yjJedkIHA.5368@.TK2MSFTNGP04.phx.gbl...
> Hi
> How about NET STOP?
No can do John. NET STOP stops the service outside of the Cluster
environment. What will happen is the Windows Cluster service will detect
the service down then automatically restart it! What I need is a Cluster
service command line tool which gracefully stops the service per "knowledge"
if you will, of the Cluster service.|||For the default instance:
cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
For a named instance (assuming that the instance name is SQL2):
cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
/offline
Linchi
"Spin" wrote:
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>
>|||Thanks! I'll shout back on Monday if this works...
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
> "Spin" wrote:
>> Gurus,
>> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
>> Cluster command line I can run which will stop my "SQL Agent Service"?
>> --
>> Spin
>>|||"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
Worked!!!!! You are a Gentleman and a Scholar!
--
Spin
Friday, March 9, 2012
Is SQL 2005 failover cluster supported on Windows 2008 clusters?
Hi,
I'm trying to install SQL 2005 on a Windows 2008 cluster. I just want
to know if this is supported, and if there's any special procedures
required for the same.
Thanks
M Rosenblum
Since Windows 2008 is not a released product, there is no "supported"
configuration. If there is any information, it will likely be in the
Windows 2008 readme file.
Feel free to experiment and post your results.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Usentr" <usentr@.gmail.com> wrote in message
news:1194464048.828727.215070@.e9g2000prf.googlegro ups.com...
> Hi,
> I'm trying to install SQL 2005 on a Windows 2008 cluster. I just want
> to know if this is supported, and if there's any special procedures
> required for the same.
> Thanks
> M Rosenblum
>
I'm trying to install SQL 2005 on a Windows 2008 cluster. I just want
to know if this is supported, and if there's any special procedures
required for the same.
Thanks
M Rosenblum
Since Windows 2008 is not a released product, there is no "supported"
configuration. If there is any information, it will likely be in the
Windows 2008 readme file.
Feel free to experiment and post your results.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Usentr" <usentr@.gmail.com> wrote in message
news:1194464048.828727.215070@.e9g2000prf.googlegro ups.com...
> Hi,
> I'm trying to install SQL 2005 on a Windows 2008 cluster. I just want
> to know if this is supported, and if there's any special procedures
> required for the same.
> Thanks
> M Rosenblum
>
Monday, February 20, 2012
Is my SQL Server 2000 cluster 2+1 LAM enabled?
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:
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:
Is my SQL Server 2000 cluster 2+1 LAM enabled?
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:
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:
Is my SQL Server 2000 cluster 2+1 LAM enabled?
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 shippin
g
> 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 flo
at
> 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:
>
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 shippin
g
> 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 flo
at
> 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:
>
Is my SQL Server 2000 cluster 2+1 LAM enabled?
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...
> > 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!
>
>|||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...
> 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...
>> > 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!
>>|||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...
> > 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...
> >> > 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!
> >>
> >>
> >>
>
>|||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...
> 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...
>> > 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...
>> >> > 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!
>> >>
>> >>
>> >>
>>
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...
> > 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!
>
>|||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...
> 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...
>> > 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!
>>|||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...
> > 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...
> >> > 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!
> >>
> >>
> >>
>
>|||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...
> 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...
>> > 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...
>> >> > 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!
>> >>
>> >>
>> >>
>>
Subscribe to:
Posts (Atom)