ERASEFILES & ERASEFILES_REMOTE ignored
The result is having backup disks running full quickly with all effects and work coming with it.
I usually use BACKUP DATABASES [*] and BACKUP LOGS [*] with the ERASEFILES & ERASEFILES_REMOTE options.
The log also Always states something like this at the bottom:
4/3/2013 3:15:16 AM: The backup set on file 1 is valid.
4/3/2013 3:15:16 AM: Deleting old backup file: H:\Backup\databasename\FULL_INSTANCENAME_databasename_20130401_031500.sqb
4/3/2013 3:15:16 AM: Deleting old backup file: \\networkname\directories\INSTANCENAME\databasename\FULL_INSTANCENAME_databasename_20130319_031500.sqb
4/3/2013 3:15:24 AM: Copied H:\Backup\databasename\FULL_INSTANCENAME_databasename_20130403_031500.sqb to \\networkname\directories\INSTANCENAME\databasename\FULL_INSTANCENAME_databasename_20130403_031500.sqb.
But on the new cluster I completely miss this part..... Locally (erasefiles) as well as on the networkdrive copies (erasefiles_remote). I just continues with the next database.
Now I must say that the old part is running version 6 something
The new cluster is running SQL Backup version 184.108.40.206 & Service application version 220.127.116.11
I already notice that the copy action is now a seperate action as I receive seperate emails from the copy to network action on success.
But I really need ERASEFILES & ERASEFILES_REMOTE to work! By default the FILEOPTIONS = 1 is not added when using the GUI. Also tried adding that, but to no avail.