Skip to main content
Druva Documentation

Phoenix file server backups fail due to VM clones

 

Problem description

In some situations, the server connection between the Phoenix file server agent and the Phoenix cloud may become inconsistent. The backups may fail in such cases, and the latest recovery points may not be healthy. This may happen when administrators install the Phoenix file server agent inside VMware virtual machines to protect specific files, folders, or volumes during backups.

Cause

You may run into this issue when the file server in question is a VMware virtual machine that was cloned from a server where the Phoenix agent was installed. The original file server machine and the cloned virtual machine coexist in your environment. The file server agent on both the original server and the cloned VM try to establish a connection with the Phoenix cloud, thereby creating a conflict. Your VMware administrator or System administrator can help you determine if the original server was cloned or not. 

Resolution

Option 1:  Uninstall the Phoenix file server agent from the clone VM

  1. Identify the clone VM and log in to the guest OS of this VM.
  2. Uninstall the Phoenix file server agent from this VM. Follow the instructions as per the operating system of the clone:
  3. Once the file server agent has been uninstalled from the clone VM, login to the original file server machine and perform the following tasks:
    1. Stop the Druva Phoenix Agent Service.
    2. Navigate to the following location and rename all the *.db files.
      • WindowsC:\ProgramData\Phoenix\FS\state\backup\<backupsetid>\*.db
      • Linux: /var/Phoenix/FS/state/backup/<backupsetid>/*.db
    3. Once the files have been renamed, restart the Druva Phoenix agent service.
  4. Go to the Phoenix Management Console and navigate to the original file server. Make a small dummy change to the content rule for the backup set of this file server. You can include or exclude some data and update the content rule. You can revert this change once the content rule has been saved.
  5. Initiate a manual backup (Backup Now) of the original file server. This will ensure that the backup of the original server is successful.

Option 2: Configure the clone VM as a new Phoenix file server 

If you  want to protect the clone VM then you can configure it as a new Phoenix file server. As a new Phoenix file server it can coexist with the original file server machine.

  1. Identify the clone VM and log in to the guest OS of this VM.
  2. Uninstall the Phoenix file server agent from this clone VM.
  1.  Follow the instructions in the Install the agent and register a server article to download the Phoenix agent for file servers, install it on the VM, and register the VM as a new server in the Phoenix Management Console.
  2. Log in to the original file server and perform the following tasks:
    1. Stop the Druva Phoenix Agent Service.
    2. Navigate to the following location and rename all the *.db files.
      • WindowsC:\ProgramData\Phoenix\FS\state\backup\<backupsetid>\*.db
      • Linux: /var/Phoenix/FS/state/backup/<backupsetid>/*.db
    3. Once the files have been renamed, restart the Druva Phoenix agent service.
  3. Go to the Phoenix Management Console and navigate to the original file server. Make a small dummy change to the content rule for the backup set of this file server. You can include or exclude some data and update the content rule. You can revert this change once the content rule has been saved.
  4. Initiate a manual backup (Backup Now) of the original file server. This will ensure that the backup of the original server is successful.