Forum Discussion

Umetri_ChJ's avatar
Umetri_ChJ
Level 3
14 years ago

Failed on System Logon Account credentials

Hi,

We're running Backup Exec2010 R2 (SP1 and all Liveupdates hotfixes) on a 2008 R2 SP1 server (not DC) and suddenly the backups for this server have started failing. All other (remote) backups of over 2003 and 2008 R2 servers work fine.

Last successful (full) backup was to tape on July 3, but that one took about 18 hours instead of normally 3½ hours. Next backup was supposed to be a differential backup to disk, but that one was cancelled when not finished after approx 8 hours.

When running test runs I can see that credentials for C: and D: are successful for System Logon Account.

BUT credentials failed for System Logon Account for Shadow Copy Components, System State, SQL Server BKUPEXEC and xml file.

Any ideas what to do???

2010
Backup and Recovery
Backup Exec
  • pkh's avatar
    pkh
    14 years ago

    It is a known problem that backing up the system state of a Server 2008 R2 server takes a long time.  This problem is supposed to be resolved in BE 2010 R3.  You should upgrade to R3.  Your existing licence keys will work.  You can download R3 from the fileconnect site or www.backupexec.com.

  • robnicholson's avatar
    robnicholson
    Level 6
    14 years ago

    Has the remote agent possibly got upgraded on the target server to R3 by any chance? Our backups started failing with the same error message when we did a test deployment of BE 2010 R3 and in doing so, upgraded the agent on our primary file server.

    Our backup strategy is currently therefore broken until we can escalate upgrading the production server.

    Rob.

  • Umetri_ChJ's avatar
    Umetri_ChJ
    Level 3
    14 years ago

    The problem is when backing up the local server, the one running Backup Exec.

    /Christina

  • CraigV's avatar
    CraigV
    Moderator
    14 years ago

    A. Is your service account a domain admin at a minimum?

    B. Have you added your service account to the server's local admins group?

    C. If you're running an AV, can you check and make sure it isn't blocking access to the entries above?

  • Umetri_ChJ's avatar
    Umetri_ChJ
    Level 3
    14 years ago

    The backups worked fine a few days ago and no changes has been done to accounts or antivirus since then.

  • Umetri_ChJ's avatar
    Umetri_ChJ
    Level 3
    14 years ago

    The backup runs fine when removing System State from selection list, but that is not the long solution

  • pkh's avatar
    pkh
    Moderator
    14 years ago

    Post the error messages that you get when you back up the system state.

  • Umetri_ChJ's avatar
    Umetri_ChJ
    Level 3
    14 years ago
    Set status             : Failed

    Resource name          : \\SERVUM6\System?State
Logon account          : System Logon Account

    Error                  : e0008703 - The test run has detected a potential problem. See the job log for details.

    Agent used             : Yes

    ServUm6 is the server running Backup Exec.
    When actually running the job it hangs on System State.

  • pkh's avatar
    pkh
    Moderator
    14 years ago

    It is a known problem that backing up the system state of a Server 2008 R2 server takes a long time.  This problem is supposed to be resolved in BE 2010 R3.  You should upgrade to R3.  Your existing licence keys will work.  You can download R3 from the fileconnect site or www.backupexec.com.

  • Umetri_ChJ's avatar
    Umetri_ChJ
    Level 3
    14 years ago

    What is strange to me is that it has been working for a long time and suddenly backup took 18 hours instead of 3,5 and next is that is sort of hangs.

    From Symantec Support I got the suggestion to upgrade to R3, I will do that after vacation period.