Backup Exec Monitoring Is Not Working

Last Modified

Tue Dec 01 22:06 GMT 2020

Description

  • Backup Exec Monitoring Is Not Working
  • Backup Exec account not valid
  • Instance Not Found

Environment

  • N-able N-central

Solution

Account Validity

Under Settings > Monitoring Options you will see the Backup Exec configuration. This either tries to log in with the listed account, or if it does not exist creates a read-only account for backup monitoring. If you have problems with the account configured locally on the device for backup exec, try a non-existent account or leave the default account name (nablebackupexec or nablebkupexec4 for later versions of N-able N-central).
  • Backup Exec may discover jobs using nablebkupexec user and simple default password but then may report that the account the agent uses may not be valid when jobs are added to be monitored.,
  • Password complexity may not be met, try a more complex password such as: 'P@ssword123',
  • You may also need to change the username for similar reasons so just add a number to the end of the username.

Instance Not Found (or other issues with the DB instance)

The service is expecting the default instance of BEDB, and other settings may become problematic.
  • Try changing the SQL setting to 'SQL Server Express' or 'SQL Server',
  • If that doesn't work, you can select Custom and enter the name of the instance:
Note: when entering the instance, use the simple name such as 'backupexec' rather than 'MSSQLSERVER\backupexec'. You can also try simply 'MSSQLSERVER' to look through the default locations, but this still will try to look for BEDB.