May 22, 2007 at 1:06 pm
I've always done Log Shipping with homegrown scripts. I've inherited a couple of servers that are using SQL log shipping. When I go into the Database Maintenance plan screens, and click on the Log Shipping tab, there are no entries there for the Destination Server. Is this normal? There are jobs on the destination server that look like just normal Database Maintenance plans, but are named Log Shipping for etc... The whole thing is failing. I'm just wondering if the destination server name should show up in the list box under that tab?
Thanks,
Ariadne
May 23, 2007 at 9:19 am
The destination server name should show up on the log shipping tab for the maintenance plan of the server you are shipping from. For example if you are shipping from server A to server B, the maintenance plan on server A should have the destination server (B) in the log shipping tab. Make sure that server B is registered in Enterprise Manager on server A, otherwise you will not be able to see any information. Server B should just have jobs that are named "log shipping ..." with no maintenance plan.
Hope this helps
May 23, 2007 at 1:20 pm
Thank you Ronda! That's exactly what I expected. Now I've stripped out the entire process and started from scratch, but everytime I try to initiate the maintenance plan, the gui just hangs forever. I'm not showing any database connections, no file building on the harddrive, nothing. What does it do at the beginning?
May 23, 2007 at 2:09 pm
I was having trouble initially as well. These are the things that I had to make sure to do before it would work.
Make sure the files where you are shiping from and to are shared between the servers and permissions are set correctly.
Make sure that the SQL Server instance is not called (local) on either of the servers.
When setting up the log shipping database restore it with the standby option. I used T-SQL to do this since it took a long time to restore the database.
May 24, 2007 at 2:26 pm
Thank you Ronda! I finally ended up stripping out log shipping altogether to try and start again. Unfortunately, now I've got a known bug popping up and it won't let me get around it at all! I've got over every table I can think of to find the offending record but can't find it.
Now getting:
The specified primary_server_name.primary_database_name('M') already exists.
I've checked all tables in all three servers (source, destination, monitor) to find anything on this database and can't. All entries were stripped out. I still have log shipping set up on other databases, and am now wondering if that is the problem?
Also the gui is telling me that the database isn't in standby mode, and I know for a fact that it is, as I did what you did and used a straight SQL statement to do the restore and put it in standby mode.
May 25, 2007 at 7:15 am
Sorry, that is out of my range of knowledge, however I found this posting that may be useful.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=259180
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply