Community

Subscribe
Highlighted
Accepted Solution

Oncommand deleted object still in the database

Hi all, checking on DFM database I see that there are really old data into it that have the "deleted" flag setup but are still into the database. There are also really old objects that don't exist anymore and in my view can be safely deleted (old storage that don't exist anymore or old volumes).

I see that there are sometimes really many of those items.... doing a dfm volume list -a return 7700 objects (volumes) while doing a dfm volume list return only 700.

My question is: can I delete those objects or they're needed by DFM in some way? Should they be automatically cleaned by DFM after a time period or they'll remain in the database indefinitely?

This is an example of some aggregate objects:

1009 itromfs22:aggr1-2008-11-04 12:07:37.000-1 AggregateunknownYes  dfmmonitor
1010 itromfs22:aggr1-2008-11-04 12:07:37.000-1.snapshot AggregateunknownYes  dfmmonitor
8212 itromfs22:aggr1-2010-03-08 00:04:49.000-1 AggregateunknownYes  dfmmonitor
8213 itromfs22:aggr1-2010-03-08 00:04:49.000-1.snapshot AggregateunknownYes  dfmmonitor
22234 itromfs22:aggr1.snapshot             Aggregate32_bit No                

Regards

Francesco

Re: Oncommand deleted object still in the database

HI,

They will remain in the database. For now we don’t have any mechanism where DFM deletes them after a certain period of time.

Also see this post https://communities.netapp.com/message/69742#69742.

Thanks,

Arun

From: c-xdl-communities

Sent: Wednesday, January 18, 2012 11:49 PM

To: Chakravarthy, Arun

Subject: - Oncommand deleted object still in the database

<https://communities.netapp.com/index.jspa>

Oncommand deleted object still in the database

created by Francesco Duranti<https://communities.netapp.com/people/f.duranti> in OnCommand Mgmt Software - View the full discussion<https://communities.netapp.com/message/72020#72020>

Hi all, checking on DFM database I see that there are really old data into it that have the "deleted" flag setup but are still into the database. There are also really old objects that don't exist anymore and in my view can be safely deleted (old storage that don't exist anymore or old volumes).

I see that there are sometimes really many of those items.... doing a dfm volume list -a return 7700 objects (volumes) while doing a dfm volume list return only 700.

My question is: can I delete those objects or they're needed by DFM in some way? Should they be automatically cleaned by DFM after a time period or they'll remain in the database indefinitely?

This is an example of some aggregate objects:

1009 itromfs22:aggr1-2008-11-04 12:07:37.000-1 Aggregate

unknown

Yes

dfmmonitor

1010 itromfs22:aggr1-2008-11-04 12:07:37.000-1.snapshot Aggregate

unknown

Yes

dfmmonitor

8212 itromfs22:aggr1-2010-03-08 00:04:49.000-1 Aggregate

unknown

Yes

dfmmonitor

8213 itromfs22:aggr1-2010-03-08 00:04:49.000-1.snapshot Aggregate

unknown

Yes

dfmmonitor

22234 itromfs22:aggr1.snapshot

Aggregate

32_bit

No

Regards

Francesco

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/72020#72020>

Start a new discussion in OnCommand Mgmt Software by email<mailto:discussions-community-products_and_solutions-storage_management_software@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2026>

Re: Oncommand deleted object still in the database

Hi Francesco,

When you delete any volume from dfm using "dfm volume delete <volume-name-or-id>" command then that volume doesn't delete permanently from dfm database, only dfm stop monitoring that volumes.

So, the volumes those have deleted flag mark as "Yes", that means those volumes are deleted using "dfm volume delete <volume-name-or-id> command and dfm is not monitoring those volumes", so, dfm volume list -a command list those volumes because those volumes are not permanently deleted from dfm database.

So, "dfm volume list -a"  command will list all the volumes present in dfm database while "dfm volume list" command will list only those volume for which Deleted flag marked as "No" and in other word, dfm volume list

command will list only those volume which are monitor by dfm server.

To delete the objects permanently from dfm database, please refer the post link that Arun mention in his post.

Regards,

Gireesh

Re: Oncommand deleted object still in the database

Yes. You can delete the objects using "dfm volume delete -f <Volume Id>" command. You need to restart your dfm services after running this command.

-KJag

Re: Oncommand deleted object still in the database

Just a question about it... it's safe to clear those "old" data related to volume/aggregate that don't exist anymore in the database using the "delete -f" or they are in some way used by DFM for some kind of historical report?

arunchak ha scritto:

HI,

They will remain in the database. For now we don’t have any mechanism where DFM deletes them after a certain period of time.

Also see this post https://communities.netapp.com/message/69742#69742.

Thanks,

  Arun

Re: Oncommand deleted object still in the database

HI Fransisco,

AFAIK they are not used by DFM. Deleted objects are not monitored so I don't think it has to do anything with reporting.

I would like to tell you one scenario where I use the deleted object:

Say, I have a LUN and I would want to stop monitoring it so would have deleted the LUN from dfm "dfm lun delete <id>". Now the LUN is marked deleted in DFM and gets listed under -a option.

After a month, I want to monitor the LUN again and want to add the same object in DFM, then I do the following (use dfm lun add)

[root@shoemaker-rhel6x64-01 ~]# dfm lun list -a | grep -i 1532

1532 vserver01_arun:/lun_07_vol/lun07                                   Yes     (object deleted is YES)

[root@shoemaker-rhel6x64-01 ~]# dfm lun add 1532 (Adding back the LUN to enable monitoring on it)

Added LUN vserver01_arun:/lun_07_vol/lun07 (1532).

[root@shoemaker-rhel6x64-01 ~]# dfm lun list  | grep -i 1532

1532 vserver01_arun:/lun_07_vol/lun07                                   No (Added LUN is now showing as not deleted)

[root@shoemaker-rhel6x64-01 ~]# dfm lun add help

NAME

    add -- re-monitor deleted LUNs

SYNOPSIS

    dfm lun add { all | <objects> ... }

Hope this is useful.

-Arun

Re: Oncommand deleted object still in the database

Hi Francesco,

Once you delete any aggregate/Volume using -f option then all the history data for that volume or aggregate will get deleted and you can not retrieve that data  after this.

So, this is not safe operation.

Regards,

Gireesh

Re: Oncommand deleted object still in the database

I would say, I agree with Gireesh, and hence we do not recommend this to the customer. If eventually the db size increases considerably due to the deleted objects customers should contact NetApp support for pruning the db.

There was a post regarding this in the community.

Re: Oncommand deleted object still in the database

The deleted objects are not at all used in any of the reports as its in deleted state. But you can't retrive the history data for the deleted objects anymore, once deleted using -f.

If you really dont want those objects, you can delete them from DB.

-KJag

Re: Oncommand deleted object still in the database

The use case of this option (-f option ) is, suppose you deleted some object from storage system but still dfm data base store the records for that object some period of time.

So, in this case you can delete such object forcefully from dfm database using -f option.

Regards,

Gireesh