UNSOLVED
VSS failed to get comp=BCD FileGroup list
In our environment there are two servers failed generating below errors. I have checked with server administrator for availble free space and both physical and virtual memory. They have enough free space and memory available. I have checked rebooting one server and found no improvment. The server rebooted has 8GB of physical and virtual memory and 23GB used out of 40GB storage
This is the complete error. To say Networker give poor and incomplete errors is an understatement. But here it is:
1 retry attempted
No full backups of this save set were found in the media database; performing a full backup
43705:save: Save Operations value is ignored on this OS platform.
ERROR: VSS failed to get comp=BCD FileGroup list, writer=ASR Writer, error=0x80070008: Not enough storage is available to process this command.
in directives
7154:save: Unable to set up VSS filesystem directives. Failed to back up C:\.
same error for all other drives E & F
This is the complete error. To say Networker give poor and incomplete errors is an understatement. But here it is:
1 retry attempted
No full backups of this save set were found in the media database; performing a full backup
43705:save: Save Operations value is ignored on this OS platform.
ERROR: VSS failed to get comp=BCD FileGroup list, writer=ASR Writer, error=0x80070008: Not enough storage is available to process this command.
in directives
7154:save: Unable to set up VSS filesystem directives. Failed to back up C:\.
same error for all other drives E & F
530
0
Posted November 4th, 2009 00:00
What is the Operating System? Is it Windows 2008 R2? If yes then have a look at esg107680:
Symptoms:
* wsus02:D:\ ERROR: VSS failed to get comp=BCD FileGroup list, writer=ASR Writer, error=0x80070008: Not enough storage is available to process this command.
* wsus02:D:\ in directives
* wsus02:D:\ 7154:save: Unable to set up VSS filesystem directives. Failed to back up D:\.
Cause:
Windows 2008 R2 is currently not supported by NetWorker
Resolution:
Windows 7 and Windows Server 2008 R2 reached RTM on 7/22/2009 and will be launched by Microsoft on 10/22/2009.
NetWorker support for Windows 7 and Windows Server 2008 R2 is expected in Q2 2010.
Regards,
Mustafa530
0
Posted November 4th, 2009 11:00
They were probably reading the same article530
0
Posted November 4th, 2009 11:00
Actually that article is not correct as that support is coming much earlier.530
0
Posted November 4th, 2009 11:00
Its windows 2008 R2. I heard the same from EMC that windows 2008 R2 is supported in Q2 2010.530
0
Posted February 23rd, 2010 06:00
Hello there.
We have assigned a driveletter for the boot partition. After this the client was saved successfully.
Kind Regards,
Rolf530
0
Posted November 8th, 2010 05:00
yes, that way it works. Have many thanks.
Best regards,
Thomas
530
0
Posted April 18th, 2011 23:00
Hi Rolf & Thomas,
Windows always assign a drive letter to boot drive.
I am also facing the same issue with Networker 7.6 on Windows 2008 R2. Can you please elaborate the solution?
Waiting for the reply.
Regards,
Atif
530
0
Posted April 21st, 2011 02:00
matifk wrote:
Windows always assign a drive letter to boot drive.
I believe they were referring to reserved drive. This one needs letter to be assigned. I believe in 7.6SP2 this is handled by NW automatically. In previous versions, you assign drive letter as workaround (see esg108377).
94
0
Posted April 22nd, 2011 07:00
ArchuPeri,
Please access power link and review the following EMC knowldegebase article:
Windows 2008 R2 64-bit backup failed
There is also a Microsoft KnowledgeBase article for this issue:
Error message: "Not enough server storage is available to process this command"
Please review both of these articles. Depending on your situation will depend on which one you follow.
Let me know if this helps!
Thanks,
Mark
ble1
6 Operator
•
14354 Posts
•
56186 Points
530
0
Posted October 27th, 2009 15:00
You didn't mention which NW version is running on client and what is the version of Windows you run. Depending on that, there might be few VSS patches which you may find useful. In case that you can't resolve it, if this is win2k3, you can allways switch off VSS.