How about talking to your network guys and bonding the two interfaces to the same IP? There's been plenty of talk about it on these forums before. It would bond the nics below the IP level so they can both share and load balance the same IP's traffic. From a cisco perspective you're talking about etherchannel, in windows its called teaming. I've got several solaris boxes here, but none configured this way. Perhaps one of our resident Solaris gurus could chime in? The only other way I can come up with to do this is how we run our backend dr network here. Give the 2nd interface another hostname, and configure a policy to use it. When the first interface fails, manually run the policy with the 2nd hostname. Alternately, fix the nic issue? -Jonathan
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Sigrist Sent: Monday, July 23, 2007 8:24 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Help please Hello my dear gurus. I tried REQUIRED_INTERFACE, as someone suggested, but didn't work because, when my first interface fail (the required one) and the second one (192.168.2.153) comes up, I'm still unable to do backup. The workaround is to manually edit /etc/hosts of the server, change the ip address of the desired machine to 192.168.2.153 and run the manual backup. Any other thoughts ? Thank you again. Solaris 10 Netbackup 4.5_FP6 Today I was looking at the "Activity Monitor" and saw that one of my scheduled backups didn't run. I tried to run manually and received the same error: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 07/20/2007 09:27:48 ORA-19506: failed to create sequential file, name="crin9ski_1_1", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: Failed to open for backup. So I searched for some light in the bprd logs and found: 09:35:13.368 [1326] <2> logconnections: BPRD ACCEPT FROM 192.168.200.153.47732 TO 192.168.2.86.13720 09:35:13.386 [1326] <16> connected_peer: gethostbyaddr() for 192.168.200.153 failed, HOST_NOT_FOUND (1) 09:35:13.404 [1326] <32> bprd: cannot determine connection host name 09:35:13.409 [10131] <2> listen_loop: select() interrupted 09:37:51.725 [10131] <2> bprd: socket fd from accept() is 7 That's why the backup failed, the master server don't know this ip, because the /etc/hosts show that the machine I'm backing up has the IP address 192.168.200.150. My problem is that I have 2 NIC's on this machine for redundancy. One has the IP 150 and the other has the ip 153. When the first one fail, the second one answer for the machine. What can I do to netbackup recognize both IP as the same machine? Thank you so much. __________________________ Daniel Abramides Sigrist DBA Oracle Projeto SIGRES Tel: (11) 3824-2074 Telefonica Pesquisa e Desenvolvimento Rua Brigadeiro Galvao, 291 - 7ยบ Andar Barra Funda - Sao Paulo, SP [EMAIL PROTECTED]
<<image003.jpg>>
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
