Protected system crashes after initiating a backup

• Sonntag, 20. Mai 2012 01:56

   

   
  

  0

  Just deployed SCDPM 2012 primarily for long-term protection using tape.  We were able to pull off a successful backup of about 5 TB of data from one of our Server 2008 R2 boxes but we have a Server 2003 box (Dell PowerEdge 1950, 4 GB Physical Memory, 4 GB Virtual Memory, 1.6 GHz Quad Core E5310 CPU) that is causing us some grief each time we kick off a recovery point on the ~1.5 TB of data it manages.  Each time, the agent will pull about about 390GB of data and then the System event log starts throwing these errors until the system becomes wedged and ultimately has to be restarted in order to resume normal operation. Based on the initial event, it seems like the culprit is McAfee VSE (v8.8), but we've got other similar systems using McAfee with the same ePolicy policies that have no issues with SCDPM.

  --------------------------

  Event Type: Warning
  Event Source: mfehidk
  Event Category: (256)
  Event ID: 519
  Date: 5/19/2012
  Time: 3:40:42 AM
  User: N/A
  Computer: **
  Description:
  Process **\SVCHOST.EXE pid (912) could not be successfully validated with the mfevtp service and was blocked from performing a privileged operation with a McAfee driver.

  --------------------------

  Event Type: Error
  Event Source: Kerberos
  Event Category: None
  Event ID: 7
  Date: 5/19/2012
  Time: 3:41:56 AM
  User: N/A
  Computer: **
  Description:
  The kerberos subsystem encountered a PAC verification failure.  This indicates that the PAC from the client (DPMSRVR$) in realm DOMAIN had a PAC which failed to verify or was modified.  Contact your system administrator.
  

  --------------------------

  Event Type: Error
  Event Source: Srv
  Event Category: None
  Event ID: 2020
  Date: 5/19/2012
  Time: 3:42:33 AM
  User: N/A
  Computer: **
  Description:
  The server was unable to allocate from the system paged pool because the pool was empty.

  --------------------------

  Event Type: Error
  Event Source: Application Popup
  Event Category: None
  Event ID: 333
  Date: 5/19/2012
  Time: 3:42:39 AM
  User: N/A
  Computer: **
  Description:
  An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.

  --------------------------

  The 333 error then repeats itself over and over until the system becomes wedged and someone logs in as a console user and restarts it.  After doing some digging it appears that after the DPM kicks off the backup, the amount of Paged Memory used rapidly increases until this event occurs.  So I found this KB article http://support.microsoft.com/kb/312362 and implemented it's suggested actions but the issue still persists.  For instance, just for giggles, I kicked off a DPM backup on this box at 9:30 PM last night and started monitoring the amount of Paged Memory, here's what I recorded...

  Paged Kernel Memory (K)
  9:33 PM  = 67340
  9:44 PM  = 99180
  9:55 PM  = 117716
  10:07 PM = 155708
  10:18 PM = 176864
  10:39 PM = 181584

  11:00 PM = Went to bed :)

  Any help would be greatly appreciated - I've done everything but bang my head against the desk :) Thanks in advance.

  • Antworten
  • Zitieren