Skip to main content

How can we help you?

Druva Documentation

DRaaS errors

This topic provides a list of Druva DraaS errors that you may encounter while working with Phoenix. 

AWS_DR4

Error Message: Bucket creation failed

Error Description: This error occurs due to one of the following reasons:

  • If the attached AWS IAM policy does not have sufficient permissions. OR
  • If you have exceeded bucket limit count on your AWS account.

Error Solution: To resolve this error:

  • Check the mentioned IAM policy on Druva portal. Verify that the content of the IAM policy attached to the IAM role matches the content defined in the DruvaIAMPolicy topic. OR
  • Contact Druva Support.

AWS_DR5

Error Message: S3 key does not exist

Error Description: This error occurs if the required keys are not found in the S3 bucket.

Error Solution: To resolve this error, contact Druva Support.

AWS_DR8

Error Message: No key present at specified to do multi-part upload

Error Description: This error occurs if the required keys are not present in the S3 bucket.

Error Solution: To resolve this error, contact Druva Support.

AWS_DR9

Error Message: Specified bucket does not exist.

Error Description: This error occurs if the required S3 bucket is not present.

Error Solution: To resolve this error, contact Druva Support.

AWS_DR12

Error Message: Attached policy do not have sufficient permissions.

Error Description: This error occurs if the attached AWS IAM policy does not have sufficient permissions.

Error Solution: To resolve this error:

  • Check the mentioned IAM policy on the Druva portal. Verify that the content of the IAM policy attached to the IAM role matches the content defined in the DruvaIAMPolicy topic. OR
  • Contact Druva Support.

AWS_DR18

Error Message: VMDK size is greater than 2 TB.

Error Description: This error occurs if the Cloud DR configured virtual machine has more than 2 TB size of VMDK.

Error Solution: Ensure that the maximum VMDK size does not exceed 2 TB.

AWS_DR19

Error Message: OS is not supported in AWS.

Error Description: This error occurs if cloud DR configured virtual machine is not supported in AWS.

Error Solution: Check the supported OS matrix in AWS documentation.

AWS_DR23

Error Message: Marking cloud DR request as stale.

Error Description: This error occurs if:

  • One update DR  copy request is in running state and four other update DR copy requests are in the queued state for the same virtual machine. After the first request completes, the next request from the pending queue will be picked. So out of the four queued requests, three will fail with AWS_DR23 error. OR
  • A Druva AWS proxy restarts while an update DR copy request is in running state and other requests are in a queue, the last request in the queue will be picked and the rest will fail.

AWS_DR24

Error Message: VM is not valid to create AMI.

Error Description: This error occurs when AWS import image operation fails.

Error Solution: To resolve this error:

AWS_DR26

Error Message: boto/boto3 has raised unauthorized operation error.

Error Description: This error occurs if the attached AWS IAM policy does not have sufficient permissions.

Error Solution: To resolve this error:

  • Check mentioned IAM policy on Druva portal. Verify that the content of the IAM policy attached to the IAM role matches the content defined in the DruvaIAMPolicy topic. OR 
  • Contact Druva Support.

AWS_DR28

Error Message: Unable to access AWS resources, check IAM policy.

Error Description: This error occurs if the attached AWS IAM policy does not have sufficient permissions.

Error Solution: To resolve this error:

  • Check mentioned IAM policy on Druva portal. Verify that the content of the IAM policy attached to the IAM role matches the content defined in the DruvaIAMPolicy topic. OR
  • Contact Druva Support.

AWS_DR29

Error Message: Unable to read file. Please retry later.

Error Description: This error occurs if the AWS API call fails due to the failure of the EC2 metadata service.

Error Solution: To resolve this error, verify that the content of the IAM policy attached to the IAM role matches the content defined in the DruvaIAMPolicy topic.

AWS_DR31

Error Message: EBS Volume storage limit is exceeded.

Error Description: This error occurs if the limit of the Amazon EBS volume storage is reached.

Error Solution: To resolve this error, check the limit of the AWS account storage. Ensure that the total size of all the virtual machines configured in the DR plan does not exceed the maximum AWS account storage limit. For more information, see Amazon EC2 service limits. [External link to AWS documentation].

AWS_DR32

Error Message: EBS Volume is attached to an instance.

Error Description: This error occurs:

  • At the time of the failover job if the EBS volume is attached to an EC2 instance, or
  • At the time of the update DR copy job if It is not successfully detached from the Druva AWS proxy EC2 instance

Error Solution: To resolve this error, check if the volume is used by an EC2 instance other than the Druva AWS proxy.

AWS_DR34

Error Message: EBS Snapshot creation limit is reached.

Error Description: This error occurs if the limit for creating the number of the Amazon EBS snapshots is reached.

Error Solution: To resolve this error, check the maximum number of EBS snapshots that can be created in the AWS account. For more information, see Amazon EC2 service limits. [External link to AWS documentation].

AWS_DR35

Error Message: Rate limit for creating concurrent snapshots of an EBS Volume has been exceeded.

Error Description: This error occurs if the rate limit for creating concurrent snapshots of an EBS volume is reached.

Error Solution: To resolve this error, check the number of the multiple snapshots of the same EBS volume created. For more information, see Amazon EC2 service limits. [External link to AWS documentation].

AWS_DR36

Error Message: Amazon EC2 Resource Limit exceeded.

Error Description: This error occurs if the limit of the AWS EC2 resource is reached.

Error Solution:  To resolve this error, check the maximum number of EC2 instances that can be created in the AWS account. For more information, see Amazon EC2 service limits. [External link to AWS documentation].

AWS_DR37

Error Message: The number of pending EBS snapshot has exceeded the limit.

Error Description: This error occurs if the limit of the number of pending AWS EBS snapshots is reached.

Error Solution: To resolve this error, check the limit of the maximum pending EBS snapshots allowed in the AWS account. For more information, see Amazon EC2 service limits. [External link to AWS documentation].

AWS_DR41

Error Message: The specified volume does not exist.

Error Description: This error occurs if the specified EBS volume is not present in the AWS account at the time of failover.

Error Solution: To resolve this error, check if the volume that is used by the Druva AWS proxy, is present in the AWS account.

AWS_DR46

Error Message: The specified snapshot does not exist.

Error Description: This error occurs if the specified EBS snapshot is not present in the AWS account at the time of failover.

Error Solution: To resolve this error, check if the snapshot that is used by the Druva AWS proxy, is deleted.

AWS_DR47

Error Message: The snapshot that you are trying to delete is in use by one or more AMIs.

Error Description: This error occurs if the deletion of the specified EBS snapshot fails because the snapshot is associated with one or more AMIs.

Error Solution: To resolve this error, check if the snapshot is present in the AMI.

AWS_DR53

Error Message: The specified EBS volume is not attached to an instance.

Error Description: This error occurs if the specified volume fails to attach to an EC2 instance.

Error Solution: To resolve this error,  check the total number of EBS volumes attached to the EC2 instance. The number should be less than 22 including the boot volume.

AWS_DR54

Error Message: The specified Amazon S3 URL cannot be accessed.

Error Description: This error occurs if the specified AWS S3 URL cannot be accessed due to insufficient permissions.

Error Solution: To resolve this error, check if the content at the S3 URL exists and has sufficient access permissions. Ensure that the IAM policy attached to the Druva AWS proxy matches the policy downloaded from the Management Console.

AWS_DR55

Error Message: The number of concurrent snapshots has exceeded the limit.

Error Description: This error occurs if the limit of creating the concurrent AWS EBS snapshots on a specified AWS EBS volume is reached.

Error Solution: To resolve this error, check the limit of the maximum concurrent snapshots in the AWS account. For more information, see Amazon EC2 service limits. [External link to AWS documentation].

AWS_DR57

Error Message: The number of EBS volume attached to an instance has exceeded the limit.

Error Description: This error occurs if the limit of attaching the number of AWS EBS volumes to an EC2 instance is reached.

Error Solution: AWS supports only 22 volumes. To resolve this error, detach any of the volumes excluding the boot volume. Perform the backup and DR restore again. 

AWS_DR58

Error Message: No device is available for attaching EBS volume.

Error Description: This error occurs if a device is not available for attaching the AWS EBS volume to the EC2 instance.

Error Solution: To resolve this error, check if the recently detached EBS volumes are completely detached. If the EBS volume is in the detaching state, the device later is unusable. Restart the Druva AWS proxy, if no jobs are running. 

AWS_DR65

Error Message: AMI doesn't exist.

Error Description: This error occurs if the AMI for failover is not present in the AWS account.

Error Solution: To resolve this error, check if the AMI for failover is available in the specified region of the AWS account. Run the update DR copy/DR restore job for the virtual machine to get a new DR copy and retry the failover job. 

AWS_DR67

Error Message: Retry limit exceeded for volume state.

Error Description: This error occurs if the specified EBS volume is not in the valid state for a long time.

Error Solution: To resolve this error, trigger a new update DR copy/DR restore job.

AWS_DR68

Error Message: Attempted to create more buckets than allowed.

Error Description: This error occurs if the limit of creating the number of AWS S3 buckets in the AWS account is reached.

Error Solution: To resolve this error, check the limit of creating the number of S3 buckets in the AWS account. Increase the limit of the number of S3 buckets. For more information, see Amazon S3 service limits. [External link to AWS documentation].

AWS_DR69

Error Message: Incorrect snapshot state

Error Description: This error occurs if the snapshot creation of the specified EBS volume fails because the snapshot is in the error state.

Error Solution: To resolve this error, trigger a new update DR copy/DR restore job.

AWS_DR82

Error Message: The request reached the service more than 15 minutes after the date stamp on the request.

Error Description: This error occurs if the AWS API call expires due to the unsynchronized system time or delay in reaching in the AWS server.

Error Solution: To resolve this error, check if the Druva AWS proxy time is in sync with the NTP server.

AWS_DR83

Error Message: A queue with this name/URI already exists.

Error Description: This error occurs if an SQS queue with the same name already exists.

Error Solution: To resolve this error, check if an SQS queue with the same name is created. If the queue is not created by Phoenix, delete the queue. The queue that Phoenix uses starts with the phrase: phoenix_. You can use this phrase to search for the queue.

AWS_DR85

Error Message: The specified queue doesn't exist.

Error Description: This error occurs if the required SQS queue is not present in the AWS account. The queue that Phoenix uses starts with the phrase: phoenix_. You can use this phrase to search for the queue.

Error Solution: To resolve this error, check if the SQS queue got deleted from the AWS account and run a new failover job. 

AWS_DR91

Error Message: You do not have sufficient access to perform this action.

Error Description: This error occurs if insufficient permissions are assigned to an IAM role.

Error Solution: To resolve this error, Verify that the content of the IAM policy attached to the IAM role matches the content defined in the DruvaIAMPolicy topic.

AWS_DR94

Error Message: The request has failed due to a temporary failure of the server.

Error Description: This error occurs if the AWS API call fails due to a temporary failure of the AWS server.

Error Solution: To resolve this error, retry the job.

AWS_DR95

Error Message: The request was denied due to request throttling.

Error Description: This error occurs if the AWS SQS API call is throttled by the AWS server.

Error Solution: To resolve this error, check the limit of the SQS requests handled by AWS.  For more information, see Amazon SQS Limits. [External link to AWS documentation.]

 

AWS_DR96

Error Message: Not enough free addresses in the subnet.

Error Description: This error occurs if the VPC subnet selected for failover does not have a free IP address.

Error Solution: In the AWS Management console, determine the number of available IP addresses in the selected VPC subnet. If the VPC subnet does not have any free IP addresses, terminate a few EC2 instances. Alternatively, select a different VPC subnet in the failover settings of your virtual machine.

AWS_DR102

Error Message: VMDK size greater than 16 TB is not supported.

Error Description: This error occurs if the DR configured virtual machine has a VMDK with size more than 16 TB.

Error Solution: Ensure that the size of the VMDK attached to the virtual machine configured for DR does not exceed 16 TB. 

AWS_DR116

Error Message: Security Group reconfiguration failed.

Error Description: AWS allows a maximum of five security groups to be assigned per EC2 instance by default. When the number of security groups assigned to the VM in the failover settings of the DR plan exceeds this maximum value, you may run into this issue. The failover succeeds, but the security group reconfiguration fails.

Error Solution: Ensure that the number of security groups assigned to the VM in the failover settings is lesser than the maximum value defined for your AWS account. Contact AWS support if you want to increase the maximum number of security groups you can assign per EC2 instance.

AWS_DR119

Error Message: Security group reconfiguration failed.

Error Description: You may run into this error if the security group does not exist.

Error Solution: The security group does not exist in the specified network or VPC. Check the VM failover settings and the network mapping settings to ensure that the security group belongs to the same network or VPC.

AWS_DR128

Error Message: AWS was not able to validate the provided access credentials. The authentication with Boto APIs failed possibly due to the following reason:

-System time of DR Proxy EC2 Instance not synchronized with AWS NTP Servers

Error Description: This error occurs when the Druva AWS proxy instance is out of sync with the AWS NTP servers.

Error Solution: To resolve this error synchronize the system time on the Druva AWS proxy instance with the AWS NTP servers using the following command sudo ntpdate 169.254.169.123

AWS_DR130

Error Message: Unable to locate Credentials.

Error Description: The Druva IAM role is attached to the Druva AWS proxy during its deployment. You may run into this error during a DR copy job if, for some reason, this role gets detached from the Druva AWS proxy.

Error Solution

 Identify the Druva AWS proxy used during the DR Restore job (Also referred to as DR copy job). Attach the Druva IAM role to this proxy using the AWS Management Console. Perform the following tasks to accomplish this:

  1. Log in to the AWS Management Console.
  2. Go to the EC2 service.
  3. In the left navigation pane, click Instances under Instances.
  4. Select the identified instance > Action > Security > Modify IAM role.

Select the DruvaIAMRolePL role from the drop-down list, and then click Save.

AWS_DR131

Error Message: Could not connect to EC2 endpoint URL

Error Description:  This error occurs when the Druva AWS proxy cannot access the AWS EC2 service.

Error Solution: To resolve this issue,

  • If you have an AWS EC2 endpoint, ensure it is associated with the subnet in which the Druva AWS proxy resides. Additionally, the security group associated with the AWS EC2 endpoint must allow HTTPs (Inbound and Outbound Rules) for the VPC CIDR of the Druva AWS proxy.
  • If you have not configured an AWS EC2 endpoint in your VPC then ensure that the Druva AWS proxy is able to reach AWS EC2 service via internet/NAT gateway.

AWS_DR132

Error Message: Could not connect to S3 endpoint URL

Error Description: This error occurs when the Druva AWS proxy is unable to access the AWS S3 service.

Error Solution:  If you have an AWS S3 endpoint in the VPC, ensure that the route table of the Druva AWS proxy's subnet is associated with the AWS S3 endpoint. If you have not configured an AWS S3 endpoint in your VPC then ensure that the Phoenix AWS Proxy is able to reach AWS S3 service via internet/NAT gateway.

AWS_DR255

Error Message: Boto3 Client encountered a generic error.

Error Description: This error occurs if the AWS API call fails due to a generic error.

Error Solution: To resolve this error, contact Druva Support.

DR1

Error Message: Phoenix Internal Error.

Error Description: This is an internal error.

Error Solution: To resolve this error, contact Druva Support.

DR2

Error Message:  Phoenix Internal Error.

Error Description: This is an internal error.

Error Solution: To resolve this error, contact Druva Support.

DR3

Error Message:  Insufficient space to write on the EBS volume.

Error Description: This error occurs when the EBS volume does not have adequate space for the DR copy data.

Error Solution: To resolve this error, retry the DR copy job. For further assistance, contact support.

DR4

Error Message:  Phoenix Internal Error.

Error Description: This is an internal error.

Error Solution: To resolve this error, contact Druva Support.

DR5

Error Message:  Phoenix Internal Error.

Error Description: This is an internal error

Error Solution: To resolve this error, contact Druva Support.

DR6

Error Message: DR Restore not supported.

Error Description: This error occurs if:

  • A VMDK is excluded from  the virtual machine backup.

Error Solution: Ensure that the disk is not excluded from the backup of the virtual machine.

DR7

Error Message: Update DR copy/DR Restore job skipped since the Druva AWS proxy associated with the job is disconnected.

Error Description: This error occurs if the DR restore job is skipped because the Druva AWS proxy associated with the job is disconnected.

Error Solution: Ensure that the Druva AWS proxy with version 4.8.0 or later is connected to Phoenix Cloud. 

DR8

Error Message: Last DR Restore of the VM is running on a Druva AWS proxy which is unavailable.

Error Description: This error occurs when an update DR copy/DR restore job is already running and you run another DR restore job. 

Error Solution: You must manually cancel the first DR restore job of a virtual machine for which the associated Druva AWS proxy is disconnected.

DR9

Error Message: Can not start DR restore. No upgraded Druva AWS proxy available for server, Please upgrade.

Error Description: This error occurs when the Druva AWS proxy is in the disconnected state and the DR restore operation fails. 

Error Solution: Ensure that the Druva AWS proxy is up and running during the DR restore operation. Ensure that at least one Druva AWS proxy with 4.8.0 or later is connected to the Phoenix Cloud.

DR10

Error Message: VM removed from DR plan.

Error Description: This error occurs when a virtual machine is deleted from the DR plan for which the DR restore job is in progress.

Error Solution: To resolve this error, ensure that the virtual machine is configured for the DR plan.

DR11

Error Message: Transient error occurred, Please retry restore job again.

Error Description: This transient error occurs if the Druva AWS proxy is reconnecting to the Phoenix server while copying the data to the Druva S3 bucket.

Error Solution: To resolve the error, retry the Update DR Copy (DR restore) job.

DR12

Error Message: DR Restore job skipped as we have upgraded proxy deployed.

Error Description: This error occurs if you deploy the proxy version 4.8.0 or later but:

  • This DR restore job was in the queued state on the older proxy (4.7.6 or earlier)
  • New update DR copy (DR restore) jobs are added to the  Druva AWS proxy version 4.8.0 or later

Error Solution: Only older queued jobs fail. New update DR copy (DR restore) jobs run on the Druva AWS proxy version 4.8.0 or later. 

DR13

Error Message: DR Restore marked as skipped as new restore request received for same DR Plan and VM.

Error Description: This error occurs when multiple DR restore jobs are triggered for the same DR plan and the same virtual machine. In this case, the last triggered job is processed and all the previous jobs are marked as skipped.

DR14

Error Message: DR Running Restore job's timeout & expired.

Error Description: This error occurs when a DR restore job, which is currently in the running state, exceeds the timeout period of 3 days and expires due to the unavailability of the Druva AWS proxy. 

Error Solution: To resolve the error, ensure that the Druva AWS proxy is connected to the Druva Cloud .

DR15

Error Message: Write failed on the EBS volume.

Error Description: This error occurs when the DR copy job is unable to write to the EBS volume because of an IO error.

Error Solution: To resolve this error, retry the DR copy job.

DR4097

Error Message: No Bootable disk found.

Error Description: This error occurs if the bootable disk is not found during the instance boot because of the following reasons:    

  • The bootable disk is excluded from the backup.
  • The bootable disk has an unsupported File system, therefore, the disk cannot be mounted. 
  • The disk partition scheme has an LVM or LDM setup and one of the disks is excluded from the backup, therefore, the disk cannot be mounted.
  • If the boot order is incorrect in the VMX file provided by the virtual machine

Error Solution: To resolve the error:

  • Check if FLR is working for the virtual machine to verify if this is a boot disk.  
  • Check if the original virtual machine is in the consistent state and is bootable.
  • Perform an alternate virtual machine restore and check if the restored virtual machine is bootable.

DR4098

Error Message: Instance is not reachable from AWS SQS.

Error Description: This error occurs when the failover instance cannot reach AWS SQS.

