Logshipping -Restore error in SQL server 2008

  • I am trying to configure Log Shipping between a production and DR Server in SQL server 2008 with out Monitor Server. The configuration of Log Shipping seems to be working successfully,

    The jobs are all running as per my intended schedule. Logs are being created and shipped (appearing in the intended directory of the secondary server).

    Before setting up Log Shipping I did a manual restore of a full backup and immd T-Log backup of the database from Prod to DR with 'standby' option, and then during LogShipping Config chose the option 'No, The Secondary Database is Initialised'

    The database in DR is in Standby/ReadOnly Mode

    Backup job from prod and Copy job from DR is running with out any issues and I am able to see copied Log files in Secondary/DR server folder.

    The problem occurs when the LSRestore Job runs. It reads all the available Log files, but chooses to ignore them all and returns the following messages...

    Skipped Log Backup File .....

    Could not find a log backup file that could be applied to secondary Database.

    The Restore job seems to be successfully completed, but nothing is restoring all the time.

    *******************************************

    Error Message :

    Message

    2012-05-05 00:30:00.92Starting transaction log restore. Secondary ID: '322701ba-5e6f-49f7-a4a4-0566d1dcda07'

    2012-05-05 00:30:00.92Retrieving restore settings. Secondary ID: '322701ba-5e6f-49f7-a4a4-0566d1dcda07'

    2012-05-05 00:30:00.92Retrieved common restore settings. Primary Server: 'GBEXE11DB11', Primary Database: 'Xposure', Backup Destination Directory: '\\GBBED12DB07.emea.mrshmc.com\D$\logshippingbackup_xposure', File Retention Period: 2880 minute(s)

    2012-05-05 00:30:00.94Retrieved database restore settings. Secondary Database: 'Xposure', Restore Delay: 1, Restore All: True, Restore Mode: Standby, Disconnect Users: True, Last Restored File: <None>, Block Size: Not Specified, Buffer Count: Not Specified, Max Transfer Size: Not Specified

    Message

    2012-05-05 00:30:01.09Skipped log backup file. Secondary DB: 'Xposure', File: '\\GBBED12DB07.emea.mrshmc.com\D$\logshippingbackup_xposure\Xposure_20120504210001.trn'

    Message

    2012-05-05 00:30:01.14Skipped log backup file. Secondary DB: 'Xposure', File: '\\GBBED12DB07.emea.mrshmc.com\D$\logshippingbackup_xposure\Xposure_20120504211500.trn'

    2012-05-05 00:30:01.17Skipped log backup file. Secondary DB: 'Xposure', File: '\\GBBED12DB07.emea.mrshmc.com\D$\logshippingbackup_xposure\Xposure_20120504213001.trn'

    2012-05-05 00:30:01.19Skipped log backup file. Secondary DB: 'Xposure', File: '\\GBBED12DB07.emea.mrshmc.com\D$\logshippingbackup_xposure\Xposure_20120504214500.trn'

    2012-05-05 00:30:01.22Skipped log backup file. Secondary DB: 'Xposure', File: '\\GBBED12DB07.emea.mrshmc.com\D$\logshippingbackup_xposure\Xposure_20120504220000.trn'

    2012-05-05 00:30:01.31Could not find a log backup file that could be applied to secondary database 'Xposure'.

    2012-05-05 00:30:01.31The restore operation was successful. Secondary Database: 'Xposure', Number of log backup files restored: 0

    2012-05-05 00:30:01.31Deleting old log backup files. Primary Database: 'Xposure'

    2012-05-05 00:30:01.33The restore operation was successful. Secondary ID: '322701ba-5e6f-49f7-a4a4-0566d1dcda07'

    2012-05-05 00:30:01.33----- END OF TRANSACTION LOG RESTORE -----

    Exit Status: 0 (Success)

    ***********************************************

    ***I tried restore the copied logs manually and it is working.But donโ€™t know why as per the schedule, restore job is not able to restore the logs.

    Note : One more database is configured as logShipping in the same Prod and DR.That is working perfectly with out any issues.

    Also, SQL server and Agent is running on Domain\Service Account.So, there is no point of sufficient permissions issue.

    Any help greatly appreciated

  • Are you saying you can take all the files copied to th secondar and manually restore them successfully?

    The error suggests you are missing a log backup somewhere

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" ๐Ÿ˜‰

  • Yes, i am able to restore the copied logs manually.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply