Log Shipping Copy Job reports successful, but copies nothing

I have set up log shipping between 2 servers but cant get it to
function correctly.
Everything seems to be fine, the backup job happens, dumping the
transaction log to the network share on the primary server(also the
monitoring server).
The copy job runs and completes in 1 second or less, but doesn't seem
to move anything even though it reports success.
If I look at the copy/restore history in the log shipping monitor, it
continuously says that the copy succeeded, but no files were moved and
the last file moved is first_file_00000000.trn
I have checked the settings for the shares, and they are both fine.
I am able to log into the secondary server using the Sql Agent account
and map to the network share on the primary server where the log files
are being created. No problem there.
If I manually move the files the restore job works fine.
The log_shipping_secondary table is getting updated by the restore job
too, and I am using sql authentication with the
log_shipping_monitor_probe account set to sysadmin and db_ownber in
msdb.
It seems to be just the copy jobs never seeming to find any files even
when they are there.
I am starting to go crazy! HELP!
-Gregory
Gregory,
usually when I troubleshoot this issue it is a problem with the setup of
directories and shares, which can be confusing in the wizard. Please can you
remove the existing maintenance plan and set up the directories/shares below
then recreate the plan.
You need a folder eg c:\ProductionLogs that is shared
(\\server\PRODUCTIONLOGS) on the production server.
You need a directory on the standby server c:\shippedlogs, not shared.
In the maintenance plan, the transaction log backup directory is
c:\ProductionLogs
The network sharename is \\server\PRODUCTIONLOGS
The destination is c:\shippedlogs.
HTH,
Paul Ibison
|||Log shipping gives me no love.
I tried as you suggested, created new network shares, deleted the
maintenance plan and recreated the plan using the info you supplied.
It continues to give me the same problem.
This is in the history for the job:
Executed as user: XXXXXXX\UserID. output
---
---
(null)
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998. The step succeeded..
So informational.
Beautiful huh?
Additional info:
The servers are not on a domain, they are both in a workgroup.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Gregory,
there isn't an easy way for me to debug this, and no offence to you but I'd
like to ensure this is not a setup issue.
Please can you send me screenshots of the options you select when you go
through the wizard?
TIA,
Paul Ibison