Error Solution: To resolve this error:

  • If SQS endpoint is configured, check if the configured subnet for failover instance is associated with the SQS endpoint. 
  • If SQS endpoint is not configured, ensure that the instance launched in public subnet must have a public IP address and the instance that is launched in a private subnet does not have a public IP address. Do not select isolated subnets.

    For more information, see How to fix the failover failure when an instance is not reachable from AWS SQS.

DR4099

Error Message: OS is not supported.

Error Description: This error occurs if Phoenix does not support the operating system of the virtual machine that you want to configure for disaster recovery. 

Error Solution: To resolve this error, ensure that you configure virtual machines for disaster recovery whose operating systems are supported by Druva DraaS. For more information, see Support matrix.

DR4100

Error Message: Agent: failed to start failover.

Error Description: This error occurs if the Druva AWS proxy fails to update the instance status for the virtual machine. See the client logs for more details. 

Error Solution: To resolve this error, check the client logs for details. Contact Druva Support.

DR4102

Error Message: Requested failover job was running for more than 24 hrs. Marking it as failed.

Error Description: This error occurs if the failover instance is in the requested or initializing state for more than 24 hours. This occurs when the Druva AWS proxy abruptly exits and fails to update the instance status on the server.

Error Solution: To resolve this error:

  • Check if the Druva AWS proxy is connected and the Druva server is running.
  • Check if the Druva AWS proxy is configured with the necessary permissions.

DR4103

Error Message: Failover failed for all VMs in DR plan.

Error Description: This error occurs if the failover fails for all the virtual machines associated with a DR plan. 

Error Solution: To resolve this error, check the job summary details.

DR4104

Error Message: DR copy on the customer's AWS account was never created. 

Error Description: This error occurs if the DR restore was never triggered for the virtual machine.

Error Solution: To resolve this error, trigger update DR copy (DR restore) for the virtual machine.

DR4105

Error Message: DR copy using the Druva AWS proxy version 4.8.0 or later was never created.

Error Description: This occurs when the first DR restore job is triggered for the virtual machine but the job ends abruptly or it expires. 

Error Solution: To resolve this error, run the update DR copy (DR restore) job for the virtual machine.

DR4106

Error Message: DR copy using the Druva AWS proxy version 4.7.6. or earlier was never created.

Error Description: This occurs when the DR restore job is triggered for the virtual machine but the job ends abruptly or it expires.

Error Solution: To resolve this error, run the update DR copy (DR restore) job for the virtual machine.

DR4107

Error Message: Selected VM is unconfigured from the DR plan.

Error Description: This error occurs if the virtual machine gets unconfigured from the DR plan while triggering the DR failover.

Error Solution: To resolve this error, check if the virtual machine is configured for disaster recovery.

DR4108

Error Message: Selected VM's backup set is deleted.

Error Description: This error occurs if the backup set associated with a virtual machine is deleted while triggering the DR failover.

Error Solution: To resolve this error, check if the virtual machine is configured for backup.

DR4109

Error Message: One or more VM's failover failed in DR plan.

Error Description: This error occurs if the failover triggered for the virtual machine fails.

Error Solution: To resolve this error, check the summary details of the failover job.

DR4111

Error Message: Current proxy is incompatible to do failover. If DR copy is updated using Druva AWS proxy version 4.8.0 or later, need Druva AWS proxy version 4.8.0 or later for failover.

Error Description: This error occurs if the virtual machine is restored using the latest proxy and has the EBS snapshot, however, the failover is triggered on the virtual machine with the older proxy.

Error Solution: To resolve this error, ensure that the latest Druva AWS proxy is connected.

DR4119

Error Message: Failover got aborted as recovery workflow step is failed. 

Error Description: This error occurs when the recovery workflow stops at a particular step due to the failure of that step. For example, if an error occurs during the execution of a post-boot script, and you have enabled the checkboxes to abort failover on the failure of the VM Boot and script execution steps for the virtual machine, the recovery workflow fails.

Error Solution: To resolve this error, disable the Abort recovery operation if any VM in this boot step fails to boot checkbox to continue the workflow execution. Else, correct the respective script for the virtual machine.

DR4121

Error Message: Failed to reconfigure security group.

Error Description: This error occurs if the association of the security group to the failover instance during failover fails.

Error Solution: Contact Druva Support.

DR4122

Error Message: Failed to change IAM role of the failed over instance.

Error Description: This error occurs if the association of the IAM role to the failover instance during failover fails.

Error Solution: Contact Druva Support.

DR4124

Error Message: Phase-1 of VM conversion into AWS EC2 instance is timed out.

Error Description: This error occurs when an AWS driver ingestion for converting a virtual machine into an AWS EC2 instance exceeds the expected time.

Error Solution: To resolve this error, perform the following:

  • Retry by upgrading the failover instance type corresponding to your source virtual machine configuration.
  • Ensure that you use the supported operating system as listed in the Support matrix.

DR4125

Error Message: Phase-2 of VM conversion into AWS EC2 instance is timed out.

Error Description: This error occurs when an AWS driver ingestion for converting a virtual machine into an AWS EC2 instance exceeds the expected time.

Error Solution: To resolve this error, perform the following:

  • Retry by upgrading the failover instance type corresponding to your source virtual machine configuration.
  • Contact Druva Support.

DR4126

Error Message: Phase-3 of On-Boot script execution timed out.

Error Description: This error occurs if the script timeout specified is less than the actual time taken for the script execution.

Error Solution: To resolve this error, perform the following steps:

  1. On the Job Details page, click Download Job Logs for the failover job.
  2. In the PhoenixLogs-<JobID>.zip file, and navigate to the PhoenixLogs-<JobID>/failover/<number>/Phoenix.<timestamp>-<JobID>.zip/Phoenix-TW-<timestamp>-<JobID>_phase3.zip/Logs folder.
  3. Verify the phase 3 logs and add sufficient time for the script execution.

DR4130

Error Message: Failover instance is not moving into the running state.

Error Description: This error occurs if the EC2 instance is stuck in the pending state although the failover operation is completed.

Error Solution: To resolve this error, verify the state of the EC2 instance on the AWS Management Console. If the state of the instance is stuck in the pending state beyond 10 minutes,  restart the EC2 instance.

DR4131

Error Message: Failed to resume Failover. Please retry Failover for the specified VM.

Error Description: This error occurs if the client got restarted and the failover could not be resumed for the virtual machine.

Error Solution: To resolve this error, you can retry failover for the virtual machine by selecting the individual virtual machine on the Production or Test Failover page.

DR8191

Error Message: Server: Internal Error.

Error Description: This error occurs if the Phoenix Cloud failed to run the job. 

Error Solution: Contact Druva Support

DR8195

Error Message: System command required for conversion not found.

Error Description: This error occurs if one of the system commands required for the conversion is not found on the source virtual machine.

Error Solution: To resolve this error, check the error text on the Management Console. If the command is not found on the source virtual machine:

  1. Install the required package for the command
  2. Backup the virtual machine
  3. Update DR copy

Note: Commands that are needed on the virtual machine are basic system commands such as blkid, mount, mkinitrd etc.  

DR8197

Error Message: Command timed out during execution.

Error Description: This error occurs if one of the commands required for the conversion took more time than expected.

Error Solution: To resolve this error, run the command on the source virtual machine. If the command execution is stuck, resolve the command execution.  

DR8198

Error Message: Failed to access mount point.

Error Description: This error occurs if one of the mount points on the virtual machine is not accessible.

Error Solution: Verify if the NFS/CIFS mounts mentioned in the /etc/fstab file are working on the source virtual machine. Remove the access points which are inaccessible.

DR8207

Error Message: The kernel module specific for the version cannot be found.

Error Description: This error occurs if the kernel module compatible with the virtual machine kernel version is not found.

Error Solution: To resolve this error,  check if the kernel version on the source virtual machine is a stable version. Else, upgrade the kernel version to a stable version.

DR8209

Error Message: Failed to install grub2

Error Description: This error occurs when the grub installation on the virtual machine fails as the grub legacy or grub2 is not installed on the virtual machine.

Error Solution: To resolve this error, check if the grub package is not installed on the virtual machine and the automatic installation fails on the source virtual machine. Install grub2 on the source system manually.

DR8210

Error Message: VM has no grub (grub-legacy or grub2) installed.

Error Description: This error occurs if the grub legacy or grub2 package is not installed on the virtual machine.

Error Solution: To resolve this error, ensure that grub-legacy or grub2 is installed on the source virtual machine. Else, install the grub package on the source virtual machine.

DR8215

Error Message: Execution was possibly blocked by the anti-virus

Error Description: This error occurs if the required command execution is blocked by antivirus on the virtual machine.

Error Solution: To resolve this error, either whitelist the command execution, or disable the antivirus, or uninstall the anti-virus on the source virtual machine, and then:

  1. Backup the virtual machine
  2. Update DR copy

DR8217

Error Message: EBS volume is corrupted.

Error Description: This error occurs if one or more EBS volumes on the virtual machine are corrupted.

Error Solution: To resolve this error, run the fsck command on the source virtual machine and check for the errors or any unusual output.

DR8218

Error Message: Unsupported partition type - MS shadow copy partition.

Error Description: This error occurs if the MS Shadow Copy partition is present in the virtual machine. Druva disaster recovery does not support disks with MS Shadow Copy partition.

Error Solution: To resolve this error, remove the drive with the MS Shadow partition.

DR8219

Error Message: The disk for volume with the assigned drive letter could not be brought online.

Error Description: This error occurs if the disk cannot be brought online.

Error Solution: To resolve this error, bring the disk online manually on the source virtual machine.

DR8220

Error Message: System volume was not found on any of the attached disks.

Error Description: This error occurs if the system volume information is not found on the virtual machine.

Error Solution: To resolve this error, check if the system volume is present on the source virtual machine.

DR8221

Error Message: Registry folder was not found on any of the attached disks.

Error Description: This error occurs if the registry folder should is not present on the virtual machine.

Error Solution: To resolve this error, check if the registry folder exists on any of the volumes of the attached disks.

DR8224

Error Message: FileSystem type is not supported.

Error Description: This error occurs if the FileSystem type of one of the volumes is not supported.

