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

Log shipping configuration - HELP

I'm having a difficult time making sence of the schedule SQL Server has
configured for my copy and restore jobs. I can't tie the monitor information
back to any of it.
My log shipping configuration does a backup every 120 minutes between 5AM
and 2:59AM; I run backups @. 3AM. The copy/load Frequency is set to 120
minutes with a load delay is 15 minutes.
Actual results are not what I expected, the log backups occur as expected
5AM, 7AM,9AM ect.., but the copy and restore jobs created on the secondary
are behind by 1 hour. Both the copy and restore jobs are executing on a 6AM,
8AM, 10AM schedule. Cany some one explain why this is happening? It is
causing an out of sync condition.
What effect does the load delay have on the restore job schedule.
Not sure it will help but look at
http://www.mindsdoor.net/SQLAdmin/LogShipping.html
If you want to replace it.
"Jerrick D.H" wrote:

> I'm having a difficult time making sence of the schedule SQL Server has
> configured for my copy and restore jobs. I can't tie the monitor information
> back to any of it.
> My log shipping configuration does a backup every 120 minutes between 5AM
> and 2:59AM; I run backups @. 3AM. The copy/load Frequency is set to 120
> minutes with a load delay is 15 minutes.
> Actual results are not what I expected, the log backups occur as expected
> 5AM, 7AM,9AM ect.., but the copy and restore jobs created on the secondary
> are behind by 1 hour. Both the copy and restore jobs are executing on a 6AM,
> 8AM, 10AM schedule. Cany some one explain why this is happening? It is
> causing an out of sync condition.
> What effect does the load delay have on the restore job schedule.
>
|||Nigel,
Thank you for taking the time to respond. I was using a similar process as
the one documented by mindsdoor, but switched to SQL automated process, and
I like it. Since I could not find a valid reason for the delay, I played
around with the job schedules until they woked they way I wanted them too.
"Nigel Rivett" wrote:
[vbcol=seagreen]
> Not sure it will help but look at
> http://www.mindsdoor.net/SQLAdmin/LogShipping.html
> If you want to replace it.
> "Jerrick D.H" wrote:

