02-04-2013 03:11 AM
Hi,
I've started getting the Disk storage server is down(2106) error. I'm having trouble trying to trouble shoot it. We have a staging area attached via fibre. There ar no windows event log errors for the time it went down.
I've looked in bpdm and bptm but I can't find anything obvious in there.
Windows 2003 R2 x86
NBU 7.5.0.3
Solved! Go to Solution.
02-04-2013 05:13 AM
This may be a timeout caused, as you say, by the servers being very busy.
It may be a lack of network ports or it may just be a communications timeout whilst checking the disks.
Add the following file (just a flat file with no file extention - so caraful that you are viewing extentions and it doesnt get created as a text file) to the Master and Media Servers:
<install path>\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO
Open it up in notepad and put the value of 800 in it.
This just gives disk status checks a better timeout value which usually helps when things are very busy
02-04-2013 03:52 AM
hi,
what kind of storage server you are using?
Pure disk or Data domain?
let us know the output of below file
Install path\veritas\netbackup\bin\nbdevquery -listdp -stype <storagetype -U
02-04-2013 03:55 AM
Please tell us more about your Disk_Staging storage server.
32-bit W2003? This means Advanced Disk, right? Not Basic Disk?
Configured on Master or on a media server?
Extract from Troubleshooter:
02-04-2013 03:56 AM
I'm not sure we are using a storage server, I've never heard of this before. It's just a basic disk. That command says no disk pools found. Confused!
02-04-2013 04:06 AM
please provide the nbemmcmd -listhost -verobose for the media server which is in issue.
and also, if that is the basic disk,
just log into the server , go to the baisc disk directory and try to create one text file, and see how it works.
if creating text file fails, than you need to work with your windows again, and storage team to fix that.
02-04-2013 04:48 AM
It is intermittent I must add. The errors started on the 02/02/2013 and only lasted an hour. No errrors since then, but we have had them for a few weeks intermittently. It's configured on a master server.
02-04-2013 05:04 AM
hi,
if its working fine now, you are good to go..
if you get this error in future, its better to practice, to start from the OS disk level,as its basic disk.
check if the disk is accssible from the OS level or not,
then try to check the the disk status.
make sure your disk is not reaching High disk I/O performance.
02-04-2013 05:08 AM
It is working now yes, but as I've had this problem for the last two weeks, it will happen again. It usually happens through the night so I will be unable to check.
I have suspected it is when the disk is being highly utilised actually.
Thanks for your help
02-04-2013 05:13 AM
This may be a timeout caused, as you say, by the servers being very busy.
It may be a lack of network ports or it may just be a communications timeout whilst checking the disks.
Add the following file (just a flat file with no file extention - so caraful that you are viewing extentions and it doesnt get created as a text file) to the Master and Media Servers:
<install path>\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO
Open it up in notepad and put the value of 800 in it.
This just gives disk status checks a better timeout value which usually helps when things are very busy
02-04-2013 05:22 AM
Thanks I will try that.