Error Solution: To resolve this error, ensure that Druva DraaS supports the FileSystem type. For more information about the supported FileSystem Types, see Druva DraaS Support matrix.

DR8225

Error Message: Unable to identify partition using parted command.

Error Description: This error occurs if the parted command is unable to identify the disk partition of the virtual machine.

Error Solution: To resolve this error, run the parted command manually and check for any unusual output on the source virtual machine.

DR8228

Error Message: AWS API Call Error.

Error Description: This error occurs if the failover instance fails to call the AWS S3 or SQS APIs that are required for failover.

Error Solution: To resolve this error, check if the failover instance has enough permissions of EC2, S3, and SQS. Check the IAM policy associated with the failover instance.

DR8229

Error Message: S3 Bucket does not exist or no permission to access.

Error Description: This error occurs if the failover instance does not have sufficient permissions to connect to the AWS S3 bucket.

Error Solution: To resolve this error, check if the failover instance has enough permissions of AWS S3. Check the IAM policy associated with the failover instance.

DR8231

Error Message: Not all drive letters were mounted

Error Description: This error occurs if one or more drives fail to mount during failover.

Error Solution: To resolve this error, check manually if any drive is not mounted on the source virtual machine. Else, mount the drive.

DR8232

Error Message: Generic Error occurred during attribute collection

Error Description: This error occurs if an incorrect attribute is collected during failback.

Error Solution: Contact Druva Support.

DR8233

Error Message: Failed to collect information of network interfaces as mandatory commands might be missing

Error Description: This error occurs if Phoenix fails to collect the network interface information on the source virtual machine due to missing commands. For example, due to missing ip or ifconfig commands, the backup proxy fails to collect the NIC details.

Error Solution: To resolve the error, check if all the NIC commands are working. Else, contact Druva Support.

DR8234

Error Message: User is not allowed to execute command

Error Description: This error occurs if Phoenix fails to execute a command on the source virtual machine due to insufficient privileges of the user.

Error Solution: To resolve this error, check if the user is able to log into the source EC2 instance and can run the sudo command. For more information on creating a sudo user and enabling SSH access to the user, refer to the following documentation:

DR8235

Error Message: User is not allowed to run sudo on host

Error Description: This error occurs if the configured user is not allowed to run the sudo command on the source virtual machine.

Error Solution: To resolve this error, check if the user is able to log into the source EC2 instance and can run the sudo command. For more information on creating a sudo user and enabling SSH access to the user, refer to the following documentation:

DR8236

Error Message: User is not in sudoers file

Error Description: This error occurs if the configured user is not listed in sudoers file.

Error Solution: To resolve this error, check if the user is able to log into the source EC2 instance and can run the sudo command. For more information on creating a sudo user and enabling SSH access to the user, refer to the following documentation:

DR8238

Error Message: requiretty is not disabled in sudoers file

Error Description: This error occurs if requiretty is enabled for a command or the specified user is not available in the sudoers file.

Error Solution: To resolve this error, disable requiretty on the source EC2 instance and try again.

DR8239

Error Message: Failed to collect OS CPU information

Error Description: This error occurs if Phoenix fails to collect the CPU information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following:

  • Check the progress logs and identify the command that failed.
  • Get the job logs and find the attribute command that failed.
  • Contact Druva Support.

DR8240

Error Message: Failed to collect OS hardware information

Error Description: This error occurs if Phoenix fails to collect the operating system hardware information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following:

  • Check the progress logs and identify the command that failed.
  • Get the job logs and find the attribute command that failed.
  • Contact Druva Support.

DR8241

Error Message: Failed to collect OS memory information

Error Description: This error occurs if Druva fails to collect the operating system memory information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following:

  • Check the progress logs and identify the command that failed.
  • Get the job logs and find the attribute command that failed.
  • Contact Druva Support.

DR8242

Error Message: Failed to collect OS dhcp information

Error Description: This error occurs if Druva fails to collect the network information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following:

  • Check the progress logs and identify the command that failed.
  • Get the job logs and find the attribute command that failed.
  • Contact Druva Support.

DR8243

Error Message: Failed to collect OS hostname

Error Description: This error occurs if Druva fails to collect the operating system hostname information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if the hostname command is present on the source virtual machine and works correctly.
  • Contact Druva Support.

DR8244

Error Message: Failed to collect OS architecture information.

Error Description: This error occurs if Druva fails to collect the operating system architecture information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if the uname or wmic command is present on the source virtual machine and works correctly.
  • Contact Druva Support.

DR8245

Error Message:Failed to collect OS kernel information

Error Description: This error occurs if Druva fails to collect the operating system kernel information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if the uname command is present on the source virtual machine and works correctly.
  • Contact Druva Support.

DR8246

Error Message: Failed to collect OS attributes collection

Error Description: This error occurs if Druva fails to collect the operating system attributes from the source virtual machine during failback.

Error Solution: Contact Druva Support.

DR8247

Error Message: Failed to collect OS release data

Error Description: This error occurs if Druva fails to collect the operating system release information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if the uname or systeminfo command is present on the source virtual machine and works correctly.
  • Contact Druva Support.

DR8248

Error Message: Failed to collect OS lvm information

Error Description: This error occurs if Druva fails to collect the operating system logical volume details from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if lvm2 (Logical Volume Manager) is installed on the source virtual machine and the following commands work correctly: vgscan, lvs, pvs, lvdisplay, vgdisplay.
  • Contact Druva Support.

DR8249

Error Message: Failed to collect OS storage information

Error Description: This error occurs if Druva fails to collect the operating system storage information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if the following commands are present on the source virtual machine and work correctly: df, du, btrfs, diskpart, get-disk, get-partition.
  • Contact Druva Support.

DR8250

Error Message: Failed to collect OS mount information

Error Description: This error occurs if Druva fails to collect the operating system mount information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if the mount command is present on the source virtual machine and works correctly.
  • Contact Druva Support.

DR8251

Error Message: Failed to collect OS disk information

Error Description: This error occurs if Druva fails to collect the operating system disk information from the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Check if the following commands are present on the source virtual machine and work correctly: lsblk, fdisk, parted, lvmtoolsdiskpart. Retry failback.
  • Contact Druva Support.

DR8252

Error Message: Failed during attribute collection

Error Description: This error occurs if an unexpected issue occurs during attribute collection from the source virtual machine. Or the virtual machine is not compatible. See the Support Matrix

Error Solution: Contact Druva Support.

DR8253

Error Message: Failed to collect OS filesystem information

Error Description: This error occurs if Druva fails to collect the filesystem information on the source machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Windows: Ensure that the fsutil or msinfo32 command is present on the source EC2 instance.
  • Linux: Ensure that one of the following commands is present on the source EC2 instance: df, lsblk, mount, fsck.
  • Contact Druva Support.

DR8254

Error Message: Cache Logical Volumes were found on the source

Error Description: This error occurs if the Cache Logical Volumes are found on the source virtual machine during failback.

Error Solution:  To resolve this error, perform the following actions:

  • Remove the Cache Logical Volumes from the EC2 instance and trigger failback.
  • Contact Druva Support.

DR8255

Error Message: Snapshot Logical Volumes were found on the source

Error Description: This error occurs if Snapshot Logical Volumes are found on the source virtual machine during failback.

Error Solution: To resolve this error, perform the following actions:

  • Remove the Snapshot Logical Volumes from the EC2 instance and trigger failback.
  • Contact Druva Support.

DR8256

Error Message: Thin Logical Volumes were found on the source

Error Description: This error occurs if Logical Volumes are found on the source virtual machine during failback.

Error Solution:  To resolve this error, perform the following actions:

  • Remove the Logical Volumes from the EC2 instance and trigger failback.
  • Contact Druva Support.

DR8257

Error Message: Failed to disable services of source cloud

Error Description: This error occurs if a failure occurs while disabling the cloud-specific service on the source virtual machine during failback.

Error Solution: Contact Druva Support.

DR8259

Error Message: Failed to disable VMware timesync plugin

Error Description: This error occurs if Druva fails to disable the VMware timesync plugin while converting the source virtual machine into the target virtual machine.

Error Solution: To resolve this error, perform the following actions:

  • Disable the VMware timesync plugin works correctly on the source machine.
  • Contact Druva Support.

DR8260

Error Message: Failed to install VMware tools.Not enough free disk space

Error Description: This error occurs if the installation of the VMware tools on the target virtual machine fails due to insufficient disk space on the virtual machine.

Error Solution: To resolve this error, perform the following actions:

  • Increase the disk space of the virtual machine and install VMware tools.
  • Contact Druva Support.

DR8261

Error Message: Failed to install VMware tools probably due to missing dependencies

Error Description: This error occurs if the installation of the VMware tools on the target virtual machine fails due to some dependencies.

Error Solution: Contact Druva Support.

DR8262

Error Message: WMI query failed

Error Description: This error occurs due to multiple reasons when queries to wmi fail.

Error Solution: To resolve this error, refer to the following documentation:

DR8263

Error Message: Admin share cannot be found

Error Description: This error occurs if the  SMB/admin share of the source EC2 instance is not reachable.

Error Solution:

Note: We recommend running DR Failback Checks using VMware backup proxy of version 6.0.4 or later before triggering the DR Failback job.

To verify the access the  SMB share, run the <ip-of-ec2>/Admin$ command on in the Windows > Run field from any Windows computer.

If the access is denied, perform the following steps on the failover instance:

  1. Ensure that the security group associated with the EC2 instance allows ports 445 and 50000 in the inbound rules. All ports must be allowed in the outbound rules.

    DRaas error message correctionv2.png
     
  2. Enable rules for port 445 and port 50000:
    1. Login to the EC2 instance as an Administrator user.
    2. Open the Windows Firewall with Advanced Security console.
    3. Go to Inbound Rules.
    4. Open the port 445 and port 50000. Select the rule and click Enable Rule.
      SMB.JPG
  3. If on-premise network firewall exists:
    Whitelist port 445 and 50000 over the on-premise network firewall from vCenter network to the Failover instance.

DR8264

Error Message: Source Component has failed

Error Description: This error occurs if any source component fails.

Error Solution: To resolve this error, contact Druva Support.

DR8265

