October 2014 update rollup for Windows Server 2012 R2 and Data Protection Manager 2012 R2

Hello all,
After installing the October 2014 update rollup for Windows Server 2012 R2 (KB2995388) on our Windows 2012 R2 Core Edition backup jobs of System State start to Fail, below the generic error:
The replica of Non VSS Datasource Writer on hostname.domain is inconsistent with the protected data source. All protection activities for this data source will fail until the replica is synchronized with consistency check.
The job was cancelled. The user either cancelled the job or modified the associated protection group.
Removing the update rollup all jobs complete without errors. Somebody is expiriencing the same issue? How can we resolve the problem?
Thnks, Andrea

Hi Andrea,
Have you installed the update 2919355?
To apply update 2995388, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2.
According to the official website, the issue which you described is not listed as the known issue.
Please uninstall this update and continue to monitor the official website for the latest news.
Best Regards.
Steven Lee
TechNet Community Support

Similar Messages

  • Error loading Virtual Machine Manager 2012 and Data Protection Manager 2012 modules together

    Hi.
    Very strange issue: when i try to load together Virtual Machine Manager 2012 and Data Protection Manager 2012 modules - script fails. If first loaded Virtual Machine Manager 2012 module:
    Import-Module : Cannot load Windows PowerShell snap-in C:\Program Files\Microsoft Data Protection Manager\DPM2012\bin\ObjectModelCmdlet.dll because of the following error: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property
    for more information.
    Loader Exceptions:
    Could not load type 'Microsoft.Internal.EnterpriseStorage.Dls.Utils.AlertTypes.AlertEnum' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    At C:\Program Files\Microsoft Data Protection Manager\DPM2012\bin\Modules\DataProtectionManager\DataProtectionManager.psm1:2 char:14
    + Import-Module <<<<  (Join-Path $cmdletDllPath ObjectModelCmdlet.dll)
        + CategoryInfo          : ResourceUnavailable: (:) [Import-Module], PSSnapInException
        + FullyQualifiedErrorId : PSSnapInLoadFailure,Microsoft.PowerShell.Commands.ImportModuleCommand
    If first loaded DPM 2012 module::
    Import-Module : Cannot load Windows PowerShell snap-in C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Microsoft.SystemCenter.VirtualMachineManager.dll because of the following error: Unable to load one or more of the requested
    types. Retrieve the LoaderExceptions property for more information.
    Loader Exceptions:
    Could not load type 'Microsoft.VirtualManager.Utils.TypeConverterEnumHelper`1' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.TypeConverterEnumHelper`1' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineException' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Method 'get_BootOrder' in type 'Microsoft.SystemCenter.VirtualMachineManager.ClientObjectHWSettingsSourceAdapter' from assembly 'Microsoft.SystemCenter.VirtualMachineManager, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have
    an implementation.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMStartAction' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Method 'get_BootOrder' in type 'HardwareConfigSettingsAdapter' from assembly 'Microsoft.SystemCenter.VirtualMachineManager, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have an implementation.
    Could not load type 'Microsoft.VirtualManager.Utils.VMStartAction' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMStartAction' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMStartAction' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMSCSIControllerType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMSCSIControllerType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.ServicingTypeValues' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.FabricCapabilityType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.SKUType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.VMComputerSystemState' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    Could not load type 'Microsoft.VirtualManager.Utils.CarmineObjectType' from assembly 'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    At \\team\dfs\scripts\Admin\Scvmm\Move-VirtualMachine.ps1:103 char:16
    +         Import-Module <<<<  'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules\virt
    ualmachinemanager\virtualmachinemanager.psd1';
        + CategoryInfo          : ResourceUnavailable: (:) [Import-Module], PSSnapInException
        + FullyQualifiedErrorId : PSSnapInLoadFailure,Microsoft.PowerShell.Commands.ImportModuleCommand

    Vote if you have same problem:
    https://connect.microsoft.com/PowerShell/feedback/details/873348/scvmm-and-scdpm-powershell-modules-cant-work-together

  • VssNullProver stopped after installing Update Rollup 3 for System Center Data Protection Manager 2012 R2

    I recently installed Update Rollup 3 for System Center Data Protection Manager 2012 R2.
    As part of the update I updated all DPM Agents, including the ones on our Hyper-V Servers (which are part of a cluster). I also rebooted every DPM Protected Servers. After reboot all Hyper-V Servers raise a warning that the VssNullProvider service has stopped.
    Backup seems to work properly. I can start the VssNullProvider service manually. But after the next backup the service it is stopped again. Exactly the same issue occurs on our test Hyper-V Cluster. All our Hyper-V Servers run Windows Server 2012 R2 and
    we use System Center Virtual Machine Manager 2012 R2.
    Something is not ok with Update Rollup 3. Any suggestions?
    Boudewijn Plomp, BPMi Infrastructure & Security
    Please remember, if you see a post that helped you please click "Vote as Helpful" and if it answered your question, please click "Mark as Answer".

    Hi
    SEE NEW BLOG:
    Support Tip Service Manager alert for the VSSNullProvider service after installing
    DPM 2012 R2 UR3
    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.
    Thanks!
    Boudewijn Plomp, BPMi Infrastructure & Security | Please remember, if you see a post that helped you please click "Vote as Helpful" and if it answered your question, please click "Mark as Answer".

  • Help!  oracle report out of order after update Rollup for windows 2000 sp4

    hello once again
    i haven't received any solution of my problem, so i am again uploading it.
    ----PROBLEM IS GIVEN BELOW-----
    i am having a problem in oracle report printing (2000,6i). I have installed patch "update Rollup for windows 2000 sp4" on windows 2000. now when i send report(132 column) for printing to the printer, the report fails to expand to 132 columns and data is printed in unformatted fashion. in order to print the report correctly i have to remove the patch from the windows.i have set all parameters and
    defining page size in files like wide180.PRT in printers folder in oracle directory.
    Is there anyway to print the report without uninstalling windows patch?
    thanks

    I don't have any idea about this issue. Maybe someone else on this forum can help. Meanwhile, there are couple of places you can search for this issue:
    Search google for printing issues with this patch
    Search Microsoft forums for Windows 2000
    And if you have metalink account, search metalink forum, document/note or open a SR for this.

  • Do we need CALS for windows server 2008 R2 and 2012 R2 if 2008 R2 is just a stepping stone?

    We currently have a server on Windows Server 2008 RC SP2 64-bit with approximately 20 clients.
    We want to upgrade to Windows server 2012 R2 but first need to upgrade to Windows 2008 R2 to allow us to do a straight upgrade.
    Is it possible to upgrade to Windows Server 2008 R2 with the 5 CAL's included and then upgradeto 2012 R2 and install 20 new CAL's and keep all users accounts and domain PC's the same? 

    Ok sorry for using the wrong terminology... I was under the impression for each client (Computer) connecting to the server we will need a CAL (Client Activation License) in order for the computer to be a domain PC on the server. Do I need 20 CALS's
    for Windows Server 2008 R2 and then another for Windows Server 2012 R2 if we are only upgrading to 2008 R2 to be able to upgrade to 2012 R2 without having to do a clean install.
    For WindowsServer (Standard edition or Enterprise edition or DataCenter edition), a Client Access License (CAL) is required for each device (if you're using the per-Device CAL licensing method), or, is required for each user (if you're using the per-User
    CAL licensing method).
    (whether you use per-Device, or per-User, is up to you, it comes down to cost).
    CALs are version-specific (to a point) - i.e. if you purchased WS2008 CALs for your 20 devices, for use with your WS2008 server, and you are now upgrading that server to WS2012, you need to upgrade your CALs.
    If you are adding a second server which is WS2012, and you are keeping your WS2008 server, you need to upgrade your CALs (because you only purchased WS2008 CALs which don't grant you the rights to connect to the newer server).
    If you were to install your second server as WS2008, you wouldn't need to purchase additional CALs, because as long as the version is the same, a single CAL grant you access to unlimited server (of the same version).
    CALs can be tricky to correctly license.
    Here's some introductory reading:
    http://www.microsoft.com/licensing/about-licensing/client-access-license.aspx#tab=1
    And, none of this relates to the technical aspects of product installation/configuration at all (e.g. clean install vs. upgrade).
    Windows Server CALs are not license keys/tokens/files which you install/load/download - Windows Server CALs are quite literally paper-based (just like a drivers license or car registration). You are required to have them, to be correctly licensed, but, you
    don't physically do anything with them to own/drive a car.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Where is Support for Windows Update issues for Windows Server?

    Where is Support for Windows Update Issues for Windows Server?
    Windows Update keeps prompting to install an important update, KB2871690 and continually fails with error code 0x800f922
    I ran all the fixes I can find, it still fails.
    I also tried the manual install, fails.
    Microsoft used to provide no charge support for Windows Update issues. They additionally offer online fixes  for other versions of windows, but not server, and I can't find a forum.
    I also cannot ignore the update, it continually prompts.
    I ran the windowsupdate.diagcab and it continually states it fixes Windows Update error 0x80070057, by resetting windows update data store. It further states it fixes Problems installing recent updates.
    But it doesn't. I've run it 50 times, and it says the same thing every time.
    So there is no support for windows update, and no support for windowsupdate.diagcab.
    What's the deal?

    I've done the SFC/ SCANNOW and DISM
    here is the cbs.log
    What are we looking for?
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~BT\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360'. -
    CDISMManager::put_ScratchDir
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$Windows.~BT\sources" - CDISMManager::LoadLocalImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Dism.exe version: 6.2.9200.16384
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Executing command line: X:\$Windows.~BT\sources\dism.exe  /logpath:X:\$Windows.~BT\sources\Panther\cbs.log
    /scratchdir:X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360 /image:X:\ /is-serviceable
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\FolderProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\FolderProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\WimProvider.dll -
    CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\VHDProvider.dll -
    CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\VHDProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\ImagingProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\ImagingProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\CompatProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\CompatProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2013-12-04 19:48:20, Warning               DISM   DISM.EXE: Failed to load WimManager. Try running from the Deployment Tools Command Prompt. If the issue persists, ensure that wimgapi.dll
    and wimserv.exe are up to date.
    2013-12-04 19:48:20, Warning               DISM   DISM.EXE: Failed to add any commands.
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 physical location path: X:\ - CDISMManager::CreateImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Copying DISM from "X:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD"
    - CDISMManager::LoadRemoteImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Image Session: PID=1644 TID=1656 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Defaulting SystemPath to X:\ - CDISMOSServiceManager::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Defaulting Windows folder to X:\Windows - CDISMOSServiceManager::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Manager: PID=1612 TID=1616 Image session successfully loaded from the temporary location: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD
    - CDISMManager::CreateImageSession
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Setting SystemPath to X:\ - CDISMOSServiceManager::SetSystemPath
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Target image information: OS Version=6.2.9200.16384, Image architecture=amd64
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting the collection of providers from an image provider store type. -
    CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Get the registry path to the SOFTWARE hive located at X:\Windows\system32\config\SOFTWARE
    and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive
    2013-12-04 19:48:22, Info                  DISM   DISM Driver Manager: PID=1644 TID=1656 Further logs for driver related operations can be found in the target operating
    system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Current image session is [OFFLINE] - CTransmogManager::GetMode
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Determined WinDir path = [X:\Windows] - CTransmogManager::GetWinDirPath
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Product Type: [ServerNT] - CTransmogManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Processing the top level command token(is-serviceable). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the PE Provider.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Finalizing CBS core. - CDISMPackageManager::Finalize
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM OS Provider: PID=1644 TID=1672 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

  • Oracle report out of order after update Rollup for windows 2000 sp4

    hi
    i am having a problem in oracle report printing (2000,6i). I have installed patch "update Rollup for windows 2000 sp4" on windows 2000. now when i send report(132 column) for printing to the printer, the report fails to expand to 132 columns and data is printed in unformated fashion. in order to print the report correctly i have to remove the patch from the windows. Is there anyway to print the report without uninstalling windows patch?
    thanks

    Hi
    first of all thanks for replying .if you mean defining page size in files like wide180.PRT in printers folder in oracle directory, off course i have set parameters. thing is that printing works fine without windows patch but it gets deteriorated after installing the patch.
    Thanks

  • Data Protection Manager 2012 - Inconsistent when backing up Deduplicated File Server

    Protected Server
    Server 2012 File Server with Deduplication running on Data drive
    DPM Server
    Server 2012
    Data Protection Manager 2012 Service Pack 1
    We just recently upgraded our DPM server from DPM 2010 to DPM 2012 primarily because it is supposed to support Data Deduplication. Our primary File server that holds our home directories etc. is limited on space and was quickly running low so just after
    we got DPM 2012 in place we optimized the drive on the file server which compressed the data about 50%. Unfortunately shortly after enabling deduplication the protected shares on the deduplicated volume are getting a Replica is Inconsistent error.
    I continually get Replica is Inconsistent for the Server that has deduplication running on it. All of the other protected servers are being protected as they should be. I have run a consistency check multiple times probably about 10 times and it keeps going
    back to Replica is inconsistent. The replica volume shows that it is using 3.5 TB and the Actual protect volume is 4TB in size and has about 2.5 TB of data on it with Deduplication enabled.
    This is the details of the error
    Affected area:   G:\
    Occurred since: 1/12/2015 4:55:14 PM
    Description:        The replica of Volume G:\ on E****.net is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with
    consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.
    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
    More information
    Recommended action: 
    Synchronize with consistency check.
    Run a synchronization job with consistency check...
    Resolution:        
    To dismiss the alert, click below
    Inactivate
    Steps taken to resolve - I’ve spent some time doing some searches and haven’t found any solutions to what I am seeing. I have the data deduplication role installed on the DPM server which has been the solution for many people seeing similar issues. I have
    also removed that role and the added it back. I have also removed the protected server and added it back to the protection group. It synchronizes and says consistent then after a few hours it goes back to inconsistent. When I go to recovery it shows that I
    have recovery points and it appears that I can restore but because the data is inconstant I don’t feel I can trust the data in the recovery points. Both the protected server and the DPM servers’ updates are managed via a WSUS server on our network.
    You may suggest I just un-optimize the drive on the protected server however after I have optimized the drive it takes a large amount more of space to un-optimize it (Anyone know why that is) anyways the drive isn’t large enough to support un-optimization.
    If anyone has any suggestions I would appreciate any help. Thanks in advanced.

    Ok I ran a consistency check and it completed successfully with the following message. However after a few minutes of it showing OK it now shows Replica is Inconsistent again.
    Type: Consistency check
    Status: Completed
    Description: The job completed successfully with the following warning:
     An unexpected error occurred while the job was running. (ID 104 Details: Cannot create a file when that file already exists (0x800700B7))
     More information
    End time: 2/3/2015 11:19:38 AM
    Start time: 2/3/2015 10:34:35 AM
    Time elapsed: 00:45:02
    Data transferred: 220.74 MB
    Cluster node -
    Source details: G:\
    Protection group members: 35
     Details
    Protection group: E*
    Items scanned: 2017709
    Items fixed: 653
    There was a log for a failed synchronization job from yesterday here are the details of that.
    Type: Synchronization
    Status: Failed
    Description: The replica of Volume G:\ on E*.net is not consistent with the protected data source. (ID 91)
     More information
    End time: 2/2/2015 10:04:01 PM
    Start time: 2/2/2015 10:04:01 PM
    Time elapsed: 00:00:00
    Data transferred: 0 MB
    Cluster node -
    Source details: G:\
    Protection group members: 35
     Details
    Protection group: E*

  • Data Protection Manager 2012 R2 agent: SetDpmServer returns error 0x80004005

    I have a Windows Server 2008 R2 server running business-critical applications. This is an ancient server, and I don't know who and how installed and configured its OS. I need to protect it using DPM 2012 R2.
    I was unable to automatically deploy DPM agent to this server due to error, so I installed the agent manually. However, when I try to manually associate the agent with a DPM server, it returns the following error:
    C:\Program Files\Microsoft Data Protection Manager\DPM\bin>SetDpmServer.exe -dpmservername SERVER
    Configuring dpm server settings and firewall settings for dpm server =[SERVER]
    Configuring dpm server settings and firewall settings for dpm server =[DOMAIN\SERVER]
    SetDpmServer failed with errorcode =0x80004005, error says: To further troubleshoot failures with SetDpmServer, go to
    http://go.microsoft.com/fwlink/?LinkId=169142
    The link is invalid. I've found a Techne article mentioning this error code, which tells only to check access to the DPM server from the server with the agent. The agent does have access, but the error persists even if I turn off the firewall completely.
    I even reset the local firewall rules to default settings, but it has had no visual effect (except I had to restore several rules manually).
    I suspect that something is wrong with OS settings or services. Any ideas what can be investigated next?
    Evgeniy Lotosh<br/> MCSE: Server infractructire, MCSE: Messaging

    Hi
    If you add the following predefined default firewall rules, the setdpmserver.exe should run:
    Windows Management Instrumentation
    Remote Service Management
    File and Printer Sharing
    Hope this helps. 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.

  • Data Protection Manager 2012 on Hyper-V Windows 2008 R2 and NAS connectivity

    Hi, we currently use Symantec Backup Exec 2010/2012 on Windows 2008 R2 servers storing the data on two LAN-connected NAS servers. As part of our MS licensing package, we have obtained System Center 2012. I'm seeing if DPM can replace our BE software, but
    I'm running into a major hurdle, I can't connect (Add) either of the NAS machines. I see on DPM posts where you need to have a physical connection to the NAS (iSCSi or fiber channel) not an option on the NAS (Thecus N8800 & N8900 (no ability to add cards)
    and SMB 3.0 (appears to be a Windows 2012-only option ... I dread 2012 and don't want to move to it right now). Can my virtualized (hyper-v) W2008 R2 server see a non-connected NAS and if so, how do I pull this off.
    Thanks

    Hi 
    DPM needs local storage to connect to. you cannot use a NAS or USB device to backup to like with other backup software.

  • Data Protection Manager 2012 R2

    Hey Guys,
    We're using DPM 12r2 for our backups and we ran into an issue where basically where we lost our exchange server and our replica is inconsistent. I can see the data on the drive but I can't create a recovery point because the protection is inactive. Do any of you have an idea on what to do?
    This topic first appeared in the Spiceworks Community

    DPM doesn't support SQL 2014 yet. See
    Mike's comment and
    DPM support matrix for more information.
    If you are required to use SQL 2014, you can setup
    database mirroring — DPM 2012 R2 UR2 can backup such configuration. It's still unsupported, though.
    http://about.me/exchange12rocks

  • Tape Consumption/Utilization on System Center Data Protection Manager 2012

    Hi Guys,
    I have setup System Center DPM 2012 for Exchange 2010 Backup, the tape library that i am using is Dell TL4000 with 45 Slots and two LTO 5 Drives. The total size of Exchange backup is 33 TB but the no. of tapes used to backup are 16 LTO5 tapes.
    The native capacity of LTO5 tape is 1.5 TB and the compressed capacity is 3 TB.
    The total no. of tapes used for exchange backup are 16 therefore 16 Tapes x 3 TB = 48 TB where as the total backup size of exchange is 33 TB which means there is a complete wastage of 15 TB tape storage. 
    Does any one know if its a known issue on DPM? Is there a way where i can tweak the tape utilization? Any help will be much appreciated.
    Thanks in advance!
    Sajeel

    Hi,
    The LTO5 compression ratio is usually an average of 2:1 depending on the data being written.  Some data is not compressible like .jpg .bmp etc. so it's not predictable ahead of time how much data will fill a tape.  The fact
    that you are achieving greater than native capacity shows that compression is enabled and working.    
    Besides the data not compressing as much as you like, the only other explanation for not getting more data on a tape is it may not be filling before we either get an EOM from the drive, or we get an IO error that DPM is going to convert to an EOM.  
    To see if it is the latter check the DPMRA Errlogs for the error code 0x8007045D. 
    Open an Administrative command prompt. 
    CD C:\Program file\Microsoft System Center 2012\DPM\DPM\Temp 
    Find /I "0x8007045D" DPMRA*.Errlog >C:\temp\DPMRA0x8007045D.TXT 
    Notepad C:\temp\DPMRA0x8007045D.TXT
    If you find any, add the registry settings for BufferQueueSize and BusyRetryCount using the following
    BLOG.
    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.

  • Data Protection Manager 2012 to protect clients backup

    Hi All,
    I have a requirement to backup 200 clients data (including email PST files). I have below concerns to be clarified,
    1. 200 LAN users, does DPM new version support compression? does it compress data and do the backup process?
    2. Can we do block level backup?
    3. Least sync time between backups? can we schedule backup sync time for each 15 min with incremental backup?
    4. Does DPM support block level recovery?
    5.Does DPM support tapes? (Media Agent)
    Thanks
    Dilshan

    Hi,
    Q1. 200 LAN users, does DPM new version support compression? does it compress data and do the backup process?
    A1. You can enable on-wire compression so backup data transmitted between client and DPM Server is compressed. However all backup data on the DPM server is stored at rest in uncompressed form unless the source file is NTFS compressed on the client, then
    DPM will also store it compressed.
    Q2. Can we do block level backup?
    A2.  All short term disk to disk backups are block level backups.
    Q3. Least sync time between backups? can we schedule backup sync time for each 15 min with incremental backup?
    A3.  For Client backup, the minimum Synchronization frequency is 1 hour, the maximum frequency is 24 hours.
    Q4. Does DPM support block level recovery?
    A4.  No - all recoveries are full file recoveries.
    Q5. Does DPM support tapes? (Media Agent)
    A5. For Client protection, you must have short term to DISK protection, but you can also add long term tape protection.
    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.

  • Data protection Manager 2012 reports

    We have DPM 2012 server protect 5 sharepoint farms. It contains sharepoint, SQL and file systems protection groups. current recovery point retention period is 31 days, I need to how much data I will save if I decrease it to 15 days
    Any idea how to create report with such kind of data?

    Hi,
    there are 2 Ways:
    User the StorageCalculator Excel:
    http://www.microsoft.com/en-us/download/details.aspx?id=24375
    http://blogs.technet.com/b/dpm/archive/2010/09/02/new-dpm2010-storage-calculator-links-sep-2010.aspx
    or see the Calculation Advices:
    http://technet.microsoft.com/en-us/library/ff399599.aspx
    Seidl Michael | http://www.techguy.at |
    twitter.com/techguyat | facebook.com/techguyat

  • Recover Child Data Source - System Center Data Protection Manager 2012 SP1

    I'm trying to write a script that, given an input file, recovers data from 1st of the month redirected to a folder.
    It's all working, but I need to be able to restore only a folder from a D: drive that is protected for instance.
    how can I restore a folder and it's contents from powershell? I can restore and redirect a whole drive for the recovery point I want, but I can't figure out how to restore a childdatasource. I've identified the cds, but how can I make that a recoverableitem
    to feed the recover cmdlet?
    Mark

    Child data source isn't the way to do this, I should have checked each recoverable item in the recovery point, that would like the top level items such as top level folders/vm's/sql dbs, etc.
    Mark

Maybe you are looking for