Backup Files growing quickly on SQL Server 2016 Always On Cluster I have a two-node SQL Server 2016 Always On Cluster.  I also have a job that updates about 200 records in one table every 3 minutes.  Even when there are no updates, it does change a TimestampDt field with the current time.

Previously my backup files were growing at a manageable 10-20 MB per day.  However, now that I started making the TimestampDt field updates every 3 minutes (this was a recent change) my backup files are growing at a size of 200 MB per day.

I think that the backup is including the entire transaction log.

Here is the backup SQL Query:

SET @BackupUrl = CONCAT('https://backup.blob.core.windows.net/databasebackup/dbname-',GETDATE(),'.bak');
BACKUP DATABASE dbname
   TO URL = @BackupUrl
   ;


What is the recommended approach here?  Should I purge the transaction logs somehow on backup?  If so, how can I do that safely in an Always On Availability Group clustered environment?

Any help would be greatly appreciated.
What type of backup are we talking about?

Full? This only include the log records produced while the backup command is running (basically).

Differential? Same as above, as for the log records. As for data, it include the modified extents since last full backup. I.e., it will grow and grow until next full backup.

Log? It includes the log records since last log backup.

Also, what options did you specify for the backup command? If you post the backup command you use, we have some something to go on...