Skip to main content
Solved

Performance hit during VM Backup


Forum|alt.badge.img+8

Hi,

I’m looking into an issue with a VM that hosts a MySQL database. The MySQL admins are complaining about poor performance during VM Backups. My first guess is quiescing that is potentially causing issues. (Transport Mode is Hotadd)

The MySQL database is also being backed up using the MySQL iData Agent. This works without issues. However, the customer also wants a filesystem consistent VM backup and that is where the issue comes in.

Looking at the backup details and logs, I don’t see any issues.

Any idea what next steps I could take here? I’m looking at the possibility to take a crash consistent snapshot to test my theory.

Best answer by Jos Meijer

I would either:

  • Host the SQL VM on a NVME datastore, or
  • Host the SQL DB on dedicated disk and exclude the SQL DB disk from VM backup, this will reduce disk consolidation time which is most likely the issue.

In order to check for the performance hit with a crash consistent backup, you can, but I wouldn't leave it that way. Way to much risk on issues regarding getting the VM / SQL up and running again.

Other option is to exclude from VM backup and use File System and SQL agent only.

View original
Did this answer your question?

3 replies

Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • 638 replies
  • Answer
  • July 12, 2022

I would either:

  • Host the SQL VM on a NVME datastore, or
  • Host the SQL DB on dedicated disk and exclude the SQL DB disk from VM backup, this will reduce disk consolidation time which is most likely the issue.

In order to check for the performance hit with a crash consistent backup, you can, but I wouldn't leave it that way. Way to much risk on issues regarding getting the VM / SQL up and running again.

Other option is to exclude from VM backup and use File System and SQL agent only.


Forum|alt.badge.img+8
  • Author
  • Byte
  • 57 replies
  • July 12, 2022

Hi Jos,

Thanks for your advise. You’re right, disk consolidation might be the issue here. I didn’t think of that.

I’ll check this. I’ll get back to this post when a root cause or solution was found.

 


Forum|alt.badge.img+8
  • Author
  • Byte
  • 57 replies
  • July 14, 2022

Just to post an update. The application that is using the MySQL database is very sensible to quiescing operations. We’ll go ahead and explore the possible solutions that Jos suggested.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings