Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backupexec 2010 R3 job hangs for no reason

Created: 06 Nov 2012 • Updated: 06 Nov 2012 | 5 comments

Hi guys,

I'm having problems with one of my backup jobs. I'm trying to backup a Windows 2008 SBS server, the job has been running for a few years now. Both my backup server and my SBS server are fully up to date, Backupexec 2010 R3 is also up to date.

The backup job hangs after a random amount of time or gigabytes. It says the job is still running, but no data is being recieved. The backup job contains the filesystem, system state and exchange mailboxes.

I've tried the following things:

- remove system state from the backup job (same results)

- remove exchange from the backup job (same result)

- recreated the backup job (same result)

- reinstalled the agent

 

 

With the system state and the exchange backup removed from the selection list, I ran another backup with the client in debug mode, the following shows up:

[20652] 11/06/12 12:22:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: negative (purge) advertisement cycle started.
[20652] 11/06/12 12:22:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: no purge is pending.
[20652] 11/06/12 12:22:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: negative (purge) advertisement cycle complete.  Waiting 240 minutes before advertising again.
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: advertisement cycle started.
[20224] 11/06/12 12:25:14 [fsys\ntfs\mnet]     - Informational: Restrict Anonymous Support is enabled
[20224] 11/06/12 12:25:14 [fsys\ntfs\mnet]     - creating DLE for local machine
[20224] 11/06/12 12:25:14 [fsys\ntfs\mnet]     - EnumClusterDLEs: Could not opening cluster : Het systeem kan de opgegeven omgevingsoptie niet vinden.
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 7 returned 0(0x0) and 1 DLEs
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer: N2DSBS
[20224] 11/06/12 12:25:14 [fsys\ese]           - HrESEBackupRestoreNodes: N2DSBS = 0x00000000
[20224] 11/06/12 12:25:14 [fsys\ese]           - Recursing
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer: N2DSBS
[20224] 11/06/12 12:25:14 [fsys\ese]           - N2DSBS is an Exchange server
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer N2DSBS: 1
[20224] 11/06/12 12:25:14 [fsys\ese]           - HrESEBackupFreeNodes:
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer N2DSBS: 1
[20224] 11/06/12 12:25:14 [fsys\ese]           - Trying to open: 'LDAP://CN=Configuration,DC=N2D,DC=local'
[20224] 11/06/12 12:25:14 [fsys\ese]           - ExchangeDN: 'CN=N2DSBS,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=network2day,DC=local' LegacyExchangeDN: '/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=N2DSBS'
[20224] 11/06/12 12:25:14 [fsys\ese]           - Exchange Server Name: N2DSBS
[20224] 11/06/12 12:25:14 [fsys\ese]           - Exchange Server Distinguished Name: CN=N2DSBS,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=network2day,DC=local
[20224] 11/06/12 12:25:14 [fsys\ese]           - Exchange Server Serial Number (Version): Version 14.1 (Build 30218.15)
[20224] 11/06/12 12:25:14 [fsys\ese]           - Exchange Server DAG Link:
[20224] 11/06/12 12:25:14 [fsys\ese]           - Exchange Server Site: CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=network2day,DC=local
[20224] 11/06/12 12:25:14 [fsys\ese]           - Exchange Server Site First CN: Default-First-Site-Name
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer: N2DSBS
[20224] 11/06/12 12:25:14 [fsys\ese]           - HrESEBackupRestoreNodes: N2DSBS = 0x00000000
[20224] 11/06/12 12:25:14 [fsys\ese]           - Recursing
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer: N2DSBS
[20224] 11/06/12 12:25:14 [fsys\ese]           - N2DSBS is an Exchange server
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer N2DSBS: 1
[20224] 11/06/12 12:25:14 [fsys\ese]           - HrESEBackupFreeNodes:
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer N2DSBS: 1
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer: N2DSBS
[20224] 11/06/12 12:25:14 [fsys\ese]           - HrESEBackupRestoreNodes: N2DSBS = 0x00000000
[20224] 11/06/12 12:25:14 [fsys\ese]           - Recursing
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer: N2DSBS
[20224] 11/06/12 12:25:14 [fsys\ese]           - N2DSBS is an Exchange server
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer N2DSBS: 1
[20224] 11/06/12 12:25:14 [fsys\ese]           - HrESEBackupFreeNodes:
[20224] 11/06/12 12:25:14 [fsys\ese]           - AreYouSureThisIsAnExchangeServer N2DSBS: 1
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Nrds Message Len : 7994.
[20224] 11/06/12 12:25:14 [fsys\oracle]        - RMAN_EnumSelfDLE: AgentConfig GetOracleDBNames returned error. If Oracle Agent is installed, please run AgentConfig.
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 14 returned 0(0x0) and 0 DLEs
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 37 returned 0(0x0) and 0 DLEs
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 39 returned 0(0x0) and 0 DLEs
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 42 returned -536805816(0xE000FE48) and 0 DLEs
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
[20224] 11/06/12 12:25:14 [nrds]               - ConnectToServerEndPoint: dest=N2DAFAS, service=6101
[20224] 11/06/12 12:25:14                      - SSL connection using version TLSv1
[20224] 11/06/12 12:25:14                      - SSL connection using cipher AES256-SHA
[20224] 11/06/12 12:25:14 [nrds]               - CreateConnection type=0 on socket 3824 via BESocket OK
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: send of N2DSBS.network2day.local type 7 subtype 2 to target=N2DAFAS port=6101 succeeded
[20224] 11/06/12 12:25:14 [BESocket]           - @@@@@@@MyCloseSocket called with sockfd = 3824(0xef0)    retval = 0
[20224] 11/06/12 12:25:14 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: advertisement cycle complete.  Waiting 240 minutes before advertising again.
 

This log entry repeats itself until i cancel the job...

 

First i thought this was a VSS problem, but when I do a vss list writers, I don't see any errors.. Can anybody help me?

 

Comments 5 CommentsJump to latest comment

VJware's picture

Are there any unattended alerts ? Pls check if the BE services (especially the remote agent service) stops..any errors/warnings in the event viewer ? Is this affecting only one job or other jobs too ?

CraigV's picture

Check and make sure that no AV on the server (if 1 is installed) isn't perhaps blocking BE's access to something. I've seen McAfee block access, or even scan the BE services causing slowness and failed backups.

You can also consider a repair of BE using Add/Remove Programs and using BEutility.exe to repair the BEDB.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

MishMash's picture

Thanks guys! I've just checked the services, they are all up and running. No specific error messages in the event viewer either.

There isn't an AV installed on the source host, there is one on the BE server itself

BE used to be installed on the server that is bugging right now. I have been having this error for a while now, so i decided to move BE from this server to a new server, it didn't help :(

 

Any more suggestions?

 

MishMash's picture

Ok I did find something in the event viewer. Looks like VSS has an error..

Error Volume Shadow Copy Service: could account spsearch with status 1376 not traced. Verify domain controller and the registry key VssAccessControl.

editing:
    Writer Collecting Data
    Asynchronous operation without

context:
    Execution Context: Requestor
    Current status: GatherWriterMetadata

Error Specifics:
    Error: NetLocalGroupGetMemebers (spsearch), 0x80070560, The specified local group does not exist.
 

Could this be the error? Any suggestions?

CraigV's picture

Run: vssadmin list writers - do this from a command line and see what the output it. Anything not stable and running is in error, and a restart normally fixes this.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...