Delete PureDisk pool after RAID-Crash

[nocoffeeman]

Hi.

So we had an incident with one of our PureDisk pools had 2 diskcrashes.
This resulted in the whole RAID going down and needed to be rebuilt.

Luckily we had no important data on in that pool, as I was just running som Testimages on it.
But the problem is, I'm now trying to delete the old pool, to get the new purediskpool up and running with the new RAID and disks.

I get the following error:
Disk Pool cannot be deleted becaus Disk Volume contains images.

When I run the images on disk report. I get 24 images on this puredisk.
Ive tried the following:

nbdelete -backup_id <Backup_ID> -force
nbdelete -allvolumes -force

It only says the volume is down.
Do I need to contact support?

[eduncan]

Please review:

https://www.veritas.com/support/en_US/article.TECH150431

Use the parameter   -notimmediate  if there are multiple images to be deleted. Refer to HOWTO43656 for more details. To expire a single backup image, execute as follows. 
bpexpdate -backupid <backup_image_id> -d 0 -M <Master_server_name> -force_not_complete 

To expire ALL backup images on the disk pool, execute: 
bpexpdate -stype PureDisk -dp MSDP_DiskPoolName -force_not_complete

[manatee]

or probably, if you are using SLP, there are pending duplication jobs:

to see pending list of duplication:

./nbstlutil stlilist -image_incomplete -l

to cancel all pending duplication belonging to an SLP:

./nbstlutil cancel -lifecycle Daily_Policy

[nocoffeeman]

@eduncan wrote:

Please review:

https://www.veritas.com/support/en_US/article.TECH150431

Use the parameter   -notimmediate  if there are multiple images to be deleted. Refer to HOWTO43656 for more details. To expire a single backup image, execute as follows. 
bpexpdate -backupid <backup_image_id> -d 0 -M <Master_server_name> -force_not_complete 

To expire ALL backup images on the disk pool, execute: 
bpexpdate -stype PureDisk -dp MSDP_DiskPoolName -force_not_complete

---

Thansk for the quick response. Ive tried this, but keeps getting this error, on all the images:

@11/29/2017 08:57:33 - requesting resource @aaaaO
@11/29/2017 08:57:33 - Info nbdelete (pid=7276) deleting expired images. Media Server: nb-media3.hedmark.org Media: @aaaaO
11/29/2017 08:57:33 - Error nbdelete (pid=7276) Cannot obtain resources for this job : error [2074]
11/29/2017 08:57:33 - Error nbjm (pid=4004) NBU status: 2074, EMM status: Disk volume is down
11/29/2017 08:57:33 - Error nbjm (pid=4004) NBU status: 2074, EMM status: Disk volume is down
Disk volume is down (2074)

Edit: The diskvolume is UP

[nocoffeeman]

---

@rino19ny wrote:

or probably, if you are using SLP, there are pending duplication jobs:

to see pending list of duplication:

./nbstlutil stlilist -image_incomplete -l

to cancel all pending duplication belonging to an SLP:

./nbstlutil cancel -lifecycle Daily_Policy

---

Hi.

No pending duplications:

nbstlutil stlilist -image_incomplete -l
No images or lifecycles matching criteria found.

[Marianne · Accepted solution]

You may want to add -notimmediate to the bpexpdate command:

-notimmediate

Inhibits the call that bpexpdate makes to the nbdelete command after it expires an image on disk. If you intend to delete many images at the same time, use -notimmediate to avoid the overhead of multiple job creation for nbdelete to process. You can then run the nbdelete command later.

Run 'nbdelete -allvolumes -force' after bpexpdate.

[manatee]

---

@nocoffeeman wrote:

---

Thansk for the quick response. Ive tried this, but keeps getting this error, on all the images:

@11/29/2017 08:57:33 - requesting resource @aaaaO
@11/29/2017 08:57:33 - Info nbdelete (pid=7276) deleting expired images. Media Server: nb-media3.hedmark.org Media: @aaaaO
11/29/2017 08:57:33 - Error nbdelete (pid=7276) Cannot obtain resources for this job : error [2074]
11/29/2017 08:57:33 - Error nbjm (pid=4004) NBU status: 2074, EMM status: Disk volume is down
11/29/2017 08:57:33 - Error nbjm (pid=4004) NBU status: 2074, EMM status: Disk volume is down
Disk volume is down (2074)

Edit: The diskvolume is UP

---

why would NBU keep saying volume is down? then you said volume is up. are both of you referring to the same LUN?

[nocoffeeman]

---

@Marianne wrote:

You may want to add -notimmediate to the bpexpdate command:

-notimmediate

Inhibits the call that bpexpdate makes to the nbdelete command after it expires an image on disk. If you intend to delete many images at the same time, use -notimmediate to avoid the overhead of multiple job creation for nbdelete to process. You can then run the nbdelete command later.

Run 'nbdelete -allvolumes -force' after bpexpdate.

---

This worked! Thank you!