backup strategies for hosted enviroment ?

Im about to start a project that will be hosted by a third party web host. What is a common way to backup your database and have the backup saved ? The data may end up being several 100 MB of user settings, text etc (blog type stuff). If the DB gets to be several 100MB, then does making a backup and ftping it offsite sound reasonable ? Does ftp bandwidth usually count against your overall bandwidth usage ?

For FTP bandwidth going against your sites bandwidth... Ask your hoster - they'll tell you for sure.

For backing up, most hosts back everything up for you automatically (most of them do it daily).

What I've done in the past is every week or so I just take my DB offfline and copy it down to my computer using FTP. I then burn it. (not with fire)...

|||

Agree.

Make a backup and then ftp it to another place is the comman way. As to "make a back up every day or every week" , i would suggest you using sql server jobs. You can create a job and then schedule it run automatically every a certain time interval. You can refer to the following article to see how to create a backup job and make it run regularly:

To schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005, follow these steps:

1.Start SQL Server Management Studio.2.In theConnect to Server dialog box, click the appropriate values in theServer type list, in theServer name list, and in theAuthentication list.3.ClickConnect.4.In Object Explorer, expandDatabases.5.Right-click the database that you want to back up, clickTasks, and then clickBack Up.6.In theBack Up Database - DatabaseName dialog box, type the name of the backup set in theName box, and then clickAdd underDestination.7.In theSelect Backup Destination dialog box, type a path and a file name in theDestinations on disk box, and then clickOK.8.In theScript list, clickScript Action to Job.9.In theNew Job dialog box, clickSteps underSelect a page, and then clickEdit if you want to change the job parameters.

Note In theJob Step Properties - 1 dialog box, you can see the backup command.10.UnderSelect a page, clickSchedules, and then clickNew.11.In theNew Job Schedule dialog box, type the job name in theName box, specify the job schedule, and then clickOK.

Note If you want to configure alerts or notifications, you can clickAlerts orNotifications underSelect a page.12.ClickOK two times.

You receive the following message:

The backup of database 'DatabaseName' completed successfully.

Hope my suggestion helps

backup planning

following the installation of Ms SQL server 2000, the backup planning is not saved. Have hou got an idea?If your backups are scheduled as SQLServer Agent Jobs, they can be scripted out and then run against your new database.
I don't think you can script the maintenance plans, but a little-known fact is that they aren't anything more than glorified Wizards that create the SQLServer Agent Jobs. After this, they serve only to define what databases the job should apply to.
See Books Online for the xp_sqlmaint procedure for more details. This is the procedure that the jobs use, and you can use it yourself without going through the maintenance plan wizard.

blindman|||Thank you,
I'm going to search with this