I have the same problem too. I've noticed that it's only about databases with simple recovery model. DD cleaning runs every Tuesday but expired backups stay. I've already created the SR.
You have to run a command to purge the expired backups. We include this command in the backup job, as an additional step after the backup is performed.
You have to run a command to purge the expired backups. We include this Wegmans Login command in the backup job, as an additional step after the backup is performed.
I've noticed that it's only about databases with simple recovery model. DD cleaning runs every Tuesday but expired backups stay. I've already created the SR.
Whether this is problematic or not depends on many factors If you're not compressing your backups with SQL Server, the Data Domain will be able to deduplicate the data more efficiently, but more data will have to travel through the network.
What actually deletes the data on the Data Domain is the cleaning process.
Is the cleaning configured and scheduled?
If the cleaning is scheduled and runs regularly, then we need to investigate if MSSQL communicates with Data Domain properly what sets have expired, so Data Domain can delete them.
ble1
6 Operator
•
14354 Posts
•
56186 Points
3147
0
Posted March 20th, 2017 12:00
I assume you use DDBEA? You should move you question to DD forum - this is general area reserved for questions about DECN only.
Do you see those also after they were supposed to expire AND DD cleanup has run? (typically once per week)