Skip to main content

 

Druva Documentation

Known issues

This topic provides a list of known issues and workarounds for these issues. It also lists the issues fixed in subsequent releases. 

Known issues

The following table lists the known issues. 

Issue Description
General issues

ROBO-4082

 

While creating new administrators, Phoenix does not display the drop-down list of the available organization after selecting one organization.

Workaround

Move the cursor on the screen and again click on the Organizations option.

File server issues
ROBO-894

If you configure Linux 6.3 servers to follow the default backup policy, backup is successful with the following error:

FileAgent: Backup failed for the file /cgroup/cpuacct/cgroup.event_control in fileset root

Workaround

Exclude the cgroup folder from the backup. To know how to exclude folders, see Update backup content of a file server backup policy

ROBO-2025 If the File server is not reachable during a scheduled backup, the Jobs page does not display the entry.
ROBO-3496

File server will not backup files with names, not in the Unicode format.

ROBO-4567

Full backup on Ubuntu 16.04 (64bit) OS is successful with errors.

Workaround

During backup, exclude all the files from the following path as they do not have read permission.

  • /var/lib/lxcfs
  • /run/lxcfs
  • /run/systemd/system
SQL server issues
ROBO-561

Scheduled differential backups in scenarios where databases are added, deleted, or renamed, are treated as full backups. However, the Backup Status Report displays the type of backup as "Differential Backup". 

Note: To know the scenarios in which Phoenix treats a differential backup as a full backup, see Differential backups

ROBO-1225

If you cancel an ongoing differential backup, then the subsequent restore to the original instance will fail.

Workaround

Try restore to an alternate location.

Try full backup after you cancel a differential backup

ROBO-1266

The database backup fails if it contains small IDF and MDF files (<1MB) and the auto growth for the database file is set to a small value. IDF and MDF files (<1MB) and the auto growth for the database file is set to a small value.

Workaround

Change the auto growth for the databases to a reasonably large value (~100MB).

ROBO-3538

When Phoenix service is restarted after database and metadata upload but VSS records incomplete backup, all subsequent differential backup jobs fail until the next full backup is successful.

VMware issues

ROBO-1019

If Backup Proxy loses connectivity with Phoenix Cloud or vCenter Server, the connection status under the Backup Proxies tab appears as "Connected".

Workaround

Wait for some time to allow the status to change. 

ROBO-1023

If you changed the name of the Backup Proxy virtual machine using vSphere Client, the changed name does not reflect under the Backup Proxies tab (Manage VMware Infrastructure > <ESXi or ESXi or vCenter Server>). 

Note: This is by design. Backup Proxy continues to work as expected even if the name change does not reflect on Phoenix Master Management Console. 

ROBO-1048 Sometimes, when you restore a virtual machine, the virtual machine properties reflect the default values. 

ROBO-1050

The restored virtual machine fails to boot with error "Operating system not found". 
After the restore, the boot sequence changes as VMware gives priority to IDE. VMware gives priority to IDE. 

Workaround

After the restore, change the boot sequence manually.

ROBO-1110

If you register an instance of Backup Proxy for an ESXi or ESXi or vCenter Server using its IP address, and you register another instance of Backup Proxy for the same ESXi or ESXi or vCenter Server using its FQDN, the ESXi or ESXi or vCenter Server appears twice in the Manage VMware Infrastructure list, once with the IP address, and once with the FQDN. 

ROBO-1123

A backup that starts at the same time as the snapshot creation of a virtual machine from the vSphere Client fails with the following error:

Connection dropped before completing backup.error

Workaround

Start the backup after the snapshot creation completes. 

ROBO-1124

If you attempt to delete a snapshot of a virtual machine from the vSphere Client at the time when backup of that virtual machine is complete, the delete operation does not delete the snapshot that Phoenix previously created.

Note: This is by design. Concurrent operations (in this scenario, deleting the snapshot that Phoenix created, and deleted the snapshot that was created from the vSphere Client) on the same virtual machine are not supported. 

ROBO-1130 If you added vService Dependency to a virtual machine, backups and restores of this virtual machine complete successfully. However, the restored virtual machine does not contain the vService Dependency. 

ROBO-1142

If backup proxy loses connectivity when the backup of associated virtual machines is in progress, the backup proxy attempts to establish connection multiple times and its status under the Backup Proxies tab appears as "Pending". 

Workaround

Cancel the pending backup task and then wait for next scheduled backup, that will be successful.
ROBO-1143 Restores of virtual machines having one or more  Unicode characters in their names is not supported. 
ROBO-1170 If a virtual machine has many disks, and you attempt to restore this virtual machine, some UI elements on the Restore Data window might not appear as expected. 

ROBO-1267

Backups from virtual machines associated with a backup proxy fail if the VMware tools reset the time of the virtual machines to a value that is likely incorrect even if the time synchronization check box is not selected. 

Workaround

Disable time synchronization. For a complete set of instructions, see Disabling time synchronization in the VMware library. 

ROBO- 1481

Backup fails with an unknown error " #100011001".

Workaround

Retry backup.

ROBO-1519

Backup fails with the error "device_key" for a virtual machine that has 60 SCSI disks.

