Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.15 Kubernetes User Guide

Log truncation considerations

MySQL generates binary log files in the MySQL persistent volume claim (PVC) when you perform application-consistent backups and restores. These log files follow the naming convention mysql-bin.xxx and are part of the MySQL application log.

You may have a requirement to truncate these log files for management purposes. However, these files contain both application-consistent information and other customer-specific information. The PowerProtect Data Manager cannot intercept the customer-specific portions of the log, nor determine where to truncate around this information.

Instead, you must review the database log files and decide where to manually truncate the log, if appropriate. It is recommended that you manage these binary log files in concert with the other MySQL log files.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\