This article applies to:
OS: Windows, Linux
Product edition: Phoenix
Overview
This article provides the steps to re-register or re-add a server that was supposed to replace an existing server but was accidentally registered as a new server on the Phoenix Management Console. In such a case, Phoenix backs up both the servers simultaneously.
For example:
A Windows 2008 File Server configured on the Phoenix Management Console was supposed to be replaced by Windows 2012 R2 File Server. However, Windows 2012 R2 File server got registered as a new server on Phoenix. Therefore, two servers are backed up from Phoenix.
Re-register an existing server
The procedure to follow on the respective operating systems is as follows:
On Windows:
Stop the Hybrid Workloads Agent Client Service / Druva-EnterpriseWorkloads on the new server
On the Task Manager, verify if there are any Phoenix related processes running. Wait for them to exit or end them manually.
Rename the configuration folder to <folder name>_old. It contains the configuration information of the Druva Agent.
C:\ProgramData\Phoenix (for agent version prior to 7.0.0)
C:\ProgramData\Druva\EnterpriseWorkloads (for agent version 7.0.0 and later)Start the Hybrid Workloads Agent Client Service / Druva-EnterpriseWorkloads and start the agent. The agent asks for an activation token. If it does not, perform the above-mentioned steps again.
Get the activation token of the older server from the Phoenix Management Console. See Server re-registration for more information.
Register the new server using the token. This replaces the old server with the new server on the Phoenix Management Console. The server that was registered accidentally appears as disconnected on the console. The disconnected server can be deleted as required.
On Linux:
Stop Druva agent
/etc/init.d/Phoenix stop(for agent version prior to 7.0.0)
service Druva-EnterpriseWorkloads stop(for agent version 7.0.0 and later)Rename the configuration folder to <folder name>_old. It contains the configuration information of the Druva Agent.
/etc/Phoenix/ (for agent version prior to 7.0.0)
/etc/Druva/EnterpriseWorkloads/ (for agent version 7.0.0 and later)Start Druva agent
/etc/init.d/Phoenix start(for agent version prior to 7.0.0)
service Druva-EnterpriseWorkloads start(for agent version 7.0.0 and later)Get the activation token of the older server from the Phoenix Management Console. See Server re-registration for more information.
Register the new server using the token. This replaces the old server with the new server on the Phoenix Management Console. The server that was registered accidentally appears as disconnected on the console. The disconnected server can be deleted as required.