cancel
Showing results for 
Search instead for 
Did you mean: 

Final error: 0xe000ff18 - A communications failure has occurred with a Virtual Machine resource.

ang_stinis
Level 2

Dear Admin,

I am using version : Veritas Backup Exec 16 version 16.0 Rev. 1142 (64 bits)

I like to backup my non-windows VM (NON GRT)

below is my log :

 

<?xml version="1.0" encoding="UTF-16"?>

-<joblog>

<job_log_version version="2.0"/>


-<header>

<filler> </filler>

<server>Job server: MNGMT1S </server>

<name>Job name: Unix Non-GRT Weekly FULL </name>

<start_time>Job started: Monday, 19 December, 2016 at 4:58:20 PM </start_time>

<type>Job type: Backup </type>

<log_name>Job Log: BEX_MNGMT1S_00503.xml </log_name>

<job_backup_type>Job Backup Method: Full </job_backup_type>

<filler> </filler>

</header>

<media_mount_date> Drive and media mount requested: 19/12/2016 4:58:20 PM </media_mount_date>


-<media_drive_and_media_info>

<media_mount_date> Drive and media information from media mount: 19/12/2016 4:58:20 PM </media_mount_date>

<drive_name>Drive Name: B2D </drive_name>

<media_label>Media Label: B2D000032 </media_label>

<media_guid>Media GUID: {3e4feb41-33e5-4b1b-ab18-86c90bb13c93} </media_guid>

</media_drive_and_media_info>


-<backup>

<filler> </filler>

<title>Job Operation - Backup </title>

<retention_period>Backup Set Retention Period: 1 Week.</retention_period>

<compression>Compression Type: None </compression>

<encryption>Encryption Type: None </encryption>

<verify_option>WARNING: The option 'Verify after backup completes' was not selected. Performing a verify operation to make sure that media can be read after the backup has completed is recommended. </verify_option>

<filler> </filler>


-<machine>

<machine_name>V3S</machine_name>

<misc>Backup Exec server is running Backup Exec version 16.0.1142.0. </misc>


-<ex_box>

<misc>Agent for Windows(V3S) is running Backup Exec version 16.0.1142.0. </misc>

</ex_box>

<NewLine/>

<snapshot_running>Snapshot Technology: Started for resource: "VRTSRV::\\SMY-CLUSTER.Hyper-V?HA?VM\SMG01S". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). </snapshot_running>

<snapshot_init_info>The following volumes are dependent on resource: "C:\CLUSTERSTORAGE\VOLUME3" . </snapshot_init_info>

<snapshot_init_info>The snapshot technology used by VSS for volume C:\CLUSTERSTORAGE\VOLUME3 - Microsoft CSV Shadow Copy Provider (Version 1.0.0.1). </snapshot_init_info>

<info>Network control connection is established between 10.2.2.60:56549 <--> 10.2.2.30:10000 </info>

<info>Network data connection is established between 10.2.2.60:56609 <--> 10.2.2.30:60378 </info>


-<OperationErrors Type="vrt_comm_failure">


-<CED>

<ced_disp_text>V-79-57344-65304</ced_disp_text>

<ced_version>16.0.1142</ced_version>

<ced_module>eng-vrtsrv-backup</ced_module>

<ced_error>V-79-57344-65304</ced_error>

<ced_language>EN</ced_language>

<ced_build>Retail</ced_build>

<ced_os>Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x2</ced_os>

</CED>
- The Virtual Machine resource is not responding. Backup set canceled.
</OperationErrors>


-<OperationErrors Type="vrt_comm_failure">


-<CED>

<ced_disp_text>V-79-57344-65304</ced_disp_text>

<ced_version>16.0.1142</ced_version>

<ced_module>eng-vrtsrv-backup</ced_module>

<ced_error>V-79-57344-65304</ced_error>

<ced_language>EN</ced_language>

<ced_build>Retail</ced_build>

<ced_os>Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x2</ced_os>

</CED>
- The Virtual Machine resource is not responding. Backup set canceled.
</OperationErrors>

<agent_shutdown_timeout>The network connection to the Backup Exec Remote Agent has been lost. Please check for network errors. </agent_shutdown_timeout>

</machine>


-<machine>

<machine_name>V4S</machine_name>

<misc>Backup Exec server is running Backup Exec version 16.0.1142.0. </misc>


-<ex_box>

<misc>Agent for Windows(V4S) is running Backup Exec version 16.0.1142.0. </misc>

</ex_box>

<NewLine/>

<snapshot_running>Snapshot Technology: Started for resource: "VRTSRV::\\SMY-CLUSTER\Hyper-V?HA?VM\NSVPX02S". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). </snapshot_running>

