Question : SQL 2005 Backup to network location, with multiple fulls and tlogs

All,

I am backing up my DB and t-logs to backup devices that refer to a network location (UNC.) They work well.

Each new daily full backup overwites the previous file.  This leaves me in an bad spot if the SQL server catches fire during the backup process, among other weaknesses.

What I'd prefer to do is backup the DB to a different file every day of the week, repeating.  So every Monday I'd back up to the Monday.bak.  If sever catches fire during this process, I restore Sunday.bak. Since the Monday.bak didn't complete, I should still have the t-logs running since Sunday.bak, right?

I am able to do this with multiple backup jobs pointing to multiple backup devices.  This is much work when expanded to include all of our DB across all our servers.

Is there a canned plan that can accomodate what we want?

Thanks in advance.

Answer : SQL 2005 Backup to network location, with multiple fulls and tlogs

The trick is to let SQL Server generate the filename (unless you really need to use specific names).  It will track which files it needs to delete or not.  

Do you really need to use specific names?