How to add the native backup without breaking the regular LiteSpeed backup strategy?
Example:
A Full native backup nightly and copies to a reporting server. This disrupts the chain of backups on the LiteSpeed job, which does Full, Diffs, and Tlogs. The following error displays when restoring and applying the LiteSpeed Differential backup after applying the LiteSpeed Full backup on another server :
"This differential backup cannot be restored because the database has not been restored to the correct earlier state."
The reason this occur is the native Full is completed after the LiteSpeed Full backup. LiteSpeed will need the native full applied instead of the LiteSpeed Full backup
RESOLUTION 1:
Apply the native Full backup and then apply the LiteSpeed Differential backup
RESOLUTION 2:
You can change the native job by adding the @with = 'COPY_ONLY'. Do this would prevent interrupting the backup chain from LiteSpeed.
Note, native SQL Server 2005 supports full and log backups that are a copy-only backup, which does not affect the normal sequence of backups (LSN numbers). A copy-only backup is created independently of the regularly scheduled, conventional backups.
LiteSpeed extended stored procedures do not support the 'COPY_ONLY' feature in Versions 4.5 thru 4.8. This process must be run in the Native SQL Server. Beginning with Version 5.0, this feature is supported.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy