Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Operation Startup Error (4). MoverConnect to <Media-Srv> failed

Updated: 23 May 2010 | 5 comments
Kai-Oliver Kuhl's picture
0 0 Votes
Login to vote

After 1 1/2 year of nearly flawless operation all of a sudden we encountered the above error. No alert was given, no message sent, just this error in the job log and of course, the job has not run successfully.

The error occurs right at the start of job execution.
Knowledgebase and news-groups don't say anything about it.

System: NetWare v4.11SP9a, BE v9.0/4202, Drive SONY SDX-500C

Any hints, where this "MoverConnect" trouble might stem from?

TIA, Kai-Oliver

discussion Filed Under:

Comments

Richard Bastiaansen's picture
11
Jul
2005
0 Votes 0
Login to vote

Hello Kai,

Sice 4 days ago I had the same problem on our Novell 6.0 server. I looked in the SYS/etc/hosts file and checked the server's own ip adres. This Ipadres must be set in this hosts file en match it's own IP adres. I changed it accidentally so the Veritas software did not recognise the server and it's ip adres anymore. ;-) HOpe this will be helpfull for you.

Kindly regards,

Richard

Kai-Oliver Kuhl's picture
11
Jul
2005
0 Votes 0
Login to vote

Hi Richard, thanks for your hint!
I'm not aware of changes to the servers ip address, but we also had some trouble with SAP (Novells Service Advertising Protocol). Every now and then it seems to stall out of the blue and the console command "display servers" doesn't display any entry at all, not even the servers name itself. Sometimes a server restart is necessary to recover from this situation. So the error very well may point to the same trouble when using IPX/SPX (SAP) resources.

George Johnson 2's picture
19
Aug
2005
0 Votes 0
Login to vote

Seem to be getting the same message - out of the blue - nothing has changed on NetWare 5.1. Did rebooting the server solve the issue or were there other problems encountered?

George Johnson 2's picture
19
Aug
2005
0 Votes 0
Login to vote

Okay, contacted symantec, and upon reply this did the trick for my environment: NW5.1 sp7, Bkupexec 9.1 build 1167 . . .

To resolve the issue we suggest the following :
1) BESTOP at the media server prompt.
2) Rename the folder SYS:BKUPEXEC\MM to MM.OLD
NOTE: SYS is the default volume during installation. This location may vary if a custom installation occurred.
3) Create a new folder called MM in the BKUPEXEC directory.
4) BESTART at the server prompt.
NOTE: The MM directory contains information about existing partitions and User Media Sets. If Backup Exec is running in Partition Management mode, new partitions will need to be created. User Media Sets will also need to be recreated.

MartinioLu's picture
06
Apr
2009
0 Votes 0
Login to vote

Had the same issue

Hello,

I had the same problem, and for some unknown reason the hosts file really changed.
I modified it, ran a test and it worked properly.

Thanks for the infos!

Kind regards,

Martin