Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kid_on_the_block
Posting Yak Master
172 Posts |
 Posted - 2006-02-08 : 22:45:24
|
| Just Read this :- A complete database backup is very simple to execute and use in recovery. If your data doesn't change often, you might simply schedule a nightly full backup of your database. Even if you need more frequent backups, regularly scheduling a full database backup each hour might be sufficient (if your database is small enough).Now what does a small database mean , can someone please let me the size in (GB) that a DB is considered to be small (even a range would do ) & How much time does the backup take , or should taken on a dual processor server. I mean need to get a rough idea Thanks... |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-02-08 : 22:52:31
|
| Small is relative, depends on how much disk you have.Not knowing your system hardware or load, the best way to determine how long a backup will take is for you to run one and see how long it takes.CODO ERGO SUM |
 |
|
|
kid_on_the_block
Posting Yak Master
172 Posts |
Posted - 2006-02-08 : 22:57:23
|
| Disk is round about 250 GB & the DB size that i just looked at with the sp_helpdb DBname gave me 7 GB , when i went to all task & backup database the process got over in 2 minutes , is that the right way to backup , cause i read some where that on a Raid 5 , the backup speed it 10GB/hr .Please help |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-02-08 : 23:02:17
|
| I would consider 10 GB/hour very slow.You backup speed was around 200 GB/hour, and that sounds more normal.CODO ERGO SUM |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2006-02-08 : 23:57:31
|
| SOme of the stuff that you read online was written in the early to mid 90's and many things have changed since then. 10GB/hour is very slow, 180GB+/hour is what you should be seeing (as MVJ stated) with somewhat current hardware. Keep this in mind whenever reading articles online.I would consider a small database something that you can backup in less than 5 minutes. The size is going to vary depending on what hardware you use and how it is configured. Typically this is a database that would be less than 10GB in size. I would consider a database that is 10 - 50 GB in size to be a medium sized database, 50 - 500 is a large database and 500GB+ is a VLDB. Again, these sizes are rough estimates and are based upon the hardware that I use, YMMV. Your backup speed is going to depend on a how fast your disk is that your database resides on and where you send the backup. If you send your backup to another locally attached disk you are going to get very good backup times, if you send your backup across the LAN to tape or a NAS or other fileshare your backup speeds are going to suffer.-ec |
|
|
|
kid_on_the_block
Posting Yak Master
172 Posts |
Posted - 2006-02-09 : 01:20:58
|
| Thanks a ton. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-02-09 : 03:53:11
|
| "Even if you need more frequent backups, regularly scheduling a full database backup each hour might be sufficient"I definitely wouldn't do that - even if my database was "small enough" - utterly pointless, and still only gets you recovery position of "hourly" - whereas if you did a full backup less frequently (daily is about right) and then transaction backups frequently (somewhere between hourly and even ten minutes) then you can recovery to any point-in-time [for which you have full backup plus all subsequent intervening transaction backups]Kristen |
|
|
|
|
|
|
|
|
Backups