Corrected....

Host name on Master for Production host name pointing at maintenance network IP.

Exchange backups are going across the maintenance network.

Thanks

Andrew

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Ashby,
Andrew
Sent: Wednesday, October 15, 2003 9:30 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NBU 4.5 running backups over maintenance network


We have Netbackup 4.5 FP5 in a small environment which has both a production 
and maintenance network.     Our Master is also our Media server.
Clients are Exchange Servers as well as a couple of F&P servers.    Some 
Servers have a connection to maintenance network, some do not.
All running on Win2k SP4.

When we were at NBU 3.4 - you could add a registry key to the client - 
REQUIRED_INTERFACE and using a host file force the backups to run over the 
maintenance network.  Even though initiated from the scheduler over the 
production network, the client sent the backup stream over the maintenance 
network.
As you may know, with the Exchange Agent, you must use the Exchange Server name 
(=equals the production Hostname) - for Netbackup to be able to backup the 
Information Store.

Now we upgrade to 4.5 and the problem is - it goes over the production network. 
  The only way to get it to run over the maintenance network is to have the 
Required Interface variable set on both the Client and the NBU Server.     
Doing this, however, procludes all systems that don't have a maintenance 
network connection from being able to run.

Does anyone know a way around this?    Currently all of our backups are running 
over the production network - which is not good.

Thanks

Andrew

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu