April 22, 2009 at 11:43 am
I have set up log shipping but have to manually copy the .trn files as the copy job, although it ends successfully does not copy any files from the primary to the secondary. The restore job applies them successfully after I have manually copied them.
The msdb.log_shipping_plan table on the secondary server shows the following:
{A6AB91A-D012-448E-8A6F-1B027A26D998}
U-BMTH-OPXDB-01.MNDT_Batching_logshipping
*****Source Server= U-BMTH-OPXDB-01
*****Source Dir= \\U-LPL-PROD-18\MNDT_Batching_Logs
Destination Dir F:\Microsoft SQL Server\MSSQL\BACKUP\MNDT_Batching_Logs
{C5A56988-3D05-4FB1-B970-1D17F0C9D17F}
{A551DFBD-9853-4B2A-8A88-90DFF0731CB3}
2880
1440
My primary server is U-BMTH-OPXDB-01 and my secondary is U-LPL-PROD-18, so why does my Source Dir say U-LPL-PROD-18. Is this my problem?? what is the copy job supposed to do and what have I specified incorrectly please?
April 23, 2009 at 4:45 am
david.tomlinson (4/22/2009)
I have set up log shipping but have to manually copy the .trn files as the copy job, although it ends successfully does not copy any files from the primary to the secondary
.
Why are you manually copying files, this has to be performed by copy job. Did the copy job run ever on secondary server? If ran did it run successfully?
April 24, 2009 at 2:05 am
As my note says...... The copy job runs to EOJ but does not copy the file. That is the problem I have!
April 24, 2009 at 2:19 am
Yes, the source directory should be your primary server's shared folder.Also give full permissions to the shared folders on both the servers.
Re-configure again by giving the correct paths.
Also on secondary server,create a separate folder for the logbackup files and give full permissions.
April 24, 2009 at 2:38 am
Yes how and where, I thought I had given the correct paths. On what part of the wizard is that source directory specified please.
April 24, 2009 at 3:26 am
There is an option in the configuration wizard about the source dircetory.
I think you have given \\U-LPL-PROD-18\MNDT_Batching_Logs there.give primary's folder here.
Also for the secondary, create a separate folder instead of F:\Microsoft SQL Server\MSSQL\BACKUP\MNDT_Batching_Logs and give full permissions.
April 24, 2009 at 3:58 am
I followed Microsofts document http://technet.microsoft.com/en-gb/library/cc966381.aspx
and specified the Transaction Log Folder, which for me is H:\MSSQL\BACKUP\MNDT_batching\Log_Shipping and has a share name of Log_Shipping
and on the next screen, the Transaction log Share, I specified the Log_Shipping share.
It seems that this step is the bit I did wrong but I cannot see what is wrong????
When I added the Log Shipping Destination, Add Destination Database, I specified the name of the directory on the secondary server that my logs should be copied to and this bit is corrrect.
April 24, 2009 at 4:35 am
Did the job LSCopy_ has ever run, if so can you pls. send run details
April 25, 2009 at 7:20 am
Whenever I have set up log shipping previously I have always started by creating the necessary shares on the primary and sceondary servers and granting the required privilges on those shares.
I then create a simple text file called test.txt on the primary server in the location where you intend to write the transaction log back up.
I then go onto the secondary server and try to copy test.txt file from the primary server transaction log location to the secondary server transaction log location using xcopy. If there are any permission type issues this generally flags up the problem.
If you don't have a permissions issue, I have had the type of problem you mentioned before when the secondary server wasn't communicating properly with the monitor server. When the communication problem was resolved it all worked. Unfortunatly I can't remember the specifics.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply