none
DPM2012 sp1 Scheduled Recovery points not running RRS feed

  • Question

  • Hi

    I have a clean install of Windows Server 2008 R2 sp 1 and installed DPM 2012 sp1.  I've installed agents on my servers through the typical agent install in DPM wizard and setup a protection group.  The DPM server has a ton of space (27 TB).

    I've got 4 servers in my protection group, Exchange 2010 CAS, Exchange MBX, file server and a SQL server.  All servers are 2008 R2 Sp1.  My protection group is set to create recovery points twice a day (8am and 6pm) and for 30 days and do a consintancy check every 4 hours.  if I right click on a server and select create recovery point now it works just fine but I'm just not getting it to auto create recovery points as set through the protection group.  I've got green ticks all the way down the page on the Protection Status column.  I don't see any backup errors in event viewer, it's just like nothing is happening, each day I'm trying little tweaks to the protection group to try and get it to run itself but still no joy.

    Any ideas?

    Monday, March 4, 2013 9:17 AM

Answers

  • I have fixed the issue.

    I don't think it likes the Dedicated SQL server option(i.e an instance on another server).  I reinstalled it selecting the install SQL server on itself option and now the backup jobs run according to the schedule.

    Wednesday, March 6, 2013 3:00 PM
  • I ran into this issues years ago with DPM 2010, and it was the SQL server. If the DPM is pointed to a different server for its SQL instance, and the DPM prep tool is not properly run you will have troubles.

    My case was specific to the DPM2010\SQLPrep files being completely missing. No TriggerJob.exe for SQL to run - so no error message is actually reported. The SQL job runs, fails to execute TriggerJob, SQL doesn't care and nothing is reported as being failed since the DPM Job doesn't actually run.

    Did you run the SQL Prep tool on the SQL server prior to installing DPM, and pointing it to the SQL Server? Just curious in case someone else finds this in a search query -

    Friday, March 8, 2013 6:01 PM

