DataDomain OST (OpenStorage Technology) backups fail with status 800 / 2074, disk volume is down. Status 2074

Article:TECH128377  |  Created: 2010-01-02  |  Updated: 2013-10-25  |  Article URL http://www.symantec.com/docs/TECH128377
Article Type
Technical Solution

Product(s)

Environment

Issue



DataDomain OST backups fail with status 800 / 2074, disk volume is down.


Solution



Backups to a DataDomain appliance using an OST storage unit fail immediately with "status 800 / 2074, disk volume is down."

Firstly, ensure that the DataDomain OS is compatible with both the OST plugin version and the version of NetBackup.  A compatibility list is available at http://my.datadomain.com.

Typically, if you have upgraded one of the 3 components then you need to upgrade the others (see DD_Boost compatibility list from the documents section of the above site).



To continue troubleshooting, increase the unified logging value 'DebugLevel' to 6 on the media server, for unified logging originators 202, 222 and 220:
vxlogcfg -a -p 51216 -o 202 -s DebugLevel=6
vxlogcfg -a -p 51216 -o 220 -s DebugLevel=6
vxlogcfg -a -p 51216 -o 222 -s DebugLevel=6
(don't forget to reduce DebugLevel values back to zero once you have finished troubleshooting).

Check for these errors from the 222 log file:

04/02/10 09:06:16.412 [Debug] NB 51216 dps 220 PID:2816 TID:3800 File ID:222 [No context] 5 [sts::recvReply] ed8: sts::recvReply: recv line: stslog=STH_ESERROR: dpsProxy: C:\Program Files\Veritas\NetBackup\bin\\ost-plugins\libstspiDataDomain.dll:stspi_open_server STS_EPLUGIN nfs ost2getinfo failed (nfs: Operation not permitted)
04/02/10 09:06:16.412 [Debug] NB 51216 dps 220 PID:2816 TID:3800 File ID:222 [No context] 5 [sts::recvReply] ed8: sts::recvReply: recv line: stslog=STH_ESERROR: dpsProxy: libsts opensvh() 10/04/02 09:06:16: v10_open_server failed in plugin C:\Program Files\Veritas\NetBackup\bin\\ost-plugins\libstspiDataDomain.dll err 2060046
04/02/10 00:00:26.188 [Debug] NB 51216 dps 220 PID:2816 TID:3540 File ID:222 [No context] 5 [workInfo::doWork] dd4: workInfo::doWork: can't connect to server, -1
04/02/10 00:00:26.188 [Debug] NB 51216 dps 220 PID:2816 TID:3540 File ID:222 [No context] 5 [workInfo::doWork] dd4: workInfo::doWork: errorAll
04/02/10 00:00:26.188 [Debug] NB 51216 dps 220 PID:2816 TID:3540 File ID:222 [No context] 5 [workInfo::doWork] dd4: workInfo::doWork: error'ing all pending volumes
04/02/10 00:00:26.672 [Debug] NB 51216 dps 220 PID:2816 TID:2872 File ID:222 [No context] 5 [update::run] b38: update::run: UPDATING (3 @ 1):
04/02/10 00:00:26.672 [Debug] NB 51216 dps 220 PID:2816 TID:2872 File ID:222 [No context] 5 [update::run] b38: update::run: diskGroup = dd690_stor1_dp
04/02/10 00:00:26.672 [Debug] NB 51216 dps 220 PID:2816 TID:2872 File ID:222 [No context] 5 [update::run] b38: update::run: diskVolume = lus0
04/02/10 00:00:26.672 [Debug] NB 51216 dps 220 PID:2816 TID:2872 File ID:222 [No context] 5 [update::run] b38: update::run: volumeState = down-server


To correct this on the DataDomain, log on to the DataDomain and run the following commands (depending on whether your version of DDOS uses 'ost' or 'ddboost' commands):
 
1. For earlier DDOS versions that use the 'ost' commands:

nfs show clients
This may show:
/backup/ost   *        (rw,no_root_squash,no_all_squash,secure)     <------ shows clients as secure
 
If /backup/ost has been exported as secure, this limits connecting ports numbers to < 1024.  You need to change this to insecure in order for Netbackup to communicate correctly with the DataDomain.
 
nfs del /backup/ost *
nfs add /backup/ost * rw,no_root_squash,no_all_squash,insecure
ost disable
ost enable
nfs show clients
This should now show the export as insecure:
/backup/ost   *        (rw,no_root_squash,no_all_squash,insecure)
 
2. For later DDOS versions that use the 'ddboost' commands instead of 'ost' commands:
 
nfs show clients

This may show:
/backup/ost   *        (rw,no_root_squash,no_all_squash,secure)     <------ shows clients as secure
If /backup/ost has been exported as secure, this limits connecting ports numbers to < 1024.  You need to change this to insecure in order for Netbackup to communicate correctly with the DataDomain.
 
 
nfs del /backup/ost *
nfs add /backup/ost * (rw,no_root_squash,no_all_squash,insecure)
ddboost disable
ddboost enable
nfs show clients
This should now show the export as insecure:
/backup/ost   *        (rw,no_root_squash,no_all_squash,insecure)
 
Note:  The 'insecure' flag only means that the clients are using port numbers above 1024 to connect to the DataDomain. It does not mean that security is being compromised in any way.

At this point, the disk volume and pool are most likely up.   If they are still down after a few minutes, confirm that you have the correct username and password configured for that media server, by running the following update on the media server:

 

# /usr/openv/volmgr/bin/tpconfig -update -storage_server dd690 -stype DataDomain  -sts_user_id sysadmin  -password <password>

After this the disk volumes polling is successful and show as 'UP'.


Legacy ID



348373


Article URL http://www.symantec.com/docs/TECH128377


Terms of use for this information are found in Legal Notices