holland-discuss team mailing list archive

[Andrew Garner <muzazzi@xxxxxxxxx>]

Holland 1.0.8 has been tagged in github and the packages pushed to
build.opensuse.org.   As before, these can be installed via the repos here:

http://download.opensuse.org/repositories/home:/holland-backup/

The changelog can be found here:

https://github.com/holland-backup/holland/blob/v1.0.8/CHANGES.txt

~Andy


On Fri, Jan 18, 2013 at 11:13 AM, Tim Soderstrom
<tim@xxxxxxxxxxxxxxxxxxxxx>wrote:

> That was my thought but wanted to make sure. Looking good so far with my
> distribution. I'm about ready to migrate at least one cloud server over to
> the OpenStack (CloudServers 2.0 or whatever it's called now) so I can check
> to see how Holland works on a fresh install, though I doubt it'll be an
> issue. Even so, I'll test that here soon. Our Rackspace managed servers are
> still Red-Hat, but I can try these on our development DBs (which are using
> LVM) so long as MBU won't complain loudly.
>
> On Jan 18, 2013, at 11:07 AM, Andrew Garner wrote:
>
> dpkg should only prompt if both (1) the config file had been edited by you
> between releases and (2) the version shipped has changed between releases.
>   Otherwise, dpkg silently leaves the user's changes in place (if user
> modifications have been made) or silently updates the config file (if the
> user has not made changes, and the new package config file differs).
>
> The default holland.conf has not changed since 1.0.6.
>  providers/mysqldump.conf had some minor changes - I think just a comment
> was updated indicating the additional option of 'pbzip2' for the
> compression method.
>
> ~Andy
>
>
> On Fri, Jan 18, 2013 at 8:46 AM, Tim Soderstrom <tim@xxxxxxxxxxxxxxxxxxxxx
> > wrote:
>
>> So far so good! I had to remember how to update the Apt key database but
>> other than that the upgrade from 1.0.6 to 1.0.8 went smoothly and I'm not
>> running into any issues. I don't have LVM setup on any of the Ubuntu boxes
>> I use so I am not easily able to test that at this very moment. Also, I
>> noticed that the install process did not ask me to replace
>> /etc/holland/holland.conf which I found odd. I did ask me about replacing
>> /etc/holland/providers/mysqldump.conf. My /etc/holland/holland.conf is the
>> same version I had before. Not sure if this was by design or a potential
>> issue so thought I would mention it.
>>
>> Other than that, I report no issues on my 12.04 box I've tested on thus
>> far.
>>
>> On Jan 16, 2013, at 1:54 PM, Andrew Garner wrote:
>>
>> Holland 1.0.8 is pretty much ready to go.  I have built packages in OBS
>> for RHEL/CentOS and Debian/Ubuntu here:
>>
>> http://download.opensuse.org/repositories/home:/holland-backup:/staging/
>>
>> And of course you can build packages or instal from the github repo, as
>> desired.
>>
>> I will be tagging the official release later this week and once the
>> packages are tested more thoroughly they'll go to the main OBS repos.
>>
>> v1.0.8 is mostly a bunch of bug fixes that are long overdue.  The list of
>> changes can be found here:
>>
>> https://github.com/holland-backup/holland/blob/master/CHANGES.txt
>>
>> The main new features are:
>>
>> * before/after/failed-backup commands that can run various actions
>> before/after or when a backup fails
>>
>> see: http://docs.hollandbackup.org/config.html
>>
>> * The mysqldump plugin now has an option to auto-exclude invalid views,
>> that would otherwise cause a mysqldump run to fail.  The definition of
>> invaild views are extracted (when possible) and saved to an
>> 'invalid_views.sql' file in the backup directory.
>>
>> * The MySQL LVM based plugins verify the database configuration can be
>> consistently backed via an LVM snapshot.  This avoids cases where innodb
>> data or log files files are on separate volumes from the datadir and we
>> cannot guarantee a consistent backup.  'force-innodb-backup' can be enabled
>> to ignore this check.
>>
>> see: http://docs.hollandbackup.org/provider_configs/mysql-lvm.html
>>
>> * The MySQL LVM plugins also abort when backups are being saved on the
>> snapshot-origin, which is a common cause of backup failures or serious
>> performance degradation.  There is a new option
>> force-backup-to-snapshot-origin to ignore this check.
>>
>> see: http://docs.hollandbackup.org/provider_configs/mysql-lvm.html
>>
>> * The xtrabackup plugin has been updated to support percona-xtrabackup
>> 2.0 and non-streaming backups w/ --apply-logs at the end are supported now.
>>
>>
>> see: http://docs.hollandbackup.org/provider_configs/xtrabackup.html
>>
>> ~Andy
>>  _______________________________________________
>> Mailing list: https://launchpad.net/~holland-discuss
>> Post to     : holland-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~holland-discuss
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>
>