Make internal SCCM Backup task mor flexible
Currently the SCCM backup task is interacting with the database directly creating a full backup every time. When using other backup products (as TSM) the use of SCCM backup and a full set of files is simply not possible since we increment the backup counter. TSM differential backups will not work until a new full backup has been run.
The ask is to either enable flexibility to be able to use different SQL backup mechanism apart from SCCM internal or to be able to run the backup task without triggering a SQL Backup.
Yes; please stop having SCCM manage database backups. An environment with SCCM (or Endpoint Management) should have a real DBA. But if you insist on doing database backups, please make them be able to be set to copy-only full backups.