Hi Mark,

I too are experiencing the exact same issues with a Windows 2008 r2 x64 server. I have logged a call, but as yet not had any feedback.

Have you managed to resolve your issues?

Cheers,

Mark.

Hi Mark,

     Make sure you are using NetWorker 7.5.2. No other version of NetWorker supports Windows 2008 R2.

Regards,

Rovin D'Souza.

Hi Rovin,

I have since installed the 7.5.2 client and have now successfully performed a backup. I noticed that the BCD Boot files error still occurs, but it no longer appears to fail the complete job.

Cheers,

Mark.

Hi Rovin,

Thanks for the message. Will installing NetWorker 7.5.2 client be sufficient to resolve this issue, or does the NetWorker Server also need to be 7.5.2?

Is there an ETA for the release to support W2K8 R2 in 7.6 known?

Many thanks,

Mark.

Mark,

     Installing the client will be sufficient. NetWorker 7.5.2 was released in the beginning of Q2 2010. It might be included in the furture versions of 7.6.

Rovin D'Souza.

Mark,

     Thanks great. Happy that I was of help to you.

regards,

Rovin D'Souza.

1 - Problem - The ftp site does not appear to be functioning.  It is asking for user id and login and does not accept anonymous logins, nor does it accept my emc.com id and password.  Can someone please check on this.

2 -  Is there any information for when the problem will be resolved in the 7.6 client.?

Thanks,

Marc

Hi,

The link to the cumulative fixes is working again now.  There appears to have been a technical issue with it that has been fixed.  You can use the above link now to download the version you need.

-Bobby

We are having this issue on our NetWorker backup system for just one Server 2008 R2 client. We have many other Server 2008 R2 clients that don't have any issues.

NetWorker server running 7.6.1.2 build 436 (the most current)

NetWorker client 7.6.1.2 build 436

We get excactly the same error.

Is there a resolution yet?

Regards,

Johannes

Hello all,

Have you tried assigning a letter to the reserved partition?

As you know, by default Windows 2008 R2 creates a System Reserved partition, but no unit letter assigned to it, so VSS cannot identify the volume ID for that partition. I think this error message is related to that.

Also, try using the following bakcup command:

save -a '"ignore-all-missing-system-files=yes"'

Thank you.

Carlos.

Hi Carlos.

We are using the save -a '"ignore-all-missing-system-files=yes" option for another client that would otherwise fail the backup.

That does not help the problem client we have with the problem described in this post. The method of assigning a drive letter was a workaround for Server 2008 R2 clients before NetWorker 7.5.2, that is for 7.5.1 clients and older.

Regards,

Johannes

Hello all!

The problem with VSS is often thought to be the fault of the backup software.  However, you also need to consider what Microsoft has to say about this.  Belows is a list of Microsoft KB information.  This is for your review only and it is up to you to decide if it applies to your environment.

Windows Server VSS issues:

Below are some articles that should be reviewed by a Windows server administrator. These articles pertain to VSS and possible issues that may occur.

Knowledge base articles - known Windows 2003 VSS issues:

A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003 - Last Review: July 2, 2010

http://support.microsoft.com/kb/833167

Exchange VSS backup fails on an Exchange Server 2003 server - February 20, 2010

http://support.microsoft.com/kb/924262

Various issues may occur on a Windows Server 2003-based computer that is running the Volume Shadow Copy Service - April 27, 2010 - April 27, 2010

http://support.microsoft.com/kb/940032

Exchange Server 2003 data backup and Volume Shadow Copy services

http://support.microsoft.com/kb/822896

Knowledge base articles - known Windows 2008 VSS issues:

VSS snapshot creation may fail after a LUN resynchronization on a computer that is running Windows 7 or Windows Server 2008 R2 - November 25, 2009

http://support.microsoft.com/kb/976099

Backup fails with VSS Event ID 12292 and 11 on Windows Server 2008 and Windows Server 2008 R2 - January 20, 2010

http://support.microsoft.com/kb/2009513

No VSS writers are listed when you run the “vssadmin list writers” command in Windows Server 2008 R2

http://support.microsoft.com/kb/2009550

http://support.microsoft.com/kb/2009533

General VSS articles to review:

The backup process may fail and a time-out error may occur in Volume Shadow Copy Service writers

http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/77862/VSS-Writer-errors-during-backup

Event ID 9840 or 9607 is logged when a VSS backup operation fails in Exchange 2007 or in Exchange 2003

http://support.microsoft.com/kb/930800

Best Practices for Using Volume Shadow Copy Service with Exchange Server 2003

http://technet.microsoft.com/en-us/library/aa996004(EXCHG.65).aspx

Also, I performed a search in the Powerlink and found the following information:

VSS SYSTEM FILESET backup is failing because of the error with writer VSS BCD BOOT FILES

KB article esg115298

Symptoms Windows 2008 VSS backup fails Error: VSS BCD BOOT FILES - Error saving writer Error: VSS BCD BOOT FILES - ERROR: Aborting backup of Saveset VSS SYSTEM FILESET: because of the error with writer VSS BCD BOOT FILES Error: VSS BCD BOOT FILES - Get file attributes returned error 3 for VSS file \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3Boot\BCD VSS BCD BOOT FILES - Error saving file path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3Boot\BCD that is associated with Shadow Copy path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3Boot\BCD. The system cannot find the path specified error: VSS BCD BOOT FILES - ERROR: Could not open dir = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy235\boot Cause BUG ID NW116382 Resolution Work in progress, please contact EMC NetWorker support for the latest update

I hope this helps!

Mark