January 27, 2011 at 11:26 am
Logshipping on one of my prod boxes is failing from last 3 weeks. basically copy job is working fine and copying the log files from source to destination. Restoration part is failed.
I want to know the easy process for bringing back to normalcy. (if this can be fixed by just restoring the latest backup from source on to target , then i can do that)..
please guide me on steps to do and precautions to be taken.
Regards
January 27, 2011 at 12:21 pm
It would be good if you posted the error message when the restore fails. Also look in the logs and see what happened 3 weeks ago when it started failing.
In essence yes, restore the last full backup with NO RECOVERY.
This is assuming there isn't something odd wrong like a access haing been changed.
To keep things a bit cleaner I tend to clean up the lgo file folder so there are only log backups from after the last full backup, but this isn't essential.
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
January 27, 2011 at 12:35 pm
am not seeing any specific error. on restore job history, it says step failed. 🙁
January 27, 2011 at 12:51 pm
Right Click on the restore job--->Properties--->Steps--->Highlight Step 1--->click Edit
Paste what it says in
Type:
Run as:
Command:
January 27, 2011 at 1:16 pm
TYPE: oPERATINGSYSTEM COMMAND(Cmdexec)
Run as: SQl server agent
Command: "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqllogship.exe" -Restore 02443D0C-6EE6-4139-B9B9-6E272E0324B8 -server EBFFwoe3
in view job history, error Message is..
Executed as user: EBFFwoe3\SYSTEM. The step failed.
January 28, 2011 at 9:33 am
NewBeeSQL (1/27/2011)
TYPE: oPERATINGSYSTEM COMMAND(Cmdexec)Run as: SQl server agent
Command: "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqllogship.exe" -Restore 02443D0C-6EE6-4139-B9B9-6E272E0324B8 -server EBFFwoe3
in view job history, error Message is..
Executed as user: EBFFwoe3\SYSTEM. The step failed.
Check which service account are you using for sql agent
Go to control panel services-->sql server agent
or
(MUST RUN FROM SERVER)
DECLARE @serviceaccount varchar(100)
--Retrieve the Service account from registry
EXECUTE master.dbo.xp_instance_regread N'HKEY_LOCAL_MACHINE',
N'SYSTEM\CurrentControlSet\Services\SQLSERVERAGENT',
N'ObjectName',
@ServiceAccount OUTPUT,
N'no_output'
--Display the Service Account
SELECT @Serviceaccount
Check if sql agent service account has proper privilege in the shared folder where transaction logs are kept from primary server.
January 31, 2011 at 9:09 am
Thanks all..Restoring the latest full backup from source fixed the issue.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply