If you need to manually upload or renew an expired key on an active master/primary server, copy the JSON file directly into the designated operating system directory: Operating System Default Destination Directory /usr/openv/var/global/customer_registration/ Windows Server \var\global\customer_registration\ Verification & Troubleshooting
Downloads a single file containing all Account IDs associated with your profile. This is useful if you manage multiple master servers across different accounts. Step 4: Download and Deploy Click the Download icon next to your chosen account.
: Locate the Account ID associated with your primary server. The portal will display all account IDs linked to your Veritas single sign-on (SSO) account. Download the File : how to download veritascustomerregistrationkeyjson verified
. Ensure you save this to a secure location, as it contains sensitive account information. Why You Need This File key is primarily used for: Usage Insights
The veritas_customer_registration_key.json file is a critical component required for and Usage Insights to function within NetBackup environments. It is not a license key but rather a registration file that links your master server to your specific account ID for telemetry and usage tracking. If you need to manually upload or renew
When using an aggregate key, the NetBackup UI will prompt you to select the specific Account ID associated with the primary server.
If you are unable to locate the file in the portal, check the following: : Locate the Account ID associated with your primary server
Open the file using a secure text editor like Notepad++ or VS Code. A verified Veritas JSON key should contain structured code blocks enclosing details like: Customer Name Entitlement ID Expiration Date Cryptographic Signatures Run a Hash Check
To ensure that the file was downloaded completely without corruption, you can perform a quick verification check.
If the download button doesn't trigger, try using Incognito mode or clearing your cache.
If you want to troubleshoot your specific deployment, let me know: