07-03-2012 03:50 AM
Hi
I’m slowly going off this product.
We have had this system ( backup exec 2010 –R3) running since the beginning of this year (had another version previously) and yesterday it decides to not backup 2 servers and do weird things in the selection area of a job.
If I open a selection list and look at the view by resource, where I normally would get a tick or slash in a server selection box. I get nothing. However the selection details list has all the includes and excludes.
If I select a server is automatically fill’s in the correct selection of data I want to backup, but does not save this if I leave the page?
The other jobs I have all look ok.
The two servers that backed up ok last week are both in the selection detail list and if I look at resource credentials they are there also but if I test a connection I get an error saying it cannot communicate with the agent.
Alan.
Solved! Go to Solution.
08-20-2012 06:24 AM
OK managed to find where the time out is located
c:\programdata\symantec\liveupdate\settings.liveupdate
Raised the value from 45 to 600 and i started to get the updates down correctly.
Once down i pushed them out to all the clients and.......I can now see all the servers correctly and it now backs up the TMG correctly which is on another port not the default one.
Many thanks for all the help.
Alan.
07-03-2012 04:09 AM
Hi Alan,
Have you loaded BE 2010 R3 SP2 and any available patches? If not, do so, and you then need to push-install these to any remote servers you might have.
Then check again. You should also ensure that the BE services are not being actively scanned by any AV running on that media server.
Thanks!
07-03-2012 04:47 AM
Hi, i will do what you have said, but why all of a sudden has this happened.
Its stopped my mission critical backups from working.
The live update does not work, im now in the process of fire fighting this.......
Alan.
07-03-2012 04:50 AM
LU doesn't work? What error are you getting?
Anything in the Alerts section of BE, or in the Event Viewer that you can post here?
07-03-2012 04:54 AM
From this link:
http://trialware.norton.com/files/fc/Backup_Exec_2010_13.0.5204_MultiPlatforms_Multilingual_DVD.iso
Install it on top of your current system, you will not lose any settings or logs.
After that, you will be able to run live update without trouble.
Push the updated agent to all your servers, specially on those two that you are having problems with.
Regards,
07-03-2012 05:59 AM
HI i downloaded the SP2 (not from the link above as i did not see the post), the installed updates show that i have SP2, but still the update utility gives me errors.
It seems to connect and finds 4 extra updates but then waits at 0% complete.
It eventualy failes with LU1835 failed to respond in a reasonable amout of time.
I decided to forget this and push out SP2 to the agents, which went well but needs a reboot to finish the install.
So ill remote in tonight and reboot the servers in question.
Ill let you know the results tomorrow.
Alan.
07-03-2012 06:46 AM
Alan: For that LU error, check the TN below:
http://www.symantec.com/business/support/index?page=content&id=TECH53376
Thanks!
07-03-2012 08:06 AM
Ok have gone throught that, the only one that i cannot find is the:
How to configure the time-out value for HTTP downloads in LiveUpdate version 2.5 and later
The link is dead and if i google it i get the same link?
The other have all come up clear and im still having the problem. see below:
The following Symantec products and components are installed on your computer.
> Symantec Backup Exec (TM) 2010 R3
Initializing...
Connecting to liveupdate.symantecliveupdate.com...
Downloading catalog file (1 of 1), complete.
Opening update list
The digital signature found on the catalog file has been signed by Symantec Corporation.
Processing update list
Opening update list
Processing update list
The following updates have been found:
> Symantec Backup Exec (TM) 2010 R3, 258249.4 KB
Total Download 258249.4 KB
Downloading Symantec Backup Exec (TM) 2010 R3 (1 of 4), failed.
LU1835: The LiveUpdate server failed to respond in a reasonable amount of time. This could happen because you could not connect to the server, the server is now unavailable, or you became disconnected to the server. Try running LiveUpdate again.
Downloading failed, error summary...
LU1835: The LiveUpdate server failed to respond in a reasonable amount of time. This could happen because you could not connect to the server, the server is now unavailable, or you became disconnected to the server. Try running LiveUpdate again.
LiveUpdate session is complete.
Alan.
07-03-2012 08:20 AM
Did you consider checking if the remote agent is running on the affected machines, if the logon account you are using in BE can access these servers. Can you map a drive from these machines to the backup server? Could you please post a screenshot of the selection list, when attempt creating a new job for these servers? The remote agents have been updated after any updates were installed on the backup server, I presume.
07-03-2012 08:27 AM
Still trying to get the full set of updates down from live update, I have manually update the BE server to sp2.
What i dont understand is why when everything has worked fine and no changes have took place, this happens.
The BE server can see\ping\browse the servers in question and the "push" tool to install agents on the servers says that everything is ok.
Doing a full reboot of all servers tonight, so will post tomorrow.
Alan.
07-03-2012 09:17 AM
A screenshot of the backup selections and an excerpt from the debug monitor, while browsing the affected servers would help.
http://www.symantec.com/business/support/index?page=content&id=HOWTO23073 Make sure you invoke this utility and select all the checkboxes and then attempt to browse the selction list.
07-03-2012 10:47 AM
Hi,
Have you tried to repair LU through Add/Remove Programs?
Thanks!
07-04-2012 01:27 AM
HI, the backup failed on the two servers again.
The system backup the other 5 ok even thought they dont show in the selection box only TXT version in the details panel.
I ran the debug monitor on one of the servers we are having problems with and one line got my attention.
On the server in question we are using ndmp port 11000 and have done so for the last few months, this is what i see when i try to browse to that server.
It is looking for port 10000 not 11000 which it used previously?
rds] - Accepted new connection.
BENETNS: [04/07/12 09:17:56] [6448] [nrds] - AcceptConnection: SSL was requested
BENETNS: [04/07/12 09:17:56] [6448] [nrds] - AcceptConnection: Failed Server Side SSL handshake.
BENETNS: [04/07/12 09:17:56] [6448] [BESocket] - @@@@@@@MyCloseSocket called with sockfd = 616(0x268) retval = 0
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\shared] - FS_ResolveDevName: [\\W8S-TMG01.MSMCOLLEGE.local]
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\mb2] - MB2-Resolve returned 1
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\notes2] - Notes Agent:CLNFileSystem::ResolveDeviceName
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\adc] - ADC_ResolveDeviceName: pid = 6312, checking \\W8S-TMG01.MSMCOLLEGE.local
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [beutil] - ApplyRegExp(): Invalid input (\\W8S-TMG01.MSMCOLLEGE.local). Parsing Failed.
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [beutil] - GoodEvName(): Invalid EV device (\\W8S-TMG01.MSMCOLLEGE.local).
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [beutil] - ApplyRegExp(): Invalid input (\\W8S-TMG01.MSMCOLLEGE.local). Parsing Failed.
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [beutil] - GoodEvName(): Invalid EV device (\\W8S-TMG01.MSMCOLLEGE.local).
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [beutil] - Input Error (e000fe23) for Type: (43)
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\ev] - EVM_ResolveDeviceName: Function Enter
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [beutil] - ApplyRegExp(): Invalid input (\\W8S-TMG01.MSMCOLLEGE.local). Parsing Failed.
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\ev] - EVM_ResolveDeviceName: Invalid device name (\\W8S-TMG01.MSMCOLLEGE.local). Parsing Failed.
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\ev] - EVM_ResolveDeviceName: Function Exit
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [fsys\ntfs] - Not valid device name : \\W8S-TMG01.MSMCOLLEGE.local
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [dsss\rpc] - RPCDsSession::GetLoginCredentials: Connecting to BEM API as user: MSMCOLLEGE\administrator
BESERVER: [04/07/12 09:17:56] [8152] -1 Client requested key (1341390028).
BESERVER: [04/07/12 09:17:56] [8152] 01 Server Configuration: Client added: 9
BESERVER: [04/07/12 09:17:56] [8152] -1 Client 'W8S-APP01' connected('','MSMCOLLEGE\administrator'): 0xa8e86d0
BESERVER: [04/07/12 09:17:56] [8152] 01 Server Configuration: Client removed: 8
BESERVER: [04/07/12 09:17:56] [8152] -1 Client 'W8S-APP01' Disconnected:0xa8e86d0
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [ndmp\ndmpcomm] - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [ndmp\ndmpcomm] - ndmpConnectEx: Querying the neighbour advertisement cache to discover information on 'W8S-TMG01.MSMCOLLEGE.local' ...
BENETNS: [04/07/12 09:17:56] [8592] NRDS API - client connected.
BENETNS: [04/07/12 09:17:56] [8592] NRDS API - client disconnected.
BEREMOTE: [07/04/12 09:17:57] [0000] [14468] [ndmp\ndmpcomm] - ndmpConnectEx : Control Connection information: A connection was established between end-points 172.16.1.6:52702 and 172.16.1.8:10000.
BKUPEXEC: [04/07/12 09:17:57] [0025] [Info] VSN received: type = ACTJOBEX_UPDATE
BKUPEXEC: [04/07/12 09:17:57] [0025] [Debug] VSN is a MODIFY
07-04-2012 01:34 AM
Yep, uninstalled, reinstalled.....promised the server i would take it on holiday with me......nothing.
07-04-2012 06:32 AM
How do i force the BE server to talk to the Agent on port 11000.
I have removed the agent from the server and from the deploy wizard, I have added it back in but it still freezes the BE program if i browse to the server.
alan.;
07-04-2012 06:36 AM
07-04-2012 07:01 AM
Ive already done most of that with the server having the problem, I have set the Port to 11000.
I have tried several times to change the ports on the BE server but it always uses 10000.
Alan.
07-05-2012 02:53 AM
Right, I have removed the two servers that are not talking to the BE server.
I now get a good set of backups on the remaining servers, but they still dont show in the view by resource panel?
Im going on holiday now for two weeks, and when i return ill attempt to get the two servers to connect....
Speak to you all later.
Alan
08-20-2012 06:24 AM
OK managed to find where the time out is located
c:\programdata\symantec\liveupdate\settings.liveupdate
Raised the value from 45 to 600 and i started to get the updates down correctly.
Once down i pushed them out to all the clients and.......I can now see all the servers correctly and it now backs up the TMG correctly which is on another port not the default one.
Many thanks for all the help.
Alan.