Backing up through MySQL Workbenc - Which dump options are required?

[robax]

Hi everyone

I just have a quick question about creating a db backup.

I have MySQL Workbench 6.2 installed and I know how to go about exporting data. I am exporting to a self-contained SQL file solely for the purpose of being able to restore the website if something terrible goes wrong. I regularly save a copy of the SQL file plus a zip of the file system.

What I want to know is whether I need to select any of these options on the export page:

Dump Structure and Data << I always choose this option
Dump Stored Procedures and Functions << Should I also take this?
Dump Events << prob not?
Dump Triggers << maybe?
Include create Schema << don't know?

I've done some research but it's not clear what is best for the purpose.
Thanks for any advice on this.
Rob

[RodG]

What I want to know is whether I need to select any of these options on the export page:

Dump Structure and Data << I always choose this option

Yes

Dump Stored Procedures and Functions << Should I also take this?
Dump Events << prob not?
Dump Triggers << maybe?

No, No, No.

Include create Schema << don't know?

Unsure. 'Yes' if the exported sql contains 'DROP tables/database'. No if the export contains 'TRUNCATE tables'.

Cheers
RodG

[robax]

Thanks for the info Rod, much appreciated!

Let me know if you need any tips with your Windows setup (was just reading another thread of yours). Mine has been on Windows since 2006 and the latest install to 2012 was dead simple.. did everything one-click via the Windows Platform Installed in IIS Manager.
Rob

[RodG]

Let me know if you need any tips with your Windows setup (was just reading another thread of yours). Mine has been on Windows since 2006 and the latest install to 2012 was dead simple.. did everything one-click via the Windows Platform Installed in IIS Manager.
Rob

I think you've misunderstood my problem. It is the ozpost module that doesn't install correctly on Windows servers, and the problem(s) are related to some of the 'low level' code that the module is trying to do and it is the file/folder path naming conventions that are causing the problem.

lat9 has been kind enough to supply me with *most* of the fixes needed, but there are still a few remaining that don't *appear* to affect functionality (so I've been told), but they do create error logs.
I don't like my code to be creating error logs. :-)

Cheers
RodG