ROBO -1531

Backup fails if in vRDM disks the same LUN is mapped on two different disks.

Workaround

Unmap the LUN from both disks and then map to only one of the disks.

ROBO-1533

Before restore, if the VRDM disk is changed to an independent VRDM, the guest repair will fail.

ROBO-1534

VMware restore fails when you try to restore a virtual machine/Disk Restore from Higher Version VC to lower version VC.

ROBO- 1572

Restore fails when the bus sharing mode of a virtual machine is modified. The backup will also fail if the bus sharing mode is not set to "None".

ROBO-1587

The backup proxy utility command does not work after upgrading backup proxy.

Workaround

  1. Find the currently installed RPM.
    Command: rpm -qa | grep druva

  2. Remove existing RPM.
    Command: rpm -e <curr_rpm_name>

  3. Install the new RPM.
    Command: rpm -ivh <new_rpm_name.rpm>

ROBO-1592

Virtual machine restore fails with the error "vim.fault.FileAlreadyExists". 
In case of standalone ESX, if the restored virtual machine is deleted from the inventory of its folder and VMX is in the backend.

Workaround

Rename the folder in the backend in order to restore the virtual machine. 

ROBO-2042

While configuring the proxy server with the agent or CloudCache, if you misspell the proxy type, the proxy will still be configured successfully with default Socks5 protocol.

ROBO-2501

During backup, if you update the proxy configuration then the ongoing backup will fail.

ROBO-2662

If the Phoenix service restarts multiple times during FLR, the initiated restore may fail if the restored folder contains files that cannot be deleted.

ROBO-3147

While activating the Backup Proxy, if it does not get connected to the VCenter. The Backup proxy will remain in the not connected state till we restart the Backup Proxy service.

ROBO-4132

The Backup activity report, displays the first VM  backup as Incremental instead of full.

ROBO-4189

If you delete a Backup Proxy during a VM backup, the detailed log request will fail with an Internal error.

ROBO-5444

If a rule (for example Rule1) is applied to a folder (for example Folder1) in a data store, and a rule (for example Rule1a) is applied to its subfolder (for example Folder1a).

  • In the Rule1a, already configured VMs are excluded from auto-configuration (Exclude already configured VMs setting is checked.)
  • In the Rule1, already configured VMs are included for autoconfiguration. (Exclude already configured VMs setting is unchecked.)

If there is a virtual machine (for example VM1) in Folder1a that was manually configured. Rule1a does not auto configure VM1, but VM1 becomes eligible for auto-configuration using Rule1. However, VM1 is not configured using Rule1. 

ROBO-5852

A full restore to an original location of an encrypted virtual machine does not overwrite a VMDK file.

Workaround

Delete the detached VMDK file after restoring the encrypted virtual machine.

ROBO-5958

In Linux, if the root folder ("/") is selected for a file restore, the file level restore job ends with the message "Successful with error" and the files are not restored. 

ROBO-6252

The backup proxy OVA fails to deploy on a standalone ESXi version 6.5 using the Web UI. This is a VMware issue. Druva is working with VMware to resolve this issue. 

Workaround

Deploy backup proxy OVA using the vSphere client 6.0.

ROBO-6455

Phoenix does not support backup and restore for virtual machines with disks using NVMe controller. 

Note: Backup and restore for virtual machines with disks using NVMe controller will be supported in a future release. 

DRaaS issues

ROBO-2996ROBO-2996

If you restart a DR proxy services while the DR restore is in progress, the DR restore status will reset to 0%.

ROBO-3011

Cloud DR for LVM is only supported if the LVM has a file system.

ROBO-3062

If you have disabled the DR status of the virtual machine and then update the server group, then the DR status for that virtual machine will automatically be enabled.

ROBO-3063 The DR restore job will fail if cache network is disconnected.
ROBO-3124

If you have scheduled an “immediate after backup” option for the DR policy, and after a successful backup the proxy is down, then the job will not be created for DR.

ROBO-3169

The AWS account number on the Manage DR policy page does not match with the AWS account number on the Update DR policy page.

ROBO-3171

If you configure a virtual machine in the region where DR proxy is absent, then in such scenario, the virtual machine Update Server Group page does not display any policy name in the DR policy tab.

ROBO-4133

If you have backed up a virtual machine with distributed vSwitch and you are restoring that virtual machine on ESX that does have access to distributed vSwitch then the restore fails with an Internal error "VMWARE_VMOMI65535".

ROBO-6070

For scheduled backup job retry, if backup job switches on multiple Backup Proxies, then the requests for job logs generate multiple but same Log Request jobs.

CloudCache issues

ROBO-5184

While editing the CloudCache details on the Edit CloudCache Details page, if you select the Backup to Cloud if unable to backup to Cache option and click Save, the checkbox still appears clear. However, the backup will continue to cloud if CloudCache is not connected.

You can view the current state (Enabled/Disabled) of the Backup to Cloud if unable to backup to Cache option on the Summary tab of the Manage CloudCache page.

ROBO-6366

Group administrators do not receive an email notification if the CloudCache attached to the group is decommissioned.

  • Was this article helpful?