<snapshot_init_info>The following volumes are dependent on resource: "C:\CLUSTERSTORAGE\VOLUME2" . </snapshot_init_info>

<snapshot_init_info>The snapshot technology used by VSS for volume C:\CLUSTERSTORAGE\VOLUME2 - Microsoft CSV Shadow Copy Provider (Version 1.0.0.1). </snapshot_init_info>

<media_mount_date> Drive and media mount requested: 19/12/2016 5:07:32 PM </media_mount_date>

<media_switch_to_overwrite> No appendable media could be mounted. Switching to overwrite operation on scratch media. </media_switch_to_overwrite>


-<media_drive_and_media_info>

<media_mount_date> Drive and media information from media mount: 19/12/2016 5:07:33 PM </media_mount_date>

<drive_name>Drive Name: B2D </drive_name>

<media_label>Media Label: B2D000033 </media_label>

<media_guid>Media GUID: {6c8facd3-2d5c-4f78-96b0-ba92edb42e98} </media_guid>

</media_drive_and_media_info>

<info>Network control connection is established between 10.2.2.60:56617 <--> 10.2.2.40:10000 </info>

<info>Network data connection is established between 10.2.2.60:56640 <--> 10.2.2.40:56376 </info>


-<OperationErrors Type="vrt_comm_failure">


-<CED>

<ced_disp_text>V-79-57344-65304</ced_disp_text>

<ced_version>16.0.1142</ced_version>

<ced_module>eng-vrtsrv-backup</ced_module>

<ced_error>V-79-57344-65304</ced_error>

<ced_language>EN</ced_language>

<ced_build>Retail</ced_build>

<ced_os>Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x2</ced_os>

</CED>
- The Virtual Machine resource is not responding. Backup set canceled.
</OperationErrors>


-<OperationErrors Type="vrt_comm_failure">


-<CED>

<ced_disp_text>V-79-57344-65304</ced_disp_text>

<ced_version>16.0.1142</ced_version>

<ced_module>eng-vrtsrv-backup</ced_module>

<ced_error>V-79-57344-65304</ced_error>

<ced_language>EN</ced_language>

<ced_build>Retail</ced_build>

<ced_os>Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x2</ced_os>

</CED>
- The Virtual Machine resource is not responding. Backup set canceled.
</OperationErrors>

<agent_shutdown_timeout>The network connection to the Backup Exec Remote Agent has been lost. Please check for network errors. </agent_shutdown_timeout>

</machine>

</backup>

<ced_context_version>16.0.1142</ced_context_version>

<ced_context_module>eng-no_fs-backup</ced_context_module>

<ced_context_language>EN</ced_context_language>

<ced_context_build>Retail</ced_context_build>

<ced_context_os>Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x2</ced_context_os>


-<footer>

<filler> </filler>

<end_time>Job ended: Monday, 19 December, 2016 at 5:07:47 PM </end_time>

<engine_completion_status>Job completion status: Failed </engine_completion_status>

<filler> </filler>

<completeStatus>6</completeStatus>

<errorDescription>Final error: 0xe000ff18 - A communications failure has occurred with a Virtual Machine resource. </errorDescription>

<errorCategory>Final error category: Resource Errors</errorCategory>

<umiOriginator>79</umiOriginator>

<justErrorCode>-536805608</justErrorCode>

</footer>

</joblog>

5 REPLIES 5

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Solution

Workaround:
- Uninstall BE16 Remote Agent from the Hyper-V Hosts (cluster nodes)
- Install BE15 Remote Agent on the Hyper-V Hosts (cluster nodes)
OR
Backup the VM's as physical servers using the Agent for Windows backup method

 

Hi Collin, Thanks for your reply.

I saw the link you gave me, it is asking me install BE15 Remote Agent on Hyper-V Hosts.

Okay, but where i can get BE Remote Agent 15 ? since i am using BE16 now.

TQ

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Unfortunately that's a suggestion for customers that still have the BE agent 15 installer (having done an upgrade)

 

We are working on a proper fix but in the meantime you will have to backup the VMs using the agent inside the VMs and not using the Hyper-V agent against the host. (which is the other suggestion in the article)

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

As an update we are currently looking to provide a full fix for this early in the New Year - although we cannot confirm this as QA testing of the changes needs to be completed (which of course might identify other issues)

Hi, thanks for the help, it helped me. For version BE20.2

- Uninstall BE20.2 Remote Agent from the Hyper-V Hosts (cluster nodes)

- Install BE16 Remote Agent on the Hyper-V Hosts (cluster nodes)