aws appliance backup error job vmware onpremisses

Question

We have two appliances on-premisses, on two different vcenters.
Both apparently have successful jobs, but some errors too.

When get error, received the error:
Miscellaneous: Error opening disk on the virtual machine during backup data processing. Aborted backup job

Most jobs work, but some give errors and I can't figure out why. Even vCenter, the same appliance, both Windows and Linux give an error message when there is an error.

However, 70% of the VMs that I inserted in the backup plan are working, but I don't understand the error for the rest.

See below the cloudwatch logs:

2025-05-09T17:23:54.463Z
LoggingFunc - 2025-05-09T17:23:54.463Z error -[91070] [Originator@6876 sub=vimaccess] GetFileName: Cannot create disk spec for disk [vsanDatastore] 2bbc3467-08a2-0ad3-e4434bfb5928/intruntime-000002.vmdk.;

LoggingFunc - 2025-05-09T17:23:54.463Z error -[91070] [Originator@6876 sub=vimaccess] GetFileName: Cannot create disk spec for disk [vsanDatastore] 2bbc3467-08a2-0ad3-e4434bfb5928/intruntime-000002.vmdk.;
2025-05-09T17:23:54.463Z
LoggingFunc - VixDiskLib: Error occurred when obtaining the file name for [vsanDatastore] 2bbc3467-08a2-e4434bfb5928/intruntime-000002.vmdk. Error 1 (Unknown error) (Cannot create disk spec for disk.) at 3344.;

LoggingFunc - VixDiskLib: Error occurred when obtaining the file name for [vsanDatastore] 2bbc3467-e4434bfb5928/intruntime-000002.vmdk. Error 1 (Unknown error) (Cannot create disk spec for disk.) at 3344.;
2025-05-09T17:23:54.467Z
LoggingFunc - VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [vsanDatastore] 2bbc3467-08a2-0ad3-e4434bfb5928/intruntime-000002.vmdk. Error 1 (Unknown error) at 7133.;

LoggingFunc - VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [vsanDatastore] 2bbc3467-08a2-0ad3-e4434bfb5928/intruntime-000002.vmdk. Error 1 (Unknown error) at 7133.;
2025-05-09T17:23:54.467Z
LoggingFunc - VixDiskLib: VixDiskLib_Open: Cannot open disk [vsanDatastore] 2bbc3467-08a2-f3a6-e4434bfb5928/intruntime-000002.vmdk. Error 1 (Unknown error) at 7211.;

LoggingFunc - VixDiskLib: VixDiskLib_Open: Cannot open disk [vsanDatastore] 2bbc3467-08a-0ad3-e4434bfb5928/intruntime-000002.vmdk. Error 1 (Unknown error) at 7211.;
2025-05-09T17:23:54.518Z
WarningFunc - VDDK_PhoneHome: HTTP response error in VddkVacHttpsPost with http status 403 at 105.;

re:Post Agent · Accepted Answer

The error you're experiencing with your AWS Backup for VMware on-premises appliances appears to be related to issues with accessing specific virtual machine disks during the backup process. This is a known issue that can occur due to various reasons.

The error message "Error opening disk on the virtual machine during backup data processing. Aborted backup job" suggests that the backup process is unable to access or read certain VM disks. This could be caused by several factors:

1. Configuration issues: There might be misconfigurations in your VMware environment or the AWS Backup gateway.

2. Unsupported VMware version or disk type: Ensure that you're using a supported version of VMware and that the disk types are compatible with AWS Backup.

3. Network connectivity problems: There could be insufficient network bandwidth or connectivity issues between the AWS Backup gateway and your VMware environment.

4. VMware host issues: The problem might be related to the VMware host where the gateway appliance resides.

5. Change Block Tracking (CBT) issues: CBT might not be properly enabled or functioning for some VMs.

To troubleshoot and resolve this issue, you can try the following steps:

1. Verify that you're using a supported VMware version and that all your VMs have compatible disk types.

2. Check the network connectivity between your AWS Backup gateway and the VMware environment. Ensure you have sufficient bandwidth (recommended minimum of 1000 Mbps upload bandwidth for on-premises VMs).

3. Review the configuration of your VMware hosts and the AWS Backup gateway for any potential issues.

4. Verify that Change Block Tracking (CBT) is enabled and functioning correctly for all VMs in your backup plan.

5. If the issue persists for specific VMs, you may need to investigate those VMs individually for any unique characteristics or configurations that might be causing the problem.

6. Consider increasing the number of backup gateways if you have a large number of VMs to back up, as this can help distribute the workload and potentially reduce errors.

If these steps don't resolve the issue, you may need to contact AWS Support for further assistance, as they can provide more detailed troubleshooting based on your specific environment and configuration.  
**Sources**  
[Troubleshoot VM issues - AWS Backup](https://docs.aws.amazon.com/aws-backup/latest/devguide/vm-troubleshooting.html)

aws appliance backup error job vmware onpremisses

Relevant content