• State Not Answered
  • Replies 10 replies
  • Subscribers 30 subscribers
  • Views 3480 views
  • Users 0 members are here
Options
Related

Export of a VM fails due to timeout.

marc_65284
over 1 year ago

Rapid Recovery Core 6.7.0.387

vCenter 7

ESXi Hosts are 6.5

I've attempted twice now to export a protected VM to a new vm back to vCenter and it's failing due to timeout. The progress bar never moves and 0 of x bytes are restored. There are no other error messages than the following vague ones:

A background job of type 'Export to virtual machine', summary 'Export of volumes [\\Hard disk 1] to ['newvmname' on vcenter target 'vcenter:443'] for 'originalvmname' (VMware ESXi export)', has failed.

 The export has failed

 Cannot perform an export task :

 * Timeout Exception: Writing to virtual disks operation has been failed.

The export of 'originalvmname' to 'newvmname' on vcenter target 'vcenter:443' has failed.

 The export has failed

 Cannot perform an export task :

 * Timeout Exception: Writing to virtual disks operation has been failed.

I thought it might be account permissions at first as I was using the dedicated RR backup account so for the second job, I used my account which has full access but that didn't work either. Frustated. 

Not to mention this forum said "Your posting frequency has exceeded allowed rates. Please wait 10 minutes to post again." and I haven't even posted a thing yet. Wonderful!

Parents
  • 0 over 1 year ago

    Hello Marc,

    It may be related to the account permissions as you mentioned. You can test with the "administrator@vspere.local" account or check if the RR backup account has the following permissions in VMWare.

    Rapid recovery ESXi 6 | 6.5 | 6.7 permissions (4039423)

    Please let us know the outcome.

    Regards,

    Luciano

  • 0 over 1 year ago in reply to Luciano.Guerra

    Hi Luciano

    I verified the permissions and they all match what's required. I also tried putting it into the administrators group and it still fails.

    I can see the VM get created in vCenter and vCenter logs show successful actions. It's just when RR is needing to export the data is where it stalls. Nothing in the logs on either side show what's happening.

    We are configured to use direct backup from the SAN and I'm wondering if this is causing the issue. Does the export process leverage the same network paths as the backup process does?

    Also still having a heck of a time posting to this forum. Replies keep failing with "An error occurred. Please try again or contact your administrator".

Reply
  • 0 over 1 year ago in reply to Luciano.Guerra

    Hi Luciano

    I verified the permissions and they all match what's required. I also tried putting it into the administrators group and it still fails.

    I can see the VM get created in vCenter and vCenter logs show successful actions. It's just when RR is needing to export the data is where it stalls. Nothing in the logs on either side show what's happening.

    We are configured to use direct backup from the SAN and I'm wondering if this is causing the issue. Does the export process leverage the same network paths as the backup process does?

    Also still having a heck of a time posting to this forum. Replies keep failing with "An error occurred. Please try again or contact your administrator".

Children