One thing I have noticed about SMSQL backups scheduled through Windows scheduled tasks:

When you go through the backup wizard in SMSQL you will specify the databases you currently have that you want to be backed up and it will create a scheduled task for you (either SQL agent or Windows scheduled task).

If you add a new database to the SQL server later it will *not* be included in your existing backup sets.  If you want the backup to always include new databases you will need to modify the scheduled task.

Here is an example of a scheduled task command after running through the backup wizard:

"C:\Program Files\NetApp\SnapManager for SQL Server\SMSQLJobLauncher.exe" new-backup  –svr ‘<Server Name>’  -d  ‘<Server Name>’, ’6′, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’ -RetainBackups  5 -lb -bksif -RetainSnapofSnapInfo 0 -trlog  –mgmt daily

Modify the run command so it looks like this:

"C:\Program Files\NetApp\SnapManager for SQL Server\SMSQLJobLauncher.exe" new-backup  –svr ‘<Server Name>’’  -RetainBackups  5 -lb -bksif -RetainSnapofSnapInfo 0 -trlog  –mgmt daily

Now any new database added will automatically be included the next time that backup job is executed

Popularity: 11% [?]