Subscribe

Error: Vss Requestor - Backup Components failed.This file is currently not available for use on this computer.[HYPER-V 2008R2]

Hi,

I got following error for last night backup:

Jog log of snapmanager for hyper-v:

[24/02/2014 22:03:52, (26)] Backup task: failed to complete
[24/02/2014 22:03:53, (26)] An error occured while creating the hyper-V backup.
[24/02/2014 22:03:53, (26)] Backup task failed to succeed. Error: Vss Requestor - Backup Components
failed.This file is currently not available for use on this computer.
[24/02/2014 22:03:53, (26)] An error occurred while processing the backup.
Error: Vss Requestor - Backup Components failed.This file is currently not available for use on this computer.

Observation:

Sequence of events in event log when backup succeeds:
1. SnapManager for Hyper-V backup is now started
Dataset Name = Virtual-Machines
Backup id = beb14914-3588-45e0-8990-dfdc6ec0f992

2. ONTAP VSS hardware provider service has started, and it goes on...

But, this time, it did not start VSS hardware provider service rather failed immediately.

Event log for failed backup shows this:

1. SnapManager for Hyper-V backup is now started
Dataset Name = Virtual-Machines
Backup id = 371b6bc5-dbf3-401c-afcd-58422e020e16

2. Backup of the Dataset Name: Virtual-Machines
Backup id: 371b6bc5-dbf3-401c-afcd-58422e020e16 failed to execute
Error :Error: Vss Requestor - Backup Components failed.This file is currently not available for use on this computer.

Thanks,

-Ashwin

Re: Error: Vss Requestor - Backup Components failed.This file is currently not available for use on this computer.[HYPER-V 2008R2]

Hi Ashwin,

I had a similar problem on a Hyper-V 2012R2 Host (Error: Vss Requestor - Backup Components failed Hyper-V. The volume shadow copy provider is not registered in the system.).

It happened only with one of the 2 nodes in the cluster. I updated it and rebooted, it helped for one backup, but now it's the same failure again...

Did you get any help on this? I might open a Case today if the basic VSS Troubleshooting doesn't help.

Regards,

Ronald.