Having a bloated backup history can cause issues in Disaster Recovery Scenarios.
It is generally regarded as a best practice to keep a more streamlined version of the backup and job history tables.
This condition will check if you have more than 60 days worth of backup history stored in MSDB. If this check is true it will reurn a value of 1 and fire off any associated actions.
It is suggested that you change the history variable inside the condition to one that meets your needs and then use the "Execute SQL" action to purge the required amount of history.
More details on how to accomplish this through the Microsoft stored procedure sp_delete_backuphistory can be found here - https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-delete-backuphistory-transact-sql?view=sql-server-2017
More details on how to set up actions can be found at https://docs.sentryone.com/help/actions
Running the follwing query will allow you to see which tables are taking up a large amount of space.
SELECT OBJECT_NAME(i.object_id) as objectName,
i.[name] as indexName,
SUM(a.total_pages) as totalPages,
SUM(a.used_pages) as usedPages,
SUM(a.data_pages) as dataPages,
(SUM(a.total_pages) * 8 ) / 1024 as totalSpaceMB,
(SUM ( a.used_pages) * 8 ) / 1024 as usedSpaceMB,
(SUM(a.data_pages) * 8 ) / 1024 as dataSpaceMB
FROM msdb.sys.indexes i
INNER JOIN msdb.sys.partitions p
ON i.object_id = p.object_id
AND i.index_id = p.index_id
INNER JOIN msdb.sys.allocation_units a
ON p.partition_id = a.container_id
GROUP BY i.object_id, i.index_id, i.[name]
ORDER BY SUM(a.total_pages) DESC, object_name(i.object_id)
GO