locked
DPM 2012 R2 and Bare Metal Recovery/System State System Protection Hyper-V Generation 2 VM Support

    Question

  • I have a physical Server 2012 R2 vhost running 2 Server 2012 R2 VMs setup as Generation 2 based. My DPM 2012 R2 server will perform the backup of the vhost just fine, but will consistently fail on the two Generation 2 based VMs. After further researching, I noticed that the physical Server 2012 R2 does not contain a EFI System Partition but the two VM's do (99 MB right in front of the C: boot partition).

    When I try to get a backup/sync change through DPM, it fails I'm guessing because of the EFI partition. The event log on the VM server indicates Event ID 521 with error code 0x80780119. Launching Windows Server Backup, the failed status gives: There is not enough disk space to create the volume shadow copy (because I'm guessing it is trying to store those on the EFI partition) The two VMs were loaded from ISO based installation. I guess my question is:

    Does DPM 2012 R2 support generation 2 VMs Bare Metal Recovery backups due to the EFI partition?


    Gary Adkins

    Thursday, December 19, 2013 4:19 PM

Answers

  • UPDATE-2

    The Windows product group has determined that this is a code defect and are working on a fix.  In the meantime, you can use one of the following workarounds so DPM initiated BMR backups succeed.

    Solution 1) Permanently disable WINRE so a snapshot is not attempted on the recovery partition when Windows image backup (BMR) is taken.

    a) open an administrative command prompt.
    b) Run: reagentc /disable
    c) BMR backups will now succeed. To enable WINRE again run: reagentc /enable

    Solution 2) Use a DPM pre-backup and post-backup script to disable WINRE before the BMR backup is taken and Re-enable WINRE after the BMR backup completes.

    Using pre-backup and post-backup scripts

    a) On the Windows 2012 R2 protected server (hyper-V guest) replace the ScriptingConfig.xml file with the new one below.


    LOCATION:  C:\Program Files\Microsoft Data Protection Manager\DPM\Scripting\ScriptingConfig.xml

    CONTENT OF NEW ScriptingConfig.xml.  Note the trailing space in "System Protection " <--must be trailing space.


    <?xml version="1.0" encoding="utf-8"?>
    <ScriptConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.microsoft.com/2003/dls/ScriptingConfig.xsd">
    <DatasourceScriptConfig DataSourceName="System Protection ">
    <PreBackupScript>C:\temp\Disable-WINRE.cmd</PreBackupScript>
    <PostBackupScript>C:\temp\Enable-WINRE.cmd</PostBackupScript>
    <TimeOut>5</TimeOut>
    </DatasourceScriptConfig>
    </ScriptConfiguration>


    b) Make the following two batch files (disable-winre.cmd and enable-winre.cmd) and save them in c:\temp folder on the protected server.

    Disable-WINRE.cmd content.

    reagentc /disable


    Enable-WINRE.cmd content.

    reagentc /enable


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.




    Tuesday, January 07, 2014 6:57 PM
    Moderator