Log Shipping (can't "auto_fix" user after db restore)

Anyone,
I've implmented log shipping and it's working fine for the most part, but
since it's in a "read only" state,
I can't run a sp_change_users_login to remap my reports_readonly user to the
login on the secondary server.
Thus, this user can not access the read only database at all.
Anyone else seen this, or have a fix for it.
Thank you,
Wayne
Note the SID of that user in sysusers table within that database.
After that, drop the login and recreate it using sp_addlogin and the most
important being to use the SID noted from the sysusers table above
Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
!!!
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> Anyone,
> I've implmented log shipping and it's working fine for the most part, but
> since it's in a "read only" state,
> I can't run a sp_change_users_login to remap my reports_readonly user to
the
> login on the secondary server.
> Thus, this user can not access the read only database at all.
> Anyone else seen this, or have a fix for it.
> Thank you,
> Wayne
>
|||i'll give it a shot... thanks..
Wayne
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Note the SID of that user in sysusers table within that database.
> After that, drop the login and recreate it using sp_addlogin and the most
> important being to use the SID noted from the sysusers table above
> Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
> !!!
>
> "Wayne" <wgadberry@.comcast.net> wrote in message
> news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
but
> the
>
|||Worked like a champ Hassan.. you the man..
Wayne
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23wqQ3RzbEHA.2816@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> i'll give it a shot... thanks..
> Wayne
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
most[vbcol=seagreen]
luck[vbcol=seagreen]
> but
to
>

Log Shipping (can't "auto_fix" user after db restore)

Anyone,
I've implmented log shipping and it's working fine for the most part, but
since it's in a "read only" state,
I can't run a sp_change_users_login to remap my reports_readonly user to the
login on the secondary server.
Thus, this user can not access the read only database at all.
Anyone else seen this, or have a fix for it.
Thank you,
WayneNote the SID of that user in sysusers table within that database.
After that, drop the login and recreate it using sp_addlogin and the most
important being to use the SID noted from the sysusers table above
Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
!!!
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> Anyone,
> I've implmented log shipping and it's working fine for the most part, but
> since it's in a "read only" state,
> I can't run a sp_change_users_login to remap my reports_readonly user to
the
> login on the secondary server.
> Thus, this user can not access the read only database at all.
> Anyone else seen this, or have a fix for it.
> Thank you,
> Wayne
>|||i'll give it a shot... thanks..
Wayne
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
> Note the SID of that user in sysusers table within that database.
> After that, drop the login and recreate it using sp_addlogin and the most
> important being to use the SID noted from the sysusers table above
> Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
> !!!
>
> "Wayne" <wgadberry@.comcast.net> wrote in message
> news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
but[vbcol=seagreen]
> the
>|||Worked like a champ Hassan.. you the man..
Wayne
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23wqQ3RzbEHA.2816@.TK2MSFTNGP11.phx.gbl...
> i'll give it a shot... thanks..
> Wayne
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
most[vbcol=seagreen]
luck[vbcol=seagreen]
> but
to[vbcol=seagreen]
>

Log Shipping (can't "auto_fix" user after db restore)

Anyone,
I've implmented log shipping and it's working fine for the most part, but
since it's in a "read only" state,
I can't run a sp_change_users_login to remap my reports_readonly user to the
login on the secondary server.
Thus, this user can not access the read only database at all.
Anyone else seen this, or have a fix for it.
Thank you,
WayneNote the SID of that user in sysusers table within that database.
After that, drop the login and recreate it using sp_addlogin and the most
important being to use the SID noted from the sysusers table above
Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
!!!
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> Anyone,
> I've implmented log shipping and it's working fine for the most part, but
> since it's in a "read only" state,
> I can't run a sp_change_users_login to remap my reports_readonly user to
the
> login on the secondary server.
> Thus, this user can not access the read only database at all.
> Anyone else seen this, or have a fix for it.
> Thank you,
> Wayne
>|||i'll give it a shot... thanks..
Wayne
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
> Note the SID of that user in sysusers table within that database.
> After that, drop the login and recreate it using sp_addlogin and the most
> important being to use the SID noted from the sysusers table above
> Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
> !!!
>
> "Wayne" <wgadberry@.comcast.net> wrote in message
> news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> > Anyone,
> >
> > I've implmented log shipping and it's working fine for the most part,
but
> > since it's in a "read only" state,
> > I can't run a sp_change_users_login to remap my reports_readonly user to
> the
> > login on the secondary server.
> > Thus, this user can not access the read only database at all.
> > Anyone else seen this, or have a fix for it.
> >
> > Thank you,
> > Wayne
> >
> >
>|||Worked like a champ Hassan.. you the man..
Wayne
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23wqQ3RzbEHA.2816@.TK2MSFTNGP11.phx.gbl...
> i'll give it a shot... thanks..
> Wayne
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
> > Note the SID of that user in sysusers table within that database.
> >
> > After that, drop the login and recreate it using sp_addlogin and the
most
> > important being to use the SID noted from the sysusers table above
> >
> > Look at sp_addlogin in Books Online along with @.sid parameter.. Good
luck
> > !!!
> >
> >
> > "Wayne" <wgadberry@.comcast.net> wrote in message
> > news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> > > Anyone,
> > >
> > > I've implmented log shipping and it's working fine for the most part,
> but
> > > since it's in a "read only" state,
> > > I can't run a sp_change_users_login to remap my reports_readonly user
to
> > the
> > > login on the secondary server.
> > > Thus, this user can not access the read only database at all.
> > > Anyone else seen this, or have a fix for it.
> > >
> > > Thank you,
> > > Wayne
> > >
> > >
> >
> >
>