Re: transaction log shipping on a cluster - 05-02-2008 , 11:13 AM

"Kevin3NF" <kevin (AT) SPAMTRAP (DOT) 3nf-inc.com> wrote

Quote:

The SQL backup is configured on the instance, not the node. Forget you are on a cluster. Connect to the instance via Mgmt Studio, right click the database>>Properties>>Transaction Log Shipping and go from there. The instance can only run on one node at a time, and it does not matter which node it is on when you configure it.

Thanks so much for the clarification!

Quote:

-- 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 in message news6789F5E-6577-4640-8FB8-0DEA710B8BC0 (AT) microsoft (DOT) com... "Kevin3NF" <kevin (AT) SPAMTRAP (DOT) 3nf-inc.com> wrote in message news:%23dvt2%23ErIHA.5940 (AT) TK2MSFTNGP04 (DOT) phx.gbl... The cluster does not enter into the Log Shipping picture in any way. Either the Source SQL Server is up, or its not. Thanks for that reply...just so I'm clear...do I need to configure the primary backup on both servers in the cluster, or just on the active one? I'm a little hazy on when/if anything has to be done on both members of cluster or just the active node. 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 in message news:uiu5nf9qIHA.3940 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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