SQL 2000 Backup strategy.

Recently somone asked about a MySql backup strategy, and was told that "this is a MS shop". OK, so now I'll ask about a SQL backup stategy. I'm hoping for great things

My site will soon start collecting mission critical information and I'm looking for a backup/recovery strategy that I can use to supplement the DASP "once per day" database backup.

I'm making the assumption that a glitch may corrupt the SQL database, so I want to perform some periodic Database Data duplication. I wanted something that I could manage and initiate the recovery process.

I had planned to create some additional databases which I would update periodically, and use them as backups. BUT I just found out (to my surprise) that DASP only supports one SQL database per user (website). This has put a serious crimp in my plans.

"Support" suggested I implement some off-line storage, but I trust the net infrastructure and my own PC even less. Plus I don't want to be doing multi megabyte uploads as the recovery process.

So... what do others do about protecting against data corruptions? Am I the only one concerned about losing a day's worth of data ???

Phil.

 

If you will be using sql statements such as insert, update and delete to make data changes and additions, you could log all of the statements to a file per day.

This would allow you to have your database restored to the last backup which I assume is nightly, and then you could fix the statements that have the bad data and then execute each statement in the order needed. Although there are a lot of details to work out, it is a solution.


quote:Originally posted by OurCoolHouse

Recently somone asked about a MySql backup strategy, and was told that "this is a MS shop". OK, so now I'll ask about a SQL backup stategy. I'm hoping for great things

My site will soon start collecting mission critical information and I'm looking for a backup/recovery strategy that I can use to supplement the DASP "once per day" database backup.

I'm making the assumption that a glitch may corrupt the SQL database, so I want to perform some periodic Database Data duplication. I wanted something that I could manage and initiate the recovery process.

I had planned to create some additional databases which I would update periodically, and use them as backups. BUT I just found out (to my surprise) that DASP only supports one SQL database per user (website). This has put a serious crimp in my plans.

"Support" suggested I implement some off-line storage, but I trust the net infrastructure and my own PC even less. Plus I don't want to be doing multi megabyte uploads as the recovery process.

So... what do others do about protecting against data corruptions? Am I the only one concerned about losing a day's worth of data ???

Phil.



</blockquote id="quote"></font id="quote">

Eric Brasher