Agentless, cloud-native backup for Google Cloud
Post Reply
mdyer
Novice
Posts: 7
Liked: never
Joined: Dec 12, 2023 5:42 pm
Full Name: Michael Dyer
Contact:

MySQL Backup Performance

Post by mdyer »

I am testing Veeam Backup for Google with a 375GB MySQL instance.

Snapshots complete in ~3 minutes.
Backups to Cloud Storage (standard bucket) via a Worker complete in ~5 hours 15 minutes with ~15GB transferred.
Initial and subsequent backups appear to take the same amount of time.

Q. Is this amount of time "normal"?
Q. Is there anything I can do to improve backup performance?
Grimarr
Veeam Software
Posts: 36
Liked: 6 times
Joined: Sep 29, 2016 9:56 am
Full Name: Dmitry Rybakov
Contact:

Re: MySQL Backup Performance

Post by Grimarr » 1 person likes this post

Hello Michael,
5h 15 min for 15GB really doesn't seem to be the optimal performance, however this may be the expected time under certain conditions.
Here are two major points that I would suggest taking into account:
If you have a repository located far away from the source instance, the backup speed is limited by network speed between selected regions.
Highly loaded production instance. If you use a connection to a production instance as the source when the database load is high, you also can expect the backup operation to be slow.

I would suggest trying to change the configuration used for the backup policy - switch to using the staging server as the data source, schedule the policy run to the period of time when the instance is not under production load, and consider using repository located in the same region as the production instance.
mdyer
Novice
Posts: 7
Liked: never
Joined: Dec 12, 2023 5:42 pm
Full Name: Michael Dyer
Contact:

Re: MySQL Backup Performance

Post by mdyer »

Thanks Grimarr,

- The MySQL server is located in us-east1-c
- The policy region is us-east1
- The bucket region is us-east1 (standard)
- I am backing up using a staging server.

After the snapshot completes (~3 minutes), it takes around 55 minutes for the snapshot to be restored to the staging server.
The remaining ~4 hours is is the worker processing the dump from the staging server.
nielsengelen
Product Manager
Posts: 5838
Liked: 1220 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: MySQL Backup Performance

Post by nielsengelen »

Hi Michael,

I would recommend opening a support case to have this investigated with an extra pair of eyes. We can do some tweaking for sure to speed it up.

Please let us know the case ID once you've created it.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
mdyer
Novice
Posts: 7
Liked: never
Joined: Dec 12, 2023 5:42 pm
Full Name: Michael Dyer
Contact:

Re: MySQL Backup Performance

Post by mdyer »

Vitaliy S.
VP, Product Management
Posts: 27463
Liked: 2825 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: MySQL Backup Performance

Post by Vitaliy S. »

Yes, free users should wait, as the new version has just been released. However, if you're on a trial key, you should also get full support as per Anton's post.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest