Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Backup Timer Job after PWA Restore RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello everyone,

    whenever I restore a PWA instance (be it a server migration or transfer to a development server), most SharePoint Timer Jobs are not created. This includes OLAP and most important PWA Backup Timer Jobs.

    That means in the restored PWA instance under Server Settings, you will still OLAP Cubes and Project Server Backups (projects, resource pool, calendars, etc.) being listed as running regularly, but the jobs will in fact not run at all. If you check SharePoint Central Administration / Review Job Definitions, you will see no timer jobs for the newly restored PWA instance. At least one customer has experienced data loss because the restored instance that listed running daily backups under PWA / Server Settings / Schedule Backups didn't actually run any backups.

    Is there anything I am doing wrong? Is there some setting that I overlooked that prevents those setting to properly work in a PWA restore?

    Kind regards,
    Adrian

    Wednesday, October 31, 2012 8:23 PM

Answers

All replies

  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi Adrian,

    You are not doing anything wrong, you just have to edit the scheduled times to recreate the jobs in Central Admin on the restored farm. See the post provisioning section on this blog post:

    http://pwmather.wordpress.com/2012/04/10/projectserver-2010-environment-rollover-steps-powershell-ps2010-msproject-sp2010/

    Thanks

    Paul

    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Wednesday, October 31, 2012 8:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Paul,

    thank you for your answer. Even though I didn't explicitly state it, I was well aware that setting all PWA Jobs 1h back and forward will recreate all the missing jobs. The main reason I posted is whether this behaviour is officially documented somewhere, or whether this is one of the "it's broken and you'll learn it over time by reading blogs" things.

    Kind regards,
    Adrian

    Saturday, November 24, 2012 6:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Adrian,

    it's one of the

    "it's broken and you'll learn it over time by reading blogs"

    things that makes us sometimes think that we should better have applied for a different job :-)

    Kind Regards

    Christoph

    Monday, November 26, 2012 1:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    things that makes us sometimes think that we should better have applied for a different job :-)

    But someone else might have gotten it wrong ;)

    Anyway, that's probably as much an answer as I'll get. In 2013, the Timer Jobs seem to be unified, so this issue might be gone. I haven't played with backups/restore enough to test this though:
    http://technet.microsoft.com/en-us/library/jj219512.aspx

    Kind regards,
    Adrian

    Monday, November 26, 2012 9:56 PM