2074 - Disk Volume is down

[Adnan_M_F]

Hello,

We've created a new "DiskPool" after it crashed earlier. However backups on the pool fail with Error code 2074.

Tried to follow these KB articles 000008526 & 000017160 however the status of the disk volume still remains DOWN.

Any help would be much appreciated.

Regards,

Adnan

[Marianne]

Please start at the beginning and tell us more about the disk pool - 

Type?
Basic or Advanced disk? Local disk or network share?
MSDP?
OST?

Can you please share the steps that you have followed to create the disk pool?

[Adnan_M_F]

Thank you Marianne.

Below is details of the pool:

Disk Pool Name : Netbackup_Disk_Pool
Disk Type : PureDisk
Disk Volume Name : PureDiskVolume
Disk Media ID : @aaaaP
Total Capacity (GB) : 16986.20
Free Space (GB) : 16201.65
Use% : 4
Status : DOWN
Flag : ReadOnWrite
Flag : AdminUp
Flag : InternalDown
Num Read Mounts : 0
Num Write Mounts : 1
Cur Read Streams : 0
Cur Write Streams : 0
Num Repl Sources : 0
Num Repl Targets : 0

The disk is storage on a SAN. We used the wizards to create the disk pool. 

Also we gave the same disk pool name as it was earlier (before we had stroage failure). To delete disk pool earlier we had followed 000011549

[Michael_G_Ander]

I would check the spoold & spad logs to see if there was some indication of what the underlying problem is.

Btw. did you delete the old .cfg file under netbackup/bin/ost-plugin, before recreating the pool ?

these old files have given me problems when recreating pools.

[Adnan_M_F]

Hello Michael,

Nice catch !!!

Went on to check the spoold and spad logs, however both were not running. Then noticed that both "Netbackup Deduplication Engine" and "Netbackup Deduplication Manager" services got disabled. So made them automatic and tried to restart. (The media server is also the master server)

However the just dont seem to start, and give error "Windows could not start the NB Deduplication Engine (or Manager) on local computer ..... Error 1: Incorrect function"

Tried to trace the startup process on cmd, and this is what i get:

C:\>cd "Program Files\Veritas"\pdde\

C:\Program Files\Veritas\pdde>spoold.exe --start -trace
Error: 22: -trace: unknown arg

C:\Program Files\Veritas\pdde>spoold.exe --start --trace
Error: 22: _dctPathAddA: invalid NULL parameter
Error: 22: _dctPathAddA: invalid NULL parameter
Error: 22: _dctPathAddA: invalid NULL parameter
Warning: 2: __openReaderA: could not open file C:\Program Files\Veritas\pdde\
Error: 2:
BadValue : (none)
File : C:\Program Files\Veritas\pdde\
Section : Symantec\PureDisk\ContentRouter
Entry : ConfigFilePath
Reason : Empty or missing configuration directive, file not found or access denied.

C:\Program Files\Veritas\pdde>spad.exe --start --trace
Starting service spad: .failed
Error: 1: The spad service could not start in a timely fashion. The service is currently in a stopped state and returned an exit status of 0 to the Se
rvice Control Manager.

[Adnan_M_F]

Since it was a new disk pool, we've again deleted it and started it from beginning.

So followed the article 000011549 to delete the MSDP disk pool. 

Everything went fine, all steps were followed however on step 13 to run PDDE_deletConfig script we had the following error:

C:\Program Files\Veritas\pdde>PDDE_deleteConfig.bat
ERROR: The system was unable to find the specified registry key or value.
EtcPath=
An error has occured while attempting to configure. Aborting...

Any help appreciated.

Thanks.

[Marianne]

Maybe time to log a Support call with Veritas?

IMHO - what you need at this point in time is ' a second pair of eye'. 
Veritas engineer should be able to see via Webex why you see these error messages regarding missing config files and missing registry entries.

[Adnan_M_F]

Thanks Marianne.

After the PDDE script failure, I realised that some registries must be corrupted so simply ran the "Netbackup Repair" from installation/setup files. After that created the new MSDP storage server and to my surprise it worked. Still monitoring it though, if all goes well for couple of days, will notify that as a workaround not a solution. 

[watsons]

Probably worth to mention the NBU version next time..

because in pre-7.6 , spoold relies on postgreSQL to start properly. PostgreSQL is no longer there after 7.6. The event logs maybe able to tell us if starting a service is working or not.

[Adnan_M_F]

Alright a day since after the repair, backup jobs are running fine. Both Netbackup Deduplication Engine and Manager services are up and running without any problems. Unless there is another issue due to this configuration, this would be the last update. Its a workaround not necessarily a solution to the problems I was facing. 

NBU version: 7.6.1.1

Master/Media Server: Windows Server 2008 R2