Backup Session fails for only one filesystem with BMA timeout (313 Views)
Reply
Frequent Visitor
Sandeep_Pawar
Posts: 2
Registered: ‎11-20-2013
Message 1 of 3 (313 Views)

Backup Session fails for only one filesystem with BMA timeout

We have a problem with HP data Protector 8.0. The backup session fails for one of the filesystem from the backup session. There are 8 filesystems in the backup specification out of which only one particular filesystem is failing with BMA timeout error. The all 8 filesystem are 8 different LUNs from the HP EVA 6500 storage box. The backup client is HP OpenVMS and Cell Manager is Windows 2008 R2.

 

We discovered this few weeks back and at that time SmDaIdleTimeout = 120 min and SmMaIdleTimeout = 140 min i.e default. Then we incresed the timeout values to SmDaIdleTimeout = 150 min and SmMaIdleTimeout = 170 min and it solved the problem.

 

But recently this week end we again observed same issue with the new timeout values for the same filesystem. 

 

The backup session is incremental backup and the size of data is 3-4 GB max. Though the size of the data being backed up is very less it takes about 4-5 hours to back up.

Duration: 4:16
GB Written: 0.04

 

The other filesystems are getting backedup properly regardless of the data size.

 

please can some one help me to find a root cause and resolution for this issue.

 

--------------------------------------------------------------------------------------

[Warning] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 5/20/2014 6:00:19 PM
[61:2013] Some of the backup devices are occupied. Session is waiting
for all the devices to get free.

[Major] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 5/20/2014 8:23:33 PM
[61:1002] The VBDA named "/$1$DGA415" on host anuap1
reached its inactivity timeout of 7200 seconds.
The agent on host will be shutdown.

--------------------------------------------------------------------------------------

[Warning] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 6/7/2014 6:00:22 PM
[61:2013] Some of the backup devices are occupied. Session is waiting
for all the devices to get free.

[Major] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 6/7/2014 9:11:20 PM
[61:1002] The BMA named "HP:Ultrium 5-SCSI_9" on host anuap1
reached its inactivity timeout of 10200 seconds.
The agent on host will be shutdown.

[Major] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 6/7/2014 9:11:36 PM
[61:3003] Lost connection to VBDA named "/$1$DGA415"
on host anuap1.
Ipc subsystem reports: "Bad message format."

--------------------------------------------------------------------------------------

[Warning] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 6/6/2014 6:00:21 PM
[61:2013] Some of the backup devices are occupied. Session is waiting
for all the devices to get free.

[Major] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 6/6/2014 9:11:08 PM
[61:1002] The BMA named "HP:Ultrium 5-SCSI_4" on host anuap1
reached its inactivity timeout of 10200 seconds.
The agent on host will be shutdown.

[Major] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 6/6/2014 9:11:19 PM
[61:3003] Lost connection to VBDA named "/$1$DGA415"
on host anuap1.
Ipc subsystem reports: "Bad message format."

--------------------------------------------------------------------------------------

 

 

Thanks,

 

Sandeep

 

 

 

 

HP Expert
Bob_Clark
Posts: 1,499
Registered: ‎08-14-2013
Message 2 of 3 (284 Views)

Re: Backup Session fails for only one filesystem with BMA timeout

Frankly, I am surprised that increasing SmDaIdleTimeout and SmMaIdleTimeout worked for this problem, even for a short while.  Usually all that will do is to increase the amount of time before the timeout

 

Were these consecutive messages:

 

[Warning] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 5/20/2014 6:00:19 PM
[61:2013] Some of the backup devices are occupied. Session is waiting
for all the devices to get free.

[Major] From: BSM@liberate-dp "ANUAP1_FileSystem_Backups" Time: 5/20/2014 8:23:33 PM
[61:1002] The VBDA named "/$1$DGA415" on host anuap1
reached its inactivity timeout of 7200 seconds.
The agent on host will be shutdown.

 

If so, you are trying to use a device that is currently occupied, and DP will wait around forever, or, until the timeout expires

 

I would first check to see if you have any sessions currently in a Mount Request state.  If you do, see if there are also sessins Queueing.  If you have sessions Queueing, start aborting them, newest ones first, until you get ot the Mount REquest session, then delete that

 

if you don't have Mount Requests, check your Monitor to see if you have sessions In Progress.  Try to abort these, starting with the newest.  They  may not abort, and you will need to exit the GUI, stop DP, go to the Task Manager, bring up a list fo running processes, look to see if any of these processes are still running

 

bsm

rsm

csm

msm

asm

 

If you see any, then, kill the process. Start Data Protector.   At the command prompt, run

 

   cd \Program Files\Omniback\bin

   omnidbutil -clear

 

Check your devices to be sure that there are no tapes stuck in the drives.  If not, try running the backup again

 

I don't want to get too far ahead of myself, but the usual reason for Timeouts on other OS-types is that KeepAlive needs to be enabled. Before you get into that, I want to be sure that it is not a hung session that is causing this

 

If you want to read more about KeepAlive on Open VMS

http://h71000.www7.hp.com/doc/732final/6631/6631pro_005.html#keepalive  Section 2.1.6.6

Frequent Visitor
Sandeep_Pawar
Posts: 2
Registered: ‎11-20-2013
Message 3 of 3 (256 Views)

Re: Backup Session fails for only one filesystem with BMA timeout

Hi Bob,

 

Thanks. Parallaly we have opened a case with HP. They asked us to add few parameters related to keepalive you mentioned and we let the backup run as per schedule. Next day the scheduled backup ran sucessfully.

 

Now I have a query, We just did following changes on Cell manager in omnirc file.

 

OB2IPCKEEPALIVE=1
OB2IPCKEEPALIVETIME=900
OB2IPCKEEPALIVEINTERVAL=60
OB2INETTIMEOUT=600

 

and in addition to that the two variables we increased earlier in global file  i.e.

 

SmDaIdleTimeout = 300  

SmMaIdleTimeout= 340

 

Do we need to change any parameter on oVMS server as this is the server being backed up? If yes, will there be any performance issue since from oVMS server point of view?

 

Please advice.

 

Thanks & Regards,

 

Sandeep

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.