transaction log shipping on a cluster

#1

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship to
a warm (not-clustered) standby server. Both the cluster and warm standby are
running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I assume
the shared directory for the transaction logs must be on the SAN as well so
that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g>

TIA

#2

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#3

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#4

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#5

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#6

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#7

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#8

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#9

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA

#10

The cluster does not enter into the Log Shipping picture in any way. Either
the Source SQL Server is up, or its not.

And yes, put the backed up log files on one of the shared drives in the SQL
resource group.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:

Hi All: I'm hoping someone can either point me to a whitepaper or let me
know if there are any gotchas about setting up transaction log shipping on
an active/passive cluster. The cluster is the primary and I want to ship
to a warm (not-clustered) standby server. Both the cluster and warm
standby are running 2003R2 and sql 2005 sp2.

I have the two cluster servers connected to a SAN that holds the database.
The two servers also have locally connected drives they boot from. I
assume the shared directory for the transaction logs must be on the SAN as
well so that if there's a failover the same network share is present?

Or is there a different way to configure it specific to a cluster
environment? Any gotchas before I bring down the whole system? <g

TIA