Subject | Does GBak use Forced Writes when restoring? |
---|---|
Author | Steve Summers |
Post date | 2007-10-26T15:13:26Z |
I've looked all over for the answer to this, but can't find it.
There's obviously no parameter to control it, and logically, there
would be no reason to worry about corruption in a database you're
RESTORING anyway. (if the power fails or something goes wrong, you
have to start over whether it's doing synchronous or asynchronous
writing, so why not do the writes as fast as possible?) So it would
make sense that it is already doing this, but I'd like to know for
sure. If it's NOT, it might also be possible to control it - perhaps
by setting the DB to forced=off before backing it up.
Anyone know the answer to this, or do I need to spend some time
experimenting?
There's obviously no parameter to control it, and logically, there
would be no reason to worry about corruption in a database you're
RESTORING anyway. (if the power fails or something goes wrong, you
have to start over whether it's doing synchronous or asynchronous
writing, so why not do the writes as fast as possible?) So it would
make sense that it is already doing this, but I'd like to know for
sure. If it's NOT, it might also be possible to control it - perhaps
by setting the DB to forced=off before backing it up.
Anyone know the answer to this, or do I need to spend some time
experimenting?