Problem backing up Exchange Mailboxes

[Punce]

I'm using Backupexec v7 on my NT4 PDC, and I have Microsoft Exchange 5.5 on an NT4 BDC.

When I create a backup job, and go to the Selections tab, I navigate to my Exchange Server through the 'Entire Network' branch. When I've done that, I can see MS Exchange Directory / Information Store / Mailboxes.

The first time I clicked on MS Exchange Mailboxes, I could see all of the mailboxes. I selected the ones I wanted to backup, and it seemed to have accepted it.

But now when I click to expand the Microsoft Exchange Mailboxes branch, to select individual mailboxes to backup, I get an Error dialogue box with the following data:
__________________________

Error
The specified network name is no longer available
__________________________

I restarted all of the Backupexec services, and it seemed to let me in again - but the second time I try, I get the same error.

What's going on?

 

[divyan]

Try Backup Exec.8.6...the stablest version around...

Divyaprakash

 

[Guest_imported]

It sounds like you may have a name resolution issue. Check into your WINS configuration and settings, anything to do with NIC updates, CRC errors on the port, etc. You may be able to ping successfully, but if you have errors, there may be a time out due to the increased transmission / retry times and not be finding the resource.
You also may be having a conflict in WINS. Use NBTSTAT to determine or use your WINS manager to check. Also, Be sure to check to see who your master browser is. if it is not the pdc. restart the computer browser service on the PDC to restablish it's master browser status. Make a note of who the master browser was and disable that PC. If you have continual issues of master browser status, you may have issues with hubs, switches where there may be communication breakdowns. Here, we have disabled workstations computer browser services.

 

[dankelt]

This document suggests that by logging onto the server as a different user than what the backup exec services start as will cause this error.

http://seer.support.veritas.com/docs/191600.htm

Dan

 

[Punce]

Thanks dankeIt for that link, even though logging on as the correct user didn't sort the problem, something else on that link worked!

I did have v7.3 revision 2371, which this is a known bug. They recommended to update to revision 2575. This I did, after finding the patch on their website, and now it works.

Thanks again, I'm very pleased to be able to have sorted this out with the help of you guys... Keep up the good work.

Mark