Error Message: Failed to connect to the source

Error Description: This error occurs if a backup proxy fails to connect to the EC2 instance, which is selected for failback.

Error Solution: To resolve this error, perform the following:

  • Verify if the EC2 instance is online on the AWS Management Console.
  • Try to connect the EC2 instance to backup proxy.
  • Contact Druva Support.

DR8266

Error Message: Failed to connect to the source, credentials are invalid

Error Description: This error occurs if you provide invalid credentials of an EC2 instance while initiating a failback.

Error Solution: To resolve this error, perform the following:

  • Verify if the EC2 instance is online on the AWS Management Console.
  • Try to connect the EC2 instance to backup proxy.
  • Contact Druva Support.

DR8267

Error Message: Failed to connect to the source, share not available

Error Description: This error occurs if the source virtual machine is not reachable from the target virtual machine or the SMB service is not accessible from the target virtual machine.

Error Solution: Contact Druva Support.

DR8269

Error Message: Failed to match volume serial number

Error Description: This error occurs if Druva fails to map the source machine devices to target machine devices.

Error Solution: Contact Druva Support.

DR8270

Error Message: Failed to execute Win32_ShadowStorage WMI query

Error Description: This error occurs when Druva fails to collect the hardware information of the operating system.

Error Solution: Contact Druva Support.

DR8271

Error Message: VMware tools installation failed to install vmtools service

Error Description: This error occurs if the installation of VMware tools fail on the target virtual machine.

Error Solution: Contact Druva Support.

DR8272

Error Message: Snapshot on one or more volumes failed - there is not a sufficient storage available for snapshot creation

Error Description: This error occurs if the source EC2 instance does not have enough storage space to create a snapshot.

Error Solution: Contact Druva Support.

DR8273

Error Message: Volume size mismatch detected. One or more source volumes were resized, data transfer cannot continue

Error Description: This error occurs if the size of one or more volumes is changed on the EC2 instance when a failover job is running.

Error Solution: To resolve this error, perform the following actions:

  • Retrigger the failback job. Do not change the size of any volume when a failover job is running.
  • Contact Druva Support.

DR8274

Error Message: One of volumes selected for data transfer does not exist on source any more

Error Description: This error occurs if one or more volumes are removed, deleted, or unmounted from the EC2 instance when a failover job is running.

Error Solution: To resolve this error, perform the following actions:

  • Retrigger the failback job. Do not remove, delete, or unmount any volume when a failover job is running.
  • Contact Druva Support.

DR8278

Error Message: Partition creation failed

Error Description: This error occurs if Druva fails to create partitions on the target virtual machine similar to that on the source virtual machine

Error Solution: Contact Druva Support.

DR8279

Error Message: snapshot was deleted on the source

Error Description: This error occurs if one or more snapshots used by the Hybrid Workloads agent is deleted on the source virtual machine due to insufficient VSS space.

Error Solution: Contact Druva Support.

DR8280

Error Message: Failed to read volume

Error Description: This error occurs if Druva fails to read one of the volumes present on the source virtual machine.

Error Solution: Contact Druva Support.

DR8281

Error Message: Failback already running on source

Error Description: This error occurs if Druva identifies another failback process running on the source virtual machine.

Error Solution: Contact Druva Support.

DR8283

Error Message: Failed to take VSS Snapshot set of selected volumes

Error Description: This error occurs if Druva fails to take VSS snapshot on the source virtual machine because one of the failed VSS writers.

Error Solution: Contact Druva Support.

DR8284

Error Message: The target worker instance did not configure properly

Error Description: This error occurs if the target virtual machine fails to parse data correctly.

Error Solution: Contact Druva Support.

DR8285

Error Message: Unable to shutdown source

Error Description: This error occurs if Druva fails to shut down the source virtual machine.

Error Solution: Contact Druva Support.

DR8288

Error Message: Failed to find /etc/fstab

Error Description: This error occurs if /etc/fstab could not be located on the source EC2 instance.

Error Solution: To resolve this issue, ensure that /etc/fstab is present on the source EC2 instance to failback.

DR8289

Error Message: Failed to find device or file-system mentioned in /etc/fstab

Error Description: This error occurs if the devices or file system specified in /etc/fstab is not present on the source EC2 instance.

Error Solution: To resolve this issue, verify that the devices and the file system specified in the /etc/fstab file is present on the source EC2 instance.

DR8290

Error Message: No file system is set to be mounted at /

Error Description: This error occurs occur if no file system is mounted at root.

Error Solution: To resolve this error, check manually if the file system is mounted on the source EC2 instance. Else, mount the files ystem.

DR8291

Error Message: Destination host is not routable or cannot be resolved.

Error Description:  This error can occur during a DR failback if the failover EC2 instance has stopped, terminated, or is not reachable from the failback VM. This error can occur during DR Failback Checks if the failover EC2 instance has stopped, terminated, or is not reachable from the VMware backup proxy.

Note: This message is displayed as a warning in DR Failback Checks where the VMware backup proxy is version 6.0.4. Here we are checking connectivity to the failover EC2 instance via the VMware proxy network.

Error Solution: To resolve this error, ensure that:

  1. Ensure that the failover EC2 instance is running during a DR failback.
  2. If the error occured during a DR failback, ensure that the failover EC2 instance is reachable from the selected destination network i.e. vCenter/ESXi Network. The destination network settings are defined in the Destination VMware Settings tab in the Failback Settings.
  3. If the error occurred during the DR Failback Checks, ensure that the failover EC2 instance is reachable from the network associated with the VMware backup proxy in the selected backup proxy pool. 
  4. If the Failover EC2 instance runs the Linux OS, ensure that port 22 is allowed in the inbound rules of the security group attached to the failover EC2 instance.

    8291.png
  5. If the failover EC2 instance runs the Windows OS, ensure that port 445 and port 50000 are allowed in the inbound rules of the security group attached to the Failover EC2 Instance.
    1. To verify access to the SMB share, run the <ip-of-ec2>/Admin$ command from the Windows > Run box on any Windows computer.

    2. If the access is denied, perform the following steps on the failover EC2 instance:

      1. Ensure that the security group associated with the EC2 instance allows ports 445 and 50000 in the inbound rules. All ports must be allowed in the outbound rules. 

      2. Enable rules for port 445 and port 50000:

        1. Login to the EC2 instance as an Administrator.

        2. Open the Windows Firewall with Advanced Security console.

        3. Go to Inbound Rules.

        4. Open the port 445 and port 50000. Select the rule and click Enable Rule
      3. If there is an on-premise network firewall, then whitelist port 445 and 50000 over the on-premise network firewall from the vCenter network to the failover instance.

DR8292

Error Message: Failed to start conversion service on source machine due to failed dependencies or service getting blocked by Anti-Virus

Error Description: This error occurs if the source EC2 instance has some dependencies missing or services blocked by the antivirus.

Error Solution: To resolve this error, whitelist the command execution or disable the antivirus, or uninstall the anti-virus on the source EC2 instance. Also, ensure all the dependencies are present.

DR8293

Error Message: Credentials are invalid

Error Description: This error occurs if the source EC2 instance credentials are invalid.

Error Solution: To resolve this error, ensure that the source EC2 instance credentials are valid.

DR8294

Error Message: OS present on source machine is not supported

Error Description: This error occurs if the operating system of the source EC2 instance is not supported for failback support matrix.

Error Solution: To resolve this error, please check if the operating system of the source EC2 instance is supported for failback. See Support matrix.

DR8295

Error Message: SSH pwauth is disabled in the cloud_init file. If you proceed you might not be able to login to the target instance/VM.

Error Description: You may get this warning during DR failover or DR failback. The following configurations in the cloud_init file may cause issues with the login:

  • SSH pwauth is disabled in the cloud_init file. 
  • Lock password is enabled in the cloud_init file.

Error Solution: To resolve this error, enable SSH pwauth and disable the lock password in the cloud-init file on the source EC2 instance.

DR8296

Error Message: Source does not have enough free space on {mountpoint}. Minimum 1757.81 Mb space is required.

Error Description: You get this warning during the DR failback checks if the Linux Failover EC2 Instance does not have sufficient storage space of 2 GB on the mentioned volume.

Error Solution: For a successful DR failback, make sure that more than 2 GB free space is available on the volume mentioned in the error message.

DR8297

Error Message: rsync error occurred

Error Description: This error occurs when the rsync command on the source virtual machine is broken.

Error Solution: To resolve this error, ensure that the rsync command on the source virtual machine works correctly.

DR8298

Error Message: Some dependencies are missing on source machine

Error Description: This error occurs when the perl and ifconfig commands, which are needed for the installation of VMware tools, are not installed on the source EC2 instance. 

Error Solution: To resolve this error, install the perl and ifconfig commands on the source EC2 instance.

DR8299

Error Message: SSH Connection error occurred between source and target machine

Error Description: This issue occurs during the attribute collection phase. This issue occurs due to a connectivity issue between the target virtual machine and the source EC2 instance.

Error Solution: To resolve this error, perform the following actions:

  1. Check the connectivity of the source virtual machine from the local network where the target virtual machine is deployed.
  2. Check the AWS security group of the source EC2 instance and ensure that the inbound port 22 is open.

DR8300

Error Message: /etc/fstab configuration error occurred

Error Description: This issue occurs when the root mount is included in the exclude mount or the mount point has an unsupported LVM layout. LVM supports only the linear logical volumes.

Error Solution: To resolve this error, refer to the Support matrix. Contact Druva Support.

DR8301

Error Message: Password of source machine is either expired or must be changed

Error Description: This error occurs when the password of the source EC2 instance expires or changes.

Error Solution: To resolve this error, log into the source EC2 instance with the valid credentials. Contact Druva Support.

DR8302

Error Message: sudo configuration on source machine caused error

Error Description: This issue occurs when sudo is configured with the requiretty setting and the NOPASSWD is not set for the user in the sudoers file.

Error Solution: To resolve this error, see How to set up sudo privileges.

DR8303

Error Message: Destination port is not reachable. Firewall blocks or port is different.

