Return
-
Title
Automated restore process requires a FULL backup to be restored first every time? Can the Automated Restore be used ONLY with tlogs? -
Description
We see that the automated restore process requires a FULL and will not work with a directory that just contains the subsequent tlogs. If so, what would I give our clients/customers to use to restore subsequent log files automatically on a specified schedule? Ideally it would sweep through a directory, ignoring older log files already restored, restoring the next ones in the chain, and leaving ones ahead of where we are in the restore process alone. Completed (or old) restore files will eventually move to an archive folder.
Can the Automated Restore Process be used ONLY with tlogs for a customer of ours that is receiving files from us via an FTP site?We cannot use LiteSpeed Log Shipping because our customers are on a separate network than we are.It would be good to have the ability to restore any new tlogs since the most recent automatic restore, without having to restore a full backup first every time.
-
Cause
This is being tracked as enhancement request LS-1591: "automated restore be able to restore tlog backups to a database in a recovering state". -
Resolution
WORKAROUNDYou could send over all the backups (full, diff and tlogs) needed to do so (perhaps on a weekly schedule) and run automated restore on those files overwriting the old out of date database with the new data. It's always going to need a full backup to go along with it though. Automated restore will not restore to a database that already exists unless you overwrite it.
STATUS
This request is being evaluated by Product Management and Development for for possible inclusion in a future release of LiteSpeed for SQL Server.
-
Defect ID
LS-1591