Paul, Please clarify what you mean by "the application" I assume Netbackup. Good question. Hadn't thought of that. You may have to make Netbackup think of it as a completely separate media server, and device host all the way through. That way the it knows what path (NIC) to take when running a backup. I need to think about this some more.
What version of Netbackup are you using? ============================= Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] "Esson, Paul" <[EMAIL PROTECTED]> 03/04/2008 04:12 AM To <[EMAIL PROTECTED]> cc <veritas-bu@mailman.eng.auburn.edu>, <[EMAIL PROTECTED]> Subject RE: [Veritas-bu] Media Server with multiple NICS Carl, I had thought along similar lines but will the application not expect to see a device host in the netbackup configuration with the same name as is referenced in the Media Server setting of the storage unit? Regards, Paul Esson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 03 March 2008 13:35 To: Esson, Paul Cc: Esson, Paul; veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] Media Server with multiple NICS Greetings Paul, OK, I guess I mis-interpreted your question, apoligies. My initial thoughts are that you could set up a different DNS name for each interface on the media server. Then create a different storage unit that refers to each Media server name, and have that storage unit refer to the interface associated with the name. Then modify the backup policy to use the policy storage unit that refers to the interface you want to use. Just a thought.. In our environment we have multiple media servers and we direct backups to what ever media server we want for a particular policy. My guess, ( and it is only a guess) is that you could do a similar thing using one media server with multiple NIC's. I guess you could open a case with Symantec. Other people may have actual experince with this. Regasrd ============================= Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] "Esson, Paul" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 03/01/2008 07:02 AM To "Esson, Paul" <[EMAIL PROTECTED]>, <veritas-bu@mailman.eng.auburn.edu> cc Subject Re: [Veritas-bu] Media Server with multiple NICS Folks, My clients won't have multiple NICS only the Media Server because its receiving input from multiple subnets so the use of REQUIRED_INTERFACE on the client won't help. I basically want to send certain clients to certain interfaces/addresses on the Media Server. Doesn't the Master tell the client where to send it's backup data via the policy information i.e. storage unit/device host? In a normal backup scenario nbjm starts the backup using bpcd to start bpbrm on the Media Server. The bpbrm process in turn starts bptm which then uses bpcd to start bpbkar on the client. Its the interaction between bpbkar on the client and bptm on the Media Server that I am trying to control but in my case the Media Server is a different host from the Master. Regards, Paul Esson ________________________________ From: Esson, Paul Sent: Fri 29/02/2008 18:33 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Media Server with multiple NICS Folks, Is anyone out there using Media Servers with multiple NICs on separate networks? I am trying to understand how to force clients to use specific interfaces on the Media Server when sending backup data or receiving restore data. Do I need to create multiple storage unit and Media Server entries to be able to target the clients through the policy? Or am I on the wrong track altogether? NBU 6.5 Solaris 10 Master and Media Servers - Media Servers have 4 NICs and clients are on multiple subnets. Regards, Paul Esson _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications.
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
