Skip to main content
- Troubleshooting
- No image available
- "Server already registered" error while activating file server agent
- Activation of Phoenix workload gives Resource not found : tokenID (Error Code : PHOENIX127)
- Analytics page errors out or shows blank
- App-aware backup completes with “Failed to add SQL writer entry” error.
- App-aware backup completes with “Failed to check writer services” error
- App-Aware backup failed with Windows error: [Error2]The system cannot find the file specified
- Application-aware backup completes successfully with error- Network Adapter is not up on VM
- App aware backups complete with required field username not provided (not @optional) error
- App aware backup completes successfully with Credentials are not assigned to Guest VM error
- App aware backup completes successfully with the error The guest operations agent is out of date
- App aware backup completes successfully with VM State: poweredOff error
- App aware backup completes successfully with VM Tools status: toolsNotRunning error
- App aware backup completes with could not create directory error
- App aware backup completes with failed to establish new connection error
- App aware T-Log backup fails with Exit code VMware21
- App aware T-Log backup fails with the VMware27 error
- App aware T-Log backup job fails with exit code VMware24
- Assuming drive cache error while opening the backup proxy
- Avoid timestamp mismatch for backup job and snapshot
- AWS Proxy deployment fails due to AWS Availability Zone limitation
- Backups on Standby DB failing with ERROR ORACLE DTC 21
- Backups stuck at Pinging Sync Server on 0% on the Unix system
- Backup and restores do not proceed with the VSS
- Backup and restore from CloudCache server fails
- Backup and restore from Windows CloudCache fails with - An attempt was made to access a socket in a way forbidden by its access permissions
- Backup completes with successful with error but the logs show the PHOENIX23 error
- Backup fails due to virtual memory exhaustion
- Backup fails with an error message “ERROR at line 1:\nORA-01034: ORACLE not available\nProcess ID: 0\nSession ID: 0”
- Backup fails with Phoenix encountered incorrect folderpath error
- Backup job stuck at 0 percent due to Delayed write failed or Disk is full
- Backup Proxy activation fails while fetching the UUID
- Backup proxy activation fails with the PHOENIX232 error
- Cleaning up unnecessary space on PBS/CloudCache
- CloudCache auto-upgrade fails when triggered from admin console
- CloudCache installation ends prematurely
- CloudCache warning - Server fails to connect to CloudCache to back up or restore
- Cloud Cache fails to connect to Phoenix cloud with the error - DLL Load Failed
- Commands to control services on UNIX clients
- Database discovery fails on SQL server and server doesn’t get registered under “All SQL Resources” in the Phoenix console
- Data scan reported in Phoenix console is more than the size of the folder on the disk
- Differential database backup of AG database gets converted to full backup
- Discovery of RAC database for Oracle DTC workload is not working
- DRaaS deployment with CloudFormation fails with a Create Failed error
- DraaS failover checks fails with error "Incorrect instance type"
- DRaaS failover to AWS fails with Error: Instance type is invalid for conversion
- DRaaS restore of Domain Controller Virtual Machine fails with AWS_DR24 error
- DRaaS v1.0 does not retain network file for Linux Server
- Druva Phoenix Oracle PBS shows disconnected on the Phoenix console after the reboot
- DR Failback- unknown user name or bad password
- DR failover failed with error code AWS DR255
- DR job fails due to low disk space on the drive
- DR restore fails due to memory full
- DR restore fails with INTERNAL65535 error
- DR restore job fails for Encrypted volumes
- Encrypted VM backup shows the Invalid configuration for device error on VMWare backup proxy
- Error 1935 during Phoenix Agent installation
- Error while activating Phoenix on a Linux server
- Error while creating a custom role
- Error while creating backup set using a content rule that is attached to another backup set on the same server
- Event ID - 12289 during backup due to floppy drive
- Failed to Power on Linux Cloudcache and Backup proxy VM
- Failed to refresh VM list while deleting VMs and vhost
- Failed to register Windows File Server agent on Phoenix Cloud after providing activation code
- Fail to activate a Linux file server error Invalid argument error : Invalid timezone (#10000007f) (Error Code : PHOENIX127
- File Server agent installation failed on the OpenSUSE Linux
- File Level Restore (FLR) fails on VMware Cloud on AWS (VMC) with error failed to establish a new connection
- File restore completes successfully but the destination folder is empty
- File server backups completing with errors - PhoenixFSSnapshot executable timed out
- File Server backups from Linux server fail with Phoenix322 error
- File Server backups stuck in queue state
- File Server/NAS backup completes with status: Successful with errors
- File server backup fails with Backup Window Expired
- File server backup fails with exit code Phoenix 322 Error message: ”Database disk is malformed.”
- File Server Backup fails with INTERNAL65535
- File server backup fails with error PHOENIX80
- File server backup fails with the Unable to query USN Journal error
- File server restore from cold recovery points fails
- File Server shows in disconnected state on UI
- File Server/Hyper-V/SQL server backup fails with PHOENIX189
- First backup after configuration of the file server fails with Backup Window Expired
- Full VM or disk restore to alternate location fails with error - The virtual machine version is not compatible with the version of the host.
- Full VM Restore failing with an error “Logon failure: The user has not been granted the requested logon type at this computer. (0x80070569)”
- How to back up Microsoft Windows 2003 server OS via SMB with Druva Phoenix
- How to Re-Configure web-proxy for Linux Cloudcache server
- How to run a manual backup for a File server backupset
- Hyper-V backups fail with PHOENIX54 error
- Hyper-V backups fail with the HYPERV28 error because the backup includes both CSV and non-CSV volumes
- Hyper-V Backup fails with Disk Merge error HYPERV23
- Hyper-V backup fails with error 'Operation timedout of gathering writer metadata'
- Hyper-V FLR Proxy showing disconnected after live migration from one host to another
- Hyper-V file level restore error- Failed to fetch file list- Internal Error
- Hyper-V VM backup fails with HYPERV3 error
- Hyper – V VM backup fails with HYPERV1 Error
- Installation/Upgrade of Hybrid workload agent prompts for reboot
- Kernel panic error on the backup proxy
- Linux Cloud Cache is showing as ‘Disconnected’ in the Phoenix Console
- Linux NAS backup fails with error Phoenix 370
- Login fails with SSO after timeout from Druva console with ADFS as IdP
- Login to backup proxy failed with ‘Authentication token manipulation error’
- Manually test VSS Shadow Copy Creation Using the Diskshadow Utility in Windows
- MS SQL VM Servers not visible in Phoenix Console
- NAS Backup failed after changing the credentials for NAS device
- NAS backup fails with the filename, directory name, or volume label syntax is incorrect error
- Non-synced data resides on Phoenix CloudCache
- Not able to select the host while restore of the VM to an alternate location
- Nutanix Backup Proxy deployment failure with error “"Error occurred while reading cluster credentials”
- Nutanix Full VM Restore and VM disk Restore fail with the Error: AHV 200
- Nutanix VM Backup fails with Error AHV100
- Oracle backup or restore fails to find an available port to start IOServer
- Oracle DTC archive log backup fails with ORACLE DTC5
- Oracle DTC Backup failed for RAC database with ORACLE DTC5
- Oracle DTC backup fails with INTERNAL65535
- Oracle DTC Database discovery failure alerts received after Oracle server upgrade
- Oracle incremental data file backup fails with the "RMAN Backup has failed. Please check RMAN logs for more details" error
- Oracle PBS backup failing with error ORACLE31
- Oracle PBS does not show the ZFS pool mounted
- Oracle Phoenix Backup Store backup job is in the queued state or stuck in running state
- Oracle Phoenix Store activation fails with the error: Phoenix1
- Phoenix Agent activation fails with Phoenix1 - global name SyncLog is not defined
- Phoenix agent installation error: Another installation is in progress
- Phoenix Agent installation fails due to an error during the installation of assembly policy
- Phoenix agent installation fails with an error while applying security settings
- Phoenix Agent Service fails to start with error “specified service has been marked for deletion”
- Phoenix Agent setup does not start or launch on Windows servers
- Phoenix backup fails with PHOENIX54 error
- Phoenix backup fails with the 'PHOENIX158 error: Backup window expired' after content rule was modified
- Phoenix Backup Store OS throws the nfsd:blocked for more than 120 seconds error
- Phoenix file server backups fail due to VM clones
- Phoenix VMware backup fails on a VM with event id 1000 for VMware Tools
- Phoenix Windows Server activation fails with the error - Druva Phoenix Client service is not running
- Playbook - How to Collect logs and troubleshoot Oracle PBS and Oracle DTC issues
- Possible Causes for Hyper-V FLR restore issues
- Possible causes for Phoenix backups failing to Windows CloudCache
- Possible causes for Phoenix backups failing with the backup window expired error
- Possible causes for slow VMware FLR(File Level Restore)
- Possible causes of Cloud Cache Decommissioning process gets stuck
- Possible Causes of Proxy Deployment failure
- Recover a ransomeware-affected server using Phoenix
- Registration of vCenter backup proxy fails with PHOENIX127
- Rename Hyper-V host with a different name
- Restore completes with errors without recovering a single file
- restore failure due to incompatible machine version on the host
- Restore of a file server fails with PHOENIX304
- Restore of a VMware virtual machine fails with error VMWARE VMOMI65535
- Restoring a Hyper-V Full VM to a different host fails
- RMAN backups fails with an error 0RA-19870 AND 0RA-19625
- Runtime Error while running Scanner CLI utility
- Scenarios when the performance of an incremental VM backup is impacted and the job fails with the Backup Window Expired error.
- Share backups on Linux NAS proxy fail with error PHOENIX265
- Shortcut access to Phoenix agent fails
- Snapshot of VM failed
- socket error while create_connection with Error 10060
- Some rights are disabled on the create role page
- Some VMs missing from the list on All Virtual Machines tab
- SQL App aware backup completes successfully with the error VM credential is invalid
- SQL backups fail with the error PHOENIX185
- SQL backups fail with snapshot error PHOENIX54
- SQL backup failed: Vss Error: Operation timedout of gathering writer metadata
- SQL backup failed for only one database with INTERNAL 65535 error
- SQL backup fails with error VSS65535
- SQL Backup fails with SQL3
- SQL backup fails with VSS10 error
- SQL backup hangs and fails with Backup Window Expired
- SQL differential backup runs as full due to backup start time mismatch
- SQL differential backup runs as full due to shrinking database size
- SQL discovery fails with ODBC SQL server errors
- SQL log backups fail with error SQL8
- SQL log backup completes with “Successful with errors”
- SQL Log backup fails with a database corruption error
- SQL Log backup fails with error “INTERNAL 65535” with an entry in detailed logs 'No last log commit information available'
- SQL Log backup fails with error “last backup LSN from the primary database is greater than the current local redo LSN”
- SQL Log backup fails with the error SQL8: Database is already open and can only have one user at a time
- SQL log chain broken issue when the same VM is backed up using VMware/HyperV policy on Druva
- SQL restores fail with the VSS1 error
- SQL server backup fails with SQL 6 error
- SQL TLOG backup failure with exit code SQL8 for Windows 2008 R2 SP2 server
- SQL Transaction Log backup succeeds with errors
- The activation of the VMware Backup proxy fails with the error message "reason = 'unexpected error reading property'".
- The ESXi or VM hangs during VMware backup
- The size of the Snapshot on the Storage after a Linux File Server Backup is multiple times (more than 10x) bigger than the original Linux File Server
- The SQL Resource Name will display first 15 characters if the SQL server hostname contains more than 15 characters
- Troubleshooting "Server already registered" error while activating file agent
- Troubleshooting backup issue on Phoenix Cloud for VMware server
- Troubleshooting Error 1450 ReadFile', 'Insufficient system resources exist to complete the requested service. (#100000017)
- Troubleshooting issues with Phoenix CloudCache
- Troubleshooting Spectre and Meltdown
- Troubleshooting SQL backup failure with VSS
- Troubleshooting SQL T-Log backup failure with exit code Phoenix 318
- Troubleshooting the alert CloudCache unable to read write on Volume
- Troubleshoot Error registering Phoenix Server
- Troubleshoot error while editing backup sets
- Troubleshoot Oracle configuration issues
- Troubleshoot the error while deploying backup proxy
- Troubleshoot volume mounting error
- Unable Power on the Druva Phoenix Backup Proxy
- Unable to add a NAS device - Credentials invalid
- Unable to boot a P2V VM after a successful restore
- Unable to browse Files/Folder for FLR (File-level restore) for Hyper- V Restore
- Unable to create an organization administrator
- Unable to create new Administrator
- Unable to discovery Hyper-V VMs due to English package not installed
- Unable to discover Hyper-V VMs on Phoenix Management Console for Hyper-V host with non-English language
- Unable to discover the SQL Database
- Unable to login via SSO
- Unable to ping or RDP to the EC2 instance after a DR failover
- Unable to power on backup proxy
- Unable to update NAS Share credentials from Phoenix Management Console
- User databases gets skipped during SQL Appaware backup
- vCenter registration using desktop client fails
- Virtual machine refresh fails with the 'Failed to refresh vm list while deleting vms and vhost' error
- VMware: VM is not getting detected in the Phoenix console
- VMware app-aware backup process completes with a status of "Successful with Errors".
- VMWARE Appaware VM backup fails with error as unable to find IP Address of VM Object
- VMware app aware backups of SQL databases complete successfully with errors
- Vmware backups do not run as per the set timezone
- VMware backups fails for Windows 2008 R2 with winerror 1168
- VMware backups fails with error code PHOENIX127
- VMware Backups fails with error VMWARE VMOMI1
- VMware backups fail with error VMWARE VDDK1 and VMware logs show 'Failed to connect to peer'. Error: The remote host certificate has these problems.
- VMware backups fail with NFC errors
- VMware backups fail with VMWARE VMOMI1 error and VSS error 12289
- VMware backups fail with VMWARE VMOMI1 error and VSS error 8193
- VMware backups fail with VMWARE VMOMI65535 - A general system error occurred
- VMware backups in Phoenix fail with Error in reading data from the Disk
- VMware backups stay in the queued state with IO error Error 28 no space left on device
- VMware backups stuck at 0% and fails with Backup Window expired
- VMware backups to CloudCache fail with PHOENIX82 error
- VMware backup fails if auto-enabled CBT is selected for a VM with incompatible hardware
- VMware backup fails with error: VMWARE VMOMI65535-Unable to communicate with the remote host
- VMware backup fails with Failed to extract and set OS attributes collection from Prerequisites or VMX data
- VMware backup fails with message “Failed to extract and set OS attributes collection from Prerequisites or VMX data”
- VMware backup fails with the 'Backup Window Expired' error when the transport mode is changed from HotAdd
- VMware backup fails with the VMWARE VMOMI65535 error: File is larger than the maximum size supported by datastore
- VMware backup proxy activation fails because of special characters in the hostname
- VMware backup proxy activation fails when the backup proxy resides in vApp
- VMware Backup Proxy gives the permission missing errors when we try to activate it using the ProxyConf command in the VMC environment.
- VMware backup proxy not visible on Druva console
- VMware backup proxy not visible or the status is disconnected on Phoenix console
- VMware backup proxy not visible with the Unable to set vCenter credentials error
- VMware Backup Proxy OVF deployment fails
- VMware disk restore fails with Internal Error (Error Code : VMWARE VMOMI65535)
- VMware file-level restore fails with the error - Failed to browse the guest VM
- VMware FLR browse fails to mount volumes
- VMware FLR does not retain modified date to the restored folders
- VMWare FLR Restore getting browse time out
- Vmware Proxy Deployer fails to deploy proxy with Failed to call the OVA URL
- VMware proxy upgrade fails from the Phoenix console
- VMware SQL Application-Aware transaction log backup reports a canceled status
- VMware VM backups fails with Phoenix 1 Internal Error
- VMware VM Restore fails with Error VMWARE VDDK1
- VM backups fails with Invalid VCenter/ESXi host credentials
- VM backups fail in a Hyper-V Cluster configuration
- VM backups fail with error code VMWARE_VDDK1
- VM backup fails with 'Failed to find VM with UUID' error
- VM backup fails with error VMWARE VMOMI65535
- VM backup fails with INTERNAL65535
- VM backup fails with the error code VMOMI1 on a virtual machine running on Windows Server 2019
- VM backup fails with the INTERNAL65535 error - AttributeError NoneType object has no attribute product
- VM backup fails with the VMWARE VDDK65535 error
- VM backup fails with the VMWARE VDDK65535 error (memory allocation error)
- VM backup fails with VMWARE_VDDK65535 error after ESXi or vCenter certificate update
- VM backup failure due to insufficient space in the datastore
- VM backup job completes successfully but generates Event IDs 50, 57, 137, 140, or 12289 (2006849) on Windows virtual machine
- VM backup stalled with the error "got exception while parsing LCN and size from ntfscluster command” after a successful snapshot
- VM becomes unresponsive during a snapshot removal
- VM jobs get queued due to disconnected Backup Proxy status on Phoenix Console
- VM Loses Connection During Snapshot Removal
- VM not visible in Phoenix console due to missing UUID
- VM Restore to original location fails with Failed to find VM with UUID error
- VM vCenter proxy host deployment fails
- While performing VMware File Level Restore (FLR),files are getting skipped with info: “Skipping symbolic link” for NTFS De-Dedupe Volume
- While Upgrading, Uninstalling, Installing Druva Phoenix Agent on a Windows Server we get error “The feature you are trying to use is on a network resource that is unavailable”
- Windows File server backup stays in Queued where Pre-scripts are added in the policy
- How to
- No image available
- Best practices
- No image available
- FAQs and Reference Reads
- No image available
