Problem description
Phoenix detects the file server based on the unique Device ID present under C:\ProgramData\Phoenix.
The issue is seen when multiple servers with the same Device ID try to connect with Phoenix Cloud. Due to security reasons, only one server is allowed by Phoenix Cloud to connect.
Cause
The causes could be one of the following:
Phoenix client installed on one server and the same machine is used as a template/ cloned for other machines.
You installed the Phoenix client on one server and copied the Phoenix folder under ProgramData from that server to other servers.
Traceback
C:\ProgramData\Phoenix\main_service.log
[2020-02-04 01:45:30,890] [ERROR] <_MainThread(MainThread)> Error <class 'inSyncLib.inSyncError.SyncError'>:Server is busy. Try later. (#100000050) (Error Code : PHOENIX80).
'requests.exceptions.ConnectionError'>:HTTPConnectionPool(host='localhost', port=20809): Max retries exceeded with url: /scan/24520C/abort (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x00000000170FBDA0>: Failed to establish a new connection: [Errno 10061] No connection could be made because the target machine actively refused it',)). Traceback -Traceback (most recent call last):
[INFO] [CS 31405] [customerid: <NA> siteid:<NA>] device:459735 device_fqdn changed from vc03.druva.com to VB03.druva.com Resolution
Re-install the Druva Phoenix agent to create an unique entry for the device.
Steps
1. Download the Druva Agent setup.
2. Stop the Druva Phoenix Service.
Start > Run > Services.msc
3. Rename the Phoenix folder ( C:\Programdata\Phoenix ) to Phoenix_old.
This is an additional step as uninstallation will not remove the Phoenix folder.
4. Uninstall the Druva Phoenix agent.
Start > Run > appwiz.cpl
5. Install the Downloaded setup.
6. Re-register the server.
This will keep the existing Restore point of the server.
7. Re-register the other servers as New.
8. Trigger the backup.