My Backup Jobs Aren't Working - Permission Issue?

  • I set up a pair of Job Agents to backup the database for a web application weekly and daily
    the SQL works - but the job(s) don't  - do I need to explicitly grant permission - and to who?

    not the Administrator account - that's what a person logs in as

    thanks

    newbie DBA - and not by choice

  • Seggerman-675349 - Wednesday, March 7, 2018 8:54 AM

    I set up a pair of Job Agents to backup the database for a web application weekly and daily
    the SQL works - but the job(s) don't  - do I need to explicitly grant permission - and to who?

    not the Administrator account - that's what a person logs in as

    thanks

    newbie DBA - and not by choice

    Please post the full text of the error message you receive.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • I don't get any error message (unless I don't know where to look) - I just see every morning that no backup has run

  • Seggerman-675349 - Wednesday, March 7, 2018 8:54 AM

    I set up a pair of Job Agents to backup the database for a web application weekly and daily
    the SQL works - but the job(s) don't  - do I need to explicitly grant permission - and to who?

    not the Administrator account - that's what a person logs in as

    thanks

    newbie DBA - and not by choice

    How you setup the jobs?
    SSIS Package? Maintenance Plans? TSQL Code?

  • log on to the server using an account Machine Name \Administrator
    open Management Studio
    go to Job Agents at the bottom
    Add New Job
    add Step with T-SQL to do backup (which if pasted into Query Window works)
    Add Schedule
    I added an alert to notify my client when it completes (I had to add his email elsewhere)

  • Seggerman-675349 - Thursday, March 8, 2018 5:37 AM

    log on to the server using an account Machine Name \Administrator
    open Management Studio
    go to Job Agents at the bottom
    Add New Job
    add Step with T-SQL to do backup (which if pasted into Query Window works)
    Add Schedule
    I added an alert to notify my client when it completes (I had to add his email elsewhere)

    What message is shown of the job step in the job history?  (expand the job in Job History to get the jobstep output)
    You can additionally add some PRINT statements to the T-SQL code in the jobstep. That way you can extra check if the code has run, becuase this print output will also be visible in the job history.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • the job history shows - nothing
    the T-SQL runs fine in a Query window
    the job is  Enabled - but doesn't run

  • Seggerman-675349 - Thursday, March 8, 2018 9:09 AM

    the job history shows - nothing
    the T-SQL runs fine in a Query window
    the job is  Enabled - but doesn't run

    Some other things t check -

    Check the SQL Agent log to see if there is any related warnings or errors.
    Check the SQL Agent log to see if the Agent service was running when the job was suppose to run.
    Try manually executing the job - not the t-sql itself but the job.
    Make sure the schedule is also enabled and set correctly - look at the dates, make sure there is no end date, make sure it's not set to run once or in the past.
    Look at the job activity monitor (in the jobs folder in SSMS) and see if the next run date and time is listed.

    Sue

  • the job history says there are not scheduled - but the Schedules within each job says they are

    the server is fairly new - and it looked like the JobAgent wasn't running
    I' left clicked and said Start
    maybe that will do the trick

    thanks to the wise ones - I am the DBA out of necessity

  • Seggerman-675349 - Thursday, March 8, 2018 9:09 AM

    the job history shows - nothing
    the T-SQL runs fine in a Query window
    the job is  Enabled - but doesn't run

    Did you also check if the attached schedule is enabled? When the job is enabled, but don't display a "next run" in the Job Activity monitor, most of the times the schedule isn't enabled. This will happen if the end-date of the schedule has been passed or if the schedule was set to a one-time occurrence.
    Open the properties of the job and navigate to the attached schedules window. Check the box "enabled" in the Job schedule properties.

    And of course: if the SQL Agent service is not started, no SQL jobs will be executed (as you mention in your last post).

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • they ran! I just needed to start the Job Agent service
    as I said, s DBA but not by choice

    thanks folks

  • Seggerman-675349 - Friday, March 9, 2018 10:14 AM

    they ran! I just needed to start the Job Agent service
    as I said, s DBA but not by choice

    thanks folks

    Make sure that the agent service is set to auto start so if the box or SQL Server is restarted, the agent service will restart as well.

  • Seggerman-675349 - Wednesday, March 7, 2018 8:54 AM

    I set up a pair of Job Agents to backup the database for a web application weekly and daily
    the SQL works - but the job(s) don't  - do I need to explicitly grant permission - and to who?

    not the Administrator account - that's what a person logs in as

    thanks

    newbie DBA - and not by choice

    the account the sql server agent runs under will need read\write permission to the location where the files are stored.
    Are the files stored on the local server or a unc backup path

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • a real DBA took over - and she / he moved the backups to some cloud space

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply