Encrypted source set gets duplicated as an encrypted set even when this duplicate job is set to use no encryption

Problem

Encrypted source set gets duplicates as an encrypted set even when this duplicate job is set to use no encryption. The Duplicate Job Log carries the encryption and compression settings as set in the Duplicate job. If the source set is encrypted and while duplicate this source set another encryption key/pass phrase is used, the duplicate backup set will still be using the pass phrase used for the source backup.

Error Message

NA

Cause

A duplicate backup copies the data from source set as it is. The data is not decrypted even if the duplicate job is set to use no encryption. The Duplicate Job Log shows no encryption used as set in the duplicate job.

The data is not going to be decrypted and then re-encrypted with another pass phrase (encryption keys) if a different pass phrase is set in the duplicate job i.e. source set used x encryption key and duplicate of this source set uses y encryption key so each one gets encrypted with its own key. This is not the case and a duplicate of the encrypted source set will continue to use the encryption key used to encrypt the source set. If this is attempted in the Duplicate Job, the following info message appears "Backup Sets which are already encrypted will not be re-encrypted. The selected key will only apply to unencrypted backup sets "

Solution

It is essential that the encrypted key pass phrase be remembered as this is what is required to read (catalog, restore) from the encrypted media. If the encryption key pass phrase is not present in Backup Exec then an alert is popped up during a catalog to feed in the encryption pass phrase before the media can be cataloged and if catalog is present for that set, restore or browse of this set will require the encryption pass phrase to be present in BE if not present already.
Note: The encrypted backup set can be distinguished easily as they show up with a lock sign in Backup Exec.