Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

5082

January 18th, 2017 06:00

How to delete a DataDomain storage system in NetWorker 8.2.3.

Hi,

I'm trying to delete a DataDomain device (DDOS 5.6.2) from NetWorker (release 8.2.3).

I receive the error message "A device exists on the DDR.

When I check devices, there is no device for the DD device to be deleted.

Additional information: Several VLANs and several EBRs are used. Using the "new device wizard", I've created three Data Domain Devices to support the different EBRs in the different VLANs. Unfortunately, I've to delete two of those devices, because the devices hostname do not fulfill the requirements for DNS.

With kind regards

Michael

14.3K Posts

January 20th, 2017 01:00

It seems to be related somehow to integration with VC - not sure if there is some extra dependency as I do not run such setup.  Best bet is to open a ticket with support.  Not sure if you could remove it by forcing it with nsradmin (for example, while NSR is down), but you may try that as well.

2.4K Posts

January 18th, 2017 13:00

This makes sense as you should not be able to delete the whole DD.

Go to "Devices" (2 steps up), then select your DD device here.

  Unmount the media

  Delete the device

January 18th, 2017 14:00

Hi Bingo,

and that's what's confusing me. There is no related device under "Devices". The NetWorker Device should be "Data Domain Systems name"_"Storage_Path". But there is no such entry. I've created a screenshots during the Device Creation:

The device from step "Adding Data Domain Device" is not listed under "Devices", as far as I remember I've deleted it already. The device is also not listed in nsradmin.

I thought that my problem is maybe caused, by the fact, that I've used the "New device Wizard" to create a new Data Domain System with a different IP of an existing one (to support EBRs in different VLANs).

Any further idea?

Thanks and regards

Michael

14.3K Posts

January 19th, 2017 12:00

I also have DDs defined on each VLAN and could remove it in the past (didn't try with version you have) so that should not be an issue.  I wonder if some device leftover exists...  if this is on Linux, can you do following on backup server:

grep "evice access" -A1 /nsr/res/nsrdb/*/*

So, you are looking at the value of device access information and you wish to see if any is defined for DD VLAN path you have or wish to remove.  As this line is usually long and therefore escaped to new line, I used -A1 to list line below the one where I found the string I'm grepping.

January 19th, 2017 14:00

Hi Hrvoje,

grep "evice access" -A1 /nsr/res/nsrdb/*/* didn't contain the device I want to delete.

I did also run grep -i DataDomainSystem-to-be-deleted -A1 /nsr/res/nsrdb/*/*
Output:

/nsr/res/nsrdb/09/27008f19000000002fd766580a4e605f:hosts: DataDomainSystem-to-be-deleted;

/nsr/res/nsrdb/09/27008f19000000002fd766580a4e605f-inuse filecopy streams: 0;

--

/nsr/res/nsrdb/09/27008f19000000002fd766580a4e605f:name: DataDomainSystem-to-be-deleted;

/nsr/res/nsrdb/09/27008f19000000002fd766580a4e605f-OS version: Data Domain OS 5.6.2.0-543944;

Maybe also interesting to know, when I run the "new device wizard" to add a new DD device, only one device is listed (the one I didn't delete):

Thanks and regards

Michael

January 19th, 2017 14:00

I've just tried to delete another DataDomain System (same problem), here is the daemon.raw:

38752 01/20/2017 03:18:07 AM  2 0 0 469301024 3486 0 NW server nsrd NSR warning DataDomainSystem-to-be-deleted_Storage_path unmounted Label.002

0 01/20/2017 03:18:44 AM  1 5 0 2126501632 19800 0 NW server nsrdisp_nwbg NSR notice 01/20/17 03:18:44.443400 Running nsrvim....

0 01/20/2017 03:18:44 AM  1 5 0 3979175680 19799 0 NW server nsrdisp_nwbg NSR notice 01/20/17 03:18:44.443969 Running nsrvim....

106637 01/20/2017 03:18:45 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: nsrvim starting on NW server (process 19821).

106637 01/20/2017 03:18:45 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Connecting to NetWorker on 'NW server'.

106637 01/20/2017 03:18:45 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: nsrvim starting on NW server (process 19824).

106637 01/20/2017 03:18:45 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Connecting to NetWorker on 'NW server'.

106637 01/20/2017 03:18:45 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Querying NSR hypervisor resource 'vCenter_host'

106637 01/20/2017 03:18:45 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Connecting to service at https://vCenter_host/sdk

106637 01/20/2017 03:18:45 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Querying NSR hypervisor resource 'other_vCenter_host'

106637 01/20/2017 03:18:45 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Connecting to service at https://other_vCenter_host/sdk

106637 01/20/2017 03:18:46 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Querying for inventory at https://vCenter_host/sdk

106637 01/20/2017 03:18:47 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Querying for inventory at https://other_vCenter_host/sdk

106637 01/20/2017 03:18:47 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Updating NSR hypervisor resource 'other_vCenter_host'

106637 01/20/2017 03:18:47 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Finished updating NSR hypervisor resource 'other_vCenter_host'

106637 01/20/2017 03:18:47 AM  1 3 0 3979175680 19799 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: nsrvim exiting on NW server (process 19821).

0 01/20/2017 03:18:47 AM  1 5 0 3979175680 19799 0 NW server nsrdisp_nwbg NSR notice 01/20/17 03:18:47.630711 Reading Hypervisor Environment now.

106637 01/20/2017 03:18:50 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Updating NSR hypervisor resource 'vCenter_host'

106637 01/20/2017 03:18:50 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: Finished updating NSR hypervisor resource 'vCenter_host'

106637 01/20/2017 03:18:51 AM  1 3 0 2126501632 19800 0 NW server nsrdisp_nwbg RAP notice job 'nsrvim' progress message: nsrvim exiting on NW server (process 19824).

0 01/20/2017 03:18:51 AM  1 5 0 2126501632 19800 0 NW server nsrdisp_nwbg NSR notice 01/20/17 03:18:51.037265 Reading Hypervisor Environment now.

38752 01/20/2017 03:19:12 AM  1 5 0 469301024 3486 0 NW server nsrd NSR notice DataDomainSystem-to-be-deleted _Storage_path Erase operation in progress

90960 01/20/2017 03:19:40 AM  1 5 0 1837086464 3696 0 NW server nsrsnmd NSR notice Erasing all data from device 'DataDomainSystem-to-be-deleted _Storage_path'

71193 01/20/2017 03:19:45 AM  0 0 0 469301024 3486 0 NW server nsrd NSR info Deleted media Notice: Deleted volume: volid=6740442, volname=~1484862580~Label.002, pool=EBR-POOL, location=?

0 01/20/2017 03:19:46 AM  5 3 12 469301024 3486 0 NW server nsrd RAP critical Resource does not exist

146681 01/20/2017 03:19:47 AM  1 5 0 4191680256 3786 0 NW server nsrmmd NSR notice Shutting down with mmd #301839366 as requested by nsrsnmd

January 20th, 2017 02:00

Hi Hrvoje,

how could someone know all those details about NetWorker? You're right, stopping NetWorker on the NetWorker server, specifying the resource database manual (nsradmin -d /nsr/res/nsrdb) and afterwards deleting the DataDomain devices using nsradmin works. I'm happy and impressed.

Thanks a lot

Michael

2.4K Posts

January 23rd, 2017 03:00

Deleting a resource is not an issue - finding the right one is often more critical.

But beware of dependencies as NW will not be active to assist you.

BTW - I just verified with NW 8.2.4.1 that you can in fact successfully delete a DD from the NW Admin GUI.

No Events found!

Top