Running Veritas 9.1 across multiple subnets.

I'm running Veritas 9.1 in a Windows 2003 environment.  We have 3 different subnets that we would like to backup various folders on.  Within Veritas I can pick the folders/files I wish to backup, create the job but when I attempt to run a test job I receive the error message under the job log file that "unable to attach to drive" for any subnets outside of the one the software is working on (I have Veritas on 2 of the 3 subnets in question and receive the same message regarding the other subnets).  Any ideas?
dvstevenAsked:
Who is Participating?
 
PashaModCommented:
Closed, 250 points refunded.
PashaMod
Community Support Moderator
0
 
BILJAXCommented:
ok, you need to map the remote folders via IP.   Also, you have to have the user-defined option enabled under Options.   Also, make sure you can ping and connect to those directories via \\IPADDRESS\share from the server running Veritas.   Also, you may need Remote Agent for Windows (I'm assuming windows workstations) and Remote Agent for Windows Servers.   Deploy those to the target systems and enjoy the backup goodness.



AC

Remote Agent:

http://seer.support.veritas.com/docs/253058.htm

0
 
pgm554Commented:
Do you have everybody licensed correctly?
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
dvstevenAuthor Commented:
Thanks for the reply.....
I have the Remote Agents setup on the target systems (hence the reason I can backup to the same subnet the software\backup server the remote agents on those subnets, just not across them).  Since I have various folders on each of the other servers are you suggesting that I map the drive via IP on the server running Veritas?  
I was under the impression that Veritas uses netbios for resolution and there was a way to use a fowarding type of address within our routers\switches to do basically this.  That is what I was actually looking for, but I'll try the mapping of the root drives, but where?
Thanks
0
 
BILJAXCommented:
Sounds like you have an issue at your DNS server then.    Can the backup server PING the target machines?  Veritas used to use NETBIOS.
0
 
dvstevenAuthor Commented:
The backup server can ping all the machines without any problem, and I don't have any problems seeing them when choosing a backup job.  In looking at the Veritas website the only mention I find of subnets is to setting up a seperate job when changing to a different network job.  Our network consultant thought that he had heard of these problems with Veritas before and mentioned something about the forwarding or possibly masking address options within our network.  I'm not familiar enough with the intracacies of networks to follow this.
0
 
BILJAXCommented:
hmm, I'm without words since we don't have a problem here and we backup over 4 subnets.
0
 
BILJAXCommented:
You may want to try having the Backup job run on the dc.
0
 
dvstevenAuthor Commented:
Actually it is running on the dc.    We didn't have any problem until we subnetted our network for use with VOIP.  I do appreciate all you help on this though.  We have data between two of the locations going over wireless with the base stations assigned to the same subnet, along with one of the ports on our remote switch, but the third location (that both of the other subnets can see to schedule a jog but neither can attach to during the test run) is connected at our colo over two seperate t-1s from our other locations.  This is interesting that you can backup over subnets.  Maybe it's time to contact Veritas.
0
 
BILJAXCommented:
http://www.veritas.com/be_support/www?cmd=landing&product_code=10

http://support.veritas.com/solutions/directassist.htm


There's the contact for Veritas.    For the life of me, I think it's the way you have your network subnetted.   Why didn't you just run a VLAN to split data/voice packets?
0
 
pgm554Commented:
Two things:
Try adding an ip helper setting your routers
Add the new server ip addresses to a hosts file on the backup server(system32/etc).
0
 
dvstevenAuthor Commented:
I appreciate all the answers but I found the solution.  It had to do with choosing to use a particular interface during job setup, I had to pick the NIC card in the box I'm running Veritas on and then the use any interface checkbox on the same screen.  No more unable to attach drives message.  Thanks all.  Steven
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.