| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Comments:
<0> can anyone tell me how to tell what type of tables im using, so i can figure out if i should use hotcopy or mysqldump?
<1> You should use mysqldump regardless.
<1> SHOW TABLE STATUS;
<2> hmm decisions decisions i hate them
<0> why is mysqldump better to use than hotcopy?
<1> Let me make them for you.
<2> single query containing subquery or two queries with the result of the first one stored in a user variable
<1> WinterSilenc3, Portable.
<3> **** this is confusing
<1> plasmoduck, Read the docs. It tells you what to do...
<0> will[werk], so mysqldump is better than mysqlhotcopy because it can work on both types of tables?
<0> what is the difference between the two types of tables anyway?
<1> Because you can do more with it
<1> Check the wiki. Short description of each table type (I think in the FAQ)
<0> really like what? and what is better for reliable backups?
<0> cause i want to do incremental backups safely
<2> as opposed to "unsafe backups" you mean
<1> GhettoJava, RTFM!
<0> when backing up my mysql database should i shutdown the sql database, also if im using something like mysqldump do i really need to copy the physical myisam files?
<1> 1.) Depends on how. That's the safe way to do it. 2.) No
<1> WinterSilenc3, RTFM!
<0> will okay oaky, but obviously you read the manual and you think mysqldump is best for backups, seems like every aritcle i read says mysqldump is thee worse thing to do database backups with
<0> so dont be an ***hole
<0> I mean arent you in this channel to help others, calm down.
<1> lol
<1> Don't take things so seriouslly...
<1> * GhettoJava has quit ("RTFM in IRC means "I have no clue either, bud"")
<0> sorry that I like hearing real experienced people then reading some badly put together manually with spelling errors out the ***.
<1> <1> GhettoJava, RTFM!
<1> <1> WinterSilenc3, RTFM!
<1> What badly put together manual? What article(s) are you reading?
<0> =)
<4> manual?
<1> I must figure out why I keep spelling it "seriouslly"...
<1> manuel!
<5> there's a manual? wow...
<0> articles I found on google and digg, people say mysqldump is best for debugging and migration but it does db backups SLOWLY
<4> !rtfm mysqldump
<6> (The mysqldump Database Backup Program) : http://dev.mysql.com/doc/mysql/en/mysqldump.html
<1> I didn't say mysqldump was fast...
<0> no you said it was best for database backups.
<0> if backups take hours like 24 hours its not going to be good in a production environment :)
<1> Yes. Because you can open it up in a text editor and read it. Because you can migrate that to other DBs. etc.
<0> espcially if need backups everyday
<1> It does not take me 24 hours to run a mysqldump.
<0> depends on the size of the databases, right...
<0> so it could take 24 hours.
<1> Ofcourse
<1> So could hotcopying
<0> can i go rtfw
<0> :)
<4> WinterSilenc3: if you really care, spend $$ on a system that can do snapshots and use that.
<4> only ~ $100k, no biggy
<1> Or use replication? Bin logging?
<1> SAN boxes...
<7> WinterSilenc3: just use replication so you have a secondary server that you can bring down for the backup
<1> mysqldump, imho, gives me the most flexibility to do whatever. Which in a "backup" sense, means a lot.
<7> weekly mysqldump snapshots off the replicated slave with nightly backups of the binary log files. Keeps you pretty safe
<0> inviso, I get what you're saying but a replication server is not a backup, its actually a very bad idea to consider replication a backup.
<1> Why?
<1> Your broad statement is just as wrong as ours.
<0> cause whatever you do to the primary server takes place on the replication
<0> so what if all databases are dropped on the main server, well on the replication server they will be dropped too, so where is your backup then>
<1> But it protects against hardware failure.
<1> Same thing goes on with your nightly snapshots.
<0> well i am looking for a TRUE backup technique not just hardware failure protection
<1> Replication is part of it so you keep availibility on your main server.
<0> will: not really, the filesystem snapshots i do is nothing like mysql replication.
<1> So you can run mysqldumps. So you can easily shutdown the slave server.
<0> will I see what you're saying and am not denying you, but replication is not a backup methodology.
<1> It's part of it.
<0> its just not or it would be called mysql backup instead of mysql replication :)
<4> you replicate; you backup from replication
<4> preferably to a paper copy of the binary data.
<7> WinterSilenc3: it's not a backup.. It's a means to facilitate backup. It also serves as a failover
<1> I don't believe anyone here said repliation was the only thing you do for backup.
<1> Replication also implies binlogs, which is also a critical part of backing up.
<7> stone tablets. Carve it on stone tablets. Then, cover with a thin layer of sugar water to give it that oh so sweet shine
<1> Probably the BEST way for backup...
<0> inviso right and a failover is not a backup....
<0> data is not backed up to a replication server
<0> all data and changes to that data are copied over, making it a very bad idea to call it a backup.
<7> WinterSilenc3: dude. Replicate to a slave. Shut down slave. Backup slave. Start up slave and replication resumes. Rinse, repeat, drown yourself.
<1> You don't listen do you?
<0> inviso, i get what you're saying yes it be better to do my backups on the replication server, my point is that a replication server IS NOT A FREAKING BACKUP
<1> HE DIDN'T SAY THAT.
<8> Hey, is there a way I can see what queries are being p***ed to mysql from another application?
<1> !m La_PaRCa query log
<6> La_PaRCa: (The General Query Log) : http://dev.mysql.com/doc/mysql/en/Query_log.html
<0> will then maybe im lost what is he saying?
<8> will[werk], kthksbye
<1> WinterSilenc3, "<0> inviso, i get what you're saying yes it be better to do my backups on the replication server," That's what he said and you seem to understand that.
<7> WinterSilenc3: Of course it's not. Take it down as often as you like to make snapshot backups. You were complaining about uptime earlier. Replication addresses that for backup purposes. One ridiculous problem at a time please.
<0> i do
<1> WinterSilenc3, So stop saying "my point is that a replication server IS NOT A FREAKING BACKUP"
<0> inviso: I see what you're saying like i told will.
<0> will i only said it once, and you both know that is true.
<1> We didn't say otherwise.
<0> and i didnt say you didnt so what is the problem?
<1> You heh
<0> obviously.
<1> So, now that we've explaind everything, do you have a suitable backup solution?
<0> you both probably know way more than me about sql, i just here to get insight
<1> We... err.. I just pretend.
<0> but i dont want to deal with the regular cocky son of a bitches on IRC who arent interested in helping just flamming anf saying RTFM.
<1> heh
<1> So I guess you didn't like my joke...
<0> no i didn't, and im not too fond of you at the moment.
<1> :(
<1> What must I do to regain your fondness?
<0> Let me lick your penis.
<0> or how about tell me what you use to backup your sql databases, I wanted to hear real life experiences, that is why i came here...
<9> mysqldump
<1> I thought we told you? Heh. I use myqldump at night.
<0> I am paticularly intereted to find out if anyone h ere has created a script or web interface that backs up both mysql and postgresql databases.
<1> I could replicate it to another server, take slave down, and run mysqldump. I could also backup the binary logs.
<0> will: right but i have to second guess you or what kind of irc nub would I be :)
<1> I've done it all, but found out that I don't need that kind of availibilty. Overkill for my situation.
<10> Is there any way to get ENCRYPT() to return an crypt-md5 hash instead of the DES one it does by default. If you give it a crypt-md5 salt it'll compute a crypt-md5 hash.
<0> will and i also want to know why mysqldump is better than myhotcopy, besides the fact that mysqldump can be used on both types of databases
<0> cause if im not using both types why would I care...
<1> WinterSilenc3, Use mysqlhotcopy if you want. You asked for my opinion. I gave you why I wanted to use mysqldump over mysqlhotcopy.
<0> ya but I want to know why.... thats it I just want to know why buddy
<0> :)
<0> Ill love you forever.
<0> and dont say portable again damnit, cause i doubt you or anyone else uses two different type of tables on the same database.
<0> database/server
<11> I do
<4> heh
<4> also, you might want, say, data from memory tables
<0> thanks ;)
<1> Portable, meaning I can open up the file, and import the data into MSSQL or PostgreSQL.
<1> Because mysqlhotcopy gives me no benefit.
<0> ahh okay
<0> thanks
<12> Rather strange character.
<11> your answers should have been to his preconceptions
<1> heh
<1> I like going against preconceptions...
<12> Does anyone in here have any experience with clusters and replication on a large scale?
<1> CONFORM TO ME even though I know nothing.
<1> There's a good book about clusters...
<7> Yes, very strange character
<1> I think the ^ is a strange character...
<12> Anyone ever use linuxvirtualserver with replication to do HA HC systesm?
<4> yes
<1> HC?
<12> high capacity.
Return to
#mysql
or
Go to some related
logs:
#suse
what fonts are installed +gentoo
queue_la
sweex running webserver
#gaim
snd_ctl_open udev
ivazquez public key import
#sed
#ubuntu
#math
|
|