Re: [Bacula-users] Backup MySQL databases
On Tue, 25 Oct 2011 17:46:43 -0400 Phil Stracchino ala...@metrocast.net wrote: On 10/25/11 10:41, Konstantin Khomoutov wrote: MySQLdump is a valid technique, and the simplest working technique. You should not, as a rule, back up the MySQL data directory at filesystem level. It is extremely unlikely to yield a consistent backup. If you're going to attempt this, issue a FLUSH TABLES WITH READ LOCK, snapshot the MySQL directory, release the lock, then mount the snapshot and back up the snapshot. Thanks to InnoDB's write-ahead logs and crash recovery features, this technique is generally safe *IF ALL YOUR DATABASES ARE IN INNODB TABLES*. I'm not that sure regarging your claim: [1] does not indicate FTWRL does not work for MyISAM databases and [2] directly contradicts your claim by stating that certain things FTWRL does it's doing exactly to accomodate MyISAM peculiarities. I'm not for a moment asserting that FLUSH ... doesn't work on MyISAM. It actually works more reliably on MyISAM than on InnoDB. My point is that should you get a glitch - perhaps something wasn't fully flushed to disk before your snapshot - InnoDB has built-in features to recover from the error. MyISAM does not. MyISAM is, in fact, very vulnerable to data corruption from any of a number of causes. Sorry for being picky, but you seem to blame MyISAM for its property which has nothing to do with hot backups (via FTWRL). The only point of FTWRL is to make the database file to be coherent with the internal (in-memory) state of its database, and then that file is backed up simply by open/read+read.../close cycle which only deals with the filesystem and is not at all concerned with the flush really succeeded in bringing the data to the disk's platters. Transaction log is not involved in this technique as it serves a completely orthogonal task. -- Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World#153; now supports Android#153; Apps for the BlackBerryreg; PlayBook#153;. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Cannot append to LTO-4 tape
On 10/27/11 12:31, Martin Simmons wrote:
Does the setting of TWO EOF in the bacula-sd.conf match what is reported by
the drive after you reboot? E.g.
mt -f /dev/sa0.ctl geteotmodel
Yes.
I have:
Device {
Name = LTO-4
Description = LTO-4 for FreeBSD
Media Type = LTO-4
Archive Device = /dev/nsa0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes
RemovableMedia=yes
Offline On Unmount = no
Hardware End of Medium = no
BSF at EOM = yes
Backward Space Record = yes
Backward Space File = yes;
Fast Forward Space File = yes
TWO EOF = yes
Maximum File Size=2GB
}
And:
# mt geteotmodel
/dev/nsa0: the model is 2 filemarks at EOT
bye Thanks
av.
--
Get your Android app more play: Bring it to the BlackBerry PlayBook
in minutes. BlackBerry App World#153; now supports Android#153; Apps
for the BlackBerryreg; PlayBook#153;. Discover just how easy and simple
it is! http://p.sf.net/sfu/android-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Virtual Changer / Marking Volume xxxxx in Error in Catalog
Hi List ! Does someone knows why sometimes Bacula marks Volumes in Error when it can't load a Virtual Tape (a file) because it's already use by another Virtual Device in the Virtual AutoChanger ? I specified Prefer Mounted Volumes = no in the JobDefs - I use disk-changer provided with the last build of Bacula. - I have 1 AutoChanger (VTL-0) with 3 Virtual Devices (VT-0,1,2) - there is available Virtual Tapes in the Scratch Pool Logs: 29-Oct 13:56 cr0deb02-dir JobId 497: Using Device VT-0 29-Oct 13:56 cr0deb02-sd JobId 497: 3307 Issuing autochanger unload slot 6, drive 0 command. 29-Oct 13:59 cr0deb02-sd JobId 497: Warning: Volume F0005 wanted on VT-0 (/tmp/autochanger/drive0) is in use by device VT-1 (/tmp/autochanger/drive1) 29-Oct 13:59 cr0deb02-sd JobId 497: 3301 Issuing autochanger loaded? drive 0 command. 29-Oct 13:59 cr0deb02-sd JobId 497: 3302 Autochanger loaded? drive 0, result: nothing loaded. 29-Oct 13:59 cr0deb02-sd JobId 497: Warning: Volume F0005 not on device VT-0 (/tmp/autochanger/drive0). 29-Oct 13:59 cr0deb02-sd JobId 497: Marking Volume F0005 in Error in Catalog. 29-Oct 13:59 cr0deb02-sd JobId 497: 3301 Issuing autochanger loaded? drive 0 command. 29-Oct 13:59 cr0deb02-sd JobId 497: 3302 Autochanger loaded? drive 0, result: nothing loaded. 29-Oct 13:59 cr0deb02-sd JobId 497: Warning: Volume F0005 not on device VT-0 (/tmp/autochanger/drive0). 29-Oct 13:59 cr0deb02-sd JobId 497: Marking Volume F0005 in Error in Catalog. 29-Oct 13:59 cr0deb02-sd JobId 497: Warning: mount.c:217 Open device VT-0 (/tmp/autochanger/drive0) Volume F0005 failed: ERR=dev.c:549 Could not open: /tmp/autochanger/drive0, ERR=No such file or directory 29-Oct 13:59 cr0deb02-sd JobId 497: 3301 Issuing autochanger loaded? drive 0 command. 29-Oct 13:59 cr0deb02-sd JobId 497: 3302 Autochanger loaded? drive 0, result: nothing loaded. 29-Oct 13:59 cr0deb02-sd JobId 497: 3304 Issuing autochanger load slot 7, drive 0 command. 29-Oct 13:59 cr0deb02-sd JobId 497: 3305 Autochanger load slot 7, drive 0, status is OK. 29-Oct 13:59 cr0deb02-sd JobId 497: Volume F0007 previously written, moving to end of data. 29-Oct 13:59 cr0deb02-sd JobId 497: Ready to append to end of Volume F0007 It tried to load Volume F5 2 times, then it load the Volume F7. Any advices? Best Regards, Sébastien WENSKE smime.p7s Description: S/MIME cryptographic signature -- Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World#153; now supports Android#153; Apps for the BlackBerryreg; PlayBook#153;. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
