We ran backup Commands;
EXEC master.dbo.xp_slsFastCompression @database = 'DBname', @desc = 'Daily Backup', @AdaptiveCompression = 'speed', @OLRMAP = 1, @with = 'CHECKSUM', @AppendDifferential = 0, @CheckForFullBackup = 1, @ExtentsChgRatioRequireFull = '.3', @BackupDirectory = '\\backuptest\Daily', @SearchAlternateBackupDirectory = '\\backupt\Weekly', @FullBackupEscalation = 1, @ElapsedDaysRequireFull = 365;
Then when the backup file is saved in a new location ....
@BackupDirectory = '\\backupt1\Daily', @SearchAlternateBackupDirectory = '\\backupt1\Weekly'
The cleanup command runs each Saturday, my schedule assigns the database name and dates ...
EXEC master.dbo.xp_slsSmartCleanup
@database = '%{Value.name}',
@BackupExpiration = '${BackupExpiration} 18:01:00',
@LogExpiration = '${BackupExpiration} 18:01:00'
The cleanup will use the LitespeedLocal database to determine where the backup file exists, but I have moved the files to backupt1. The files will not get deleted on backupt1 and I will need to manually delete them.
SmartCleanup is working as designed. Unlike FastCompression, SmartCleanup does not have an alternate directory parameter and it does not go searching for backups when they are missing.
WORKAROUND:
1) Move the files back.
2) Update MSDB when files are moved, or
3) Delete manually.
