I have two feature requests for SQL Backup. The first is that more than one instance of the application can run on the server at the same time. We often have administrators logged into the server at the console and via remote desktop, and only one person at a time can use SQL Backup, which is an annoying limitation. The other is that although SQL Backup can write files to one directory and copy them to another location, it cannot delete the files in the second location on a schedule. So if you have a backup job that is writing to drive f: and also copying the backups to \\myFilestore, it can delete the backups on drive f: every x number of days, but not in \\myFilestore. This means that jobs must be created outside of SQL Backup to delete those backups, which usually means creating batch files and running them as scheduled tasks.
0 · Share on Twitter