Log Shipping logs never get shipped to Secondary database
-
Hi.
Could someone tell me what did i miss out in my steps when i configured our production database to our development database?
I tried on 2 separate servers and also between 2 separate instances on our development server, but it didn't work.No error after configuring Log shipping though.
Between the 2 servers - the transaction logs was backup every 1min on the pri server but log files just didnt transfer to secondary database.
Between 2 separate instances on the development server - transaction log was not even backup.
Both SQL Server 2005 workgroup edition resides on windows server 2003 and both are on work group environment (production server overseas while development server local),not domain.
Steps i took to configure log shipping:
1) Shared the folder that hold the backup file on the primary database server, even the SQL Agent was added to have read and write access.
2) Shared the folder that suppose to hold the copy transaction logs on the secondary database.
3) Restored the pri database to secondary database manually since using the wizard in object explorer doesn't seemed to work....
4)Used the object explorer wizard to configure log shipping with all the relevant network paths typed in.
Could it be that i didn't set any security settings between the 2 servers or the folders?
Hope someone help me out of this predicament
.Thank you in advance! -
Are you sure that the path that you have given for the transaction log backup file is correct and the network path for copying is also right. Are you using a monitor and can you post us the history of the backup, copy and restore jobs.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
i've already disabled the log shipping but i can do it now with the monitor and do some testing before i give you the history.I didnt configure with the monitor as i wasn't sure how to use it.Just saw alot of zeros the other day.
Give me a moment while i find the query to run the monitor and set up the log shipping again ya..
I just do know that if i try to restore from the primary db to secondary db it will return an error saying it can't open the backup file from the path ive typed.
But all the transaction logs was successfully backup in the same folder.
Not sure if secondary db can't access the folder because of security settings though..ive enable it to access under folder properties to the SQL Agent
Maybe other than sharing the folder,you would know how to configure the folder to be accessible by the secondary db?
I am very sure that the network path that i've typed is correct.
But this still doesn't explain why when i configure log shipping between my two instances on the local server,the configuration says it's successful but doesnt restore the primary db at all...
I'll set up the log shipping again and will post the history
Meanwhile,i hope someone knows what's the problem
-
i've already disabled the log shipping but i can do it now with the monitor and do some testing before i give you the history.I didnt configure with the monitor as i wasn't sure how to use it.Just saw alot of zeros the other day.
Give me a moment while i find the query to run the monitor and set up the log shipping again ya..
I just do know that if i try to restore from the primary db to secondary db it will return an error saying it can't open the backup file from the path ive typed.
But all the transaction logs was successfully backup in the same folder.
Not sure if secondary db can't access the folder because of security settings though..ive enable it to access under folder properties to the SQL Agent
Maybe other than sharing the folder,you would know how to configure the folder to be accessible by the secondary db?
I am very sure that the network path that i've typed is correct.
But this still doesn't explain why when i configure log shipping between my two instances on the local server,the configuration says it's successful but doesnt restore the primary db at all...
I'll set up the log shipping again and will post the history
Meanwhile,i hope someone knows what's the problem
-
between servers - what is the account under which your sql server service runs. If local system then you will find this problem you will need to run under a doamin account to solve this problem.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
Hi,
These are the below steps in performing log shipping,
1) On primary server, create a shared folder. Eg: c:\log
2) Backup the database on primary server to shared folder. (The database is running under fullrecovery)
3)Ensure that SQL SERVICE ACCOUNT of the secondary server has modify privileges on the shared folder of primary server,as copy job will run from secondary server accessing the shared folder in primary server
4) Restore the database on secondary server with standby option.
5) Configure the database on primary server for logshipping with 15 minutes of
logshipping frequency.
6) Do some DML on primary and this should be applied to secondary on the next log backup.
NOTE:
****
A shared folder should be created in primary server.No need to create a share folder in secondary server
Also no need to create 2 shared folders as mentioned by u,jus create 1 in the primary........also as Sugesh pointed out,u need to use a domain account for logshipping to be configured b/w 2 diferent servers.
[font="Verdana"]- Deepak[/font]
-
Also do check the error log and job history details,u shud get a clear idea.....also refer the URL, http://support.microsoft.com/kb/321247 mite be useful
[font="Verdana"]- Deepak[/font]
-
Thank you Suresh & Deepak for the helpful tips.
Can i know Deepak,what is DML that you refer to?
So am in trouble now since both servers are not set up with domain account?
Hasn't anyone done it with local log ins before?
By the way,Both of you have inspiring codes at the bottom of each post
-
Can i ask one more thing?
Does that mean since both servers are not set up with domain account i can't configure replication and mirroring too?
oh man...
-
hi dude,
what i meant to say was if u perform any data modification operations (DML) i.e if u create a table in the log shipping db in source and insert some records into a table u will come to know whether the log shipping functions properly,all the changes applied in the source will get reflected in the destination servers db as well........Yes u r rite, u need a domain account to configure replication,log shipping and mirroring b/w 2 different servers.if u use local system it is within that particular server.
[font="Verdana"]- Deepak[/font]
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply