August 7, 2012 at 6:04 am
Hi,
Trying to work with log shipping. Primary server is backup log files but the secondary isn't copying them to the secondary server. The failed job in secondary (LSCopy..) doesnt tell me anything useful.
I have the following setup:
Both primary and secondary use the same AD account for ALL services.
The AD account has full control for both the Backup location for the Log file and the Copy/Read location on the Secondary.
I used the script out button so I have that to look at, but i cant see anything wrong (Not suprising not sure what im looking at!)
Ive ran the default Log Shipping Report on both the Primary and Secondary.
On the Primary it shows the Primary being in a Good Status. The seconary shows up but has no details against it apart from that.
On the Secondary it only shows a test db i tried to see if i could Log shipping working. (This worked. So i deleted the Agent jobs and deleted the db should i have done more?)
Ive been going though the MS 2008 high availability book to set it up but its troubleshooting section is weak to say that least.. Everything says this is the easest method.. so feeling a bit disappointed at the moment 🙁
Hope someone can help.
// EDIT
Not sure if it helps but, I set up a monitor server when i created the Log shipping.
The Log_shipping_monitor_history_detail table only has info again on the Primary Agent.. nothing on the secondary.
Talking about removing.. Looking at BOL it says you just need to use the GUI and clear the Log Shipping tick box. When i do that. The jobs are not removed from the secondary server.. Is there anything else i should do on the secondary when removing log shipping..
August 7, 2012 at 10:02 am
How to: Remove a Secondary Database (SQL Server Management Studio) - SQL Server 2008 R2
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 7, 2012 at 2:14 pm
n00bDBA (8/7/2012)
Hi,Trying to work with log shipping. Primary server is backup log files but the secondary isn't copying them to the secondary server. The failed job in secondary (LSCopy..) doesnt tell me anything useful.
I have the following setup:
Both primary and secondary use the same AD account for ALL services.
The AD account has full control for both the Backup location for the Log file and the Copy/Read location on the Secondary.
I used the script out button so I have that to look at, but i cant see anything wrong (Not suprising not sure what im looking at!)
Ive ran the default Log Shipping Report on both the Primary and Secondary.
On the Primary it shows the Primary being in a Good Status. The seconary shows up but has no details against it apart from that.
On the Secondary it only shows a test db i tried to see if i could Log shipping working. (This worked. So i deleted the Agent jobs and deleted the db should i have done more?)
Ive been going though the MS 2008 high availability book to set it up but its troubleshooting section is weak to say that least.. Everything says this is the easest method.. so feeling a bit disappointed at the moment 🙁
Hope someone can help.
// EDIT
Not sure if it helps but, I set up a monitor server when i created the Log shipping.
The Log_shipping_monitor_history_detail table only has info again on the Primary Agent.. nothing on the secondary.
Talking about removing.. Looking at BOL it says you just need to use the GUI and clear the Log Shipping tick box. When i do that. The jobs are not removed from the secondary server.. Is there anything else i should do on the secondary when removing log shipping..
check carefully the job history and post any details in full.
also supply details of the following queries.
Run from the primary
exec sp_help_log_shipping_primary_database
@database = 'primary_database'
Run from the secondary
exec sp_help_log_shipping_secondary_database
@secondary_database = 'secondary_database'
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 8, 2012 at 8:06 am
Hi guys thanks for the replies...
I ran the scripts.
Primary had details.. But the Secondary was empty... Ive ended up deleting it (thank you for the link) and starting again.. seems to have worked this time!
Is it normal to get this kind of half finished result if you enable log shipping via the GUI? Secondary was over a WAN link but it managed to copy the 15gb dbe fine.. Agent jobs were created but it looks like the SP used to set up the connection didnt work???
Can i also get it confirmed how people like to remove log shipping. Im trying to piece together using BOL a clean method just using T-SQL. since
Thanks for any help and hints 🙂
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply