If performing a scheduled restore and changing the database name change the filenames automatically to match the new database name so the error / warning about the database failing wont occur. I dont want to specify a different directory to have to restore a database to

My company uses Google Apps for Business for email, so I'm not able to utilize the Backup Pro feature that emails results/logs. Could SSL/TLS support be added?

Thanks

Backups made with the copy only option checked should not be included in the backup history list of databases when restoring by default. The copy backup is used to maintain the sequence of logs so I dont think these should be shown in the

This is an OLD problem that is still VERY annoying in EAP5.

When reviewing the activity history and having scrolled down several pages, along comes "Refresh Connection" and promptly repositions the list at page 1. WHY? I don't want to be on page 1, I want to be on the CURRENT page.

Please, do something to stop this wasting our time and making the product look bad!

1. In the “Activity History” pane, please add a function to filter the results displayed in that pane, by type of backup, failed/success/warning, and date-time range: When you are trying to find a specific DIFF backup and you have to filter through +200 5-minute transaction log jobs to get to your last DIFF, it is very annoying to zero-in on the exact job you are looking for (especially when the list keeps refreshing all of the time and throwing you back up to the top of the list).

When restoring there is a UI bug on the restore step 2 of 4 screen (this existed in previous versions). If you click the ellipses next to the database data files or log files the file browser window opens but annoyingly changes the file name from the database name to name of the first file in the list. I then have to retype the database name and other changes that I want

It would be great if SQL Backup would use the native SQL Server Operators mailing system instead of his own mailing. We have implemented a mailing strategy with the Operators feature but we can't use it with SQL Backup. I have to put my email directly in SQL Backup!

I think it would be good if SQL Backup just use this mailing system instead of is own. That we, we don't have to repeat everything!

On many occasions, when trying to restore a VLDB with hundreds of files, I have ran into size-limits on the restore scripts. This has caused me to have to shorten all of my file paths and file names down to near-unrecognizable names like PTDf01.ndf just to get them all into the script, which makes the database less maintainable and more confusing. Is there some reason why the restore script cannot be several MBs long? Why is it limited to just a few KB?

INTO SHEDULE RESTORE OR BACKUP JOB ABILITY TOO ADD OTHER STEP.

If I run a full backup every sunday night and diff backups mon-sat, and on the full I specify to keep the last 2 full backups. When it deletes an old full backup, it should also delete all diff backups associated with that full backup

It would be good if you could add a new server based on a template of another server already added. If I add a new server to a group, it will usually be configured with the same backup properties as the other servers in the group.
I would like the ability to update the common properties of a group, such as backup location, encryption, retention, validation etc without having to update each individual server in turn.

When I execute a RESTORE command using the extended Stored Procedure, I'd like to use the MOVE DATAFILES TO option. But I can't use it when restoring to a NEW database in the SAME folder, because, unlike via the GUI, restoring via the extended SP uses the original filenames from the backup file. And they of course exist. I'd like an option, without having to use MOVE ... TO ... to have similar behaviour as in the GUI: a restore of backupfile X to database Y gives me files automatically renamed to Y.mdf, Y_1.mdf Y_2.mdf etc.

When you have to choose to move the files to a new location the logical file names should automatically be filled in becuase they're available and have to be used.

At the moment it seems that the order of the time-zone tabs is fixed in the order that you create them. I want them in order of timezone.

When i backup severa databases i have the option to Create a subfolder for each database. I'd also like a similar option for the copies. I know that i can edit the script to do this, but it should be automated.

Are there any plans to implement a retention policy on the hosted environment that would “clean up” older versions of the backup files so they don’t continue to take up space?

The only way I could see to clean out old version was to delete them individually. Can you implement a way to select multiple backup files to perform an action on (e.g. delete) so it doesn’t take so long?