[Veritas-bu] Listing files in a backup image or media ID
Hello all, I'm trying to find a way to list all the files and directories backed up on a specific backup_id and/or on a specific media. I haven't found any of the nice utilities in the netbackup directory that will do just that. HP-UX master server and netbackup 5.1 MP4. Wessam Aly Senior UNIX Storage Systems Admin. HPUX-CSA Certified Systems Administrator *** IMPORTANT Confidentiality: This e-mail communication and any attachments thereto contain information which is confidential and are intended only for the use of the individuals or entities named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking any action in reliance on the contents of these documents is strictly prohibited and may be illegal. Please notify us of your receipt of this e-mail in error and delete the e-mail and any copies of it. Monitoring/Viruses: Mobinil may monitor all incoming outgoing e-mails in line with current legislation. Although we have taken steps to ensure that this e-mail and attachments are free from any Virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. The Egyptian Company for Mobile Services (Mobinil) www.mobinil.com *** ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] 6.0 backing up a 5.x client on another domain
Here is the setup. I have a master server in my domain running 6.0mp4. Management wants me to backup up a client on another domain. In the other domain the maser and clients are on 5.x. In the 5.x world I can stop the backups over there but they want the master server to stay in place for 90 days. When I try and connect to the 5.x client of the 6.0 I get a 59 error. I have added my 6.0 server names in the additional servers that can access the client. Any thoughts Justin ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Listing files in a backup image or media ID
Getting list of files in a given backup set use the bplist command: Example: To see all files in the policy ATUBKS-1-ERPDB-DMXBCV that were backed up on 12/04/2006: bplist -k ATUBKS01-ERPDB-DMXBCV -s 12/04/2006 01:00:00 -e 12/05/2006 02:00:00 -R / The -k is policy, -s starttime, -e endtime, -R is recursive and / insures it will show all files from root down that are in backup. If you wanted a specific directory you put it there in place of the /. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wessam Aly Sent: Wednesday, December 27, 2006 4:37 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Listing files in a backup image or media ID Hello all, I'm trying to find a way to list all the files and directories backed up on a specific backup_id and/or on a specific media. I haven't found any of the nice utilities in the netbackup directory that will do just that. HP-UX master server and netbackup 5.1 MP4. Wessam Aly Senior UNIX Storage Systems Admin. HPUX-CSA Certified Systems Administrator *** IMPORTANT Confidentiality: This e-mail communication and any attachments thereto contain information which is confidential and are intended only for the use of the individuals or entities named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking any action in reliance on the contents of these documents is strictly prohibited and may be illegal. Please notify us of your receipt of this e-mail in error and delete the e-mail and any copies of it. Monitoring/Viruses: Mobinil may monitor all incoming outgoing e-mails in line with current legislation. Although we have taken steps to ensure that this e-mail and attachments are free from any Virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. The Egyptian Company for Mobile Services (Mobinil) www.mobinil.com *** ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Listing files in a backup image or media ID
I'm trying to find the files/directories which reside on a specific tape or by a specific backup id. that is because I found out that one of my tapes is missing and I need to replace it, so I need to know what files were on that tape so I can try to replace them. Wessam Aly Senior UNIX Storage Systems Admin. HPUX-CSA Certified Systems Administrator From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, 27 December, 2006 16:08 To: Wessam Aly Subject: Re: [Veritas-bu] Listing files in a backup image or media ID If you have Aptare Storage Console software, it will give you that information, if not I am not sure. One way is to start a restore and look at the files you have to restore from? = Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] Hello all, I'm trying to find a way to list all the files and directories backed up on a specific backup_id and/or on a specific media. I haven't found any of the nice utilities in the netbackup directory that will do just that. HP-UX master server and netbackup 5.1 MP4. Wessam Aly Senior UNIX Storage Systems Admin. HPUX-CSA Certified Systems Administrator *** IMPORTANT Confidentiality: This e-mail communication and any attachments thereto contain information which is confidential and are intended only for the use of the individuals or entities named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking any action in reliance on the contents of these documents is strictly prohibited and may be illegal. Please notify us of your receipt of this e-mail in error and delete the e-mail and any copies of it. Monitoring/Viruses: Mobinil may monitor all incoming outgoing e-mails in line with current legislation. Although we have taken steps to ensure that this e-mail and attachments are free from any Virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. The Egyptian Company for Mobile Services (Mobinil) www.mobinil.com *** ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] 6.0 backing up a 5.x client on another domain
One might assume by adding you also changed the 5.x client's master server to the 6.0 master as well? What does install_pathveritas/openv/netbackup/bin/bpclntcmd -pn return? Justin Curry [EMAIL PROTECTED] 12/27/2006 6:57 AM Here is the setup. I have a master server in my domain running 6.0mp4. Management wants me to backup up a client on another domain. In the other domain the maser and clients are on 5.x. In the 5.x world I can stop the backups over there but they want the master server to stay in place for 90 days. When I try and connect to the 5.x client of the 6.0 I get a 59 error. I have added my 6.0 server names in the additional servers that can access the client. Any thoughts Justin ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] 6.0 backing up a 5.x client on another domain
Can the clients that are getting the 59's resolve the 6.0 master in DNS? You may have to put the fully qualified domain name in the server/media list on the 5.1 clients. Bobby. From: Justin Curry [EMAIL PROTECTED] Date: 2006/12/27 Wed AM 08:57:06 EST To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] 6.0 backing up a 5.x client on another domain Here is the setup. I have a master server in my domain running 6.0mp4. Management wants me to backup up a client on another domain. In the other domain the maser and clients are on 5.x. In the 5.x world I can stop the backups over there but they want the master server to stay in place for 90 days. When I try and connect to the 5.x client of the 6.0 I get a 59 error. I have added my 6.0 server names in the additional servers that can access the client. Any thoughts Justin Bobby Williams 2205 Peterson Drive Chattanooga, TN 37421 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] 9940 tape drives and SUN SOlaris 8
We have had situations recently where the 9940B STK tape devices have disappeared from our Solaris 8 media servers. We have had to reboot to get them seen again. Anyone on the list seen this before. We are at Netbackup Enterprise Server V5.1 MP5 ... Steven R. Hudson Systems Consultant Iron Mountain 745 Atlantic Ave. Boston, MA. Work: 617-535-2849 Mobile: 617-719-5465 [EMAIL PROTECTED] - The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] STK8500 Issues [SOLVED]
Don't want to beat this to death, but IMO, less-experienced NetBackup admins and the archives will benefit from finding that a) this long-running, apparently complicated problem is really NetBackup config 101 and b) there is no behind-the-scenes, undocumented magic that should send a user off on a fit of bpexpdating. On Tue, 26 Dec 2006, bob944 wrote: [...] [summary: the normal misconfiguration: drive paths and robot drive numbers were not matched correctly] ** IMPORTANT NOTE: Something I figured out myself and then VERITAS confirmed it. If you have INCORRECT addressing and you do backups to tapes, when the tapes are used again, they will try to go the drive that originally wrote them-- I don't remember ever observing that, ACSLS or not; NetBackup uses any drive available in a STU of the right density and media server. Surely you're not confusing media-server ownership of assigned media, are you? Again, the problem only happened when all drives were in use (in the robot). I don't believe that's correct. The problem--your configuration mapped NetBackup drive indices via device names to incorrect acs/lsm/panel/drive settings--was always there. The _symptom_ you saw--hangs and waiting mounts--typically shows up when you throw enough work at it (your 45 jobs and _multiple media servers_) that MediaServerB can't use the drive it thinks it has because MediaServerA, through misconfiguration, has stuck a tape in it. This or a variation is what you kept seeing as 32 active jobs. However 1/2 or 3 (random) jobs will hang saying 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape it is requesting sometimes is and is not in the drive that it is supposed to be in, confusing... and the reason why experienced ACSLS users' advice has been to verify the end-to-end configuration and prove it one drive at a time. Classic misconfiguration; we've all done it. EVEN after you fix the addressing issue! They MUST be EXPIRED first with bpexpdate -d 0 -m MEDIA_ID so they lose that information. If at any point you have an addressing problem and write to tapes, BE SURE that you EXPIRE ALL TAPES written to during that testing phase before you do more testing-- after you ensure the address/scsi/acsls mapping is correct of course. Can you cite documentation for this? Unfortunately not; the Veritas engineer confirmed my finding verbally. That _is_ unfortunate. I believe you have misinterpreted the situation: there is no tie between a tape and a physical drive, only the normal pre-6.0 ownership of media by its media server as long as the media server has images on it. Please advise if you do come up with docs--perhaps a clarifying statement from your Veritas contact--so I and the rest of the list can learn from it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] STK8500 Issues [SOLVED]
RE: bpexpdate, see below bob944 [EMAIL PROTECTED] 12/27/2006 12:22 PM Don't want to beat this to death, but IMO, less-experienced NetBackup admins and the archives will benefit from finding that a) this long-running, apparently complicated problem is really NetBackup config 101 and b) there is no behind-the-scenes, undocumented magic that should send a user off on a fit of bpexpdating. On Tue, 26 Dec 2006, bob944 wrote: [...] [summary: the normal misconfiguration: drive paths and robot drive numbers were not matched correctly] ** IMPORTANT NOTE: Something I figured out myself and then VERITAS confirmed it. If you have INCORRECT addressing and you do backups to tapes, when the tapes are used again, they will try to go the drive that originally wrote them-- I don't remember ever observing that, ACSLS or not; NetBackup uses any drive available in a STU of the right density and media server. Surely you're not confusing media-server ownership of assigned media, are you? Again, the problem only happened when all drives were in use (in the robot). I don't believe that's correct. The problem--your configuration mapped NetBackup drive indices via device names to incorrect acs/lsm/panel/drive settings--was always there. The _symptom_ you saw--hangs and waiting mounts--typically shows up when you throw enough work at it (your 45 jobs and _multiple media servers_) that MediaServerB can't use the drive it thinks it has because MediaServerA, through misconfiguration, has stuck a tape in it. This or a variation is what you kept seeing as 32 active jobs. However 1/2 or 3 (random) jobs will hang saying 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape it is requesting sometimes is and is not in the drive that it is supposed to be in, confusing... and the reason why experienced ACSLS users' advice has been to verify the end-to-end configuration and prove it one drive at a time. Classic misconfiguration; we've all done it. EVEN after you fix the addressing issue! They MUST be EXPIRED first with bpexpdate -d 0 -m MEDIA_ID so they lose that information. If at any point you have an addressing problem and write to tapes, BE SURE that you EXPIRE ALL TAPES written to during that testing phase before you do more testing-- after you ensure the address/scsi/acsls mapping is correct of course. Can you cite documentation for this? Unfortunately not; the Veritas engineer confirmed my finding verbally. That _is_ unfortunate. I believe you have misinterpreted the situation: there is no tie between a tape and a physical drive, only the normal pre-6.0 ownership of media by its media server as long as the media server has images on it. Please advise if you do come up with docs--perhaps a clarifying statement from your Veritas contact--so I and the rest of the list can learn from it. Actually this is true and it is tied to the drive index number and has nothing to do with ACSLS. If the drives are incorrectly addressed, then backups are run, and then the drives are correctly addressed, those tapes previous written to will upon a next mount request will be mounted into the incorrect drive and result in an error. I too have done this (more times than I care to think about) and when working with Veritas support received the same resolution (going back to 3.1) about using bpexpdate. I don't recall if there was any documentation about this at the time but I'm thinking that information may be stored in the non-dot-f file or in one of the DB's on the media server (/volmgr/database). ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RMAN Not Using New Server
Ok - so I've got the new Netbackup environment running and its backing up Windows Standard jobs just fine. So I migrate my first Oracle Database. Here's where it gets interesting... The job fires on the new backup server (PBCOBK01) but only gets to connecting in the activity monitor. Looking at the logs on the local machine I find... from bphdb log... 15:50:29.763 [3740.3800] 4 bphdb do_script: INF - bphdb still working. 15:51:29.764 [3740.3800] 4 bphdb do_script: INF - bphdb still working. 15:52:29.766 [3740.3800] 4 bphdb do_script: INF - bphdb still working. 15:52:29.829 [3740.3800] 16 writeToSock: ERR - send() to server failed: An existing connection was forcibly closed by the remote host. 15:52:29.829 [3740.3800] 16 bphdb do_script: ERR - could not write keepalive to the NAME socket 15:52:29.860 [3740.3800] 4 bphdb main: file C:\Program Files\VERITAS\NetBackup\temp\obackup_class deleted. 15:52:29.860 [3740.3800] 16 bphdb main: ERR - Error code: 24 15:52:29.876 [3740.3800] 16 bphdb Exit: ERR - bphdb exit status = 24: socket write failed 15:52:29.876 [3740.3800] 4 bphdb Exit: INF - EXIT STATUS 24: socket write failed from bpcd log... 15:42:19.091 [3216.4008] 16 bpcd main: Server access denied 15:42:19.122 [3280.3580] 2 bpcd main: offset to GMT 18000 15:42:19.122 [3280.3580] 2 bpcd main: Got socket for input 452 15:42:19.137 [3280.3580] 2 logconnections: BPCD ACCEPT FROM 132.158.203.21.684 TO 132.158.203.126.13782 15:42:19.137 [3280.3580] 2 bpcd main: setup_sockopts complete 15:42:19.169 [3280.3580] 2 ParseConfigExA: Unknown configuration option on line 76: RenameIfExists = 0 15:42:19.169 [3280.3580] 2 bpcd peer_hostname: Connection from host semibkup1 (132.158.203.21) port 684 15:42:19.169 [3280.3580] 2 ParseConfigExA: Unknown configuration option on line 76: RenameIfExists = 0 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk01 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk02 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk03 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk01 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk02 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk03 and semibkup1 15:42:19.169 [3280.3580] 16 bpcd valid_server: semibkup1 is not a server 15:42:19.169 [3280.3580] 16 bpcd valid_server: semibkup1 is not a media server 15:42:19.309 [3280.3580] 2 bpcd main: output socket port number = 531 15:42:19.309 [3280.3580] 2 bpcd peer_hostname: Connection from host semibkup1 (132.158.203.21) port 684 15:42:19.309 [3280.3580] 2 bpcd main: Peer hostname is semibkup1 15:42:19.309 [3280.3580] 2 bpcd main: Got socket for output 716, lport = 802 15:42:19.309 [3280.3580] 2 bpcd main: Connected on output socket 15:42:19.309 [3280.3580] 2 bpcd main: Duplicated socket on stderr 15:42:19.309 [3280.3580] 2 bpcd main: NetBackup 5.1 0 initiated 15:42:19.309 [3280.3580] 2 bpcd exit_bpcd: exit status 46 ---exiting 15:42:19.309 [3280.3580] 4 bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46 semibkup1 is the name of my old backup server!? Why is it looking there? I removed the old server entries from the client, restarted the service, even reinstalled the client but it continues to look for semibkup1 when starting the RMAN child jobs. So the parent job starts on pbcobk01 (new master) and the child job ends up on semibkup1 and the job eventually fails. GREAT! Windows NT Backups of this same server run fine. Any ideas? Symantec support will get back to me in the next 8 hours... /sigh Thanks, -Jonathan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Renaming Media
If I have a scratch media with the id A00200 I want to re-label it to AT0221, what process would I need to follow? Please be as descriptive as possible, thanks in advance. Daniel Jimenez Backup and Recover Team ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Solaris client software
Possibilities: 1) Take a look at whether you can use the /usr/openv/netbackup/bin/install_client_files script to rsh or ftp the files to the clients. 1a) Hack the install_client_files script to use scp and sftp if you need to bypass a firewall or don't allow unsecured protocols like rsh/rcp. 2) If you can't go to them directly, run install_client_files and ftp the files to a server close to your Master (can't be a Master or Media though). Then make a tarball up of the /tmp/bp directory and copy THAT over to your client. 3) Last choice: copy over one at a time the 125-ish files that make up the NetBackup client for Solaris 8, making sure you put them all into the right place with the right permissions. And add the /etc/services entries needed. I really recommend options 1 or 2 though, if for no other reason than they'll build clients that are patched to whatever level your Master is. If you absolutely have to do option 3 for some other reason, shoot me a note offline and I'll get you something that might help. - John Nardello From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WALLEBROEK Bart Sent: Tuesday, December 26, 2006 4:11 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Solaris client software What part of the Veritas NetBackup 5.1 for Solaris install CD is needed to install the client software on a Solaris server. In other words: Instead on inserting the Installation CD in the client (which is sometimes not possible -- geographically speaking) what files are needed (minimum) to be able to install the client software on a Solaris server (so I can copy those files over and install it) ? Best Regards, Bart WALLEBROEK Systems Applications Management Support Specialist Customer Operations - SDC Deployment Tel: + 32 2 655 30 75Mob: + 32 478 31 61 77Fax: +32 2 655 41 85 S.W.I.F.T. SCRL ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN Not Using New Server
verify if the new server is defined in your RMAN script Cheers Sami Martin, Jonathan \(Contractor\) [EMAIL PROTECTED] To l.comveritas-bu@mailman.eng.auburn.edu Sent by: cc veritas-bu-bounce [EMAIL PROTECTED] Subject urn.edu [Veritas-bu] RMAN Not Using New Server 28/12/2006 08:13 AM Ok - so I've got the new Netbackup environment running and its backing up Windows Standard jobs just fine. So I migrate my first Oracle Database. Here's where it gets interesting... The job fires on the new backup server (PBCOBK01) but only gets to connecting in the activity monitor. Looking at the logs on the local machine I find... from bphdb log... 15:50:29.763 [3740.3800] 4 bphdb do_script: INF - bphdb still working. 15:51:29.764 [3740.3800] 4 bphdb do_script: INF - bphdb still working. 15:52:29.766 [3740.3800] 4 bphdb do_script: INF - bphdb still working. 15:52:29.829 [3740.3800] 16 writeToSock: ERR - send() to server failed: An existing connection was forcibly closed by the remote host. 15:52:29.829 [3740.3800] 16 bphdb do_script: ERR - could not write keepalive to the NAME socket 15:52:29.860 [3740.3800] 4 bphdb main: file C:\Program Files\VERITAS\NetBackup\temp\obackup_class deleted. 15:52:29.860 [3740.3800] 16 bphdb main: ERR - Error code: 24 15:52:29.876 [3740.3800] 16 bphdb Exit: ERR - bphdb exit status = 24: socket write failed 15:52:29.876 [3740.3800] 4 bphdb Exit: INF - EXIT STATUS 24: socket write failed from bpcd log... 15:42:19.091 [3216.4008] 16 bpcd main: Server access denied 15:42:19.122 [3280.3580] 2 bpcd main: offset to GMT 18000 15:42:19.122 [3280.3580] 2 bpcd main: Got socket for input 452 15:42:19.137 [3280.3580] 2 logconnections: BPCD ACCEPT FROM 132.158.203.21.684 TO 132.158.203.126.13782 15:42:19.137 [3280.3580] 2 bpcd main: setup_sockopts complete 15:42:19.169 [3280.3580] 2 ParseConfigExA: Unknown configuration option on line 76: RenameIfExists = 0 15:42:19.169 [3280.3580] 2 bpcd peer_hostname: Connection from host semibkup1 (132.158.203.21) port 684 15:42:19.169 [3280.3580] 2 ParseConfigExA: Unknown configuration option on line 76: RenameIfExists = 0 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk01 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk02 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk03 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk01 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk02 and semibkup1 15:42:19.169 [3280.3580] 2 bpcd valid_server: comparing pbcobk03 and semibkup1 15:42:19.169 [3280.3580] 16 bpcd valid_server: semibkup1 is not a server 15:42:19.169 [3280.3580] 16 bpcd valid_server: semibkup1 is not a media server 15:42:19.309 [3280.3580] 2 bpcd main: output socket port number = 531 15:42:19.309 [3280.3580] 2 bpcd peer_hostname: Connection from host semibkup1 (132.158.203.21) port 684 15:42:19.309 [3280.3580] 2 bpcd main: Peer hostname is semibkup1 15:42:19.309 [3280.3580] 2 bpcd main: Got socket for output 716, lport = 802 15:42:19.309 [3280.3580] 2 bpcd main: Connected on output socket 15:42:19.309 [3280.3580] 2 bpcd main: Duplicated socket on stderr 15:42:19.309 [3280.3580] 2 bpcd main: NetBackup 5.1 0 initiated 15:42:19.309 [3280.3580] 2 bpcd exit_bpcd: exit status 46 ---exiting 15:42:19.309 [3280.3580] 4 bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46 semibkup1 is the name of my old backup server!? Why is it looking there? I removed the old server entries from the client, restarted the service, even reinstalled the client but it continues to look for semibkup1 when starting the RMAN child jobs. So the parent job starts on pbcobk01 (new master) and the child job ends up on semibkup1 and the job eventually fails. GREAT! Windows NT Backups of this same server run fine. Any ideas? Symantec support will get back to me in the next 8 hours... /sigh Thanks, -Jonathan___ Veritas-bu
