MySQL Hot-Backup on Windows 7 Physical Workstation

[jmccracken112]

Hi,

I'm looking for some scripting help to create a hot-backup using mysqldump.

I have a MySQL database running on a Windows 7 x64 Pro physical computer. I have the Veeam job created and understand I need to run the mysqldump script under: Storage > Advanced Settings > Scripts. I am not a MySQL DBA, so I do not know how the script needs to look. I'm hoping there are others in my shoes that have a pre-made script I could look at. I can't be the only one right?

Couple concerns I have:
-Performance on the MySQL database side. I have a few systems with 20-50GB database sizes. These are 24/7 production systems I need to backup. My concern is this will put a large strain on the system resources during the mysqldump.
-Where the mysqldump is being stored. If the script is being run from the Veeam server, is the dump file being processed/saved on the veeam server? I'd like it to save on the local mysql server first to avoid network lag issues.

Thanks for your help.

[HannesK]

Hello,
and welcome to the forums.

the veeam mysql whitepaper should help you

Best regards,
Hannes

[jmccracken112]

Hi HannesK,

I've read through that whitepaper, but is for Linux VM -- this does not help me on a physical Windows agent. (The theory part, yes, but the scripting examples, no).
I'm explicitly asking for some scripting help here.

Thank-you,
Josh

[anda65]

Hi!

I have a physical Windows Server 2012R2 on which runs a MySQL that need not to be stopped.
Is it possible to backup this Server with a Veeam Agent for Windows Server?
In sense that i know that MySQL is not VSS-aware, so what kind of problems, for the DB on the Server and for the db in the backup, can occur?

Many Thanks,
Antonio

[Dima P.]

Hello and welcome to the community Antonio!

Veeam Agent for Windows does not have the native capabilities of protecting MySQL in application aware manner do to the lack of VSS writer for MySQL. There are two options: either to perform a cold backup (i.e. shut down MySQL application prior backup) or add the pre-job script that will 'prepare' MySQL for backup. The link to the guide that you can use as a reference is provided in one of the previos posts. Hope it helps!

[anda65]

Hello Dima, and thanks for your answer.

I have read that guide, but it is about backup VM.
I have a physical Server. Is it the same?
I have read in that guide that in case of Cold Backup, and so stopping the MySQL service, the database will be unavailable only during snapshot time. May you confirm this? May you confirm that the scripts can stay in advanced settings of backup job, even if the server is physical?

Many Thanks!

[HannesK]

Hello,
yes, physical / virtual makes no difference from a script perspective.

Yes, when you stop the database service, then the database is not available.

Best regards,
Hannes