All replies

  • Hi,

    As you have already discovered, this is not a DPM issue as DPM just leverages Windows backup.   Can you supply a screenshot of disk management inside one of the effected guests so I can try to duplicate the configuration.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, December 19, 2013 5:41 PM
    Moderator

  • Gary Adkins

    Thursday, December 19, 2013 5:59 PM
  • Thanks - setting this up now (in my spare time) and will see if I can find a workaround.  Stay Tuned..

    UPDATE

    I was able to duplicate your error:

    C:\Windows\system32>wbadmin start backup -allcritical -backuptarget:e:
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2013 Microsoft Corporation. All rights reserved.

    Retrieving volume information...
    This will back up (EFI System Partition),(C:),Recovery (300.00 MB) to e:.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

    The backup storage location that you selected is on the same physical hard
    disk as your operating system. If the hard disk fails, you may lose both
    your system data and backup data.

    The backup operation to E: is starting.
    Creating a shadow copy of the volumes specified for backup...
    Summary of the backup operation:
    ------------------

    The backup operation stopped before completing.
    The backup operation stopped before completing.
    Detailed error: ERROR - A Volume Shadow Copy Service operation error has
    occurred: (0x8004231f)
    Insufficient storage available to create either the shadow copy storage file or
    other shadow copy data.

    Log of files successfully backed up:
    C:\Windows\Logs\WindowsServerBackup\Backup-19-12-2013_18-39-24.log

    Log of files for which backup failed:
    C:\Windows\Logs\WindowsServerBackup\Backup_Error-19-12-2013_18-39-24.log

    There is not enough disk space to create the volume shadow copy on the storage l
    ocation. Make sure that, for all volumes to be backup up, the minimum required d
    isk space for shadow copy creation is available. This applies to both the backup
     storage destination and volumes included in the backup.
    Minimum requirement: For volumes less than 500 megabytes, the minimum is 50 mega
    bytes of free space. For volumes more than 500 megabytes, the minimum is 320 meg
    abytes of free space.
    Recommended: At least 1 gigabyte of free disk space on each volume if volume siz
    e is more than 1 gigabyte.
    ERROR - A Volume Shadow Copy Service operation error has
    occurred: (0x8004231f)
    Insufficient storage available to create either the shadow copy storage file or
    other shadow copy data.

    CAUSE

    The problem is that the 300MB Recovery Partition only has about 31MB free space and VSS requires minimum of 50MB to create a snapshot.

    You can see this by assigning a drive letter to the volume and doing a DIR /A


    C:\Windows\system32>mountvol
    Creates, deletes, or lists a volume mount point.

    MOUNTVOL [drive:]path VolumeName
    MOUNTVOL [drive:]path /D
    MOUNTVOL [drive:]path /L
    MOUNTVOL [drive:]path /P
    MOUNTVOL /R
    MOUNTVOL /N
    MOUNTVOL /E
    MOUNTVOL drive: /S

        path        Specifies the existing NTFS directory where the mount
                    point will reside.
        VolumeName  Specifies the volume name that is the target of the mount
                    point.
        /D          Removes the volume mount point from the specified directory.
        /L          Lists the mounted volume name for the specified directory.
        /P          Removes the volume mount point from the specified directory,
                    dismounts the volume, and makes the volume not mountable.
                    You can make the volume mountable again by creating a volume
                    mount point.
        /R          Removes volume mount point directories and registry settings
                    for volumes that are no longer in the system.
        /N          Disables automatic mounting of new volumes.
        /E          Re-enables automatic mounting of new volumes.
        /S          Mount the EFI System Partition on the given drive.

    Possible values for VolumeName along with current mount points are:

        \\?\Volume{80001a12-3033-4169-8985-5ce8dacf9b07}\
            C:\

        \\?\Volume{fa2cb1b2-93bf-4ce5-ad31-07581a9e887a}\
            E:\

        \\?\Volume{152eadd9-f001-4562-bb9c-dc0cc50c638c}\
            *** NO MOUNT POINTS ***

        \\?\Volume{889daeac-68ea-11e3-80b4-806e6f6e6963}\
            D:\

    C:\Windows\system32>mountvol x: \\?\Volume{152eadd9-f001-4562-bb9c-dc0cc50c638c}\

    C:\Windows\system32>mountvol
    Creates, deletes, or lists a volume mount point.

    MOUNTVOL [drive:]path VolumeName
    MOUNTVOL [drive:]path /D
    MOUNTVOL [drive:]path /L
    MOUNTVOL [drive:]path /P
    MOUNTVOL /R
    MOUNTVOL /N
    MOUNTVOL /E
    MOUNTVOL drive: /S

        path        Specifies the existing NTFS directory where the mount
                    point will reside.
        VolumeName  Specifies the volume name that is the target of the mount
                    point.
        /D          Removes the volume mount point from the specified directory.
        /L          Lists the mounted volume name for the specified directory.
        /P          Removes the volume mount point from the specified directory,
                    dismounts the volume, and makes the volume not mountable.
                    You can make the volume mountable again by creating a volume
                    mount point.
        /R          Removes volume mount point directories and registry settings
                    for volumes that are no longer in the system.
        /N          Disables automatic mounting of new volumes.
        /E          Re-enables automatic mounting of new volumes.
        /S          Mount the EFI System Partition on the given drive.

    Possible values for VolumeName along with current mount points are:

        \\?\Volume{80001a12-3033-4169-8985-5ce8dacf9b07}\
            C:\

        \\?\Volume{fa2cb1b2-93bf-4ce5-ad31-07581a9e887a}\
            E:\

        \\?\Volume{152eadd9-f001-4562-bb9c-dc0cc50c638c}\
            X:\

        \\?\Volume{889daeac-68ea-11e3-80b4-806e6f6e6963}\
            D:\

    X:\>dir /a /s
     Volume in drive X is Recovery
     Volume Serial Number is BA3C-AF14

     Directory of X:\

    12/19/2013  10:18 AM    <DIR>          Recovery
    12/19/2013  11:05 AM    <DIR>          System Volume Information
                   0 File(s)              0 bytes

     Directory of X:\Recovery

    12/19/2013  10:18 AM    <DIR>          .
    12/19/2013  10:18 AM    <DIR>          ..
    12/19/2013  10:57 AM    <DIR>          WindowsRE
                   0 File(s)              0 bytes

     Directory of X:\Recovery\WindowsRE

    12/19/2013  10:57 AM    <DIR>          .
    12/19/2013  10:57 AM    <DIR>          ..
    06/18/2013  07:08 AM         3,170,304 boot.sdi
    12/19/2013  10:19 AM             1,013 ReAgent.xml
    09/30/2013  01:21 PM       249,785,287 Winre.wim
                   3 File(s)    252,956,604 bytes

         Total Files Listed:
                   3 File(s)    252,956,604 bytes
                   7 Dir(s)      31,383,552 bytes free

    SOLUTION

    You can move the shadowcopy storage for the recovery partition volume to the C: volume.

    C:\Windows\system32>vssadmin add shadowstorage /for=\\?\Volume{152eadd9-f001-4562-bb9c-dc0cc50c638c}\ /on=c: /maxsize=500MB
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Successfully added the shadow copy storage association

    C:\Windows\System32>vssadmin list shadowstorage
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{80001a12-3033-4169-8985-5ce8dacf9b07}\
       Shadow Copy Storage volume: (C:)\\?\Volume{80001a12-3033-4169-8985-5ce8dacf9b07}\
       Used Shadow Copy Storage space: 0 bytes (0%)
       Allocated Shadow Copy Storage space: 0 bytes (0%)
       Maximum Shadow Copy Storage space: 2.85 GB (10%)

    Shadow Copy Storage association
       For volume: (E:)\\?\Volume{fa2cb1b2-93bf-4ce5-ad31-07581a9e887a}\
       Shadow Copy Storage volume: (E:)\\?\Volume{fa2cb1b2-93bf-4ce5-ad31-07581a9e887a}\
       Used Shadow Copy Storage space: 0 bytes (0%)
       Allocated Shadow Copy Storage space: 0 bytes (0%)
       Maximum Shadow Copy Storage space: 29.4 GB (30%)

    Shadow Copy Storage association
       For volume: (\\?\Volume{152eadd9-f001-4562-bb9c-dc0cc50c638c}\)\\?\Volume{152eadd9-f001-4562-bb9c-dc0cc50c638c}\
       Shadow Copy Storage volume: (C:)\\?\Volume{80001a12-3033-4169-8985-5ce8dacf9b07}\
       Used Shadow Copy Storage space: 0 bytes (0%)
       Allocated Shadow Copy Storage space: 0 bytes (0%)
       Maximum Shadow Copy Storage space: 500 MB (1%)

    RETEST WBADMIN

    C:\>wbadmin start backup -allcritical -backuptarget:e:
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2013 Microsoft Corporation. All rights reserved.

    Retrieving volume information...
    This will back up (EFI System Partition),(C:),Recovery(X:) to e:.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

    The backup storage location that you selected is on the same physical hard
    disk as your operating system. If the hard disk fails, you may lose both
    your system data and backup data.

    The backup operation to E: is starting.
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Creating a backup of volume (EFI System Partition) (99.00 MB), copied (0%).
    Compacting the virtual hard disk for volume (EFI System Partition) (99.00 MB), completed (0%).
    The backup of volume (EFI System Partition) (99.00 MB) completed successfully.
    Creating a backup of volume (C:), copied (0%).
    Creating a backup of volume (C:), copied (0%).
    Creating a backup of volume (C:), copied (0%).


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Thursday, December 19, 2013 6:12 PM
    Moderator
  • Mike,

    Not sure I would call that a solution. This is a work around at best, and one that certainly doesn't scale very well. Also, from what is being reported here...

    http://social.technet.microsoft.com/Forums/windowsserver/en-US/7373a7b8-01c8-4e2b-aaaa-513b7dad56f4/windows-server-2012-r2-vm-back-up-fails-with-insufficient-storage-available-to-create-either-the

    "...the backups work however after recovering the new VM image the Add ShadowStorage Map is lost and has to be recreated for backups to work again."

    ...it's not a work around that can be relied on in a production environment. So how long will we have to wait for a hotfix? Realizing without one backups of Gen2 VMs are broken.

    Saturday, January 04, 2014 6:01 PM
  • Hi,

    As mentioned earlier, this is not a problem in DPM code. The windows backup group would need to make windows server backup exclude that small 300mb Partition / volume from shadow copy list and just back it up natively.

    Please work with the Windows support group to report the problem and ask for a better solution / fix.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.



    Saturday, January 04, 2014 8:20 PM
    Moderator
  • Thanks Mike, that's pure semantics though because it's through DPM that my backups are failing...DPM code, or not. Of course it is much easier for you to say "this is not a problem in DPM code" and deflect taking any responsibility to help resolve the problem.
    Saturday, January 04, 2014 8:49 PM
  • Hi,

    From a DPM perspective, I provided a workaround to allow DPM recovery points to succeed which solves the problem as reported. There are no DPM code changes that can fix or influence Windows server BMR backup behavior.

    UPDATE - FYI - I have pinged the Windows product group to make them aware of the reported problem so they can review internally.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.



    Saturday, January 04, 2014 10:41 PM
    Moderator
  • UPDATE-2

    The Windows product group has determined that this is a code defect and are working on a fix.  In the meantime, you can use one of the following workarounds so DPM initiated BMR backups succeed.

    Solution 1) Permanently disable WINRE so a snapshot is not attempted on the recovery partition when Windows image backup (BMR) is taken.

    a) open an administrative command prompt.
    b) Run: reagentc /disable
    c) BMR backups will now succeed. To enable WINRE again run: reagentc /enable

    Solution 2) Use a DPM pre-backup and post-backup script to disable WINRE before the BMR backup is taken and Re-enable WINRE after the BMR backup completes.

    Using pre-backup and post-backup scripts

    a) On the Windows 2012 R2 protected server (hyper-V guest) replace the ScriptingConfig.xml file with the new one below.


    LOCATION:  C:\Program Files\Microsoft Data Protection Manager\DPM\Scripting\ScriptingConfig.xml

    CONTENT OF NEW ScriptingConfig.xml.  Note the trailing space in "System Protection " <--must be trailing space.


    <?xml version="1.0" encoding="utf-8"?>
    <ScriptConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.microsoft.com/2003/dls/ScriptingConfig.xsd">
    <DatasourceScriptConfig DataSourceName="System Protection ">
    <PreBackupScript>C:\temp\Disable-WINRE.cmd</PreBackupScript>
    <PostBackupScript>C:\temp\Enable-WINRE.cmd</PostBackupScript>
    <TimeOut>5</TimeOut>
    </DatasourceScriptConfig>
    </ScriptConfiguration>


    b) Make the following two batch files (disable-winre.cmd and enable-winre.cmd) and save them in c:\temp folder on the protected server.

    Disable-WINRE.cmd content.

    reagentc /disable


    Enable-WINRE.cmd content.

    reagentc /enable


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.




    Tuesday, January 07, 2014 6:57 PM
    Moderator
  • Thank you for your assistance Mike in the notification to the Windows product group to make them aware of this issue. We have opted to not run any generation 2 based VMs until this problem has been resolved. 

    Gary Adkins

    Wednesday, January 08, 2014 10:16 PM
  • Hey

    I just encountered the same problem with 2 newly installed Windows Server 2012R2 on Hyper-V R2 Free - both installed as 2nd generation machines. 

    the workaround with disabling & enabling the WinRE works, but when i try to move the shadowstorage for the recovery partition it tells me i used a wrong option !!? 

    Here are my CMD outputs (german windows ;) )

    PS C:\Users\administrator.ELAN-HANNOVER>  vssadmin list shadowStorage
    vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
    (C) Copyright 2001-2013 Microsoft Corp.
    
    Schattenkopie-Speicherassoziation
       Für Volume: (C:)\\?\Volume{34d4f59a-7260-4ce4-8c56-32c03e5f968a}\
       Schattenkopie-Speichervolume: (C:)\\?\Volume{34d4f59a-7260-4ce4-8c56-32c03e5f968a}\
       Verwendeter Schattenkopie-Speicherbereich: 0 Bytes (0%)
       Zugewiesener Schattenkopie-Speicherbereich: 0 Bytes (0%)
       Max. Schattenkopie-Speicherbereich: 7,95 GB (10%)
    
    Schattenkopie-Speicherassoziation
       Für Volume: (E:)\\?\Volume{af840e77-274a-4715-8820-9da0afd34798}\
       Schattenkopie-Speichervolume: (E:)\\?\Volume{af840e77-274a-4715-8820-9da0afd34798}\
       Verwendeter Schattenkopie-Speicherbereich: 0 Bytes (0%)
       Zugewiesener Schattenkopie-Speicherbereich: 0 Bytes (0%)
       Max. Schattenkopie-Speicherbereich: 20,0 GB (10%)
    
    Schattenkopie-Speicherassoziation
       Für Volume: (\\?\Volume{5595a40f-c830-4bb1-bfe1-7d1454f95e14}\)\\?\Volume{5595a40f-c830-4bb1-bfe1-7d1454f95e14}\
       Schattenkopie-Speichervolume: (\\?\Volume{5595a40f-c830-4bb1-bfe1-7d1454f95e14}\)\\?\Volume{5595a40f-c830-4bb1-bfe1-7
    d1454f95e14}\
       Verwendeter Schattenkopie-Speicherbereich: 5,20 MB (0%)
       Zugewiesener Schattenkopie-Speicherbereich: 2,93 GB (0%)
       Max. Schattenkopie-Speicherbereich: UNBOUNDED (2864001445%)
    
    Schattenkopie-Speicherassoziation
       Für Volume: (\\?\Volume{9308c9de-48f0-4644-b67e-b50a7efab555}\)\\?\Volume{9308c9de-48f0-4644-b67e-b50a7efab555}\
       Schattenkopie-Speichervolume: (\\?\Volume{9308c9de-48f0-4644-b67e-b50a7efab555}\)\\?\Volume{9308c9de-48f0-4644-b67e-b
    50a7efab555}\
       Verwendeter Schattenkopie-Speicherbereich: 0 Bytes (0%)
       Zugewiesener Schattenkopie-Speicherbereich: 0 Bytes (0%)
       Max. Schattenkopie-Speicherbereich: 32,0 MB (10%)

    PS C:\Users\administrator.xxx> vssadmin add shadowstorage /for=\\?\Volume{9308c9de-48f0-4644-b67e-b50a7efab555
    }\ /on=c: /MaxSize=500MB
    vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
    (C) Copyright 2001-2013 Microsoft Corp.
    
    Fehler: Ungültige Option.

    Fehler: Ungültige Option. = Error: Invalid Option

    Friday, February 14, 2014 2:58 PM
  • Hi,

    I cannot explain the "invalid parameter" error, but try using the DPM pre and post backup script solution.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, February 14, 2014 3:38 PM
    Moderator
  • Hi Mike,

    Is there any update on this issue from the Windows product team?  It's been over a month since the last update and I would hope that, given the scope of the machines that this affects, it would not be a back-burner issue for them.

    -Corbin

    Sunday, March 23, 2014 12:23 PM
  • We also encounter this issue. We have a lot of Gen2 VM's. It is NOT an option to not use them. Currently we have a big issue since this affects a lot of VM's.

    The weird thing is, it did work before. But at a certain point this started to cause a problem.

    Any update on a fix?


    Boudewijn Plomp, BPMi Infrastructure & Security

    Tuesday, March 25, 2014 11:47 AM
  • Hi,

    The Windows team has published the following KB article with the fix and workarounds:

    System image backup fails after you upgrade to Windows 8.1 and Windows Server 2012 R2


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Tuesday, March 25, 2014 3:22 PM
    Moderator
  • Thank you for the link. I must note there is no fix available yet, only a work-around. The KB talks about upgrading to Windows 8.1 or Windows Server 2012 R2. But this problem also occurs on fresh installations.

    The work-around not a scailable solution. Is there any timeframe we might expect a fix? I am not sure we need to escalate this to Microsoft Support.


    Boudewijn Plomp, BPMi Infrastructure & Security

    Monday, March 31, 2014 8:34 AM
  • I'm seeing this issue also with VMWare 5.5 guests.  I'm trying the workaround and when I manually disable reagentc, my backup job finishes successfully.  I've implemented the pre and post backup scripts on a test server.  It looks like the pre-backup script is disabling reagentc and the backup is running (issued from DPM) however my post backup script is failing to reenable reagentc. 

    Monday, April 14, 2014 7:13 PM
  • Never mind.  I was originally putting the scripts in the same folder as the scriptingconfig.xml file thinking that made better sense to have them together.  I moved them to c:\windows\temp and updated the scriptingconfig.xml file and then my backup worked.  Seems strange that it would run the disable script but not the enable script.

    Anyway, while this is a nice workaround, I'd be interested in finding out when a fix might be available. 

    Monday, April 14, 2014 7:20 PM
  • Has there been any hotfix released for this yet besides manually editing the recovery partition and disabling and re-enabling reagentc?


    • Edited by Nutshell30 Friday, May 30, 2014 12:16 AM
    Friday, May 30, 2014 12:15 AM
  • Hi,

    I would keep an eye on this Windows KB article to see if they announce a fix for the issue.

    System image backup fails after you upgrade to Windows 8.1 and Windows Server 2012 R2

    Any further inquiries should be posted in the Windows support forum.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, May 30, 2014 12:36 AM
    Moderator