Error Description: This error can occur during a DR Failback if the failover EC2 instance is reachable from the selected destination network i.e. vCenter/ESXi Network (defined in the Destination VMware Settings tab in the Failback Settings) but the Failover EC2 Instance does not have required ports open either in the security group or in the firewall.
This error can occur during DR Failback Checks if the failover EC2 instance is reachable from the network associated with the VMware backup proxy in the selected Backup Proxy pool.

Error Solution:To resolve this error:

  1. If the failover EC2 instance runs the Linux OS, ensure that port 22 is allowed in the inbound rules of the security group attached to the failover EC2 instance.
  2. If the failover EC2 instance runs the Windows OS, ensure that port 445 and port 50000 are allowed in the inbound rules of the security group attached to the failover EC2 instance.
    1. To verify access to the SMB share, run the <ip-of-ec2>/Admin$ command from the Windows > Run box on any Windows computer.
    2. If the access is denied, perform the following steps on the failover instance:
      1. Ensure that the security group associated with the EC2 instance allows ports 445 and 50000 in the inbound rules. All ports must be allowed in the outbound rules.
      2. Enable rules for port 445 and port 50000:
        1. Login to the EC2 instance as an Administrator.

        2. Open the Windows Firewall with Advanced Security console.

        3. Go to Inbound Rules.

        4. Open port 445 and port 50000. Select the rule and click Enable Rule.
      3. If there is an on-premise network firewall, then whitelist port 445 and 50000 over the on-premise network firewall from the vCenter network to the failover instance.

DR8305

Error Message: SSH Connection error occurred between source and target machine

Error Description: This error can occur during DR Failback Checks or a DR Failback job if the SSH connection is lost between the VMware backup proxy and the failover EC2 instance due to a drop in the network connection or unavailability of the EC2 instance.

Error Solution: To resolve this error:

  • Ensure that the Failover EC2 instance is running.
  • Ensure that SSH is enabled in the inbound rules of the security group attached to the failover EC2 instance and the operating system firewall.
  • Ensure that SSH login is successful using the necessary credentials without any errors.

DR8309

Error Message: Invalid mount point excluded for failback

Error Description: This error occurs if the mount point to exclude is either not present in the source EC2 instance or is from the list of restricted mount points. The restricted mount points for Linux are /, /usr, /var , and /boot, respectively.

Error Solution: To resolve this error, enter valid mount points to exclude and retrigger the failback operation.

DR8310

Error Message: Unsupported source filesystem or volume or partition

Error Description: This error can occur during DR Failback Checks or DR Failback job if the Failover EC2 instance has an unsupported file system, volume, or a partition. The DR failback job excludes all the unsupported file systems, volumes, and partitions by default during the data transfer from the failover EC2 instance to the failback VM.

Error Solution: To resolve this error, review the Support matrix

DR8311

Error Message: Unsupported source volume

Error Description: This error occurs if the source EC2 instance has an unsupported volume. Unsupported file systems, volumes, and partitions are excluded from failback.

Error Solution: To resolve this error, review the Support matrix. Contact Druva Support. 

DR8321

Error Message: Current instance type is not supported for conversion of the current OS version.

Error Description: This error occurs when the instance type selected in the DR plan is unsupported for converting the virtual machine to an Amazon EC2 instance.

Error Solution: Select the instance type mentioned in the error message or use the Auto Assign instance feature to assign a supported instance type automatically.

DR8323

Error message: Conversion of 32bit Linux sources to AWS are not supported.

Error Description: You may run into this error when a x86 (32-bit architecture) Linux virtual machine is being failed over. Linux VMs with an x86 (32-bit architecture) are unsupported for DR failovers.

Error Solution: Run DR failovers for x64 (64-bit) Linux VMs only.

DR8324

Error message: Partition table was not recognized.

Error Description: You may get this warning during DR failback checks or the DR failback job when the partition table of the disk is not recognized or the disk was not partitioned at all. No data is transferred for such disks from the failover EC2 instance to the failback VM.

Error Solution: To resolve this warning, ensure that disk is partitioned in a supported format or exclude the mountpoint associated with the disk in DR Failback settings.

DR8332

Error Message: The size of the /var/log/lastlog or /var/log/faillog file is more than 100Mb and it will be excluded during Failback data transfer.

Error Description: You may get this warning during DR Failback Checks or a DR Failback job because /var/log/lastlog or /var/log/faillog logs whose size is greater than 100MB are not transferred during the data transfer phase.

Error Resolution: To resolve this error:

  • Delete logs that are greater than 100MB from  /var/log/lastlog or /var/log/faillog or,
  • Delete all logs in the directories /var/log/lastlog or /var/log/faillog. 

DR8337

Error Message: This OS is not supported for conversion.

Error Description: This error occurs when the operating system on the virtual machine is unsupported for the conversion of the virtual machine to an Amazon EC2 instance.

Error Solution: Only the operating systems listed in the DR support matrix are supported for a virtual machine conversion into an Amazon EC2 instance.

DR8340

Error Message: Another process is using TCP port 50000, and an alternate transport port was not specified. This migration cannot proceed.

Error Description: TCP Port 50000 is used to perform data transfer during DR failback. This error can occur during the DR failback checks or the DR failback if TCP Port 50000 is not open/available in the Failover EC2 instance.

Error Solution:  To resolve this error, ensure that TCP Port 50000 is open in the failover EC2 instance and it is not used by any other process.

DR8342

Error Message: It appears that Shadow Copy Storage space is limited on volume(s). This may cause migration failure if the rate of changes on the volume would exceed transfer rate. Consider changing Source Shadow Copy storage space.

Error Description: You may get this warning during DR failback checks of a DR failback if the space allocated for  Windows shadow copy on the mentioned volume is insufficient.

Error Solution: To resolve this warning:

  • Ensure that more than 1 GB free disk space is available on the volume mentioned in the error message for a successful DR failback.
  • Follow the steps in the vssadmin resize shadowstorage article to increase the space allocated to Windows shadow copy. 

DR8345

Error Message: It appears that the Source Machine is a Domain Controller.

Error Description: You may get this warning during DR failover checks or DR failback checks when the source machine is a domain controller. 

Error Solution: During a DR failover or DR failback, the network connectivity of the domain controller with the joined VMs may break. Ensure that the failover or the failback of the domain controller does not impact the VMs joined to it.

DR8451

Error Message:  Antivirus software detected.

Error Description: You may get this warning during DR failback checks or a DR failback job if antivirus software is installed in the failover EC2 instance. The antivirus software could potentially block the execution of the Druva failback processes.

Error Solution: To resolve this error contact support.

DR8461

Error Message: Failed to login due to unknown username or bad password.

Error Description: The DR failback job may fail with this error if the username and password of the failover EC2 instance are incorrect.

Error Solution: Ensure that the username and password for the failover EC2 instance are correct.

DR8465

Error Message: Access is denied for the specified user, for example, when specified user is not in Administrators group.

Error Description: The DR failback job may fail with this error when:

  • The specified user is not a member of the Administrators group.

  • The Local Computer Policy or Domain Policy blocks access to SMB shares. You get an Access Denied error for the builtin administrator. You can access this setting in the Local Computer Policy's Windows Settings > Security Settings > Local Policies > Security Options > User Account Control. The User Account Control Admin Approval Mode for the Built-in Administrator account is enabled.

    DR error UAC.png

Error Solution:

  • Use credentials that have Administrator permissions for the DR failback job. 
  • Add the registry key-value pair on the failover EC2 instance using the following command to override security settings for the built-in administrator without changing the local computer policy or domain policy.
    reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v "LocalAccountTokenFilterPolicy" /t REG_DWORD /d 1 /f

DR8467

Error message: Failed to log in as there are no logon servers available to service the logon request.

Error Description: You can run into this issue while logging into a failover EC2 instance of a domain-joined VM during a failback job due to the following reasons:

  1. Domain controller unavailability
    The domain controller is not reachable from the failover EC2 instance because either:
    1. The domain controller IP is not reachable from the failover EC2 instance, or

    2. The domain controller DNS is not resolvable from the failover EC2 instance.

  2. DNS issues on the failover EC2 instance
    DNS configuration on the failover EC2 instance is incorrect, or the DNS server is not reachable because either:

    1. The routing configured for the DNS server on the failover EC2 instance is incorrect, or

    2. The DNS TCP or UDP ports are closed, or

    3. An unbound DNS forwarder is not serving the DNS requests.

  3. VPN configuration issues
    The VPC between the AWS VPC and the on-premises network is not configured to allow DNS traffic.

Error Solution: 

  1. Domain controller unavailability:
    1. Login to the failover EC2 instance using local administrator credentials and ensure that the failover EC2 instance and the domain controller can ping each other by the IP address. The domain controller could either be in the same AWS VPC or could be in the on-premise environment. The domain controller could be unavailable because of network configuration issues, routing issues, or a missing VPN tunnel between the AWS VPC and the on-premise environment. Troubleshoot any identified issues and ensure that the connection between the failover EC2 instance and the domain controller is stable and that the two can ping each other by IP address.
    2. Ping the domain controller from the failover EC2 instance by DNS name. If the domain controller is not reachable by DNS name, go to step 2 in the error solution.
    3. Use telnet or portqry tools to check if the domain controller is accessible from the failover EC2 instance if the ICMP protocol is blocked by a firewall or isn’t allowed in your environment. Use any open or allowed ports on your domain controller like TCP/UDP 53, TCP/UDP 88, TCP/UDP 389.
  2. DNS issues on Failover EC2 instance
    Depending on your configuration, you can set up DNS resolution between AWS and on-premises networks in different ways. First, log in to the failover EC2 instance using local administrator credentials and check if the OS is using the correct DNS server that can serve DNS requests for your domain. If a wrong DNS server is configured in the OS IP settings, then reconfigure DNS settings accordingly.
    1. If the DNS server is in the on-premises environment, check its reachability from any EC2 instance located in the same AWS VPC where failover was done using the nslookup command nslookup dc1.example.com
      If the nslookup command fails to get an IP address then check the availability of DNS TCP port 53 and UDP port 53 using the Portqry.exe tool. See Using the PortQry command-line tool for details.
    2. If an unbound DNS-forwarder is used to forward DNS requests to your on-premises environment and vice versa then check its availability and make sure that it can forward DNS requests and DNS traffic between the failover EC2 instance and the DNS-forwarder, as well as between the DNS-forwarder and on-premises DNS server. See the Amazon article for details.
  3. VPN configuration issues
    If a VPN Site-to-Site connection was configured between AWS VPC and the on-premises environment, first check the tunnel state and the routing configuration for the corresponding static route to the Domain Controller subnet. If the VPN is not configured to forward all traffic through VPN then something (DNS, Kerberos, LDAP, etc) might be getting lost along the way. See the AWS site-to-site VPN User guide for details.
    Depending on your on-premises gateway device follow the documentation to allow the DNS, Kerberos, and LDAP traffic from the corresponding AWS VPC subnet to your on-premises networks where DNS-server and the domain controller are located. 
    We recommend that you open the following ports to allow communication between the AWS VPC and on-premises networks :
  • TCP/UDP 53 – DNS
  • TCP/UDP 88 - Kerberos authentication
  • TCP/UDP 389 – LDAP
  • TCP 445 - SMB

