Forum Discussion

Kudikai's avatar
Kudikai
Level 3
12 years ago

Backup Exec 2012 & SQL Credential Testing

Backup Exec 2012 is setup to backup a single directory's contents on our SQL servers. We have SQL 2005, 2008 R2 and 2012 servers all setup like this. When the job runs, it tries to connect to the SQL instance which generates security alerts for failed logins. The job doesn't have the SQL instances selected and we don't want it connecting to the SQL instance.

How can we configure Backup Exec 2012 to not connect to SQL instances?

Backing Up
Backup and Recovery
Backup Exec
Configuring
Windows Server (2003-2008)
  • Colin_Weaver's avatar
    Colin_Weaver
    12 years ago

    As far as I know the remote agent will try to talk to all resources on a server during

    a) Agent startup

    b) Agent browse whilst creating a new backup selection

    c) During a backup job (either as you backup the resources in question or possibly at the start of each set in the job during an enumeration phase of what is on the system)

    There are probably some other trigger points as well, a remote agent debug log would actually show how often it happens.

    Against SQL (and as the previous article suggested) if you rename the bedssql*.dll on the SQL server with the agent stopped it should no longer try to access SQL, however, as the article warns SQL backups cannot run in this state (and it will almost certainly affect Sharepoint backups as well.)

    If yiou have renamed the .DLL and still find this happening then it may need a formal support case for us to look into it

  • CraigV's avatar
    CraigV
    Moderator
    12 years ago

    ...make sure the SQL instances are not selected!

    Thanks!

  • CraigV's avatar
    CraigV
    Moderator
    12 years ago

    ...did you exclude the SQL flat-files? BE should automatically do so via Active File Exclusion, but not sure how that works in BE 2012...try excluding the *.ldf/*.mdf files and try again!

    Thanks!

  • Kudikai's avatar
    Kudikai
    Level 3
    12 years ago

    The only directory that we selected was the SQL backups folder on the F: drive. Basically, SQL handles it's backup processes and we want to snag just any files it places in that one directory. It shouldn't need to logon to the SQL instances for that.

  • CraigV's avatar
    CraigV
    Moderator
    12 years ago

    ...you never know. Exclude those files and try again.

    Thanks!

  • Kudikai's avatar
    Kudikai
    Level 3
    12 years ago

    When I read this article I really thought it could be the answer so I tried it and that didn't help, but it did show me that this might not be the job's configuration that is trying to connect to the SQL instance, but the remote agent on the SQL server itself.  When I restarted the "Backup Exec Remote Agent for Windows Systems" service I get the logon failure alerts from SQL.

    I'm going to start looking down the remote agent configuration path instead of the job path now. Thanks!

  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    12 years ago

    As far as I know the remote agent will try to talk to all resources on a server during

    a) Agent startup

    b) Agent browse whilst creating a new backup selection

    c) During a backup job (either as you backup the resources in question or possibly at the start of each set in the job during an enumeration phase of what is on the system)

    There are probably some other trigger points as well, a remote agent debug log would actually show how often it happens.

    Against SQL (and as the previous article suggested) if you rename the bedssql*.dll on the SQL server with the agent stopped it should no longer try to access SQL, however, as the article warns SQL backups cannot run in this state (and it will almost certainly affect Sharepoint backups as well.)

    If yiou have renamed the .DLL and still find this happening then it may need a formal support case for us to look into it

  • Kudikai's avatar
    Kudikai
    Level 3
    12 years ago

    Colin...I'll retry renaming the DLL file on a few other servers to confirm it isn't just a fluke, and if it isn't I'll proceed with a formal support request as you suggest.