On 5/14/2014 3:11 PM, Michael Gettes wrote:
The db2bak strategy worries me cuz you’re backing up the db files and
the time it takes to back those up
on a reasonable sized ldap store is non-trivial. So, is there not a bit of worry about
indices being out of
sync with the entry store itself along with the log files managing the changes? one
would have to filesystem
snapshot the DB itself to get a sane backup of a production service, yes?
This
doesn't happen. The backup contains a consistent snapshot (achieved
by running recovery on the write-ahead log, which is in the backup set).
This is much the same as you'll see with backup on a traditional DB like
Oracle or Postgresql.
Filesystem snapshot is generally not a good idea with WAL databases
since the database already has the ability to create consistent backups
without the overhead of logging at the filesystem level.