Encrypting the Undo Tablespace

Encrypting the Undo Tablespace

The undo data may contain sensitive information about the database operations.

You can encrypt the data in an undo log using the innodb_undo_log_encrypt option. You can change the setting for this variable in the configuration file, as a startup parameter, or during runtime as a global variable. The undo data encryption must be enabled; the feature is disabled by default.

variable innodb_undo_log_encrypt
Command Line:--innodb_undo-log_encrypt
Dynamic:Yes
Scope:Global
Variable Type:Boolean
Default Value:OFF

Defines if an undo log data is encrypted. The default for the undo log is “OFF”, which disables the encryption.

You can create up to 127 undo tablespaces and you can, with the server running, add or reduce the number of undo tablespaces.

Note

If you disable encryption, any encrypted undo data remains encrypted. To remove this data, truncate the undo tablespace.

See also

MySQL Documentation

How to Enable Encryption on an Undo Log

You enable encryption for an undo log by adding the following to the my.cnf file:

[mysqld]
innodb_undo_log_encrypt=ON

See also

Encrypting the Redo Log files

Download PDF Manual

Table Of Contents

This Page

Percona Server Series

Contact Us

For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or professional services, contact Percona Sales.