Hi All,
In my log shipping setup, when i look at the LS_restore job history, it is reading through the available backups but skipping the restore with this message.
"Could not find a log backup file that could be applied to secondary database"
is it true, when there is no transactions happening in primary db, eventhough the log backups gets accumulated , restore will be skipped. All access is in place. No issue with the backup device.
Also when i try to check the restore settings in transaction log shipping under primary DB properties, im getting the below error:
"This secondary database is not functional because the required copy or restore job cannot be found. You must remove this secondary database by clicking Remove. To resume log shipping to this secondary database, add it as a secondary again using the same settings.If you resume log shipping and you specify the same restore path that you used before, any backup files that are uncopied or unrestored to this database will be copied and restored when it is added as a secondary again. Reinitializing the secondary database is unnecessary."
what could be the possible reasons, the restore is not happening?.
If someone can suggest a good book or effective on high availablity solutions(log shipping,mirroring,clustering) internals, it would be handy for me. I would like learn more on how these stuffs work internally, so that i will equipped to troubleshoot issues in future.
Thanks