Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

shadow copy component backup failure due to EFI partition

Created: 10 May 2013 | 4 comments

Hi folks

on 2 different i hav shadow copy component backup failure both of them have same configuration,: MS windows 2008 R2 SP1 ver 6.1 build 7601, both physical server.

found one of technotes which state to run command bcdedit /enum 

output from server1

C:\Program Files\Veritas\NetBackup\bin>bcdedit /enum
 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {6433896e-3e6b-11e0-9e3f-e41f13d6455a}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30
 
Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows Server 2008 R2
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {64338970-3e6b-11e0-9e3f-e41f13d6455a}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {6433896e-3e6b-11e0-9e3f-e41f13d6455a}
nx                      OptOut
 
==========================================================
output from server2
bcdedit/enum
 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {4d265bb4-7954-11e2-8637-6cae8b27a84d}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30
 
Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows Server 2008 R2
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {4d265bb6-7954-11e2-8637-6cae8b27a84d}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {4d265bb4-7954-11e2-8637-6cae8b27a84d}
nx                      OptOut

if u keenly look and compare output then 1 line is missing from output of server2 :

path                    \EFI\Microsoft\Boot\bootmgfw.efi

question is why bootmgfw.efi path is missing from output of server2

please help me understand this. not really sure this is the right forum to ask this question but it will help me put an end to shadow copy component backup failure problem.

Operating Systems:

Comments 4 CommentsJump to latest comment

Yasuhisa Ishikawa's picture
For backup failure, some relevant Technotes are published. Install 7.1.0.1 or later then try "w2koption -backup -efi_boot_enabled 1".
 
 
 
For difference of bcdedit, it is better to ask in MS's forum.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Marianne's picture

Rookie11, you never mentioned the NBU version on your clients?

What is slightly confusing about TECH197939 is the following statement at the bottom:

In this case Engineering Binaries were created for Netbackup 7.1.0.2 to resolve this issue.  E-track 2903023 contains the Engineering Binary fix for this issue at Netbackup 7.1.0.2.

 
 
All of these binaries should be included in 7.1.0.3 or later.
 
My recommentadion is to patch clients with 7.1.0.4.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

rookie11's picture

NBU version is at 7.1.0.4 this is first step we took upgraded havnt solved this problem.

to run  w2koption -backup -efi_boot_enabled 1 is ok on server 1 because it shows 

path                    \EFI\Microsoft\Boot\bootmgfw.efi

but same cannot be said for server 2. -- sorry ishikawa i do not agree with you on this buddy.

w2koption -backup -efi_boot_enabled 1 -- will enable efi boot partition . it works fine on. server1 hadow copy component backup done.

i specifically tested same command and shadow copy component backup on same boxes with same configuration and pasted bcdedit /enum output, just to discuss with all experts.

my only concern here is wat to do for server which do not show PATH for bootmgfw.efi file ?????????????

Yasuhisa Ishikawa's picture

Difference on Windows Boot Manager configuration is the matter of Windows OS. Thee are no relevance between bcdedit output and NetBackup config.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan