Subject | About nbackup |
---|---|
Author | Vander Clock Stephane |
Post date | 2011-12-25T18:57:32Z |
Hello,
on the paper nbackup look wonderfull, but what are behind the wood that
we need to know ?
for exemple i see that during the backup, the database file is locked
and all write are done in a separate delta file ... is this can slow
down the server ? especially when the separate file is merge back with
the database file ? what happen if for exemple we increase the width of
one varchar column during the backup ?
also i not understand the level strategy, in the doc they say we will
rarelly go beyong level 3 or 4 but me what i want to do is to save on a
daily basis ... so for me it's will be 30 levels min (because every
month i will reset)... what wrong in this ?
and to finish how nbackup can know what was changed from the last backup
? does it's mean that every page in the database file have a version
number ?
thanks for all
stéphane
on the paper nbackup look wonderfull, but what are behind the wood that
we need to know ?
for exemple i see that during the backup, the database file is locked
and all write are done in a separate delta file ... is this can slow
down the server ? especially when the separate file is merge back with
the database file ? what happen if for exemple we increase the width of
one varchar column during the backup ?
also i not understand the level strategy, in the doc they say we will
rarelly go beyong level 3 or 4 but me what i want to do is to save on a
daily basis ... so for me it's will be 30 levels min (because every
month i will reset)... what wrong in this ?
and to finish how nbackup can know what was changed from the last backup
? does it's mean that every page in the database file have a version
number ?
thanks for all
stéphane