Skip to main content
Druva Documentation

DRaaS errors

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

AWS_DR4

Error Message: Bucket creation failed

Error Description: This error may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 Phoenix 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur:

  • 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 Phoenix AWS proxy EC2 instance

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

AWS_DR34

Error Message: EBS Snapshot creation limit is reached.

Error Description: This error may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 Phoenix AWS proxy, is present in the AWS account.

AWS_DR46

Error Message: The specified snapshot does not exist.

Error Description: This error may occur 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 Phoenix 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 may occur 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 may occur 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 may occur 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 Phoenix AWS proxy matches the policy downloaded from the Phoenix Management Console.

AWS_DR55

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

Error Description: This error may occur 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 may occur 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 may occur 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 Phoenix AWS proxy, if no jobs are running. 

AWS_DR65

Error Message: AMI doesn't exist.

Error Description: This error may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 Phoenix 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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_DR102

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

Error Description: This error may occur 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_DR255

Error Message: Boto3 Client encountered a generic error.

Error Description: This error may occur 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:  Phoenix Internal Error.

Error Description: This is an internal error.

Error Solution: To resolve this error, ensure that there is enough space on the EBS volume. Contact Druva 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 or, 
  • The virtual machine is using the EFI/UEFI firmware

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

DR7

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

Error Description: This error may occur if the DR restore job is skipped because the Phoenix AWS proxy associated with the job is disconnected.

Error Solution: Ensure that the Phoenix 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 Phoenix AWS proxy which is unavailable.

Error Description: This error may occur 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 Phoenix AWS proxy is disconnected.

DR9

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

Error Description: This error may occur when the Phoenix AWS proxy is in the disconnected state and the DR restore operation fails. 

Error Solution: Ensure that the Phoenix AWS proxy is up and running during the DR restore operation. Ensure that at least one Phoenix 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 may occur 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 may occur if the Phoenix 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 may occur 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  Phoenix 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 Phoenix 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 may occur 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 may occur 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 Phoenix AWS proxy. 

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

DR4097

Error Message: No Bootable disk found.

Error Description: This error may occur 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 may occur 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 may occur 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 Phoenix DRaaS. For more information, see Support matrix.

DR4100

Error Message: Agent: failed to start failover.

Error Description: This error may occur if the Phoenix 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 may occur if the failover instance is in the requested or initializing state for more than 24 hours. This may occur when the Phoenix AWS proxy abruptly exits and fails to update the instance status on the server.

Error Solution: To resolve this error:

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

DR4103

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

Error Description: This error may occur 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 may occur 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 Phoenix AWS proxy version 4.8.0 or later was never created.

Error Description: This may occur 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 Phoenix AWS proxy version 4.7.6. or earlier was never created.

Error Description: This may occur 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 may occur 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 may occur 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 may occur 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 Phoenix AWS proxy version 4.8.0 or later, need Phoenix AWS proxy version 4.8.0 or later for failover.

Error Description: This error may occur 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 Phoenix AWS proxy is connected.

DR4119

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

Error Description: This error may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur if the Phoenix Cloud failed to run the job. 

Error Solution: Contact Druva Support

DR 8195

Error Message: System command required for conversion not found.

Error Description: This error may occur 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 Phoenix 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.  

DR 8197

Error Message: Command timed out during execution.

Error Description: This error may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur 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 may occur if the MS Shadow Copy partition is present in the virtual machine. Phoenix 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 may occur 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 may occur 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 may occur 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 may occur if the FileSystem type of one of the volumes is not supported.

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

DR8225

Error Message: Unable to identify partition using parted command.

Error Description: This error may occur 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 may occur 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 may occur 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 may occur 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.

DR12287

Error Message: No Space Left on the device.

Error Description: This error may occur if there is insufficient space on the virtual machine to process failover.

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

DR12288

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

Error Description: This error may occur 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.

DR65535

Error Message: DR Agent: Internal Error

Error Description: This is an internal error. 

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