<commit_before>=======
CHANGES
=======

LP# refers to holland launchpad bugs here: 
http://bugs.launchpad.net/holland-backup

GH# referes to the deprecated github bug tracker here:
https://github.com/holland-backup/holland/issues

1.0.7 - unreleased
------------------

holland
+++++++
- Fixed bug in purge-policy=before-backup that would fail to retain the
  in-progress backup and ultimately cause the backup run to fail.
- Added pre/post/failure backup command options to [holland:backup] for 
  each backupset. Contributed by osheroff
- holland purge now truncates files in increments of 256MB before running
  unlink(2) to minimize the impact of removing a very large file.
- Fixed a bug in holland.conf [logging] handling where the log-level would be
  ignored in favor of the default value for holland --log-level.

holland-mysqldump
+++++++++++++++++
- Fix bug with holland backup --dry-run and mysqldump plugin's stop-slave=yes
  option.  The slave would be incorrectly stopped in dry-run mode, but never
  restarted.
- Fixed a bug with estimate-method=const where lock-method=auto-detect would
  not properly detect when to set single-transaction because table engine
  information was not read.
- Plugin estimate method now ignores MRG_MyISAM and Federated tables when
  estimating the total backup space in order to avoid counting tables twice.
- Fixed a bug in my.cnf parsing code that did not treat my.cnf sections case
  insenstiviely.  This differed from the mysqldump behavior

holland-mysqllvm
++++++++++++++++
- Fixed a bug in the relpath implementation where paths relative to / were not
  properly calculated.  This was a bug in os.path.relpath in python <= 2.6:
  http://bugs.python.org/issue5117.  Backported the fix from python 2.7
- Fix a bug in tar archiver that was not closing the output stream at the end
  of a backup.
- Added pre- and post-args to [tar] config to allow customizing options to GNU
  tar used for archiving mysql-lvm backups.
- LVM plugins now detect when they cannot correctly backup innodb data.
  mysql-lvm will abort by default if any innodb data files reside outside the
  datadir. mysqldump-lvm will rewrite innodb-data-file-path,
  innodb-data-home-dir and innodb-log-group-home-dir in order to startup the
  bootstrap mysqld process correctly.
- added force-innodb-backup option to force a mysql-lvm backup even if it
  appears unsafe to do so.  InnoDB datafiles outside of the datadir are not
  backed up by default unless tar's pre- and/or post-args are set correctly.

holland-xtrabackup
++++++++++++++++++
- The xtrabackup plugin now fails more cleanly when the innbackupex command
  could not be found
- The xtrabackup plugin now handles failures in closing the output stream more
  gracefully.
- Updated xtrabackup plugin to support xtrabackup 2.0
- Added stream=xbstream support
- Added support for streaming=no to perform a simply directory copy backup
- Added tmpdir option - previously tmpdir was taken from the my.cnf
  defaults-file
- Added an additional-options = option, option, option for specifying
  arbitrary options to innobackupex
- Added ibbackup=path option
- Added pre-command=command option
- Added safe-slave-backup=boolean option


1.0.6 - Jan 12, 2011 
--------------------

holland
+++++++
- holland backup better differentiates between a dry-run and normal backup
  in logging output
- holland mk-config now produces cleaner output and includes a --minimal
  option to strip comments from the backupset output.
- holland now more elegantly handles running the same backupset more than
  once per second.  Previously this could result in a stack trace as the
  backupset directory already exists.
- holland now maintains newest and oldest symlinks in each backupset
  directory pointing to the newest and oldest backup.
  (Contribution from <NAME>)
- holland.conf now accepts a tmpdir option for environments where
  manipulating TEMPDIR environment variable is not convenient
