Re: [Bacula-users] correct strategy for mysql innodb and myisam backup

2017-01-12 Thread Josip Deanovic
On Thursday 2017-01-12 17:21:05 Alan Brown wrote: > On 12/01/17 14:14, Josip Deanovic wrote: > > So if one is for some reason locked to specific old version of a > > specific old proprietary application one can't do much than continue > > with the MyISAM as innodb is not an option and external sear

Re: [Bacula-users] correct strategy for mysql innodb and myisam backup

2017-01-12 Thread Alan Brown
On 12/01/17 14:14, Josip Deanovic wrote: > So if one is for some reason locked to specific old version of a > specific old proprietary application one can't do much than continue > with the MyISAM as innodb is not an option and external search engines > are not supported either. I've had to deal w

[Bacula-users] Variable in Fileset Exclude-list

2017-01-12 Thread Daniel Heitepriem
Hi everybody, is it possible to use variables or similar in exclude list of filesets? Imagine we have this job declaration: Job { Name = "tester.logs" Storage = WEST JobDefs = "DefaultJob" Schedule = "Early" Write Bootstrap = "/etc/bacula/bsr/test.bsr" Client = client1 FileS

Re: [Bacula-users] correct strategy for mysql innodb and myisam backup

2017-01-12 Thread Josip Deanovic
On Thursday 2017-01-12 08:36:53 Phil Stracchino wrote: > Most applications that "require" MyISAM "require" it for no good reason, > or depend on features that have historically been supported only by > MyISAM but are now supported in InnoDB in current MySQL releases. It > bears case-by-case examin

Re: [Bacula-users] correct strategy for mysql innodb and myisam backup

2017-01-12 Thread Phil Stracchino
On 01/12/17 00:22, Josip Deanovic wrote: > On Wednesday 2017-01-11 17:43:42 Phil Stracchino wrote: > [...] >> The truth is, MyISAM pretty much sucks and you shouldn't be using it in >> production any more. Remember that MyISAM is a 20-year-old storage >> engine, one of whose primary design criteri

Re: [Bacula-users] How to fix Bacula after tape autoloader dysfunction?

2017-01-12 Thread Charles
On 11/01/17 15:01, Alan Brown wrote: > On 11/01/17 05:16, Charles wrote: >> >> According to both the man pages and experimentation, Debian Jessie's >> mt and mtx do not support an unlock command. > > Whilst other debian versions do > > # mt --version > mt-st v. 1.3 > default tape device: '/dev/tape