The ApplyPendingChanges action performs all pending encryption and decryption actions, using an offline reorganization-style behavior.
The EncryptFile, EncryptFiles, DecryptFile, and DecryptFiles actions only mark the specified files as encrypt-pending or decrypt-pending; the file contents are not encrypted or decrypted until the next ApplyPendingChanges action. The syntax of the ApplyPendingChanges action is as follows.
jdbcrypt path=database-path
ini=initialization-file-name
action=ApplyPendingChanges
As this action does not require the master key passphrase, it can be fully scripted.
The following is an example of the ApplyPendingChanges action.
jdbcrypt path=d:\dbcrypt ini=d:\salesdb\jade.ini action=ApplyPendingChanges
The ApplyPendingChanges action writes a secondary log file called bulkcrypt.log.
The contents of each database map file are copied to a .reo file in encrypted form. The pending keyset is moved into the current keyset slot in the .reo file. When all .reo files have been created successfully, instantiation replaces the original files with the encrypted files.
You can specify that multiple files are encrypted in parallel, by specifying the number of worker threads you require in the
You should not set the number of workers to more than the number of cores in the machine, minus one (for example, on a four-core machine, specify three workers). Consider the effect of multiple workers on the disk subsystem.
Take a full offline backup of your database when the encryption or decryption process is complete, to avoid reprocessing the encryption or decryption during recovery.