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 |
|
sumwanlah
Starting Member
43 Posts |
 Posted - 2003-02-10 : 05:53:44
|
| To wat extent do long-running backups cover?I've got a VLDB of about 1TB, database recovery mode is 'Simple' at the moment. The full database backup take about 30hours to run; thankfully it's only done once a week!!! Now, at the same time, I've scheduled data import operations to run twice a day, and these usually take about 3hours average to complete, although 6-hour operations are not rare.The big question is:If the full backup kicks start in the middle of a data import, will the backup still run? During that 30-hour backup run, two other data-import windows will have run too. Will the backup contain all data that has been imported during the three data-import windows, WHILE backup still happens?Am I right to simplify this big question by asking: "will long-running VLDB full-backups take a backup of the database state at the time the backup starts, or will the backup contain everything that goes into the database during its entire 30-hour run, by which time the database would have been updated thrice?"Remember: Recovery mode is 'Simple' and yes, I am moving towards using filegroup backups to lessen my pain... Heh!------------------------What goes around...? Is the belt around my waist! |
|
|
JamesH
Posting Yak Master
149 Posts |
Posted - 2003-02-10 : 13:06:51
|
| a full backup will provide you with the database plus enough of the transaction log to do a complete restore whereas you can either add additional trans logs after the restore or set it to Recovery mode which will cause all un-committed transactions within the full backup to roll back and will not allow you to apply any additional transaction logs (BTW, this is default if you don't specify). Your jobs will be in the transaction log portion and applied after the database has restored (Although you won't see any of this) as this is SQL Servers way of knowing which changes should be applied to the database. Hope this helps.JamesH. |
 |
|
|
|
|
|
|
|
Long-Running VLDB Backups