May 15, 2009 at 7:11 am
i would appreciate if you give some links to help me because this is the first time I work on a large database.
May 15, 2009 at 7:18 am
I don't have specific links, but check out Backup in Books Online or Google "Backing up SQL Server", "Backup VLDB SQL Server", things like that.
The problem is, because everyone's database is different, I can't give you a specific strategy. You need to look at your company's needs, determine the minimum & maximum acceptible downtime for restores, look at the current backup strategy and alter accordingly, if at all.
There are different types of backups, remember. Full, Differential, FileGroup. You're probably looking at a combination of these methods to get what you need. But you need to understand your business needs first before you can determine the proper strategy.
Sorry I can't be more helpful.
May 15, 2009 at 7:40 am
Here are a couple of backup options ...
- LiteSpeed
- Striping - http://www.sqlservercentral.com/Forums/Topic704434-357-1.aspx
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
May 15, 2009 at 7:58 am
rudy komacsar (5/15/2009)
- LiteSpeed
- Striping - http://www.sqlservercentral.com/Forums/Topic704434-357-1.aspx%5B/quote%5D
Not quite what I'm talking about, Rudy. @=)
Though the striping could be used as part of the overall strategy, LiteSpeed is just a tool. It doesn't fix a bad backup strategy.
When I talk strategy, I mean: how often, what types of backups, what days will it run, what time of day(s) will it run. How speed of restoration and speed of backing up affect downtime and uptime and maintenance windows. Striping would fit more in the "where the backups go" category along with the speed of backups, but it doesn't resolve the other questions.
If, for instance, you're doing a FULL backup every night with transaction logs during the day, that's one strategy. But once you get into VLDB territory, especially if you're splitting partitions between instances and drives, the once a day FULL backup becomes cumbersome. The backup process will take forever, but restore would be decently quick. Maybe not as quick as a FILEGROUP restore, though. This is the point where you might want to look into once a week FULL backups with either DIFFERENTIAL or FILEGROUP backups during the week.
Again, though, a good backup strategy entirely dependant on the business needs. One that doesn't take those needs into account is a poor strategy that will bite the DBA in the posterior in a crisis.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply