Forum Discussion

TornadoWire1's avatar
13 years ago

Servers disappeared from favourite resources.

Hello,

Both of my Backup Exec 2010 R3 installations have started having issues with servers disappearing from under the 'Windows Systems' tree within Favourite Resources on the Selections tab. The backup/restore jobs now fail with the following error:

Restore- SQLSRVR-1.tornadowire.local
The Media Server was unable to connect to remote machine SQLSRVR-1.tornadowire.local on network interface Local Area Connection.

The servers are still communicating fine on the network and I have also re-installed the agents without a problem.

Does anybody have an idea what might be going on here?

Kind Regards

Simon Emms

  •  

    refer this older post:

    https://www-secure.symantec.com/connect/forums/agents-not-publishing-themselves-media-server

9 Replies

  • Check if the remote agent service is started on the remote server.

    Make sure media server name appears in the publishing tab of the remote agent utility.

    Check if the port#10000 is being used by beremote.exe or some other application.

    Try taking a backup by adding IP address of the remote server in the user defined selection.

  • Is the remote agent publishing to media server? Verify in the remote agent utility in client server.

    From TN: Backup Exec automatically deletes a remote computer from the Windows Systems node in the following situations:

    • The remote computer becomes disconnected from the network.

    • The Remote Agent is uninstalled from the remote computer.

    If the media server receives published information from the remote computer again, Backup Exec adds the computer name to theWindows Systems node again.

    If the media server does not receive published information within a 24-hour period, a user attention icon appears next to the remote computer's name. This icon is displayed for 13 days.


    Some of the reasons why the media server may not receive published information include the following:

    • The publishing option is disabled on the Remote Agent.

    • A media server is removed from the list to publish to.

    Here is the TN: http://www.symantec.com/docs/HOWTO22699

  • Nothing has changed as far as the remote agents are concerned and has been running fine for the last 6 months. This is affecting more than one remote agent and I cannot explain what has suddenly caused this. One one of the installations all of the remote agents have disappeared.

    All the agents are publishing to the correct server name and the remote agent service is running on all of them.

    Here is a list of all the ports in use and associated IP addresses for one the servers with Backup Exec installed. This is a virtual machine host and the remote agents are installed on the virtual machines on the same server:

     

    Active Connections

      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       232
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:2179           0.0.0.0:0              LISTENING       2652
      TCP    0.0.0.0:2301           0.0.0.0:0              LISTENING       2408
      TCP    0.0.0.0:2381           0.0.0.0:0              LISTENING       2408
      TCP    0.0.0.0:3052           0.0.0.0:0              LISTENING       1976
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       6148
      TCP    0.0.0.0:3527           0.0.0.0:0              LISTENING       3000
      TCP    0.0.0.0:5633           0.0.0.0:0              LISTENING       8216
      TCP    0.0.0.0:6101           0.0.0.0:0              LISTENING       4116
      TCP    0.0.0.0:6106           0.0.0.0:0              LISTENING       3000
      TCP    0.0.0.0:8139           0.0.0.0:0              LISTENING       1528
      TCP    0.0.0.0:8485           0.0.0.0:0              LISTENING       2416
      TCP    0.0.0.0:10000          0.0.0.0:0              LISTENING       10000
      TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       784
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       720
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       1008
      TCP    0.0.0.0:49166          0.0.0.0:0              LISTENING       888
      TCP    0.0.0.0:49246          0.0.0.0:0              LISTENING       880
      TCP    0.0.0.0:65426          0.0.0.0:0              LISTENING       1828
      TCP    127.0.0.1:8139         127.0.0.1:49180        ESTABLISHED     1528
      TCP    127.0.0.1:8139         127.0.0.1:58332        ESTABLISHED     1528
      TCP    127.0.0.1:8139         127.0.0.1:59084        FIN_WAIT_2      1528
      TCP    127.0.0.1:49180        127.0.0.1:8139         ESTABLISHED     2176
      TCP    127.0.0.1:58332        127.0.0.1:8139         ESTABLISHED     8448
      TCP    127.0.0.1:59084        127.0.0.1:8139         CLOSE_WAIT      2932
      TCP    192.168.0.5:139        0.0.0.0:0              LISTENING       4
      TCP    192.168.0.5:3389       192.168.0.67:52663     ESTABLISHED     6148
      TCP    192.168.0.5:58585      192.168.0.12:139       ESTABLISHED     4
      TCP    192.168.0.5:58590      192.168.0.8:139        ESTABLISHED     4
      TCP    192.168.0.5:58601      192.168.0.16:139       ESTABLISHED     4
      TCP    192.168.0.5:58609      192.168.0.7:139        ESTABLISHED     4
      TCP    192.168.0.5:58878      192.168.0.5:65426      ESTABLISHED     5964
      TCP    192.168.0.5:58900      192.168.0.5:65426      ESTABLISHED     3000
      TCP    192.168.0.5:58911      192.168.0.5:65426      ESTABLISHED     8216
      TCP    192.168.0.5:58912      192.168.0.5:65426      ESTABLISHED     8216
      TCP    192.168.0.5:58919      192.168.0.5:65426      ESTABLISHED     8216
      TCP    192.168.0.5:58920      192.168.0.5:65426      ESTABLISHED     8216
      TCP    192.168.0.5:58927      192.168.0.5:65426      ESTABLISHED     3000
      TCP    192.168.0.5:59017      192.168.0.13:139       TIME_WAIT       0
      TCP    192.168.0.5:59023      192.168.0.3:139        TIME_WAIT       0
      TCP    192.168.0.5:59025      192.168.0.6:139        TIME_WAIT       0
      TCP    192.168.0.5:59055      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:59064      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:59065      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:59066      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:59067      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:59068      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:59075      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:59076      192.168.0.5:65426      TIME_WAIT       0
      TCP    192.168.0.5:65426      192.168.0.5:58878      ESTABLISHED     1828
      TCP    192.168.0.5:65426      192.168.0.5:58900      ESTABLISHED     1828
      TCP    192.168.0.5:65426      192.168.0.5:58911      ESTABLISHED     1828
      TCP    192.168.0.5:65426      192.168.0.5:58912      ESTABLISHED     1828
      TCP    192.168.0.5:65426      192.168.0.5:58919      ESTABLISHED     1828
      TCP    192.168.0.5:65426      192.168.0.5:58920      ESTABLISHED     1828
      TCP    192.168.0.5:65426      192.168.0.5:58927      ESTABLISHED     1828
      TCP    192.168.0.71:59086     192.168.0.8:135        TIME_WAIT       0
      TCP    192.168.0.71:59098     192.168.0.16:135       TIME_WAIT       0
      TCP    192.168.0.87:58961     192.168.0.7:135        TIME_WAIT       0
      TCP    192.168.0.87:59019     192.168.0.13:49225     TIME_WAIT       0
      TCP    192.168.0.87:59053     62.121.6.145:80        ESTABLISHED     3000
      TCP    192.168.0.87:59057     192.168.0.13:49155     TIME_WAIT       0
      TCP    192.168.0.87:59072     192.168.0.3:3268       TIME_WAIT       0
      TCP    192.168.0.87:59074     192.168.0.3:389        TIME_WAIT       0
      TCP    192.168.0.87:59080     192.168.0.3:3268       TIME_WAIT       0
      TCP    192.168.0.87:59082     192.168.0.3:389        TIME_WAIT       0
      TCP    192.168.0.87:59088     192.168.0.7:135        TIME_WAIT       0
      TCP    192.168.0.87:59090     192.168.0.3:135        TIME_WAIT       0
      TCP    192.168.0.87:59092     192.168.0.6:135        TIME_WAIT       0
      TCP    192.168.0.87:59094     192.168.0.12:135       TIME_WAIT       0
      TCP    192.168.0.87:59096     192.168.0.13:135       TIME_WAIT       0
      TCP    192.168.0.87:59100     192.168.0.6:7072       TIME_WAIT       0
      TCP    [::]:135               [::]:0                 LISTENING       232
      TCP    [::]:445               [::]:0                 LISTENING       4
      TCP    [::]:2179              [::]:0                 LISTENING       2652
      TCP    [::]:2301              [::]:0                 LISTENING       2408
      TCP    [::]:2381              [::]:0                 LISTENING       2408
      TCP    [::]:3389              [::]:0                 LISTENING       6148
      TCP    [::]:3527              [::]:0                 LISTENING       3000
      TCP    [::]:6101              [::]:0                 LISTENING       4116
      TCP    [::]:6106              [::]:0                 LISTENING       3000
      TCP    [::]:10000             [::]:0                 LISTENING       10000
      TCP    [::]:47001             [::]:0                 LISTENING       4
      TCP    [::]:49152             [::]:0                 LISTENING       784
      TCP    [::]:49153             [::]:0                 LISTENING       720
      TCP    [::]:49154             [::]:0                 LISTENING       1008
      TCP    [::]:49166             [::]:0                 LISTENING       888
      TCP    [::]:49246             [::]:0                 LISTENING       880
      TCP    [::]:65426             [::]:0                 LISTENING       1828
      TCP    [::1]:58901            [::1]:58902            ESTABLISHED     3000
      TCP    [::1]:58902            [::1]:58901            ESTABLISHED     3000
      TCP    [::1]:58909            [::1]:58910            ESTABLISHED     8216
      TCP    [::1]:58910            [::1]:58909            ESTABLISHED     8216
      UDP    0.0.0.0:123            *:*                                    1092
      UDP    0.0.0.0:161            *:*                                    1120
      UDP    0.0.0.0:500            *:*                                    1008
      UDP    0.0.0.0:1434           *:*                                    1396
      UDP    0.0.0.0:3052           *:*                                    1976
      UDP    0.0.0.0:4500           *:*                                    1008
      UDP    0.0.0.0:5355           *:*                                    1200
      UDP    0.0.0.0:55536          *:*                                    1120
      UDP    127.0.0.1:51355        *:*                                    1200
      UDP    127.0.0.1:57082        *:*                                    888
      UDP    127.0.0.1:57135        *:*                                    2652
      UDP    127.0.0.1:61887        *:*                                    10000
      UDP    127.0.0.1:61889        *:*                                    3000
      UDP    127.0.0.1:64929        *:*                                    1008
      UDP    192.168.0.5:137        *:*                                    4
      UDP    192.168.0.5:138        *:*                                    4
      UDP    [::]:123               *:*                                    1092
      UDP    [::]:161               *:*                                    1120
      UDP    [::]:500               *:*                                    1008
      UDP    [::]:1434              *:*                                    1396
      UDP    [::]:4500              *:*                                    1008

  •  

    refer this older post:

    https://www-secure.symantec.com/connect/forums/agents-not-publishing-themselves-media-server

  • This is a known issue, refer to the below article.

    http://www.symantec.com/docs/TECH168154

  • This accepted solution in this post appears to have solved the issue, will monitor tonights backups and perform more tests tomorrow to confirm.

    Thank you

  • There are many resons to this issue, it seems there are 2 nic's on the media server, if all of above is fine then try this one.

    - Go to Tools => Options select Network and Security and chose the appropriate nic which is used for data backup.

    wait for sometime and if the remote server does not showes up under favorite, then right click on favorite and select add windows system and the server manually.

    you can also try selecting the server from the Domain computer list.

    try this if you havent already tried and let us know your observation.

  • The fix worked for me with a couple of additional steps, so in full here is what I did:

    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, drill down through Domains and then Microsoft Windows Network and right-click the remote agent server and select "establish trust relationship".

    Important! Remember to repeat step 6 with every agent computer you have! Backups wont work otherwise.

    7. Then drill down to Windows Systems under Favourite Resources, right click and select 'Add Windows Systems' and enter remote server name (Repeat  for all affected servers), click refresh and then they should all re-appear.

     

    I have tested backups and restores and these servers are now communicating fine again.

    Many thanks for everyone's help!