WampServer

What is the best way to backup (with an automatic backup schedule) and the best way to restore a WAMP MySQL database(es)???

Other related questions:

1) What types of backups are available? Full, Differential, Incremental, etc?

2) Are there any free, or native solutions?

3) What would be the proper way to restore a db? (I'm coming from a MS SQL environment)

If anyone can offer some information, it would be greatly appreciated.

Thanks!

to setup backup, follow this
[blog.jlbn.net]

Have fun,

FREE One A Day
FREE Photo
FREE Games
FREE Websites
FREE Portable GPS
FREE WAMP Guides

No offence, but that solution isn't a good one for several reasons:

1) That article says you have to switch to myISAM - I can't use myISAM - I'm using InnoDB because I need relationships...

2) It doesn't explain why you need to switch the DB's to myISAM - why can't I just back the files up, regardless of the storage type?

3) It doesn't give any help for users who use InnoDB storage engines...

I'm wondering if it's just a matter of backing up the data folder, why not just do regular tape backups of it? What does the storage engine matter? Perhaps it has something to do with the restore?

I need more info...hopefully someone out there knows more about this.

Thanks

innodb databases are all stored into log files allowing relationships..

but you cannot just copy these files and paste them around.. they will get currupted..

what you need is a automated exporter... that exports the database in sql format.

since windows doesnt suport cron , ul need to used a task scheduler to run the database dump


mysql comes with mysqldump which can dump all the databases , used with the scheduler this will be a fine backup system

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

Quote

why can't I just back the files up, regardless of the storage type?

if you want proper technical terms, head over mysql website, in here I'd like to provide simple thoughts so everybody that reads this thread can easily follow
while myisam is table locking, innodb is row locking and when copy and paste db, mysql will auto create table descriptors thus myisam still work while you only see the tables of inno but no data, in other words, no row

Quote

It doesn't explain why you need to switch the DB's to myISAM

1. myisam works much faster than inno if mostly use insert queries which are the most usages on most websites on the internet
2. much easier to maintain, backup and restore

Have fun,

FREE One A Day
FREE Photo
FREE Games
FREE Websites
FREE Portable GPS
FREE WAMP Guides

Cool - I got the backups working with mysqldump...

Is there any reason to backup the default databases, "information_schema" and "mysql" ???

Not sure what these DB's are used for....?

these contain the settings of mysql.. and are not really nessecary to backup.

"mysqldump does not dump the INFORMATION_SCHEMA database by default. As of MySQL 5.1.38, mysqldump dumps INFORMATION_SCHEMA if you name it explicitly on the command line, although currently you must also use the --skip-lock-tables option. Before 5.1.38, mysqldump silently ignores INFORMATION_SCHEMA even if you name it explicitly on the command line. "


even when using the swtich --all-databases


The mysql database will be dumped tho unless you add and ignore switch


all the details can be found on >>[dev.mysql.com]

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]