12-01-2011 10:35 PM
Most of my servers aren't publishing themselves to media server anymore. I don't know what has happened, because this used to work perfectly couple of days ago. As you can see in the picture, I am not able to backup Enterprise Vault anymore.
When I'm trying to install agents and selecting "import servers published to this media server" I am able to see only one server! Agents' publishing settings are correct, and as I said, nothing has changed.
Solved! Go to Solution.
12-23-2011 02:07 AM
I found solution for this using my contacts. Here is how I got it working:
1. Stop Backup Exec services
2. Go to \Symantec\Backup Exec\Data folder
3. Search for files with CRT file extension. Move files you found (4 pcs) to another folder.
4. Search for files with KEY file extension. Move files you found (4 pcs) to another folder.
5. Start BE services.
6. Open a selection list, right-click agent computer and select "establish trust relationship".
Important! Remember to repeat step 6 with every agent computer you have! Backups wont work otherwise.
Hope this helps.
12-01-2011 11:13 PM
Hi,
1. Are the agents running on the servers?
2. Have you checked to see if a firewall isn't perhaps blocking the RAWS agent on port 10000?
3. Have you tried to uninstall the agent and then push-install it?
Thanks!
12-02-2011 12:26 AM
Publishing is inbound (Remoet Server to Media server) on Port 6101 so that needs to be open on and firewalls as well.
12-02-2011 01:58 AM
1. Agents are running
2. There is no firewall installed, and I am able to telnet mediaserver on ports 10000 and 6101. In Remote Agent's debug logs I saw error message relating the connection to port 6101.
3. I have uninstalled and push-installed agent.
I have also installed this fix, that should fix similar issues: http://www.symantec.com/business/support/index?page=content&id=TECH161270
After installing the fix error message about connecting to port 6101 seems to have disappeared. However, problem still persists.
12-02-2011 02:53 AM
This may sound stupid....Reboot BE media server now (it has worked for me in past).
12-02-2011 03:13 AM
Nothing sounds stupid anymore when it comes to Backup Exec. I am so ready to give up, because there is always something going on. You should be able to rely on these systems.
The media server reboot didn't resolve this issue. What is the service on media server that responds to these requests?
I attached debug log from EV-server, i hope you can find something useful from it.
12-02-2011 05:43 AM
looks similar to another post - https://www-secure.symantec.com/connect/forums/ev-job-stop-work-after-update
12-02-2011 06:12 AM
As a test, change media server publishing information from name to IP address
on a client machine and see if that works. (thinking about name resolution issue
if media server IP address changed recently or something)
Refer: http://www.symantec.com/docs/TECH65151
12-02-2011 06:13 AM
It's quite similar, only the port is different in my case. Could this be related to certificate somehow? I have tried to re-establish the trust relationship, and everything seems to proceed as they should. Still I'm not able to see the server as favourite machine. Only errors I am able to see are in debug log I attached earlier.
12-02-2011 06:16 AM
I have already tried that, but unfortunately it wasn't name resolution issue this time.
12-02-2011 06:21 AM
Is this BE 2010R3 with remote agent updated, make sure trust is present:
12-02-2011 06:59 AM
Be remote debug shows: Failed Client Side SSL handshake.
After upgrading Backup Exec 2010 from R2 to R3, none of the remote servers are appearing under Favorite resources.
refer this: http://www.symantec.com/docs/TECH168154
12-02-2011 11:55 AM
As you mentioned that you are not able to see any servers under Favorite resources, I suspect that you are also not able to see the EV resources for the same reason.
Its somewhere related to the following Known Issue:
or technote " http://www.symantec.com/docs/TECH168154 "
This will not affect other normal files and folder backups but will affect EV backups as it depends heavily on publishing.
Thanks,
-Sush...
12-06-2011 10:33 PM
Sorry for late response, I have been out of office few days.
Publishing wouldn't be a problem if there wasn't EV. Is there any other ways to backup it?
12-06-2011 10:57 PM
I have tried remote and local install with same results. Installations were successfull, but the problem was same.
When I select "Establish trust relationship" nothing happens. In Debug monitor you can see these error messages:
BENETNS: [07.12.11 08:54:57] [4908] [nrds] - Accepted new connection.
BENETNS: [07.12.11 08:54:57] [4908] [nrds] - AcceptConnection: SSL was requested
BENETNS: [07.12.11 08:54:57] [4908] [nrds] - AcceptConnection: Failed Server Side SSL handshake.
BENETNS: [07.12.11 08:54:57] [4908] [BESocket] - @@@@@@@MyCloseSocket called with sockfd = 748(0x2ec) retval = 0
BENETNS: [07.12.11 08:54:57] [4908] [nrds] - Accepted new connection.
BENETNS: [07.12.11 08:54:57] [4908] [nrds] - AcceptConnection: SSL was requested
BENETNS: [07.12.11 08:54:57] [4908] [nrds] - AcceptConnection: Failed Server Side SSL handshake.
12-07-2011 11:05 PM
Please create a support case. I sit next to the guy investigating the issue.
12-08-2011 12:56 AM
I created a case yesterday, and I have also subscribed to technote 168154. I hope that your colleague will find the cure for this soon.
What method should I use now with Enterprise Vault?
12-08-2011 08:02 AM
Please create a support ticket if you are affected by this issue, and see the SSL handshake error in the beremote debugs from your remote servers.
Unfortunately, there is no work-around for Enterprise Vault backups at this time.
Thank you.
12-08-2011 11:58 PM
We have same issue here. Have opend a support case. But Support team have closed it because there is NO reason yet. Have installed all Hotfix (SP1) - cant install HF161270 because SP1 is installed.
Workaround is only to select from domain list. Not so pretty........
12-09-2011 02:47 AM
Haven't heard anything from them either. This is not good propaganda for Symantec..Have you subscibed this yet? http://www.symantec.com/docs/TECH168154 .