10-05-2017 01:52 AM
Since we moved from a nbu 7.1 to 8.0 and another hardware we still do have a DataDomain with existing images which cannot be accessed within the new environment due to incompatibility issues.
I would like to remove this storage server and diskpool completely but i cannot expire and remove images because it is not accessible. I did a "bpexpdate -stype DataDomain -dp <diskpoolname>" but i got Status 2017 disk volume is down.
Any idea how to proceed here?
thanks Kai
Solved! Go to Solution.
10-05-2017 02:34 AM
I am not 100% sure on this so cation is needed - consider to open a support request with Veritas
Before starting the operation obtain the media id for the now gone data domain. Media is @aaaa{something}.
Try using the -nodelete to the bpexpdate command. bpexpdate -nodelete will remove images from the catalog but not try to delete the image itself.
See : https://www.veritas.com/support/en_US/article.000117798
Subsequent you need to clean up the EMM table as it keep track of images it can't delete. The -fore option to nbdelete will remove the image from EMM, deletable or not.
/usr/openv/netbackup/bin/admincmd/bpimage -cleanup -allclients
/usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -force
Verify afterwards clean up is complete by running
nbdelete -deletion_stats [-U] -media_id name (name is @aaaaa{something} again.
Also check the image clean job in Netbackup.
10-05-2017 02:19 AM
Try to add -justimage .
I remember this option from years ago and not sure if it is still a valid option.
10-05-2017 02:34 AM
I am not 100% sure on this so cation is needed - consider to open a support request with Veritas
Before starting the operation obtain the media id for the now gone data domain. Media is @aaaa{something}.
Try using the -nodelete to the bpexpdate command. bpexpdate -nodelete will remove images from the catalog but not try to delete the image itself.
See : https://www.veritas.com/support/en_US/article.000117798
Subsequent you need to clean up the EMM table as it keep track of images it can't delete. The -fore option to nbdelete will remove the image from EMM, deletable or not.
/usr/openv/netbackup/bin/admincmd/bpimage -cleanup -allclients
/usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -force
Verify afterwards clean up is complete by running
nbdelete -deletion_stats [-U] -media_id name (name is @aaaaa{something} again.
Also check the image clean job in Netbackup.
10-05-2017 02:37 AM
I have been wondering since my reply why the compatibility issue was not picked up before the upgrade?
Or if the DD cannot be upgraded?
10-05-2017 02:45 AM
thanks Marianne but it is not a valid option :(
10-05-2017 02:53 AM - edited 10-05-2017 03:15 AM
since the DD is no longer needed i was not aware of the "need". I thought i can just delete :(
so this means i have to upgrade DD, install the plugin and connect...just to cleanup my database
10-05-2017 03:21 AM
10-05-2017 03:28 AM
No you don't have to - but it quite a mess to do the clean-up afterwards :D
10-05-2017 03:58 AM
thanks Nicolai
so i did a "bpexpdate -stype DataDomain -dp dd-de-dp -nodelete" which was working fine. Then i checked again for the images
[root@franbp1 ~]# bpimmedia -stype DataDomain -dp dd-de-dp
no entity was found
[root@franbp ~]# bpimage -cleanup -allclients
[root@franbp ~]# nbdelete -allvolumes -force
[root@franbp ~]# nbdelete -deletion_stats -U -media_id @aaaah
Frags : 0
KB : 0
[root@franbp ~]#
And next cleanup was running fine no longer partially successful
But i do not understand what means "quite a mess to do the clean-up afterwards" ? I am missing anything ?
10-05-2017 04:37 AM
"Quite a mess" is the reason why you requested assistance in this discussion.
This process is not automatic and not documented since this issue should not present itself with proper planning.
10-05-2017 04:54 AM
agree...thougt it would be simple but missed some parts...
thank you so much for your assistance !