all groups > sql server replication > november 2003 >
You're in the

sql server replication

group:

Log Shipping from Primary to Multiple Secondaries ?


Log Shipping from Primary to Multiple Secondaries ? Frank
11/25/2003 5:13:35 PM
sql server replication:
Hi all,

I've been racking my brains here, maybe some one can provide some
explanation.

Scenario:

SQL2000 Ent. Ed. on three servers, A B & C
SQL A - Located in Datacenter 1 (Primary)
SQL B - Located in Datacenter 1 (Secondary, Warm Standby, LS Monitor)
These two are set up for same site failover in case of hardware failure.

SQL C - Location in Datacenter 2 (Secondary, Warm Standby)
This location is set up as disaster recovery location in another city/state.

Datacenters 1 & 2 are connected via IPSEC tunnel over WAN in different
cities and *all* servers are registered in *all* EM and resolving each other
fine, shares accessible, etc...

Problem:

If I use the Database Maintenance Wizard and create Log Shipping Plan for a
DB between (SQL A <-> SQL B) it works fine and everything is nice. If I
then go to the Log Shipping tab of the Maint Plan and attempt to use the
"Add" button to ADD an additional server and specify the settings for the
SQL C server at Datacenter 2, I recieve an Error on the initialization when
it tries to copy the initial backup over to server:

"unable to copy the initialization file to the secondary server
'<server_name>'"

Now, if I delete the plan, start over and specify *both* SQL B *and* SQL C
as secondary servers using the Maint. Plan Wizard again from scratch it then
goes through, initializes and sets up *both* secondaries fine. I end up
with SQL A log shipping to SQL B and SQL C and everything is nice.

The interesting part is that if I attempt to use SQL Query Analyzer
(xp_cmdshell) to copy to the init.bak file from the Primary (SQL A) over to
SQL C it succeeds without error.

Questions:

Why would it work when I configure from the Maint. Plan wizard, but fail
when I try to ADD from the Log Shipping tab ?

How do I troubleshoot whether this error message and failure when attempting
to *ADD* additional LS secondaries to the existing Maint Plan is a bug, or
some other obscure permission problem ?

I've seen the KB article that describes this condition on a SQL Cluster with
two different domain, however I'm using neither. All three SQL servers are
part of the same workgroup, and are using the Admin account with identical
passwords for the SQL Server Service and SQL Server Agent.

Thanks in advance.

Frank

Re: Log Shipping from Primary to Multiple Secondaries ? Frank
11/28/2003 1:21:37 PM
Follow up to my own post as an FYI...

I was eventually able to successfully ADD the additional secondary (SQL C)
to the Maint. Plan by instead first manually copying and restoring a FULL
backup on SQL, then configuring the additional server to use the existing
database instead of initializing and creating it fram scratch.

Is this a limitation of the Log Shipping Wizard in SQL 2000 ?

Another snafu I ran into was after adding the SQL C secondary, even though
the Log Ship jobs on that server were running on schedule and not failing,
there were NO log files being copied over. Turns out the file path in the
log_shipping_plans table on SQL C had the path that was configured for SQL B
(which is an IP address used for the cross-over ethernet cabling between SQL
A <-> SQL B in Datacenter 1), so once I corrected that, the transaction logs
began copying over and life is good.

If anyone has any additional info on the issues I ran across and whether
they're bugs, or I did something incorrect I would appreciate the feeedback.

Thanks,

-Frank


[quoted text, click to view]

Re: Log Shipping from Primary to Multiple Secondaries ? John C.
2/22/2004 4:51:05 PM
Frank

I have the same problem and I am pissed off big time. Log shipping is presented as a walk in the park but it seems pretty unstable to me. Exactly as you said when I set up log shipping between SQLa and SQL B and then try to add another server it fails misserably

Did you try to do a role change? Half of the times I tried to use these very small, simple, cute scripts they fail.

When you say:
"first manually copying and restoring a FUL
backup on SQL, then configuring the additional server to use the existin
database instead of initializing and creating it fram scratch.

did you do a backup/restore on SQL C, place the db in standby mode, and then added SQL C from the log sipping tab

I would greatly appreciate a clarification
AddThis Social Bookmark Button