All replies

  • Hi Challow,

    Do you see Recovery Point in Recovery tab ?

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Monday, March 4, 2013 9:28 AM
  • I only see the recovery points that I have run myself.
    Monday, March 4, 2013 9:43 AM
  • Could you take a look in Monitoring Tab and verify that you have Jobs in "Today's jobs" view ?

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Monday, March 4, 2013 9:51 AM
  • Hi

    Yes if I look in Today's jobs I can see the jobs that are scheduled for later today.

    Monday, March 4, 2013 10:39 AM
  • Ok,

    In same Monitoring Tab, create a custom filter:

    Time from : 7 day ago
    Time : Today
    Jobs type : Recovery Point
    Status: all

    Give it a name and Save

    Now Do you see your Recovery Point ?

    If they are in failed state, check for Description error.

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Monday, March 4, 2013 11:11 AM
  • Ok so with that filter it shows me two Catorigies...

    Scheduled, shows me all the jobs scheduled for later today and

    Completed, shows me all the jobs that have run i.e all the ones I have run manually in the past 7 days.

    It doesn't show me any failed jobs???

    like I said earilier this is so weird.. it's as if DPM is just not doing anything automaticially.


    • Edited by Challow Monday, March 4, 2013 11:41 AM
    Monday, March 4, 2013 11:40 AM
  • You 're right... It's weird ^^

    Could you split your single Protection Group into several according to the nature of the datasources ?

    I mean for example, 1 PG for File, 1 PG for MBX, 1 PG for SQL, etc. ?

    You may begin with file and see what happend.

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Monday, March 4, 2013 1:15 PM
  • ok I'll try that.  If I take like you suggest the file server out of the protection group and put it in it's own group will I loose all my manual recovery points?
    Monday, March 4, 2013 1:23 PM
  • ok ignoare my last.. it does keeps the recovery points.

    It is scheduled to run in 20 minutes and I can see the job sitting in Today's jobs.. so I'll update you after it has run or not.

    Monday, March 4, 2013 1:45 PM
  • Ok :)

    Let us know the result.

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Monday, March 4, 2013 1:52 PM
  • ok Same as before... just nothing.  no recovery point was made... no event log, no sign that DPM even tried to do it. :(

    Monday, March 4, 2013 2:16 PM
  • Ok ^

    Check on your protected computer (File server) under %Program Files%\Microsoft Data Protection Manager\DPM\Temp

    In DPMRACurr.errlog, do you see any relevant information ? e.g. Error, Access denied, etc. ?

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Monday, March 4, 2013 2:33 PM
  • This is what I get...

    0C5C 0BB0 03/04 16:10:05.470 20 cc_extcalls.cpp(517) [00000000041252B0] 15076864-6137-4846-8DE1-B58F821A698F WARNING DM: TempErr: err=0x40 read=1 write=0
    0C5C 0BB0 03/04 16:10:19.643 20 cc_extcalls.cpp(517) [0000000004114070] 15076864-6137-4846-8DE1-B58F821A698F WARNING DM: TempErr: err=0x40 read=1 write=0
    0C5C 0BB0 03/04 16:10:26.738 20 cc_extcalls.cpp(517) [000000000410D990] 15076864-6137-4846-8DE1-B58F821A698F WARNING DM: TempErr: err=0x40 read=1 write=0
    0C5C 0F2C 03/04 16:10:47.460 03 runtime.cpp(1429) [000000000040CCC0]  NORMAL CDLSRuntime::ProcessIdleTimeout
    0C5C 0F2C 03/04 16:10:47.460 03 runtime.cpp(603) [000000000040CCC0]  NORMAL CDLSRuntime::Uninitialize, bForce: 0
    0C5C 0F2C 03/04 16:10:47.460 05 genericagent.cpp(266) [0000000000409D00]  NORMAL Agent Can Shutdown if there is only default wokitem active[1]
    0C5C 0F2C 03/04 16:10:47.460 29 dpmra.cpp(354) [0000000000409D00]  NORMAL CDPMRA::Shutting down dpmra, force-shutdown :yes
    0C5C 0F2C 03/04 16:10:47.460 03 workitem.cpp(391)   NORMAL Timing out WI [000000000043A8C0], WI GUID = {B71B4544-7067-4A30-B5FB-BA320B10D82A}, ..last DM activity happened 392028125msec back, WI Idle Timeout = 390000msec
    0C5C 0F2C 03/04 16:10:47.460 22 genericthreadpool.cpp(684) [00000000004BF7E0]  NORMAL CGenericThreadPool: Waiting for threads to exit
    0C5C 0F2C 03/04 16:10:49.460 22 genericthreadpool.cpp(684) [000000000040CCC0]  NORMAL CGenericThreadPool: Waiting for threads to exit
    0C5C 000C 03/04 16:10:51.476 03 timer.cpp(513) [0000000000497678]  ACTIVITY Shutting down timer thread.
    0C5C 0F2C 03/04 16:10:51.476 03 service.cpp(81)   ACTIVITY CService::StopThisService
    0C5C 0F2C 03/04 16:10:51.476 03 service.cpp(281) [000000000022FD50]  ACTIVITY CService::StopService()
    0C5C 0D48 03/04 16:10:51.476 03 service.cpp(298) [000000000022FD50]  ACTIVITY CService::AnnounceServiceStatus

    Monday, March 4, 2013 4:17 PM
  • I see there is an update rollup 1 now, gonna try and install that.
    Tuesday, March 5, 2013 11:13 AM
  • I have fixed the issue.

    I don't think it likes the Dedicated SQL server option(i.e an instance on another server).  I reinstalled it selecting the install SQL server on itself option and now the backup jobs run according to the schedule.

    Wednesday, March 6, 2013 3:00 PM
  • I ran into this issues years ago with DPM 2010, and it was the SQL server. If the DPM is pointed to a different server for its SQL instance, and the DPM prep tool is not properly run you will have troubles.

    My case was specific to the DPM2010\SQLPrep files being completely missing. No TriggerJob.exe for SQL to run - so no error message is actually reported. The SQL job runs, fails to execute TriggerJob, SQL doesn't care and nothing is reported as being failed since the DPM Job doesn't actually run.

    Did you run the SQL Prep tool on the SQL server prior to installing DPM, and pointing it to the SQL Server? Just curious in case someone else finds this in a search query -

    Friday, March 8, 2013 6:01 PM
  • Hi,

    I have this problem too. Please tell me, how you reinstalled SQL server on itself? Reinstall all DPM 2012 SP1 with "Use an existing instance of SQL-server" option?

    Thanks

    Monday, March 11, 2013 6:15 AM