Forum Discussion

Sorin's avatar
Sorin
Level 3
7 years ago

Disk Pool Up but Storage Server Down

Hi all,

We had a failed volume for about 1 month. We changed the disks and the volume is fine in Windows. However in NBU is a different story. 

PS C:\Program Files\Veritas\NetBackup\bin\admincmd> ./nbdevquery -liststs -stype PureDisk -storage_server hypbak01 -U
Storage Server : hypbak01
Storage Server Type : PureDisk
Storage Type : Formatted Disk, Network Attached
State : UP
Flag : OpenStorage
Flag : CopyExtents
Flag : AdminUp
Flag : InternalUp
Flag : LifeCycle
Flag : CapacityMgmt
Flag : FragmentImages
Flag : Cpr
Flag : FT-Transfer
Flag : OptimizedImage

PS C:\Program Files\Veritas\NetBackup\bin\admincmd> ./nbdevquery -listdp -stype PureDisk -dp hypbak01_dedup_1 -U
Disk Pool Name : hypbak01_dedup_1
Disk Pool Id : hypbak01_dedup_1
Disk Type : PureDisk
Status : UP
Flag : Patchwork
Flag : Visible
Flag : OpenStorage
Flag : SingleStorageServer
Flag : CopyExtents
Flag : AdminUp
Flag : InternalUp
Flag : LifeCycle
Flag : CapacityMgmt
Flag : FragmentImages
Flag : Cpr
Flag : FT-Transfer
Flag : OptimizedImage
Raw Size (GB) : 28614.00
Usable Size (GB) : 28614.00
High Watermark : 98
Low Watermark : 80
Num Volumes : 1
Max IO Streams : 40
Comment :
Storage Server : hypbak01 (DOWN)

I also tried 

PS C:\Program Files\Veritas\NetBackup\bin\admincmd> ./nbdevconfig -changests -storage_server hypbak01 -stype PureDisk -s
tate UP
Storage server hypbak01 has been successfully changed
PS C:\Program Files\Veritas\NetBackup\bin\admincmd> ./nbdevconfig -changests -storage_server hypbak01 -stype PureDisk -s
tate RESET
Storage server hypbak01 has been successfully changed
PS C:\Program Files\Veritas\NetBackup\bin\admincmd>

And restarting of the services.

Any other idea?

BIG THANKS in advance

 

8
windows server 2012

9 Replies

  • Marianne's avatar
    Marianne
    Level 6
    7 years ago

    Sorin

    Does  'failed volume '  mean that everything on the dedupe volume was lost?

    I guess this is the case as I have noticed this in your output:

    Raw Size (GB) : 28614.00
Usable Size (GB) : 28614.00

     

    Have you perhaps performed any of these steps as per the NBU Dedupe manual?

    Chapter 8: 
    This chapter includes the following topics:
    ■ About recovering the MSDP catalog
    ■ Restoring the MSDP catalog from a shadow copy
    ■ Recovering from an MSDP storage server disk failure
    ■ Recovering from an MSDP storage server failure

    • Sorin's avatar
      Sorin
      Level 3
      7 years ago

      Hi,

      And thanks for your answer.

      By "failed volume" I mean that one or two of the underline disks failed and the storage device made the volume unavailable for the OS. Once we replaced the failed drives all the data was back and available now in Windows Explorer.

      As I browse the volume now it sais 16TB of used data on the volume.

      • Nicolai's avatar
        Nicolai
        Moderator
        7 years ago

        there might be data consistency issues with the MSDP volume

        Take a look at the SPAD log file :

        /storage_path/log/spad/spad.log

        If its a reasonable size attach it to a post , do not bulk debug log text in a post