Chapter 8: Routine operation and compatibility
Share encrypted files across servers
APPX supports sharing encrypted native datafiles between systems registered to the same APPX customer, provided the systems also use the same system Encryption Passphrase and the same effective file encryption key. All three conditions must be met. Matching customer identity alone is insufficient. These are the conditions published in Sharing of Encrypted Files.
The servers can have separate APPX registrations. The requirement is the same APPX customer identity on those registrations; their full registration records do not have to be identical.
For example, a production server and a disaster-recovery server belonging to the same APPX customer can be configured to read the same encrypted backup. The native files can remain encrypted during transfer and restoration.
- Confirm that both APPX systems are registered to the same APPX customer. Ask APPX Support to confirm the customer identity if the registrations are uncertain.
- Confirm that the destination engine supports the physical file format and has the matching application structures.
- On a separate destination test installation, set the exact system passphrase and effective file or group keys from the restricted vault. Preserve the intended FMS and destination path mappings.
- Make a consistent copy while source-file access is stopped. Transfer the complete
.datand.keypair through an approved protected channel, and preserve the source copy. - Open the destination copy through APPX, verify integrity, compare record counts and complete sample values, and check application totals before accepting it.
Do not change an existing destination system's passphrase merely to open an incoming file. Such a change affects that system's other encrypted files; follow Change a key or the system passphrase when a system-wide conversion is required.
When two systems should remain separate, use different system passphrases and file keys, as recommended in the sharing reference. Keep the recovery records for each system clearly identified in the vault.