| Author |
Topic |
|
10Dawg
Starting Member
46 Posts |
 Posted - 2012-07-02 : 16:12:21
|
| I'm have 151GB of data that needs to be backed up everyday. My plan starts at 1 am and doesn't finish until 3-4 pm. Should 151 GB take that long? Is it possible to split the databases up into several backups going at one time? What other strategies are there for speeding things up?10Dawg |
|
|
10Dawg
Starting Member
46 Posts |
Posted - 2012-07-02 : 16:18:36
|
| Sorry! I'm using the backup in the maintenance plan that comes with SSMS. We are using sql 2008 and backup plan is set to full. (Boss wants point-in-time recovery).10Dawg |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-07-02 : 16:39:59
|
Are you backing up to a local disk? To tape? To a network device?quote:
We are using sql 2008 and backup plan is set to full. (Boss wants point-in-time recovery)
Unless you're also backing up the transaction log, you can't do point-in-time recovery. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2012-07-02 : 23:59:13
|
Make sure you are using backup compression. Also, make sure you have backup verification turned off in the maintenance plan.You might consider doing a "copy only" backup to the NUL device as a test to see how much the slowness is due to slow IO reading the database and how much is due to slow IO on the output backup file. The time to run the "copy only" backup to the NUL device will represent the absolute minimum run-time for the backup without moving the database to faster disk.backup database [MyDatabase] to disk = 'NUL:' with stats = 5 , copy_only CODO ERGO SUM |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
10Dawg
Starting Member
46 Posts |
Posted - 2012-07-11 : 14:44:30
|
| thanks for all the tips.10Dawg |
|
|
|
|
back up taking WAY too long.