Troubleshooting: Issue During Full VM Recovery: New Disk Creation or Attachment Failed

Troubleshooting: Issue During Full VM Recovery: New Disk Creation or Attachment Failed

KB ID: 261001
Issue:
During Full VM recovery, new disk creation or attachment to the created VM failed.
Cause:
1. Incompatibility with the target disk configuration selected from the BDR UI for new disk creation/attachment.
2. Insufficient space or permissions in the chosen storage domain for the new disk creation.
3. Special characters in the disk name.
4. Connection to oVirt engine failure.
5. Authentication failure of oVirt Engine console credentials.
Solution:
1. Verify Disk Configuration Parameters:
  1. Ensure that the correct parameters are chosen for new disk creation, including Allocation Policy, Interface, Storage Domain, and Disk Profile.
2. Check Storage Domain:
  1. Confirm that the appropriate storage domain is selected and has sufficient space and proper permissions.
  2. Ensure the connectivity of the respective storage domain.
3. Avoid Special Characters in Disk Name:
  1. Do not use special characters when adding the new disk name.
4. Check oVirt Engine Status:
  1. Ensure that the oVirt Engine status is good and that the engine is up.
  2. Use the following command to check the engine status on the oVirt Engine (self-hosted) machine:
 hosted-engine --vm-status
          Example output:
     Host host1.india.domain.com (id: 1) status
     Host ID                            : 1
     Host timestamp              : 241871
     Score                                : 3400
     Engine status                   : {"vm": "up", "health": "good", "detail": "Up"}
     Hostname                         : example.india.domain.com
     Local maintenance           : False
     stopped                             : False
     crc32                                  : 099bd52f
     conf_on_shared_storage  : True
     local_conf_timestamp      : 241874
     Status up-to-date              : True
     Extra metadata (valid at timestamp):
             metadata_parse_version=1
             metadata_feature_version=1
             timestamp=241871 (Mon Jan 15 11:12:26 2024)
             host-id=1
             score=3400
             vm_conf_refresh_time=241874 (Mon Jan 15 11:12:28 2024)
             conf_on_shared_storage=True
             maintenance=False
             state=EngineUp
             stopped=False
5. Verify oVirt Engine Console Credentials:
  1. Ensure the provided oVirt Engine console credentials are correct and valid.

    • Related Articles

    • Unable to Create VM Snapshot. Failed to Quiesce the VM.

      KB ID: 105130 Details: BDRSuite utilizes VMware snapshots for VM Backup & Replication. During the snapshot initiation for backup or replication, BDRSuite ensures VM quiescing to maintain on-disk data consistency. However, users may encounter an error ...
    • Troubleshooting: AppAware Folder Creation Failed Inside the Guest Machine in BDRsuite

      KB ID: 115076 Issue: During the operation of BDRSuite, an issue may arise when the BDRSuite application attempts to create the AppAware folder inside a guest VM running Windows. This folder is essential as it contains executables and DLL files ...
    • Alert: SNAPSHOT_FAILURE Snapshot Creation Failed While DoSnapshotSet Call

      KB ID: 104063 Issue: The "SNAPSHOT_FAILURE" alert occurs with the message "Snapshot Creation Failed While DoSnapshotSet Call" in BDRSuite. This alert is usually triggered when there is insufficient space in the volume to take a snapshot of the ...
    • MAPI Profile Creation Failed

      KB ID: 111002 Cause: The 'MSPST MS' service is not configured, leading to the failure of MAPI profile creation. Solution: Follow the steps below to resolve the issue: 1. Create a New User: Create a new user with sufficient rights through Active ...
    • Azure VM Recovery

      In the BDRSuite Backup for Azure console, Navigate to Recovery-> Restore Backup Data tab. Step 1: Select Backup Job for Restore All the backup jobs will be listed and you can click on respective restore button. Step 2: Restore Version Based on the ...