Hi,
First, for me REQUIRED_INTERFACE clearly only works for client
initiated backups and not master initiated backups.
Secondly, I tried to backup a W2003 client through the backup interface
in NBU 5.1 and it works. Master speaks to the media server through the LAN
production network and tells the media server to backup the client whoses name
is the backup network name ( -bk ). The media server then speaks to the client
and introduces itself as the media server-bk name . This name is in the server
list of the client. The client seeing that media server-bk speaks to him answer
to the media server through his own -bk interface. So the backup and restore go
to the -bk network and all is well. No needs to change the routing table.
Next, I tried the same thing on a NBU 6.0 MP4 environment, and this
time, the behavior is different despite routing tables and hosts file are the
same
The master presents always to the client as the LAN name and not the -bk name.
Then , the client answers to the master through the LAN name and not the -bk
name. I was obliged this time to modify the route table on the client to force
the client to reach the LAN adress through the -bk network.
I don't understant why this behavior. I opened a case to Symantec.
But for me , you shouldn't be forced to modify your routing table to
pass backup througput to your -bk network.
Everybody has other experiences ??
Thanks
Gilles POUSSARD
-----Message d'origine-----
De : veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]De la part de Weber,
Philip
Envoyé : mardi 5 juin 2007 15:31
À : VERITAS-BU AT mailman.eng.auburn DOT edu
Objet : [Veritas-bu] REQUIRED_INTERFACE Problem?
Master/Media Solaris9 NBU 5.1 MP6.
Client Solaris10 NBU 5.1 MP6.
Client has two network interfaces client-pub & client-bk.
I want all backup traffic to go via the client-bk interface, but unless
I add a network route for the backup server subnet over the client's
backup interface, backups fail with a 41. I was under the impression
that REQUIRED_INTERFACE was all I should need.
e.g. with bp.conf "CLIENT_NAME = client-bk" and "REQUIRED_INTERFACE =
client-bk", but with no specific network route, client-initiated
backup/restore requests appear to go OK. When I snoop the various
network interfaces during a server-initiated backup attempt, I see the
media server talking to client-bk (and getting no response), client-bk
sees incoming requests from media server, client (interface) sees
outgoing requests from client-bk to the media server... so responses are
going back over the wrong interface (and never getting there due to
firewalls).
Add the route "route add net media-server-subnet.0 subnet-defaultrouter"
and backups work fine.
So I guess REQUIRED_INTERFACE only works for traffic initiated from the
client, and the OS handles routing of reply information?
Phil Weber
Business Technology (Egg)
Storage Technical Services - Senior UNIX Technologist
Phone: 01384 26 4136
Mobile: 07748 333503
-----------------------------------------
Egg is a trading name of the Egg group of companies which includes:
Egg plc (reg no 2448340), Egg Financial Intermediation Ltd (reg no
3828289), and Egg Banking plc (reg no 2999842). Egg Banking plc and
Egg Financial Intermediation Ltd are authorised and regulated by
the Financial Services Authority (FSA) and are entered in the FSA
register under numbers 205621 and 309551 respectively. These
members of the Egg group are registered in England and Wales.
Registered office: Citigroup Centre, Canada Square, London E14 5LB.
This e-mail is confidential and for use by the addressee only. If
you are not the intended recipient of this e-mail and have received
it in error, please return the message to the sender by replying to
it and then delete it from your mailbox. Internet e-mails are not
necessarily secure. The Egg group of companies do not accept
responsibility for changes made to this message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission
of viruses, it is the responsibility of the recipient to ensure
that the onward transmission, opening or use of this message and
any attachments will not adversely affect its systems or data. No
responsibility is accepted by the Egg group of companies in this
regard and the recipient should carry out such virus and other
checks as it considers appropriate.
This communication does not create or modify any contract.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This mail has originated outside your organization, either from an external
partner or the Global Internet.
Keep this in mind if you answer this message.
This e-mail is intended only for the above addressee. It may contain privileged
information.
If you are not the addressee you must not copy, distribute, disclose or use any
of the information in it.
If you have received it in error please delete it and immediately notify the
sender.
Security Notice: all e-mail, sent to or from this address, may be accessed by
someone other than the recipient, for system management and security reasons.
This access is controlled under Regulation of security reasons.
This access is controlled under Regulation of Investigatory Powers Act 2000,
Lawful Business Practises.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
