[Veritas-bu] BMR Backups vs BMR Restore Clients

Humm.  What's odd is that the servers that are registered are on the
perimeter/dmz.  It's the ones on the inside, where the NBU master/BMR Master
lives.

I did find this in the unified logs from one of the linux hosts in question:

04/18/2007 23:00:57.524 [main.cpp:bmrmain()] Entering, line=604, command
line: bmrsavecfg -c server1.longwood.edu -p Linux_BMR -s Linux_BMR_diff -t
INCR -g 82616
04/18/2007 23:00:57.524 [main.cpp.cpp:savecfgProcessOptions()] Entering,
line=132
04/18/2007 23:00:57.525 [main.cpp.cpp:savecfgProcessOptions()] Exiting,
line=527, return BMR_SUCCESS
04/18/2007 23:00:57.525 [CBmrSaveCfg::discover()] Entering
CBmrSaveCfg::discover in CBmrSaveCfg.cpp at 239.
04/18/2007 23:00:57.525 [CBmrSaveCfg::CreateDataDirectory()] Entering,
line=193, dirName=/usr/openv/netbackup/baremetal/client/data/
04/18/2007 23:00:57.551 [CBmrSaveCfg::CreateDataDirectory()] Exiting,
line=226, rc=0
04/18/2007 23:00:57.551 [CBmrSaveCfg.cpp:setEsm()] Entering
CBmrSaveCfg::setEsm in CBmrSaveCfg.cpp at 118.
04/18/2007 23:00:57.556 [CBmrSaveCfg.cpp:setEsm()] calling timeout with a
bp.conf value of 0
04/18/2007 23:00:57.556 [BmrTimeoutCommon.cpp:BmrSavecfgTimeout()] Entering,
line=47 timeout (sec) = 0
04/18/2007 23:00:57.556 [BmrTimeoutCommon.cpp:BmrSavecfgTimeout()] Exiting.
alarm (re)set.
04/18/2007 23:00:57.557 [CBmrSaveCfg.cpp:setEsm()] Leaving
CBmrSaveCfg::setEsm rc = 0.
04/18/2007 23:02:33.716 [CBmrSaveCfg::saveDiscovery()] Entering
04/18/2007 23:02:33.767 [CBmrSaveCfg.cpp:readFileIntoTarBuffer()] Exiting,
rc=0
04/18/2007 23:02:33.767 [CBmrSaveCfg::writeBundle()] Entering.
04/18/2007 23:02:33.790 [CBmrSaveCfg::writeBundle()] Exiting,  rc=0
04/18/2007 23:02:33.790 [CBmrSaveCfg::saveDiscovery()] Exiting,  rc=0
04/18/2007 23:02:35.774 [CBmrSaveCfg.cpp:sendDiscovery()] BMROP_IMPORT
failed, rc=1
04/18/2007 23:02:35.774 [CBmrSaveCfg.cpp:LocalBmrOps()] Entering, line=535,
msgId= 27
04/18/2007 23:02:35.774 [Error] V-121-27 Failed to import Config file.
04/18/2007 23:02:35.805 [CBmrSaveCfg.cpp:LocalBmrOps()] Exiting, line=555

The last three lines are what caught my eye.  

> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu 
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf 
> Of Spearman, David
> Sent: Thursday, April 19, 2007 9:58 AM
> To: Brooks, Jason; veritas-bu at mailman.eng.auburn.edu
> Subject: Re: [Veritas-bu] BMR Backups vs BMR Restore Clients
> 
> Jason,
> 
> For what it's worth. We have two circumstances where RH3 and 
> BMR (nbu6mp4)have problems. One is servers inside a DMZ, the 
> other is with servers that have two nics running. The odd 
> thing about the dual nic servers is that if you run the 
> discovery option a BMR restore will work even though the 
> client is not in the bmr list. As far as the dmz goes we have 
> had any number of problems with that and I will not point any fingers.
> 
> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf 
> Of Brooks, Jason
> Sent: Thursday, April 19, 2007 9:50 AM
> To: veritas-bu at mailman.eng.auburn.edu
> Subject: [Veritas-bu] BMR Backups vs BMR Restore Clients
> 
> 
> Folks,
>       I've been monitoring BMR policies/hosts more closely 
> lately.  We are running 6.0MP4 and I'm having issues with a 
> few Linux BMR hosts.
> Here's the info from the Activity Monitor:
> 
> 4/18/2007 11:00:05 PM - begin Parent Job
> 4/18/2007 11:00:05 PM - begin Stream Discovery , Stream 
> Discovery Status 0 4/18/2007 11:00:16 PM - end Stream 
> Discovery , Stream Discovery; elapsed
> time: 00:00:11
> 4/18/2007 11:00:16 PM - begin Stream Discovery , BMR Save 4/18/2007
> 11:00:34 PM - started process bpbrm (2852) 4/18/2007 11:00:47 
> PM - collecting BMR information 4/18/2007 11:00:51 PM - 
> connecting 4/18/2007
> 11:00:57 PM - connected; connect time: 00:00:06 4/18/2007 
> 11:00:57 PM - transferring BMR infomation to the master 
> server 4/18/2007 11:00:57 PM - connecting 4/18/2007 11:00:57 
> PM - connected; connect time: 00:00:00
> 4/18/2007 11:02:35 PM - BMR information transfer successful 4/18/2007
> 11:02:35 PM - end writing Status 0 4/18/2007 11:02:37 PM - 
> end Stream Discovery , BMR Save; elapsed time: 00:02:21 
> 4/18/2007 11:02:37 PM - begin Stream Discovery , Policy 
> Execution Manager Preprocessed Status 0
> 4/19/2007 3:25:02 AM - end Stream Discovery , Policy 
> Execution Manager Preprocessed; elapsed time: 04:22:25 
> 4/19/2007 3:25:02 AM - begin Stream Discovery , Validate 
> Image Status 0 4/19/2007 3:25:07 AM - end Stream Discovery , 
> Validate Image; elapsed time: 00:00:05 Status 0 4/19/2007
> 3:25:07 AM - end Parent Job; elapsed time: 04:25:02 the 
> requested operation was successfully completed(0)
> 
> This host doesn't show up as a protected BMR host, despite an 
> errorless BMR save.  The server is a RHEL 3 box and should be 
> all happy as it's at 6.0MP4. Version output: cat version
> 
> NetBackup-RedHat2.4 6.0MP4
> 
> I do have other RHEL 3 boxes that register consistently as 
> BMR hosts, but this one and one other will not.
> 
> Ideas?  Anyone else seen this behavior before?
> 
> Jason
> 
> ------------
> Jason Brooks
> Computer Systems Engineer
> IITS - Longwood University
> voice - (434) 395-2034
> fax - (434) 395-2035
> mailto:<brooksje at longwood.edu> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3332 bytes
Desc: not available
Url : 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070419/40c80a92/smime.bin