Subscribe
Accepted Solution

Problem with automatic secondary volume creation / naming

Hello,

I have a problem with the automatic naming of one of my secondary volume created with OCUM 5.2.

In the dataset naming properties i have put in backup_%V.

I have try some tests and then i needed to delete the dataset.

I have also delete the volume and check if there is no deleted relationship present in the filer using snapvaut status and if needed snapvault release.

After this is have do the folowing : dfm host rediscover filer_name for both filer and i have wait that my secondary volume is no more showed in OnCommand

The problem is that now when i recreate the dataset with the same properties my volume looks like this : backup_%V_1 or backup_%V_2 etc...

What have I missed ?

Thank you in advance. .

Yannick.

Re: Problem with automatic secondary volume creation / naming

Hi Yannick,

    The problem is that even though the volume is deleted on the controller, the entry for that volume is not deleted from the dfm sybase database.

Because of this you are facing this problem. You will have to delete the entry from the database to get the naming properly else its will keep incrementing depending upon the entries in the database with same volume names.

Regards

adai

Re: Problem with automatic secondary volume creation / naming

Hi Adai,

Thanks for your reply.

Could you please explain me how to do that ?

Is there a KB ?

Thank you in advance.

Yannick.

Re: Problem with automatic secondary volume creation / naming

Use the dfmpurge tool to remove all the mark-deleted and stale objects.

https://communities.netapp.com/videos/3134

Regards

adai

Re: Problem with automatic secondary volume creation / naming

Thank you Adai, I will try to find how to remove this volume only from the database.

Yannick.