Video Screencast Help

NetBackup PureDisk backup fails with 2074 error

Created: 23 Aug 2012 | 3 comments

Circumstances - all backups sent to a PureDisk storage unit failing with status code 2074 - Disk volume is down

Would bring the disk up - /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp Pure_stunit_name -state UP

The disk storage unit would continue to go down, regardless of how often you attempt to being the device up with bperror -disk showing only 

1345752121 1 33280 8 0 0 0 *NULL* nbemm Volume Pure_stunit_name:PureDiskVolume marked down, Storage server media3 S{osrv-2060023}
1345752173 1 33280 8 0 0 0 *NULL* nbemm Volume Pure_stunit_name:PureDiskVolume monitored by media3 is down S{glp-2060038}
Tried cycling the daemons on the master server and rebooting the Windows media server but the issue persisted.
Checked the Services on the media server - media3 and noticed that NetBackup Deduplication Engine service was stopped and attempts to start would fail with the following appearing in the Event Viewer:
Originator:  SpoolD
The description for Event ID 1 from source spoold cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
26016: Store Manager: Activate failure.
Checked the SpoolD log - locatied in Storage Location/logs/spoold/spoold (i.e. f:/backups/logs/spoold/spoold) and found:
August 21 07:50:32 INFO [000000000E0FA790]: Remote is using libcr Version 7.0002.0012.053, Protocol Version 6.6.1 running on WIN32. Agent bpstsinfo.exe requesting access for DataSelection ID 2
August 21 07:50:32 INFO [000000000E0FA790]: Remote is using libcr Version 7.0002.0012.053, Protocol Version 6.6.1 running on WIN32. Agent crstats.exe requesting access for DataSelection ID 1
August 21 07:50:42 ERR [0000000007A3FD40]: 25017: FileCopyA: could not open destination file F:\backups\data/journal/0.bin
August 21 07:50:42 ERR [0000000007A3FD40]: 25017: FileMoveA: copy failed
August 21 07:50:42 ERR [0000000007A3FD40]: 25001: dcOutPlaceUpdateReplay: could not move F:\backups\data/6825.bin to F:\backups\data/journal/0.bin (object already exists)
Renamed F:\backups\data/journal/0.bin to F:\backups\data/journal/old0.bin and tried to start the NetBackup Deduplication Engine service again - after a minute the service did start
On the master server:  reran /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp Pure_stunit_name -state UP
Tested another backup and things are rolling now.
Hope this helps someone else :)

Comments 3 CommentsJump to latest comment

MilesVScott's picture

Not %100 sure but renaming containers sounds like it could cause a few problems. You may want to consult support to see about running a recoverCR -fix. Just a suggestion so that you dont run into problems later.

If my answer was helpful, please mark as a solution so others can benefit as well.

NBU,Win 2k3 Enterprise x64 SP2

Miles Scott | Holland & Knight
IT Infrastructure Specialist

f25's picture


Renaming the 0.bin or 0.bhd is like asking for trouble.

I would recommend stopping PureDisk services and then removing the  /Storage/data/journal/datastore.hdr
/Storage/data/journal/datastore.hdr_tlog should be less extreeme but may cause the CR to start a longer while.

You may consider Content Router as started when you get the following entry in the spoold.log:
# grep "Storage Cache Manager: importing complete" /Storage/log/spoold/spoold.log

BTW, do I understant correctly or does your PureDisk run on Win!?


monty_222's picture

Looks like a needs an investigation from the Syamantec support team , please open a case with the team to get help on thios .