- holland backup --help is now consistent with holland help backup
  (Fixes LP#677716)
- holland now warns about unknown options in config files
- The example plugin has been deprecated in favor of the holland-random
  plugin, which provides a more useful starting example
- previously when logging failed (disk space, permissions, etc.) a stack
  trace would be printed on stderr.  As of 1.0.6 this is only done in when
  the logging level is set to 'debug'
- holland backup --dry-run previously failed for mysqldump backups when 
  per-table exclusions were specified. (Fixes GH#60)
- config files are now read as utf8 (Fixes GH#57)
<commit_msg>note the xtrabackup apply-logs option in CHANGES.txt<commit_after>=======
CHANGES
=======

LP# refers to holland launchpad bugs here: 
http://bugs.launchpad.net/holland-backup

GH# referes to the deprecated github bug tracker here:
https://github.com/holland-backup/holland/issues

1.0.7 - unreleased
------------------

holland
+++++++
- Fixed bug in purge-policy=before-backup that would fail to retain the
  in-progress backup and ultimately cause the backup run to fail.
- Added pre/post/failure backup command options to [holland:backup] for 
  each backupset. Contributed by osheroff
- holland purge now truncates files in increments of 256MB before running
  unlink(2) to minimize the impact of removing a very large file.
- Fixed a bug in holland.conf [logging] handling where the log-level would be
  ignored in favor of the default value for holland --log-level.

holland-mysqldump
+++++++++++++++++
- Fix bug with holland backup --dry-run and mysqldump plugin's stop-slave=yes
  option.  The slave would be incorrectly stopped in dry-run mode, but never
  restarted.
- Fixed a bug with estimate-method=const where lock-method=auto-detect would
  not properly detect when to set single-transaction because table engine
  information was not read.
- Plugin estimate method now ignores MRG_MyISAM and Federated tables when
  estimating the total backup space in order to avoid counting tables twice.
- Fixed a bug in my.cnf parsing code that did not treat my.cnf sections case
  insenstiviely.  This differed from the mysqldump behavior

holland-mysqllvm
++++++++++++++++
- Fixed a bug in the relpath implementation where paths relative to / were not
  properly calculated.  This was a bug in os.path.relpath in python <= 2.6:
  http://bugs.python.org/issue5117.  Backported the fix from python 2.7
- Fix a bug in tar archiver that was not closing the output stream at the end
  of a backup.
- Added pre- and post-args to [tar] config to allow customizing options to GNU
  tar used for archiving mysql-lvm backups.
- LVM plugins now detect when they cannot correctly backup innodb data.
  mysql-lvm will abort by default if any innodb data files reside outside the
  datadir. mysqldump-lvm will rewrite innodb-data-file-path,
  innodb-data-home-dir and innodb-log-group-home-dir in order to startup the
  bootstrap mysqld process correctly.
- added force-innodb-backup option to force a mysql-lvm backup even if it
  appears unsafe to do so.  InnoDB datafiles outside of the datadir are not
  backed up by default unless tar's pre- and/or post-args are set correctly.

holland-xtrabackup
++++++++++++++++++
- The xtrabackup plugin now fails more cleanly when the innbackupex command
  could not be found
- The xtrabackup plugin now handles failures in closing the output stream more
  gracefully.
- Updated xtrabackup plugin to support xtrabackup 2.0
- Added stream=xbstream support
- Added support for streaming=no to perform a simply directory copy backup
- Added tmpdir option - previously tmpdir was taken from the my.cnf
  defaults-file
- Added an additional-options = option, option, option for specifying
  arbitrary options to innobackupex
- Added ibbackup=path option
- Added pre-command=command option
- Added safe-slave-backup=boolean option
- Added apply-logs=boolean option


1.0.6 - Jan 12, 2011 
--------------------

holland
+++++++
- holland backup better differentiates between a dry-run and normal backup
  in logging output
- holland mk-config now produces cleaner output and includes a --minimal
  option to strip comments from the backupset output.
- holland now more elegantly handles running the same backupset more than
  once per second.  Previously this could result in a stack trace as the
  backupset directory already exists.
- holland now maintains newest and oldest symlinks in each backupset
  directory pointing to the newest and oldest backup.
  (Contribution from <NAME>)
- holland.conf now accepts a tmpdir option for environments where
  manipulating TEMPDIR environment variable is not convenient
- holland backup --help is now consistent with holland help backup
  (Fixes LP#677716)
- holland now warns about unknown options in config files
- The example plugin has been deprecated in favor of the holland-random
  plugin, which provides a more useful starting example
- previously when logging failed (disk space, permissions, etc.) a stack
  trace would be printed on stderr.  As of 1.0.6 this is only done in when
  the logging level is set to 'debug'
- holland backup --dry-run previously failed for mysqldump backups when 
  per-table exclusions were specified. (Fixes GH#60)
- config files are now read as utf8 (Fixes GH#57)

{'fraction_non_alphanumeric': 0.07205169628432956, 'fraction_numerical': 0.008616047388260635, 'mean_word_length': 3.8490861618798955, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2516466', 'n_tokens_mistral': 2701, 'n_tokens_neox': 2483, 'n_words': 1241}