commvault.com commvault.com
Question

mySQL restore procedure - performance

  • 13 February 2024
  • 3 replies
  • 46 views
F
Badge +2

Hey Guys :)

Running a restore from a mysql db. Network Test is ok, but throughput is very slow (2-4GB/hr). On the client i can see i high cpu load (80-95%), and the Disk usage is also close to 100%. 

But my question is (or from the customer): Can someone please explain me how the restore is working? So what is commvault, the Agent, doing step by step? Why does it create such i high load on the cpu and the disk?

Thanks :)

KR

3 replies

Sunil
Rank
Userlevel 5
Badge +13

hi @Fusi 

Can you try doing “no recover” restore which will restore the dump files to the local disk, and then manually import the dumps to mysql server?

This will help isolate where is the bottleneck. whether it’s on the MySQL side or Commvault side.

 

Thanks,

Sunil-

F
Badge +2

Hello @Sunil,

 

thanks for you replay. Is the mysql import from a dump using the same process/method like the CV Agent is using? 

Sunil
Rank
Userlevel 5
Badge +13

Yes. CV use the same method of importing from dump.

 

Thanks,

Sunil-

Reply


Terms & ConditionsCookie settings