Problem Description
When attempting to register or activate a client device using the Druva Agent, the activation fails, and the following error message is displayed:
Error: The device is already registered.
Symptoms
Reinstalling the Druva Agent does not resolve the error.
The newly configured device does not appear as a new entity in the Druva Management Console.
Cause
Druva uniquely identifies backup targets using the system's Universally Unique Identifier (UUID). This error occurs because the target machine's system UUID is already associated with an existing device entry inside your Druva environment.
When a duplicate or reused UUID is detected, the Druva Cloud blocks the new registration to prevent data corruption and activation conflicts. This scenario commonly occurs when:
Virtual machines (VMs) are cloned without changing their hardware identifiers.
VM templates are deployed without regenerating system UUIDs.
Duplicate UUIDs are manually assigned or retained at the hypervisor level.
Hardware identifiers are preserved following certain P2V (Physical-to-Virtual) migrations or system restores.
Validation Steps
Step 1: Verify the Local System UUID
Run the appropriate command on the affected target system to collect its unique hardware identifier.
For Windows Systems: Open Command Prompt as an Administrator and execute:
wmic csproduct get UUID
For Linux Systems: Open the Terminal and execute:
sudo dmidecode -s system-uuid
Step 2: Contact Druva Support for Verification
If the activation error persists, open a ticket with Druva Support and provide:
The exact error message string.
The UUID collected in Step 1.
Druva Support will check the backend environment to identify which active or stale device entry is currently conflicting with this UUID.
Resolution
Step 1: Regenerate a Unique VM UUID
If a duplicate UUID is confirmed, collaborate with your virtualization or system administration team to assign a unique UUID to the virtual machine. The method for updating the UUID depends on the hypervisor platform being used.
Step 2: Reinstall and Reactivate the Druva Agent
Once the system UUID is unique:
Cleanly uninstall the existing Druva Agent.
Reinstall the Druva Agent on the target machine.
Rerun the activation wizard.
Verify that the device now registers successfully as a separate entity in the Druva Management Console.
Best Practices & Recommendations
To prevent registration conflicts in future deployments:
Sysprep / Generalize: Always generalize OS images (e.g., using Sysprep on Windows) and ensure hypervisors are configured to generate fresh UUIDs during VM customization.
Pre-Flight Checks: Verify UUID uniqueness across your infrastructure before deploying bulk backup agents.
Console Hygiene: Decommission and remove stale or unused device entries from the Druva Console when retiring old assets.