Help, I am new to BUexec and Hyper-V....

[tonymcclain]

I am new to BUExec and Hyper-V, so please be nice.

I having (only some) my jobs fail, and I wanted to post an error here and asked for help.

We are in the evaluation stages for backup tools.

Job Log for LESX1 Backup-LESX1 - Incremental

Completed status: Failed    See error(s)

Expand All  Collapse All

Job Information

Job server: MARS Job name: LESX1 Backup-LESX1 - Incremental Job started: Tuesday, April 11, 2017 at 2:00:02 AM Job type: Backup Job Log: BEX_MARS_00069.xml Job Backup Method: Incremental

Drive and media mount requested: 4/11/2017 2:00:14 AM

Device and Media Information

Drive and media information from media mount: 4/11/2017 2:00:16 AM Drive Name: Disk storage 0001 Media Label: B2D000015 Media GUID: {ef17140b-d590-407b-acc2-41b8b6e86e0c} All Media Used  B2D000015

Job Operation - Backup

Backup Options Backup Set Retention Period: 1 Week. Compression Type: None Encryption Type: None Server - ATLAS Backup Exec server is running Backup Exec version 16.0.1142.1009 with HF-124683. Agent for Windows(ATLAS) is running Backup Exec version 16.0.1142.0. Backup Exec server and the Agent for Windows are running different versions. V-79-40960-38521 - Snapshot Technology: Initialization failure on: "VRTSRV::\\ATLAS\Hyper-V?Virtual?Machine\LESX1". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). A virtual machine snapshot could not be created.  Use the Event Viewer on the Hyper-V host to identify the cause.  If the virtual machine is not properly configured, it may be necessary to use the Event Viewer in the virtual machine to identify the cause. The following volumes are dependent on resource: "G:" . The snapshot technology used by VSS for volume G: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).

Job Completion Status

Job ended: Tuesday, April 11, 2017 at 2:01:13 AM Completed status: Failed Final error: 0xa0009679 - A failure occurred querying the Writer status for a Hyper-V virtual machine. See the job log for details about the error. Final error category: Resource Errors For additional information regarding this error refer to link V-79-40960-38521

Errors

Click an error below to locate it in the job log Backup- ATLAS V-79-40960-38521 - Snapshot Technology: Initialization failure on: "VRTSRV::\\ATLAS\Hyper-V?Virtual?... A virtual machine snapshot could not be created.  Use the Event Viewer on the Hyper-V host to identi...

[CraigV]

Hi Tony,

You need to remove the server name and especially your domain name from the post...not good for security.

Then check out the links below for more information:

https://www.veritas.com/support/en_US/article.000115524

https://www.veritas.com/support/en_US/article.000021587

https://www.veritas.com/support/en_US/article.000012313

Thanks!

[ParagKavitke]

Hi,

The error you are receiving is related to the Hyper-V VSS writer.

You can verify if the VSS writer is in stable state on in error state by running below command on the Hyper-V server's command prompt

vssadmin list writers

This will return a list of writers; check for Hyper-V VSS Writer and it's status. It should be in 'Stable' state like shown below, 

Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {30f73964-9946-452d-8dd5-be4b8472c184}
State: [1] Stable
Last error: No error

If the status is not Stable, please try restarting your Hyper-V server and run the same command to verify.

When the VSS writer is in stable state, try running the backup job.

Hope that helps.

Parag

[pierre_wong]

I got exactly the same problem with Version 16.0 Rev. 1142.1333

Did check with "vssadmin list writers" and all showing stable

Does anyone know how to solve this problem??