Hi,
Here I have a Windows Server 2012 R2 Standard server, using Netbackup software for the backup, which is a product of Symantec company.
The server roles as file server, problem now is the backup process always failed when processing on an EFI partition.
After consulted with the product vendor, they suggested to ask MS for help..
Here is the log:
- Type: VSS_CT_FILEGROUP [2]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot<file:///\\%3f\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot>
- Volumes affected by this component:
- \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot<file:///\\%3f\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot> [Does not exist]
Here is the BCD info:
C:\Windows\system32>bcdedit /enum all /v > c:\bcd.txtFirmware Boot Manager
---------------------
identifier {a5a30fa2-3d06-4e9f-b5f4-a01df9d1fcba}
displayorder {9dea862c-5cdd-4e70-acc1-f32b344d4795}
{863b7733-7876-11e5-8f71-e4e140fa16a9}
{863b7732-7876-11e5-8f71-e4e140fa16a9}
{863b7731-7876-11e5-8f71-e4e140fa16a9}
{d344c614-8c42-11e5-80b9-806e6f6e6963}
timeout 2
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
bootshutdowndisabled Yes
default {863b7735-7876-11e5-8f71-e4e140fa16a9}
resumeobject {863b7734-7876-11e5-8f71-e4e140fa16a9}
displayorder {863b7735-7876-11e5-8f71-e4e140fa16a9}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
Firmware Application (101fffff)
-------------------------------
identifier {863b7731-7876-11e5-8f71-e4e140fa16a9}
description EFI Network
Firmware Application (101fffff)
-------------------------------
identifier {863b7732-7876-11e5-8f71-e4e140fa16a9}
description EFI SCSI Device
Firmware Application (101fffff)
-------------------------------
identifier {863b7733-7876-11e5-8f71-e4e140fa16a9}
description EFI SCSI Device
Firmware Application (101fffff)
-------------------------------
identifier {d344c614-8c42-11e5-80b9-806e6f6e6963}
description EFI SCSI Device
Windows Boot Loader
-------------------
identifier {863b7735-7876-11e5-8f71-e4e140fa16a9}
device partition=C:
path \Windows\system32\winload.efi
description Windows Server 2012 R2
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {863b7736-7876-11e5-8f71-e4e140fa16a9}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {863b7734-7876-11e5-8f71-e4e140fa16a9}
nx OptOut
Windows Boot Loader
-------------------
identifier {863b7736-7876-11e5-8f71-e4e140fa16a9}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{863b7737-7876-11e5-8f71-e4e140fa16a9}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage Recovery
displaymessageoverride Recovery
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{863b7737-7876-11e5-8f71-e4e140fa16a9}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
custom:46000010 Yes
Resume from Hibernate
---------------------
identifier {863b7734-7876-11e5-8f71-e4e140fa16a9}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence {863b7736-7876-11e5-8f71-e4e140fa16a9}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess Yes
EMS Settings
------------
identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems Yes
Debugger Settings
-----------------
identifier {4636856e-540f-4170-a130-a84776f4c654}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
-----------
identifier {5189b25c-5558-4bf2-bca4-289b11bd29e2}
Global Settings
---------------
identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit {4636856e-540f-4170-a130-a84776f4c654}
{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Boot Loader Settings
--------------------
identifier {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
{7ff607e0-4395-11db-b0de-0800200c9a66}
Hypervisor Settings
-------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Resume Loader Settings
----------------------
identifier {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
Device options
--------------
identifier {863b7737-7876-11e5-8f71-e4e140fa16a9}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi
Please let me know if any other information you need to know.
Really thanks for any help.
Regards
John