SQL Server Backups (Network)

Our e-business group will be running SQL Server as a backend and C#, ASP.NET, VB.NET application on the front end. Besides my enternal backups of user data on the database. What would you suggest for the Network team to backup and how offen. This is for productions. I usally get a full drive dump on the Dev network daily appended,and weekly archived. Any suggestion for production.

If you are asking this question you really need to have a SQL Administrator assist you in determing your strategy. This is your production server and usually your company would be brought to a stop if this server crashed. You have to determine if the company can afford to loose data and for what length of time. Some serious decisions need to be made and a backup plan and recovery plan need to be put in place.
No one can determine your risk and to what extent!

If you don't have a SQL Server admin it's good to know a few things. Backing up databases only backs up THAT database so anything NOT under the tree of the database is not going to be included in your backup and you will not be able to restore. For instance, DTS packages. You should back up the database "MSDB". You can also back up DTS packages to files as a Structured Storage File and let the network backups copy them.


Also, if you do not clear the transaction log on backup you will eventually drastically slow down the performance of SQL Server.

Suggest you google "SQL Server" + "backup" and read a few articles.

Thanks for your advice.