Remote Backup Hangs... Debug log stops at BFT_NTFS_DATABASE=
Updated: 21 May 2010 | 6 comments
I have two Active Directory servers... When I try to do a backup on one server of just a simple file on the C$ share, the backup job hangs. The job is setup to cancel after 6 hours but it does not. I can not kill the job on the backup server without killing the bengine process. I can get the backup job to fail by stopping the Remote Agent on the AD server.
In the Debug log on the remote agent
The last line is BFT_NTFS_DATABASE='....'
The next line should be Attach to \\Server\System$State
I show the connection is still active with a netstat -a.
I tried doing an uninstall -> reboot -> reinstall.
This has occurred recently. Backups were just fine this past tuesday.
Discussion Filed Under:
Comments
I just did some more trouble shooting. I tried selecting the System State for backup and hung Backup Exec. So the trouble is definately with my System State. I increased privileges of the account I am using to Domain Admin. I restarted the services and I am still getting the same trouble.
I think I have traced it down to the remote agent attempting to connect to the certificate services when checking on the system state. Why does the remote agent connect to all of these services for a simple file backup? I am not trying to backup the system state. I am trying to backup some exported log files.
Hello,
It seems the remote server backup job hangs. Are you backing it up to a tape device or a backup to disk folder? When the job hangs, what message do you get in the job monitor? Check if there are any errors in the Windows event logs. Is there enough space on the media for the job? What is the amount of data being backed up?
Revert with details.
Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.
Regards.
I am backing up to tape. There are no error messages. It will run forever. Take a look at my follow ups on this issue. Specifically my last message. Plenty of space. Nothing in the event logs. When trying to backup \\servername\share\*.log the server still does something to the system state which then tries to contact the Certificate Services installed on the box which are a backup of Certs on another box and therefore doesn't respond. I temporarily enabled the certificate server to reply and the backups worked properly. This will not do. I shouldn't need certificate server to be running when doing a backup of a file share.
Hello david,
- Please ensure that the remote agent on this server is running under the local system account.
- Check the alerts tab for any device or media alerts
NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.
Obviously the forum support failed reading comprehension. I have tracked down the reason for the issue. When backing up just a file share, backup exec makes several unnecessary connections to check the system state and registry. If Certificate Services are installed on the Remote Server, Backup exec will try to connect to it. Being an emergency backup server, I block attempts to connect to certificate services. This is causing the backup to hang. The backup is not failing and there are no error messages. I figured this out by turning on full debug logs and comparing them between two servers. Once I noticed the system state being accessed, I tried to select the system state for backup on the server that was failing. The preceding caused backup exec to freeze. I removed the block to certificate services and everything worked normally.
WHY DOES BACKUP EXEC MAKE UNNECESSARY CONNECTIONS TO THE REGISTRY, SYSTEM STATE, AND CERTIFICATE SERVICES WHEN ATTEMPTING TO BACKUP JUST A SIMPLE FILE SHARE?
Would you like to reply?
Login or Register to post your comment.