Failing "System State" and "Bare Metal Recovery" backup on DPM 2010 RRS feed

  • Question

  • When Configuring "Bare Metal Recovery" and "System State" the replica shows up as Inconsistent. When looking at the source server, an error '2155348040' is generated, meaning there is not enough harddisk space. The C:\ volume has 36GB and the D:\ Volume has 76GB space left.
    I don't understand this. The PSDataSourceConfig.xml file has a configuration "<FilesToProtect>D:\WindowsImageBackup\*</FilesToProtect> ".

    I found on URL "" the following text.
    Unlike System State protection, DPM does not have any space requirements on the protected computer for BMR protection. WSB directly transfers the backups to the DPM server.

    So I don't understand why the Replica fails, and a backup error is generated on the source machine.

    Can anyone help me out.

    Thanks for your reply,
    Monday, November 15, 2010 3:36 PM


  • Tried the following from url wbadmin.exe start backup -allcritical -quiet -backuptarget:\\server\bmrshare

    Turned out that also volume D: is marked as a critical backuptarget. Possibly caused by installing a program on the D: volume. Total Bare metal recovery was 18GB for the C volume and 130GB for the D: volume.

    When adding only "System State" to the Protection Group a recovery volume of about 140GB is suggested.

    Is this simply how it works or can I change some settings on the source server? These backup volume sizes are not what I expected.

    Thanks for your reply,

    • Marked as answer by mheijkant Sunday, November 28, 2010 6:48 PM
    Tuesday, November 16, 2010 5:22 PM