Hi,
would it be possible to have seperate ERASEFILES flags for the default backup path and the COPYTO paths.
Currently I have a custom stored proc that does a backup of the database (currently Litespeed, but I am evaluating SQlbackup as it has additional features which look quite good) to a dedicated disk share on the local LAN, and then copies it to a diskshare at our disaster recovery site. I then have a custom vb.net app that does the file cleanup and deletes old files as per whatever has been set in a custom backup table.
In this case I have a setting that says keep the local backups for 7 days, and keep the DR backups for 190 days.
So would it be possible to specify 2 ERASEFILES flags,one for the primay location (i.e. 7 days), and another for the COPYTO location (i.e 190)
cheers
Richard
Thanks for the suggestion. Although it is possible to erase files in both the local location and in the COPYTO location you can only set one value for the cut off point.
would it be possible to have seperate ERASEFILES flags for the default backup path and the COPYTO paths.
Currently I have a custom stored proc that does a backup of the database (currently Litespeed, but I am evaluating SQlbackup as it has additional features which look quite good) to a dedicated disk share on the local LAN, and then copies it to a diskshare at our disaster recovery site. I then have a custom vb.net app that does the file cleanup and deletes old files as per whatever has been set in a custom backup table.
In this case I have a setting that says keep the local backups for 7 days, and keep the DR backups for 190 days.
So would it be possible to specify 2 ERASEFILES flags,one for the primay location (i.e. 7 days), and another for the COPYTO location (i.e 190)
cheers
Richard