Upgrading with Encryption

When upgrading on the same server, no action needs to be taken regarding encryption.

When you are migrating to a different server (hardware or virtual machine), follow these steps to ensure encryption is handled properly:

Important
Encryption keys are tied to the server they are created on and are not transferable to a new server. Trying to decrypt a file from an old server with a new server's encryption key will not work.

On the old server, turn off encryption, which will cause all recordings to be decrypted. This is necessary, because the encryption keys are tied to the server they are created on, and are not transferable to a new server.
Once all recordings have been decrypted, migrate them over to the new server. How this should be done will be site specific, and depends on where the recordings are stored (local storage location, remote storage location, archive location).
After the recordings have been migrated and the records in the database have been updated to reflect the proper storage location (if needed), turn on encryption on the new server. After new encryption keys are created, internal processing will go through and encrypt all the files it can find.

Notes
If you have a lot of data, decryption may take a while. Exactly how long will depend on the average size of the files, total number of files, resource load on the server, and so on. Locally stored files are likely to be decrypted more quickly than those stored remotely as there won't be network latency issues. The possible exception is if remote storage hardware is significantly faster than local storage hardware (15K rpm disk speed vs 5400 rpm disk speed, for example). Migrated recordings can stay in .wav format. There is no need to convert them to mp3 prior to re-encrypting them. When an encrypted .wav file is played back, conversion to mp3 will take place as part of preparing the file for streaming.

Notes

If you have a lot of data, decryption may take a while. Exactly how long will depend on the average size of the files, total number of files, resource load on the server, and so on.
Locally stored files are likely to be decrypted more quickly than those stored remotely as there won't be network latency issues. The possible exception is if remote storage hardware is significantly faster than local storage hardware (15K rpm disk speed vs 5400 rpm disk speed, for example).
Migrated recordings can stay in .wav format. There is no need to convert them to mp3 prior to re-encrypting them. When an encrypted .wav file is played back, conversion to mp3 will take place as part of preparing the file for streaming.

If you have migrated to a new server and encrypted files are unplayable, if your old server is still available, follow these steps:

Disable the encryption on the old server to decrypt all the files
Copy all .wav files to the new server
Rename the files in the DB from .enc to .wav
On the new server, turn encryption on.

If you have migrated to a new server and encrypted files are unplayable because they weren't decrypted before they were migrated, if the old server is unavailable, the files will not be able to be decrypted.