Forum Discussion

PF1's avatar
PF1
Level 2
15 years ago

Can't delete storage pool after media server deleted

Hello all.
    I have a PureDisk disk pool that I am unable to delete.  I expired all images and deleted all fragments but it still would not delete.  I then deleted the media server that hosted the pool as that was it's only function, thinking that the disk pool would also be removed, however it's still there and I am now unable to remove it.  As would be expected, the following nvdevconfig command fails with the error message below:


           cmd:   nbdevconfig -deletests -storage_server TESTSRVR -stype PureDisk
           err:   DSM has encountered the following busy resource:  TESTSRVR
                    Failed to delete storage server 
TESTSRVR, invalid command parameter

For reference, master server is RHEL 5.4 x64 running NBU 7.0.

Thanks in advance.

Pat
7.1.x and Earlier
Backup and Recovery
NetBackup
  • PF1's avatar
    PF1
    15 years ago
    Hello all, and thanks for comments.

    Turns out that there were still fragments listed in the EMM expiration table because the master server couldnt connect to the media server where the image fragments were originally held.  I was able to delete them from the table with the ` /usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -force` command and then nbdevconfig removed the pool successfully.

    Thanks again!

    Pat
  • Will_Restore's avatar
    Will_Restore
    Level 6
    15 years ago

    1 If the media server has disk pools configured, remove the media server from

    the storage units that use those disk pools. For each storage unit, run the

    following command on the master server:

    /usr/openv/netbackup/bin/admincmd/bpsturep -label

    storage_unit_label -delhost host_name

    Replace storage_unit_label with the name of the storage unit and host_name

    with the name of the media server.

    2 If the media server is the only storage server for the disk pools, change the

    state of the disk pools to DOWN. To do so, enter the following command on

    the master server for each disk pool:

    /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype

    server_type -dp disk_pool_name -state DOWN

    Replace server_type with the type of storage server: AdvancedDisk, PureDisk,

    or the vendor string that identifies the OpenStorage server type.

    Replace disk_pool_name with the name of the disk pool.

    3 For each disk pool, do the following:

    ■ Remove the media server from disk pool access by entering the following

    command on the master server:

    /usr/openv/netbackup/bin/admincmd/nbdevconfig -changedp -dp

    disk_pool_name -stype server_type -del_storage_servers

    storage_server

    Replace disk_pool_name with the name of the disk pool.

    Replace server_type with the type of storage server: AdvancedDisk,

    PureDisk, or the vendor string that identifies the OpenStorage server type.

    Replace storage_server with the name of the media server.

    ■ If the disk pool is on disk storage available only to the media server and

    is no longer required, delete the disk pool as follows:

    /usr/openv/netbackup/bin/admincmd/nbdevconfig -deletedp -dp

    disk_pool_name -stype server_type


  • PF1's avatar
    PF1
    Level 2
    15 years ago
    Hello all, and thanks for comments.

    Turns out that there were still fragments listed in the EMM expiration table because the master server couldnt connect to the media server where the image fragments were originally held.  I was able to delete them from the table with the ` /usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -force` command and then nbdevconfig removed the pool successfully.

    Thanks again!

    Pat