none
DPM 2007 SP1 ID 104 Details: Catastrophic failure (0x8000FFFF) RRS feed

  • Question

  • Hello MS. The new fourm is much improved on the past one. Please could you assist me with the following.

    Affected area: F:\
    Occurred since: 7/6/2010 12:58:15 PM
    Description: The replica of Volume F:\ on *** 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)
     An unexpected error occurred during job execution. (ID 104 Details: Catastrophic failure (0x8000FFFF))
    Recommended action: Retry the operation.
     Synchronize with consistency check.
     Run a synchronization job with consistency check...
    Resolution: To dismiss the alert, click below
     Inactivate alert

    VSS writer looks ok details below. I have also rebooted the node that the volume was on (Its  a clustered file server share -Window 2008)


    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {a4d0c646-9cd2-45d9-af0c-63c99c00409f}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {1166d37c-9463-484b-bd4a-3048b8ba7593}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {53dbcfe5-6d37-4b6d-b47e-7eb34673b7a3}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {d8b216c7-3e60-4fd8-b700-d89896a93da3}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {9a94fabf-1fa6-4a7c-bc08-f1fe2f701f3e}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {f4895b15-9ec3-4cab-aa7c-53a800c27a7c}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {ec346adf-3ee0-4129-85be-c5b15d680528}
       State: [1] Stable
       Last error: No error

     

    Regards

    Nick Smitheram

     

     

     

    Tuesday, July 6, 2010 1:32 PM

Answers

All replies

  • Hey,

    I've seen this error happening when there is not enough disk space on the protected computer.

    Could you verify this?

    Brgds,

    Mike


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Tuesday, July 6, 2010 2:02 PM
    Moderator
  • 255GB Volume with 66GB free. 
    Tuesday, July 6, 2010 4:03 PM
  • housekeeping - closing old post.  Please open a new post if you still have a need.
    Friday, January 13, 2012 7:24 PM
    Moderator