NetWorker Recovery with Cyber Recovery Fails Due to BAD_DATA Error

When a user performs a NetWorker recovery through Cyber Recovery, the task fails with the following error:

Failed to run task recoverapp. Unable to get NW devices. NetWorker Error is Unable to decrypt data: BAD_DATA

This error is also reflected in the NetWorker daemon log.

Location: C:\Program Files\EMC NetWorker\nsr\logs.daemon.raw
NetWorker: How to use nsr_render_log to render .raw log files

When accessing the NetWorker Management Console (NMC) UI, a pop-up with the "BAD_DATA" error appears when attempting to navigate through the UI tabs.

This issue occurs when the source NetWorker server is a physical Windows machine, while the target NetWorker server inside the vault is a virtual machine. The problem lies with the NetWorker lockbox. On the source NetWorker server, a Datazone passphrase is being used, which is not correctly restored during the Cyber Recovery process.

Workaround: The Datazone passphrase must be updated manually in NetWorker after completing the Recover job in Cyber Recovery. The steps to fix the lockbox and Datazone passphrase issue are outlined below:

1. Delete the Recovered Lockbox: Remove the lockbox that was recovered as part of the Cyber Recovery process.
   

2. Create a New Lockbox: Manually create a new lockbox for the target NetWorker server inside the vault.
   

3. Update the Datazone Passphrase: Use the nsradmin command to update the Datazone passphrase. Ensure that the passphrase is the same as the one used on the production (source) NetWorker server.
   

4. Restart NetWorker Services: After updating the passphrase, restart the NetWorker services on the target server by running the following commands:

   net stop nsrexecd
   net start nsrd
   net start gstd

5. Validate: Log in to the NMC UI and check if the "BAD_DATA" pop-up error is resolved. Navigate through the tabs to confirm that the issue no longer appears.