The MySQL Keyring 4. Copy keys from the source keystore to the destination. 5. Unload the keyring component libraries for the source and destination keystores. 7. (Online migration only) Disconnect from the running server. 6. (Online migration only) Enable  keyring_operations  on the running server. •If the running server was using the source keystore before the migration and should continue to use it after the migration, it need not be restarted after the migration. •If the running server was using the destination keystore before the migration and should continue to use it after the migration, it should be restarted after the migration to load all keys migrated into the destination keystore. •If the running server was using the source keystore before the migration but should use the destination keystore after the migration, it must be reconfigured to use the destination keystore and restarted. In this case, be aware that although the running server is paused from modifying the source keystore during the migration itself, it is not paused during the interval between the migration and the subsequent restart. Care should be taken that the server does not modify the source keystore during this interval because any such changes will not be reflected in the destination keystore. 1. Connect to each running server manually and set  keyring_operations=OFF . This ensures that no running server is using the source or destination keystore and satisfies the required condition for offline migration. 2. Use a migration server or  mysql_migrate_keyring  to perform an offline key migration for each paused server. 3. Connect to each running server manually and set  keyring_operations=ON . 1437 The functions described here are general purpose and intended for use with any keyring plugin. A given keyring plugin might have functions of its own that are intended for use only with that plugin; see Section 6.4.4.15, “Plugin-Specific Keyring Key-Management Functions” . MySQL Server also includes an SQL interface for keyring key management, implemented as a set of general-purpose functions that access the capabilities provided by the internal keyring service. The keyring functions are contained in a plugin library file, which also contains a  keyring_udf  plugin that must be enabled prior to function invocation. For these functions to be used, a keyring plugin such as keyring_file  or  keyring_okv  must be enabled. MySQL Server supports a keyring service that enables internal components and plugins to securely store sensitive information for later retrieval. All running servers must support the  keyring_operations  system variable. Any server that does not must be stopped before the migration and restarted after. Online key migration provides for pausing keyring operations on a single running server. To perform a migration if multiple running servers are using the keystores involved, use this procedure: If an error occurs during key migration, the destination keystore is restored to its premigration state. After a successful online key migration operation, the running server might need to be restarted: Key Migration Involving Multiple Running Servers 6.4.4.14 General-Purpose Keyring Key-Management Functions