none
DPM 2010 Tape backup issue Baremetal RRS feed

  • Question

  • I have DPM 2010 SP1 installed and it perform correctly for all the server but i have error while taking Tape backup on one of SQL 2008  cluster node. The error is :

    DPM Server=TAU

    SQL Node = RHO

    The back up to tape job failed for the following reason: (ID: 3311)


    DPM encountered an error while performing an operation for R:\WindowsImageBackup\ on TAU.Xyzcom (ID: 2033).

    I have R:\WindowsImageBackup\ on SQL node but why dpm show on DPM Server for that folder. while other server in that particular Protection group working fine and have WindowsImageBackup folder in their drives as mentioned in PSdataSourceConfig.xml. I have restarted both application and DPM server but problem still remians the same. Any help..


    Xohaib

    Thursday, March 29, 2012 9:15 AM

Answers

  • I am able to solve the issue with MS Support and share with all of you..

    ISSUE

    ========

    Tape Backup of System State & BMR Fails - DPM encountered an error while performing an operation for R:\WindowsImageBackup\ on TAU.tapalworld.com (ID 2033 Details)

    RESOLUTION

    ============

    • Ran the following SQL query -:

    Use dpmdb

    select ag.NetbiosName, ds.DataSourceName, vol.MountPointPath

    from tbl_IM_DataSource as ds

    join tbl_PRM_LogicalReplica as lr

    on ds.DataSourceId=lr.DataSourceId

    join tbl_AM_Server as ag

    on ds.ServerId=ag.ServerId

    join tbl_SPM_Volume as vol

    on lr.PhysicalReplicaId=vol.VolumeSetID

    and vol.Usage=1

    where ds.DataSourceName like '%system protection%'

    • Got the following output:
    • NetbiosName DataSourceName MountPointPath
    • PI System Protection Non VSS Datasource Writer\vol_7171a5a4-58c7-43a4-acc8-50f8fe79b5fc
    • XI System Protection Non VSS Datasource Writer\vol_2575f955-6ee3-4019-9d11-01a788adbee9
    • SIGMA System Protection Non VSS Datasource Writer\vol_27b589e2-d674-4576-8d31-7c03df37db50
    • RHO System Protection Non VSS Datasource Writer\vol_2ace18df-d653-446c-8e64-6bd984129a23
    • ZETA System Protection Non VSS Datasource Writer\vol_fabfe017-3d2d-4270-9f01-abdb1e1d3a70
    • The server is question - RHO - RHO System Protection Non VSS Datasource Writer\vol_2ace18df-d653-446c-8e64-6bd984129a23
    • Stopped the protection of the server.
    • Drilled to the c:\program files\Microsoft Data Protection Manager\DPM\Volumes\Non VSS Datasource Writer\vol_2ace18df-d653-446c-8e64-6bd984129a23\Full
    • Noticed that the folder inside was C Vol.
    • Went to the PS and changed the location for Files To Protect under PSDATASOURCECONFIG.XML to C:\WindowsImageBackup.
    • Went  back to the DPM server.
    • Re-protected the server.
    • Ran a CC and created a Recovery Point on the Tape - Successful.
    • Modified the original PG - BareMetal and added the server back to it.
    • Issue is resolved..

    CAUSE:

    =========

    This issue happens when there is mismatch between the Path provided under Files to Protect option in PsDataSourceConfig.xml on the protected server and the actual folder created under the Replica Path on the DPM server. This is a known issue and we are already working on this issue.


    Xohaib

    • Marked as answer by ZafarZohaib Wednesday, May 16, 2012 6:57 AM
    Wednesday, May 16, 2012 6:57 AM

All replies

  • Having the same issue on 2 servers with DPM 2012, It is for the System Protection partition, works fin with backup to disk, failes to tape.
    Monday, April 30, 2012 7:24 AM
  • I am able to solve the issue with MS Support and share with all of you..

    ISSUE

    ========

    Tape Backup of System State & BMR Fails - DPM encountered an error while performing an operation for R:\WindowsImageBackup\ on TAU.tapalworld.com (ID 2033 Details)

    RESOLUTION

    ============

    • Ran the following SQL query -:

    Use dpmdb

    select ag.NetbiosName, ds.DataSourceName, vol.MountPointPath

    from tbl_IM_DataSource as ds

    join tbl_PRM_LogicalReplica as lr

    on ds.DataSourceId=lr.DataSourceId

    join tbl_AM_Server as ag

    on ds.ServerId=ag.ServerId

    join tbl_SPM_Volume as vol

    on lr.PhysicalReplicaId=vol.VolumeSetID

    and vol.Usage=1

    where ds.DataSourceName like '%system protection%'

    • Got the following output:
    • NetbiosName DataSourceName MountPointPath
    • PI System Protection Non VSS Datasource Writer\vol_7171a5a4-58c7-43a4-acc8-50f8fe79b5fc
    • XI System Protection Non VSS Datasource Writer\vol_2575f955-6ee3-4019-9d11-01a788adbee9
    • SIGMA System Protection Non VSS Datasource Writer\vol_27b589e2-d674-4576-8d31-7c03df37db50
    • RHO System Protection Non VSS Datasource Writer\vol_2ace18df-d653-446c-8e64-6bd984129a23
    • ZETA System Protection Non VSS Datasource Writer\vol_fabfe017-3d2d-4270-9f01-abdb1e1d3a70
    • The server is question - RHO - RHO System Protection Non VSS Datasource Writer\vol_2ace18df-d653-446c-8e64-6bd984129a23
    • Stopped the protection of the server.
    • Drilled to the c:\program files\Microsoft Data Protection Manager\DPM\Volumes\Non VSS Datasource Writer\vol_2ace18df-d653-446c-8e64-6bd984129a23\Full
    • Noticed that the folder inside was C Vol.
    • Went to the PS and changed the location for Files To Protect under PSDATASOURCECONFIG.XML to C:\WindowsImageBackup.
    • Went  back to the DPM server.
    • Re-protected the server.
    • Ran a CC and created a Recovery Point on the Tape - Successful.
    • Modified the original PG - BareMetal and added the server back to it.
    • Issue is resolved..

    CAUSE:

    =========

    This issue happens when there is mismatch between the Path provided under Files to Protect option in PsDataSourceConfig.xml on the protected server and the actual folder created under the Replica Path on the DPM server. This is a known issue and we are already working on this issue.


    Xohaib

    • Marked as answer by ZafarZohaib Wednesday, May 16, 2012 6:57 AM
    Wednesday, May 16, 2012 6:57 AM
  • Hi Xohaib,

    any update on this issue? We're experiencing this problem too on a number on servers.

    Regards,

    Jens

    Monday, June 11, 2012 7:33 PM
  • I have shared the answer Maxi...just perform the steps in your environment.

    Xohaib

    Tuesday, June 12, 2012 3:59 AM
  • Any update on this?  Having the same issue on one of our servers
    Monday, July 16, 2012 8:29 PM