Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

MSDP Decommission

Created: 30 Oct 2012 | 16 comments

The database and storage for the MSDP is unrecoverable (LUN Path removed and data deleted) . Consequently we are unable to remove the existing data structures for MSDP.

Any ideas on force deletion of MSDP datastructures.

 

Thanks,

Chris

Comments 16 CommentsJump to latest comment

cgoliver's picture

Nothing on that page helped. All of the commands fail.

Nicolai's picture

Credits to captain jack sparrow for the link.

@cgoliver - Please provide some background information:

Netbackup version

OS

You say all commands fail - What error message(s). Give us something to work with

Have you expired all images related to the deleted MSDP pool before trying to delete it - Netbackup will not delete a pool if images is still assigned to it.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

cgoliver's picture

Yes. I used the catalog search to remove all images referenced on the stu.

 

Netbackup 7.5.0.3

 

Solaris 10

 

nbemmcmd -deletehost -machinename $MASTER_SERVER -machinetype ndmp
NBEMMCMD, Version: 7.5.0.3
The function returned the following failure status: "Please Delete Disk Objects First"

Command did not complete successfully.
 

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

 

The backing store and db for PDDE are completely and irrevocably gone.

 

Thanks,

Chris
 

 

 

Marianne's picture

I agree - TN 150431 looks like a good find.

I am surprised at the short and abrupt response:

Nothing on that page helped. All of the commands fail.

And you don't give us ANYTHING to work with?

No copy & paste of the commands along with error messages?

I will give you this one TN that may be useful: http://www.symantec.com/docs/HOWTO66666

If this does not work, please log a support call. Maybe you will show Symantec engineer output of commands.....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

cgoliver's picture

The media server was not decommissioned. The backing LUN for the MSDP was inadvertantly removed and reassigned elswhere.

 

We will log a case with Symantec, as it's believed that sybase manipulation is required to fix this problem.

 

Thanks,

Chris

Marianne's picture

I fully realize that the media server was not decommissioned.

The TN tells you what can be done with nbdecommission.

Small extract:

Expire the images (if any), delete any storage units that reference the disk pool, delete the disk pool, and delete the storage server. (A reference is when the disk pool appears in the Disk pool setting of a storage unit.)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Nicolai's picture

nbemmcmd -deletehost -machinename $MASTER_SERVER -machinetype ndmp
NBEMMCMD, Version: 7.5.0.3
The function returned the following failure status: "Please Delete Disk Objects First"

You may still have a active references to the MSDP data like images, Storage Units or disk pools.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

cgoliver's picture

Nicolai,

 

There are no images, but there is a dp, which will not delete.

 

nbdevconfig -deletedp -stype PureDisk -dp dedup1_$MSDP_SERVER
Disk Pool cannot be deleted because Disk Volume (PureDiskVolume) contains images
failed to delete disk pool, invalid command parameter

 

We've run catalog checks for images on this stu and found none.

 

Thanks,

Chris

Nicolai's picture

The EMM datbase may still contain image references to the MSDP pool that re not reported by the bpimagelist comand (or catalgo search feature).

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

captain jack sparrow's picture

Wondering, why ndmp is being specified here

nbemmcmd -deletehost -machinename $MASTER_SERVER -machinetype ndmp
NBEMMCMD, Version: 7.5.0.3

It should be media server right?

 Cheers !!!

CJS

 

captain jack sparrow's picture

Not sure if it applies is your case, but worth trying

i'd similar annoyance where recently deployed media server was not getting listed under nbemmcmd -getemmserver despite all pre-reqs. More over it was not showing under device config wizard

We tried removing, NBU binaries and all it's footprint, building it from scratch, etc..

While we were unable to remove it from NBU, we used to get similar error as yours, that too without having any device being configured

After running through NBCC with support, they came up saying there was alias of this media server being pointed to another media server in NBU domain.

We removed alias and we were vrooooooommmm.... It went simply smooth.

Try removing this orphaned objects if it exists

Also would recommend to log support case and explain them, if possible ask them to assist you in getting NBCC ran on Master , it would let them identify quickly.

Hope this helps

 Cheers !!!

CJS

 

cgoliver's picture

Does anyone know the sql commands to flush out the data?

 

In the mean time we opened a case with Symantec.

 

Thanks,

Chris

cgoliver's picture

There is no alias for the media server.

captain jack sparrow's picture

Hi . Could you post an update to thread. If you have got any solution so far

 Cheers !!!

CJS

 

cgoliver's picture

Backline engineering provided a custom sql script to remove the offending rows from the appropriate tables.

 

We have not yet run the script, but we will update once complete.

 

Thanks,

Chris