DR8470

Error Message: The network path was not found while accessing SMB share

Error Description: This error occurs if the SMB/admin share network path of the failover EC2 instance is not found.

Error Solution:

Note: We recommend running DR Failback Checks using VMware backup proxy of version 6.0.4 or later before triggering the DR Failback job.

To verify the access to the SMB share, run the <ip-of-ec2>/Admin$ command on in the Windows > Run field from any Windows computer.

If the access is denied, perform the following steps on the failover instance:

  1. Ensure that the security group associated with the EC2 instance allows ports 445 and 50000 in the inbound rules. All ports must be allowed in the outbound rules.

    DRaas error message correctionv2.png
     
  2. Enable rules for port 445 and port 50000:
    1. Login to the EC2 instance as an Administrator user.
    2. Open the Windows Firewall with Advanced Security console.
    3. Go to Inbound Rules.
    4. Open the port 445 and port 50000. Select the rule and click Enable Rule.
      SMB.JPG
  3. If on-premise network firewall exists:
    Whitelist port 445 and 50000 over the on-premise network firewall from vCenter network to the Failover instance.

DR8476

Error message: Unsupported OS architecture ‘x86’ detected. Only 'x64' OS architecture is supported.

Error Description: You may run into this error when a 32-bit Windows virtual machine is being failed over. 

Error Solution: DR failovers for 32-bit  Windows virtual machines are not supported. DR failovers can only be initiated for 64-bit Windows virtual machines.

DR8477

Error message: Storage filter driver(CtxMcsWbc) detected and it can block phase-2 recovery as it prevents the upgrade from writing changes to disk.

Error Description: You may run into this error if the storage filter driver from Citrix is detected on the virtual machine that is being failed over. CtxMcsWbc storage filter driver is present which can block phase-2 recovery because it prevents the upgrade from writing changes to the disk.

Error Solution: Uninstall the Citrix storage filter driver and retry the DR Failover.

DR8481

Error message: Mountpoints marked for exclusion are not found on the EC2 instance

Error Description: You get this warning during the DR failback checks if the Failover EC2 Instance does not have the mountpoints requested for exclude in the Failback settings.

Error Solution: Select a mountpoint which exists on the Failover EC2 Instance.

DR8346

Error message: It appears that source has not enough space on volume. Druva require 2 GB free space on <volume-letter> volume

Error Description: You get this warning during the DR failback checks if the Windows Failover EC2 Instance does not have sufficient storage space of around 2GB on the mentioned volume.

Error Solution: For a successful DR failback, make sure that more than 2GB free space is available on the volume mentioned in the error message.

DR8308

Error message: Incorrect sudo configuration on the  Failover EC2 instance

Error Description: You get this warning during the DR failback checks if the sudo is configured to require a tty.

Error Solution: Perform the following steps to disable the Defaults requiretty setting so that the failback data transfer can proceed without requiring a tty:

  1. ​​Log in as root user to the Failover EC2 Instance.

  2. To open the sudoers file for editing, enter the following command:
    visudo -f /etc/sudoers

  3. Go to the Defaults requiretty line and add # at the beginning of the line. For example, #Defaults requiretty.

DR8318

Error message: The enhanced data transfer component running on the target has failed

Error Description: You get this error during the DR Failback job if the data transfer from Failover EC2 Instance and Failback VM is stopped abruptly inside the Failover EC2 Instance by an external process.

Error Solution: We recommend that you run the DR Failback checks to know any potential warnings or blockers and fix them before running next DR Failback job. For more information, see DR Failback Checks.

DR8466

Error message: Failed to login as the trust relationship between this workstation and the primary domain is failed

Error Description: You get this error during the DR Failback job or the DR Failback Checks if the credentials provided to log into the Failover EC2 Instance are domain user credentials and authentication with the Domain Controller failed using the provided credentials.

Error Solution:

  1. Verify and fix the SecureChannel between the Failover EC2 Instance and the Domain Controller by performing the following steps:

    1. Login to Failover EC2 Instance using local Administrator credentials 

    2. Open powershell using Administrator credentials  

    3. Run following command:

Test-ComputerSecureChannel

If the output of the above command is False, then run the following command:

Test-ComputerSecureChannel -Repair

If the output of the command is True, then rejoin the domain. For more information, see "The trust relationship between this workstation and the primary domain failed" error when you log in to Windows 7".

For more information about testing the SecureChannel, see Test-ComputerSecureChannel.

DR8448

Error message: Image state could be undeployable

Error Description: This issue occurs when something goes wrong during the installation or update of windows on the original VM on vCenter.

Error Solution: Make sure  you install the Windows or update correctly on the original VM. For more information, see the IMAGE_STATE _UNDEPLOYABLE state under the Windows Setup State Information section of Windows Setup States.

DR12287

Error Message: No Space Left on the device.

Error Description: This error occurs due to the following reasons:

  • If there is insufficient space on the virtual machine to process failover.
  • If the conversion of the source virtual machine into the target virtual machine fails when
    • Mapping of partition ID 2 to the volume ID fails. 
    • If the cli.exe fails to start on the source virtual machine due to missing runtime dependencies or AV software blocking execution.

Error Solution: To resolve this error, free up space up to 1 GB on the source virtual machine. Contact Druva Support.

DR12288

Error Message: Failed to execute post-conversion script on failover instance.

Error Description: This error occurs due to syntax errors or invalid statements in the script.

Error Solution: To resolve this error, perform the following steps:

  1. On the Job Details page, click Download Job Logs for the failover job.
  2. In the PhoenixLogs-<JobID>.zip file, and navigate to the PhoenixLogs-<JobID>/failover/<number>/Phoenix.<timestamp>-<JobID>.zip/Phoenix-TW-<timestamp>-<JobID>_phase3.zip/Logs folder.
  3. Get the error message details from the stderr.log file in the phase 3 logs folder and resolve the error.

DR16384

Error Message: Timeout occurred in attribute collection

Error Description: This error occurs in the following scenarios:

  • If the target virtual machine takes too long to respond during the attribute collection from the source EC2 instance.
  • If the target virtual machine does not get a correct IP address.

Error Solution: To resolve this error, check if free IP addresses are available. 

DR16385

Error Message: Timeout occurred in Phase-1

Error Description: This error occurs if the Phase-1 of conversion from the source EC2 instance into the target virtual machine exceeds the timeout value.

Error Solution: Contact Druva Support.

DR16386

Error Message: Timeout occurred in Phase-2

Error Description: This error occurs if the Phase-2 of conversion from the source EC2 instance into the target virtual machine exceeds the timeout value.

Error Solution: Contact Druva Support.

DR16389

Error Message: Checksum of target worker does not match

Error Description: This error occurs if the checksum of downloaded VMDK does not match the checksum precomputed by the Druva Cloud .

Error Solution: To resolve this error, perform the following actions:

DR16390

Error Message: Failed to connect to source EC2. Please check network connectivity or power state of EC2

Error Description: This error occurs if the target virtual machine cannot connect to the source EC2 instance due to network disconnection or a stopped source EC2 instance.

Error Solution: To resolve this error, perform the following actions:

  • Check if there is a network connection between the source EC2 instance and the network chosen for the target virtual machine.
  • Check if the appropriate security groups are attached to the source EC2 instance, for example, SSH must be enabled for Linux virtual machine, RDP enabled for Windows virtual machine.
  • If a source EC2 instance does not have a public IP address, check if the VPN tunnel is established between the networks of the source EC2 instance and the target virtual machine.

DR16391

Error Message: Preflight validation failed with blockers

Error Description: This error occurs if the conversion of the source EC2 instance into the target virtual machine fails because of certain operating system attributes.

Error Solution: To resolve this error, review the Support matrix, pre-requisites, and limitations for failback.

DR16392

Error Message: Could not write data to VMDK during failback

Error Description: This error occurs if Phoenix is not able to write data to a VMDK during failback due to network disconnection or VMware environment issues.

Error Solution: To resolve this error, perform the following actions:

DR16393

Error Message: No enough free disk space is available on datastore

Error Description: This error occurs if there is no enough free space available on the datastore.

Error Solution: To resolve this error, add more space on the datastore by removing some of the existing virtual machines or select a new datastore. 

DR16396

Error Message: Failed to download file from URL

Error Description: This error occurs when the VMware backup proxy cannot download the failback VMDK during a failback.

Error Solution:

To resolve this issue, perform the following tasks:

  1. Check if your VMware backup proxy is connected to the network.
  2. Ensure the URL mentioned in the message is accessible from the VMware backup proxy using the following command wget -q --method HEAD <vmdk-url>
  3. Initiate one failback job at a time and ensure that the VMware backup proxy can download the VMDK.

DR16398

Error Message: Unable to connect to the VCenter/ESX host

Error Description: This error occurs if a Druva client is unable to connect to the vCenter or ESX host during failback.

Error Solution: To resolve this error, perform the following steps:

  1. Verify that the vCenter credentials are provided to the backup proxy.
  2. Check if the backup proxy connects to the vCenter or ESX host.

