Solved

BackupExec 2010 R3 won't backup over different interface!

Posted on 2014-11-13
7
128 Views
Last Modified: 2014-11-25
Hi, all!  Using BackupExec 2010 R3 on Win2k8 R2 server, trying to back up files from another Win2k8 R2 server (with agent installed) across a separate interface ("VLAN198") thru switch ports specifically set up for that VLAN (198).  That specific NIC interface is selected in the BE job properties (Network & Security), both with and without a specific subnet selected (subnet x.y.198.z).  Jobs succeeds backing up files on the BackupExec server itself (local files), but fails when attempting to connect to the machine across the 198 subnet (error: Media Server was unable to connect to the remote machine using subnet x.y.198.z on network interface "VLAN198").  Please note that backups work fine thru the default subnet, and have been working perfectly since installation.  I'm trying get backups working thru specific interfaces, and keep getting this same error.

Suggestions?  I'm sure it's probably something simple that I'm missing.

Thanks!
Steve
0
Comment
Question by:SteveBottoms
  • 4
  • 3
7 Comments
 
LVL 5

Expert Comment

by:A Karelin
ID: 40441830
Is your target server in subnet x.y.198.z?
Do have route to this server throuhg the gateway or the interface in subnet x.y.198.z or traffic goes through the default gateway?
0
 

Author Comment

by:SteveBottoms
ID: 40443311
A Karelin, thanks for responding!

Yes, the target server is on the x.y.198.z subnet (ie, has a NIC configured with that IP address).  This particular subnet has no default gateway (basically peer-to-peer), and all devices in this subnet are contained within a specific VLAN.  No off-subnet routing is needed.  I can ping/browse to the target IP address from the BE server without issue.

I've pushed out the agent to the specific IP address (x.y.198.32) of the target server, EVEN THOUGH the agent is already installed and operational on that server using "Any available interface".  The backup still failed ("unable to connect to the remote machine"), so it doesn't appear to be a registered agent issue by IP address.

Steve
0
 
LVL 5

Expert Comment

by:A Karelin
ID: 40444081
Try to use only the interface from x.y.198.z subnet for the target server, for jobs, for installing the agent. Remove agent from server and reinstall.

DId you check firewalls options on your servers? Try check ports on the servers by telnet. http://www.symantec.com/docs/HOWTO22989

On the Remote Agent publishing screen:
Check the box which says 'Enable remote agent to publish the IP address and name of the remote computer and the version of the Remote Agent to media server'

DId you make "Establish Trust Relationship"?

Enable debug logs for the agent and look into.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 

Author Comment

by:SteveBottoms
ID: 40448561
A Karelin, thanks for replying.

1) I've removed and re-installed the agent on the target server, specifying the IP address as the machine in the Agent installer, and have made sure the checkbox "Enable remote agent to publish..." is checked.
2) There are no firewalls involved, software or hardware, between the Media Server and the target server.
3) A trust relationship is established as best I can tell.

Steve
0
 
LVL 5

Expert Comment

by:A Karelin
ID: 40448934
Try to use SGMON utility to perform a live debug of the BE server.
0
 

Accepted Solution

by:
SteveBottoms earned 0 total points
ID: 40455585
Still can't get it working, but I'll keep plugging away!

Thanks to those that responded!
0
 

Author Closing Comment

by:SteveBottoms
ID: 40464084
No solution at this time, so closing question.
0

Featured Post

Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you looking to recover an email message or a contact you just deleted mistakenly? Or you are searching for a contact that you erased from your MS Outlook ‘Contacts’ folder and now realized that it was important.
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now