The size of the database is one consideration, but probably more important
is how much data loss and downtime you can afford in the event of a problem.
You really need to get this information first, so you can decide how often
to do full/differential/log backups. This will also help you to decide how
much money you can reasonably allocate to your backup/availability solution.
There is a lot of information in BOL in the section called "Desiging a
Backup and Restore Strategy".
If you have the database on a NAS or SAN already, you may be able to use
features of the hardware (some storage devices support MSSQL snapshot
backup/restore). On the other hand, backing up to multiple disk devices
might be a good choice, depending on your requirements and storage
configuration.
Finally, don't forget that as a rule, backing up is easier than restoring.
So also consider how easily your solution will allow you to restore a
database if you need to. It's hard to be specific, as a lot depends on your
environment and your application/user requirements.
Simon
"peter wang" <an*******@devdex.com> wrote in message
news:3e*********************@news.frii.net...
Hi,
Could anyone tell me the backup strategy for a 1000GB database?
Thank you!
Peter Wang
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
