Workaround:
There is no way to force the LiteSpeed Differential backup to reference only the Full Backup created by LiteSpeed.
Any backup process is dependent on SQL Server. LiteSpeed and any third party tool creating a back up is issuing an command to SQL Server to do a backup (full/diff/t-log). SQL Server instead of writing the data directly to the destination, is streaming the data to us (LiteSpeed) and LiteSpeed does the compression, encryption and writes the file to the destination.
In this case, it acts no different than a SQL Server native backup or any third party backup in the point of view of SQL Server backup\recovery.
Unless the other backup tool, in this case, Netapp Snapmanager makes a copy_only backup, it will mark a checkpoint on the SQL Server side. When the LiteSpeed differential backup is invoked, SQL Server will stream us only the data changed since the last backup that was created by the other third party application.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center