Geo: you need to get a.

Ludy: Tiny, as Bachinski ***umed. mysqldump as above

Anderton: What commands make one scenario better suited than another?

Cauley: Or rather, scenario make a command better suited

Decoux: Obiano: maybe because of the I_S

Obiano: Decoux on my dumpspeed issue from earlyer? ios? its all-ssd, blazing fast – dumping the actual data afterwards is 16 GB in less than 10 minutes.

Decoux: Obiano: the I_S isn’t IO bound.

Astle: Anyone? reasons to use one method over another?

Obiano: Hm google is bad in telling me what they are other than “related to schema info” what makes sense 😛

Pyette: Geo: you seem to be after an entire tutorial of the pros/cons of every backup mechanism possible. Thanks beyond what I have time for and what others have too I ***ume.

Morillo: Geo: No, we will not spoonfeed you. We’ll give you pointers, man pages, general guidelines, even web pages that you *actually* have to read. But don’t expect use to spoonfeed you. You can allways employ a MySQL Consultant for that.

Novinger: Technically, you did spoonfeed me when you just told me to use mysqldump over anything else

Decoux: It was a hint of sorts.

Mammo: You have something simple and small.

Bushard: I kinda thought you might like someone who is interested in learning more about the why, and not just copy pasting

Decoux: Logical backups are fine for small data sets.

Dicaprio: I think its a bit dramatic to translate a ‘why’ to ‘you want to know everything about everything’

Skahan: Geo: maybe another time. not now however.

Decoux: They are impractical for larger sets.

Obiano: Replicator that acts as hot spare and is used to make consistent so with locking backups — this and only this is “neat”

Obiano: Dumpt your backup, daily dump a “init dump” – to have a point to “start a new slave on him”

Bachinski: Geo: when’s the last time you did alvm shapshot never. used xtrabackup? never set up replication? never mysqldump is a good place to start

Obiano: Then can even be used to change to ROW replication, do schema changes on the slave, and then trannsistion over your app to him, to then make old-master the new slave afterwards 3

Bachinski: Geo: anyway, try it and see

Mclauren: Decoux: is a there a main difference in moving data with one of these other sets? at the end of the day, you still need to move X amount of data, right?

Loson: So how are there speed efficiencies found between the methods?

Decoux: Geo: how long do you think a logical backup will take, if say, you had 10GB of data to export?

Decoux: Geo: what about the import process?

Tur: So it has to do with how mysql reads in the data once its moved?

Culligan: Ingesting it, vs just sticking in a database, I guess?

Decoux: Geo: what does “sticking in a database” mean?

Obiano: Imports are a ***. im running two slaves that “switch each hour” with replication stoped, so “in case” i can go from there and not need 5 hours of import+index building 😀

Seacrist: Decoux: *shrug* moving a binary file over, I guess. I don’t really know, I’m just trying to get an idea of the different concepts involved

Decoux: Geo: what is a logical backup?

Rubarts: Geo: hint 2. its all about the impact to the business operations. how long can you go without writing/reading from a database.

Handren: I’m ***uming its a dump of all the database contents/schema to a text/binary format

Rogstad: All the data in one file

Decoux: Geo: time to read about it, then.

Berenson: So yes, its a dump of all the contents

Swiler: Versus just moving the database file

Bachinski: Geo: there is no “database file”. that’s MS Access

Broyles: Decoux: any other thoughts?

Decoux: Geo: you need to get a better picture first.