Backup exec 2010 queued job status
- Backup exec 2010 queued job status upgrade#
- Backup exec 2010 queued job status software#
- Backup exec 2010 queued job status password#
- Backup exec 2010 queued job status download#
Be sure to select This is my default logon account account option.For more information please review Edit Logon Credentials options: Enter the appropriate account credential information.Version 2010 R3 and earlier - Network | Logon Accounts | and select New.Version 2012 and later - Click the Backup Exec button | Configuration and Settings | Logon Accounts | Manage Logon Accounts | and select System Account.
Backup exec 2010 queued job status password#
NOTE: The password entered is encrypted for security.ġ. On the Edit Logon Credentials dialog box, click OK.Ģ. On the Logon Account Management dialog box, click OK.ġ. On the Account Management dialog box, click OK. Click Change Password to enter the current password for this user in both the password and confirm fields.In the User name field enter the fully qualified username (e.g.If the account does not have the description, ’System Logon Account,’ depending upon version, click, ‘ Set as Default,’ OR, ’This is my default account.’.If this password is not available, select a different account or skip to section, ‘To create the system logon account.’ NOTE: If not logged on to Backup Exec server with the same user name as the Backup Exec logon account being edited, Backup Exec prompted to provide the account owner’s password before the account can be edited. Select the Backup Exec logon account you want to change, and then click Edit.If an account does or can have the description System Logon Account proceed to step 3.If no account has as a description System Logon Account and none of the accounts listed can be made into this role then skip to section, ‘ To create the system logon account,’ below.On version 2010 R3 and earlier - Network | Logon Accounts.On version 2012 and later - Click the Backup Exec button | Configuration and Settings | Logon Accounts | Manage Logon Accounts.In Backup Exec do one of the following:.Verify that the backup job in question is using the updated or newly created SLA before its next use. If neither is the case, create a new account and assign it the SLA role. Restart the BE services after making the change and run the backup job.The Backup Exec System Logon Account (SLA) on the Backup Exec server is either missing, corrupt or its credentials has changed.Ĭheck if the Backup Exec System Logon Account (SLA) on the Backup Exec server is either missing or its credentials has changed. The BE server windows firewall can also be setup to reject incoming connection from this port scanning (network security application) server IP to BE server IP:6101.
Backup exec 2010 queued job status software#
Note: Refer Port scan software (network security application) or firewall software vendor documentation to accomplish the above. TCP 192.168.2.10:6101 192.168.2.1:41029 CLOSE_WAITĦ101 is the agent browse process for Backup Exec.ġ92.168.2.1 is the IP of port scanning application (network security application) server connecting to port 6101 on the Backup Exec server.Įnsure the port scanning software (network security application) is not scanning/connecting/blocking port 6101 on Backup Exec server.Īdditionally, use the same netstat command mentioned above to check if port scanning software (network security application) is not scanning/connecting/blocking port 6101 on the Backup Exec remote agent server, if the job appears to be hung backing up a remote server. On the Backup Exec server, open command prompt and run the following netstat command to check which IP/servers are accessing port 6101:
Backup exec 2010 queued job status download#
Steps to download the Backup Exec Licenses and Installation Files within VEMS
Backup exec 2010 queued job status upgrade#
This Issue is fixed in Backup Exec 21, upgrade Backup Exec to version 21. The port scanning application (network security application) may block connection between Backup Exec server and the Backup Exec remote agent server in some scenarios causing this hang. Backup job stays in "Active: Discovering Resources".