Troubleshooting - AWS Workloads
69 articles
- Restore of AMI not working as Private IP is not within the valid subnet range
- Restore of an EBS Volume as an instance gets stuck in the CloudRanger Console
- Manual and scheduled backup jobs are not running with cloud ranger
- Snapshot and instance names do not match
- Troubleshoot Archive to S3
- Unable to create a snapshot as the database instance is not in available state
- Read only admin cannot enable MFA
- Rules Per Security Group Limit Exceeded
- Unable to generate reports on CloudRanger
- Unable to power on the instance using server schedule
- Unable to configure verification page
- Unable to activate Windows license after restore as an instance from snapshot
- Unable to specify Environment Mappings while creating a DR policy
- Unable to update CloudFormation stack "The specified bucket does not exist"
- Unable to populate KMS keys for encrypted instances while trying to copy to secondary region
- Unable to open files after restoring snapshots of Windows EC2 instance
- Updating CloudFormation stack gives error: CloudRangerInitializeSNSProvisioner
- Update of CloudFormation stack fails with error: "CloudRangerInitializeSNSProvisioner" - CREATE FAILED
- VPC Cloning fails
- Zapier Integration will not be fired due to the current plan
- CloudRanger EC2 Restore Fails with Error: 'Created by application' is not a valid tag keyCloudRanger EC2 Restore Fails with Error: 'Created by application' is not a valid tag keys
- Failed to Register Azure Subscriptions Due to Policy Restrictions and Insufficient Permissions
- EC2 backups deletion failed with error: "The backup cannot be deleted as it is the most recent snapshot in Storage and is required to process the next backups for this resource."EC2 backups deletion failed with error: 'The backup cannot be deleted as it is the most recent snapshot in Storage and is required to process the next backups for this…
- Standalone EBS Exclude Rules Fail to Exclude Volumes When Parent EC2 Instance Is Included in Backup PolicyStandalone EBS Exclude Rules Fail to Exclude Volumes When Parent EC2 Instance Is Included in Backup Policy.
- AMI backups fail with instance does not have a volume attached at root error
- Backup to Druva Cloud fails at the step "aws/monitor/btdcbackup" with the Error: "Failed to prepare backup sources"
- Adding Client Credentials fails with the Error 'Credential with this name already exists. Provide a unique name'
- RDS Backup Fails When the Instance Has More Than 100 Manual Snapshots
- Cannot add resources to DR Plan
- Cloning an Environment in CloudRanger fails with Error "The vpc 'vpc-aaabbb111222' has dependencies and cannot be deleted. Resource handler returned message: "Request limit exceeded"
- Deleting an existing Environment in Druva CloudRanger fails with the following error: Cannot read property 'stack_name' of nullDeleting an existing Environment in Druva CloudRanger fails with the following error: Cannot read property 'stack_name' of null
- Cloning an Environment in CloudRanger fails with: "One or more errors occurred: The maximum number of addresses has been reached - "The vpc 'vpc-111222333444' has dependencies and cannot be deleted."
- EC2 backups with VSS enabled fail in CloudRanger with the Error 'An error occurred in the SSM command. no AMI was created'
- Copying images of EC2 BillingProduct codes to another AWS account fails
- Failed to create a snapshot - SSMCommandInvocation - ExecutionTimedOut
- EC2 Instance Backup Failure at aws/monitor/consistentinstancesnaphotEC2 Instance Backup Failure at aws/monitor/consistentinstancesnaphot
- Instance does not have an AMI within its timeframe
- How to increase the page size output result for the CloudRanger event API
- RDS Backup Failure - Database Instance Not in Available StateRDS Backup Failure - Database Instance Not in Available State
- Multi-Factor Authentication failure with invalid security token error
- FLS Index Job fails in CloudRanger with the Error: "The instance configuration for this AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about supported instance types, region, and operating systems."FLS Index Job fails in CloudRanger with the Error: "The instance configuration for this AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about…
- File-level search jobs fail with no default VPC for this user error
- EC2 VSS Backup Fails with "Cannot call a method on a null-valued expression"EC2 VSS Backup Fails with "Cannot call a method on a null-valued expression"
- RDS Cross-Region Backup FailureRDS Cross-Region Backup Failure
- EC2 backups fail with AWS Tools for Windows PowerShell is not installed
- DR Job Fails with Error: “Tag values may only contain unicode letters, digits, whitespace, or one of these symbols: . : / = - @”DR Job Fails with Error: “Tag values may only contain unicode letters, digits, whitespace, or one of these symbols: . : / = - @”
- Login Error Couldn’t complete your authentication request
- Executing the backup policy fails with error “No policy found with that id in this Organization”
- FLS indexing jobs are failing with Instance terminated early error
- Password is not available the instance was launched from custom AMI or the default password has changedPassword is not available the instance was launched from custom AMI or the default password has changed
- EC2 Consistent AMI Backups Failing with 'Failed to Run Commands: Exit Status 1'
- EC2 Consistent AMI Backup Failure Due to Name Resolution ErrorEC2 Consistent AMI Backup Failure Due to Name Resolution Error
- Backup Imports Failing: Automated RDS Snapshots Cannot Be DeletedBackup Imports Failing: Automated RDS Snapshots Cannot Be Deleted
- Backup Failure Error: "Failed to Sign Request: Unable to Retrieve Credentials"Backup Failure Error: "Failed to Sign Request: Unable to Retrieve Credentials"
- CloudRanger DR failover job failing with “The requested configuration is currently not supported”CloudRanger DR failover job failing with “The requested configuration is currently not supported”
- Understanding Disk Usage Discrepancies in CloudRanger Backup ReportsUnderstanding Disk Usage Discrepancies in CloudRanger Backup Reports
- Unable to extract large .tar.gz files downloaded from File Level Recovery (FLR) operations on Windows machinesUnable to extract large .tar.gz files downloaded from File Level Recovery (FLR) operations on Windows machines
- EC2 AMI Restore Fails with Error "More than 50 Tags Specified"EC2 AMI Restore Fails with Error "More than 50 Tags Specified"
- EC2 AirGap backups failed with "Failed to ListSnapshotBlocksBasic" API error.EC2 AirGap backups are failing due to a persistent "Failed to ListSnapshotBlocksBasic" API error.
- EC2 restore failures with errors during snapshot creation. The failure is typically related to EBS encryption settings in the AWS environment.EC2 restore failures with errors during snapshot creation. The failure is typically related to EBS encryption settings in the AWS environment.
- Restore settings not populated during restore for EC2 instance when Backup not created by CloudRanagerRestore settings not populated during restore for EC2 instance when Backup not created by CloudRanager
- CloudRanger Login Error – “You do not have access to any Organizations in CloudRanger”CloudRanger Login Error – “You do not have access to any Organizations in CloudRanger”
- Cross-Region Restore Fails for Marketplace-Based EC2 InstancesCross-Region Restore Fails for Marketplace-Based EC2 Instances
- EC2 Backup Failure due to Invalid Instance Profile NameEC2 Backup Failure due to Invalid Instance Profile Name
- RDS Air-Gapped Backup Failure with Error: “Copying unencrypted cluster with encryption is not supported”RDS Air-Gapped Backup Failure with Error: “Copying unencrypted cluster with encryption is not supported”
- Backup Failure Due to AWS Tag Policy ViolationBackup Failure Due to AWS Tag Policy Violation
- S3 Restore Job Completes with Errors (AccessDenied) Due to KMS Permissions (Error Code 0)S3 Restore Job Completes with Errors (AccessDenied) Due to KMS Permissions (Error Code 0)
- S3 Backup Fails with "Files missed/skipped from backup"S3 Backup Fails with "Files missed/skipped from backup"
- S3 Backup Failure Due to Missing Encryption AuthorizationS3 Backup Failure Due to Missing Encryption Authorization