DR16399

Error Message: Network not found for VM

Error Description: This error occurs if the configured network is not found for the target virtual machine during failback.

Error Solution: To resolve this error, perform the following steps:

  1. Verify that a valid datastore is selected on the Destination VMware Settings page while triggering the failback.
  2. Verify that a valid network is selected on the Destination VMware Settings page while triggering the failback.

DR16400

Error Message: Resource pool not found where vm should be created.

Error Description: This error occurs if the configured resource pool is not found for the target virtual machine during failback.

Error Solution: To resolve this error, perform the following steps:

  1. Select a resource pool, which exists on the vCenter/ESXi.
  2. Contact Druva Support.

DR16401

Error Message: Folder not found where VM should restore

Error Description: This error occurs if the configured folder is not found for the target virtual machine.

Error Solution: To resolve this error, perform the following actions:

  1. Select a VM folder, which exists on the vCenter/ESXi.
  2. Contact Druva Support.

DR16402

Error Message: Invalid disk controller type

Error Description: This error occurs if the disk controller type is not found for adding a VMDK to the target virtual machine.

Error Solution: To resolve the error, perform the following actions:

  1. Ensure that the selected ESXi supports SCSi/IDE controller types, or,
  2. Select an appropriate ESXi for failback, which supports SCSI/IDE.
  3. Contact Druva Support.

DR16403

Error Message: No free disk controller slot found

Error Description: This error occurs if a free disk controller slot is not found for adding a VMDK to the target virtual machine.

Error Solution: Contact Druva Support.

DR16404

Error Message: Virtual machine not found

Error Description: This error occurs if a virtual machine corresponding to the UUID is not found.

Error Solution: To resolve this error, ensure that the Druva AWS proxy is connected to the Druva Cloud and retry the failback job.

DR16405

Error Message: Unable to shutdown VM

Error Description: This error occurs if the shutdown operation for a target virtual machine is not completed.

Error Solution: To resolve this error, ensure that the Druva AWS proxy is connected to the Druva Cloud and retry the failback job.

DR16406

Error Message: Timed out while shutting down VM

Error Description: This error occurs if the shutdown operation for a target virtual machine exceeded the timeout value.

Error Solution: To resolve this error, ensure that the Druva AWS proxy is connected to the Druva Cloud and retry the failback job.

DR16407

Error Message: Cannot add more than 4 scsi controllers

Error Description: This error occurs if the maximum limit of adding 4 SCSI controllers has reached while adding a VMDK to a target virtual machine.

Error Solution: To resolve this error, limit the number of the SCSI controllers to 4.

DR16408

Error Message: ESXI version not supported

Error Description: This error occurs if an ESXI version for the target virtual machine is not supported by Phoenix DraaS Failback.

Error Solution: Contact Druva Support.

DR16409

Error Message: Failed to update vm information on server

Error Description: This error occurs when the backup proxy fails to update the failed back virtual machine's information to the Druva Cloud .

Error Solution: Contact Druva Support.

DR16410

Error Message: Failed to aquire lock while downloading target worker

Error Description: This error occurs while downloading a target VMDK on the backup proxy.

Error Solution: Contact Druva Support.

DR16411

Error Message: Failed to acquire lock while waiting for target worker to finish downloading

Error Description: This error occurs if multiple failback jobs try to download the target VMDK on a backup proxy.

Error Solution: Contact Druva Support. 

DR16412

Error Message: Source EC2 Instance-ID does not match with the EC2 Instance-ID corresponding to the provided IP

Error Description: This error occurs when you enter an incorrect IP address of an EC2 instance during failback.

Error Solution: To resolve this error, ensure that you enter a correct IP address of an EC2 instance during failback.

DR16413

Error Message: Failed to get EC2 credentials

Error Description: This error occurs when the backup proxy fails to retrieve the password of the source EC2 instance the Druva Cloud .

Error Solution: Contact Druva Support. 

DR16414

Error Message: Failed to reset vm attributes

Error Description: This error occurs when the backup proxy fails to reset the virtual machine attributes. 

Error Solution: To resolve this error, check the progress logs for more details and resolve the error as follows:

Error Message Resolution

Warning DR16414: Unable shutdown the VM after failback. Will not able to reset the vm attributes.

Reset the attributes: guestid, ram, cpu , cpu hot add flag, cpu hot add memory flag.

Warning DR16414 : Failed to set guestid: <guestid> for VM: <vm name>.

Contact Druva Support. 

Warning DR16414 : Failed to change RAM of VM: <vmname> to :<memory int> MB.

Increase the RAM of the virtual machines. See the article for more information.

Warning DR16414 : Failed to change no of cpus of VM: <vm name> to: <no of cpu>.

Increase the number of CPUs. See the article for more information.

Warning DR16414 : Failed to disable cpu hot add flag for VM: <vm name>.

Enable the CPU Hot Add flag. See the article for more information.

Warning DR16414 : Failed to disable memory hot add flag for VM: failback_test_vm.

Warning DR16414 : Failed to disable memory hot add flag for VM: failback_test_vm.

DR16415

Error Message: One or more tags could not be attached to the VM.

Error Description: Failback for the instance failed because one or more tags could not be attached to the VM.

Error Solution: Remove the tags (Failover Instances > Failback > Failback settings) and perform the failback again and then reattach the tags to the VM through V- Center. 

DR16416

Error Message: Failback preflight execution on the source VM has timed out while calculating the disk size.

Error Description: The disk size calculation failed because you have excluded some disks (Failover Instances > Failback > Failback settings) from the source VM before triggering the failback.

By default, the timeout duration is set to 60 minutes 

Error Solution: If you can, remove the exclusion rule from Failover Instances > Failback > Failback settings.

If not, please contact Druva Support

DR16417

Error Message: Failback preflight execution on the source VM failed while calculating the disk size.

Error Description: The disk size calculation failed because you have excluded some disks (Failover Instances > Failback > Failback settings) from the source VM before triggering the failback.

Error Solution: If you can, remove the exclusion rule from Failover Instances > Failback > Failback settings.

If not, please contact Druva Support

DR16418

Error Message: One or more instances are missing or are extra during failback execution. 

Error Description: There is a mismatch between the number of instances chosen for failback and the instances that are actually failed back.

Error Solution:​​​​​​Please contact Druva Support

DR16419

Error Message: Failback failed for all the instances.

Error Description: This is a common message for all the instances in one job that did not failover successfully. 

Error Solution: In the job details, review the error messages for each instance and take action accordingly. 

DR16420

Error Message: Failback failed for one or more instances. 

Error Description: This is a common message for all the instances in one job that did not failover successfully. 

Error Solution: In the job details, review the error messages for each instance and take action accordingly. 

DR16422

Error Message: No IP Assigned to Failback VM

Error Description: The failback VM could not get an IP address in a timely manner.

Error Solution:Select a network where DHCP is configured. Alternatively, if you’ve selected a static IP address, ensure that you enter the IP address/subnet netmask, Default Gateway, and DNS for the failback VM.
image (3).png

Note: A subnet netmask value 32 is invalid.

DR16423

Error Message: IP Assigned to failback VM is unreachable from Backup Proxy.

Error Description: The network selected during failback is not reachable from the VMware backup proxy.

Error Solution: Ensure that the network selected in the failback settings is reachable from the VMware backup proxy. Disable any firewall rules that restrict access between the VMware backup proxy and the selected network.

DR16424

Error Message: Static IP assigned to the failback VM is unavailable.

Error Description: This error occurs when the Static IP assigned to the failback VM is unavailable. 

Error Solution: Ensure that the Static IP address is available and not assigned to another VM.

DR16425

Error Message:  Static IP netmask value 32 is invalid.

Error Description: This error occurs when the Static IP subnet netmask value of 32 is assigned to the failback VM.

Error Solution: Make sure to add another value than 32 for the Static IP subnet netmask.

DR16426

Error Message: VM Network is Isolated

Error Description: This error can occur due to one of the following reasons:

  • When the network is not connected to any vSwitch, or
  • Network is connected to a vSwitch but the vSwitch does not have a physical adapter, or
  • Network is connected to a vSwitch that has a physical adapter but the adapter is in a down state

Error Solution: To resolve these issues ensure that the network is connected to any vSwitch that has a physical adapter that is in an up state.

DR16427

Error Message:  ESX host IP not found

Error Description: This error can occur when the VMware backup proxy cannot get the IP address of the ESXi host.

Error Solution: Ensure that the ESXi host is reachable by IP address from the VMware backup proxy.

DR16431

Error Message: Static IP and gateway IP are in different subnet

Error Description: This error can occur when the static IP address and the gateway IP address provided in the failback settings are in different subnets.

Error Solution: Ensure that the static IP address and the gateway IP address provided in the failback settings are in the same subnet. Additionally, the provided subnet must be such that it allows the static IP to reach another IP address in the same subnet. A /32 subnet does not allow the static IP to communicate with other IP addresses in the same subnet.
Static IP and IGW in diff subnet.png

DR16432

Error Message: Datastore is inaccessible

Error Description: This error can occur if you failback a failover instance to a vCenter Datastore that is not accessible.

Error Solution: Ensure that the ESXi host can access the selected vCenter Datastore.

DR16433

Error Message: Datastore not found

Error Description: This error can occur if you failback a failover instance to a vCenter Datastore that does not exist.

Error Solution: Ensure that the selected vCenter Datastore exists, else select another Datastore.

DR24577

Error Message: Prerequisite check status of the latest DR restore job is ERROR.

Error Description: You have triggered the restore of virtual machines that have not cleared the prerequisite checks performed during backup of the virtual machines. 

Error Solution: Make sure that the prerequisite checks performed during backup are completed successfully.   

DR20480

Error Message: DR Running Failback job's timeout & expired

Error Description: This error occurs if the failback job is stuck on the client side for a long time.

Error Solution: To resolve this error, ensure that the Phoenix agent is running. Else start the Phoenix agent.

DR65535

Error Message: DR Agent: Internal Error

Error Description: This is an internal error. 

Error Solution: To resolve this error, contact Druva Support.