Hi Christian,      Pls wait for a day, I am already working on this and would update the same soon. BTW what version and OS in which your customer is running OCUM ? Regards adai ... View more

Hi Pridhvi,      As clearly mentioned in the following link https://communities.netapp.com/docs/DOC-19680 we dont have a plugins for clusterMode. Regards adai ... View more

Hi Alain,      I doubt in your case the snapmirror relationship are created using vfiler IP address and not the hosting or vfiler0 IP address. OCUM only discovers and manages vfiler relationships that are setup using hosting/vfiler0 IP and not vfiler IP. If you move your secondary from vfiler IP to physical filer IP OCUM should discover and you should be able to import them into a dataset. Pls find the link to the kb article that describes this. https://kb.netapp.com/support/index?page=content&id=3013156 Also below are some more details. PM supports and creates VSM/QSM/SV/OSSV relationship in all these topologies. Filer -> Filer Filer -> vFiler vFiler -> Filer vFiler -> vFiler OSSV->vFiler In all this cases PM creates the relationship and does the updates using filer interfaces (not the vfiler interfaces). Also PM discovers existing relationship of the above topology only if they are created using filer interfaces and not vfiler interfaces. PM creates and manages SnapMirror/SnapVault relationships that are from physical Filer to physical Filer only It will not discover a relationship that originates or ends on a vFiler. However, PM can handle primary or secondary volumes that belong to a vFiler. In a storage service, you can use a pre-existing secondary vFiler or you can ask OnCommand to create a secondary vFiler from a template (new in OC UM 5.0). But, OC UM will create a relationship from physical Filer to physical Filer even for the volumes that belong to a vFiler. PM does not officially support vFiler DR but there is a plug in available to support this that was created outside of the PM team. see here https://communities.netapp.com/groups/nmc-vfiler-plugin?view=documents PM does not support vFiler DR + snapmanager product + protection manager due to Snapdrive for Windows and Unix not being able to handle two identically named resources returned by Protection Manager Regards adai ... View more

Hi Tagawa, Pls dont move the database to NFS mount its not supported. You can instead  just move the PerfData Dir and also the database backup dir to NFS mount point. That way you should be able to clear up space in your install dir for upgrade. Regards adai ... View more

Hi Kuber,      I picked it up from Hardware Universe. But I think the De-duplication TR should also have it (TR 3505) but unfortunately I see it only updated till 8.0.1. Regards adai ... View more

Hi    Its is not recommended to upgrade like that. Pls see if you can find space. Also if you already have a latest backup taken you can skip the creation of backup step during upgrade.If you want to move around your perfdata file to a different path like NFS mount point( only perf dir and not the data dir) use the dfm datastore setup cli to move the files. Pls upgrade to 5.0.2 P1 release instead of 5.0.2  as this has additional fixes. The perf flat files which are of size 2 to 4 GB would automatically be cleaned for stale instance post upgrade to 5.0.2. The reason for the big flat files can be found in this bugs online link. http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=439756 http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=439756Initially due cleaning of the stale instances you may find little sluggishness post upgrade but this should return to normal in a week or 2 and give improved performance due to cleanup and 64bit architecture. Just to know how many stale objects you have, try to run the DFMPurge tool and if possible purge them as well. Here is the link to an how to video. DFM Purge Tool: How to Video Regards adai ... View more

Hi Kuber, I am adding some info to educate what this error means and also clarify when plugins are required. OCUM/DFM needs plugins only if configuration management feature is used. Using this you can pull/push options on the controller or a groups of controller/vFilers. The error you are getting is related to the reslimits. For Each platform model and ontap version we have a table with what is the maximum dedupe limit permitted on the controller. If you are using a ONTAP version or model for which the dfpm reslimit get does not return any thing you will hit this error. This error will also been if simulators are used as they have the model as SIMBOX and there is no reslimit entry for such a model. You will have to run these two commands. dfpm reslimit create <ontap-version> <product-model> dfpm reslimit create 8.1.2 FAS3220 Created new resource limit (274) If all the aggrs in this controllers are 64bit aggr use the below cli. dfpm reslimit set  274 maxDedupeSizeInGB=55193.6 If they are 32 bit aggrs dfpm reslimit set  274 maxDedupeSizeInGB=16384 Regards adai ... View more

Hi Francisco,      NMC 3.0.2 is not supported on RHEL 6. NMC Version 3.2 is supported on RHEL 6.0 Regards adai ... View more

Hi Scott,      I looked at the qtree report catalog and found that we do have fields that list the number of files, its limit and used as well. [root@vmlnx~]# dfm report catalog list -R qtree | grep -i file Default Display Tab: Filesystems vFiler                              Qtree vFiler (A) FilesLimit                          Qtree Files Limit FilesUsed                           Qtree Files Used FilesUsedPct                        Qtree Files Used %                            1 [root@vmlnx ~]# This is not available as a canned report instead you need to create a Custom report with these fields. To know more on reporting take a look at this video. Reporting with OnCommand 5.0 BTW this report catalog is from the Operations Manger Console and not the OnCommand Console. Regards adai ... View more

Yes, in order to create compression enabled VSM you will need a connection entry like this below. conn=multi(192.168.1.94,192.168.1.77) conn:n2 olive-oyl:dst_n2 compression=enable, - - - - And SnapProtect( or Protection Manager) will not delete the compression entry only if the following options is not set any value for both your source and destination controller. dfm host set <hostname-or-id-ip> hostPreferredAddr1=<should be empty> Check out this BugsOnline for more information. http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=381872 Regards adai ... View more

SnapProtect uses Protection Manager underneath and PM doesnt create VSM relationships with compression. Regards adai ... View more

Hi Daniel, I completely dont get your question. By default for all SnapVault relationship created by PM there are no snapvault snap sched entires. The same applies for VSM/QSM relationships as well where there are no entries in snapmirror.conf as well unless there is connection based ones. Regards adai ... View more

We are coming up with a Getting started course on how this selection is done when more than one aggr is eligible. Least-Utilized (only option prior to 5.1) –Selects aggregates with most available space –Margin can be tuned to select acceptable range Best-Fit (new with 5.1) –Selects aggregates with the least available free space that would fulfill the need –Margin can be tuned to select acceptable range ¡Global setting to select preferred algorithm   Manually resource selecting  ignores both algorithms There are two phases namely space balancing and load balancing. In space balancing phase we pick the aggr with largest free space( if least used criterion which is default)  and all those within 75% of its capacity.  By this we come up with a set of aggr, and on this set we apply the space balancing like number of qtree or relationships. In case of Best fit criterion we take the aggr that just fit and all those with in 1.75x its capacity and apply the load balancing. In case of Primary provisioning the number of qtree is used and in case of secondary provisioning we use the number of relationships. In the space balancing phase we select the aggr with largest free space and apply Regards adai ... View more

Hi Christian,      DFM does not report flex cache. But Performance adviser can give you all those performance details. Regards adai ... View more

In case of Snapmirror, we generate all those events only if the relationship is manged in DFM. Otherwise only lag error and warning messages are generated. Pls look for 206891 in bugs online soon. Regards adai ... View more

Guys try out the new dfm purge utility and also upgrade to 5.0.2P1 DFM Purge Tool: How to Video Regards adai ... View more

Yes. If the condition still exist, a new event will be generated and that would in-turn create an alarm. Regards adai ... View more

Hi Parker,      Run the dfm purge utility to get rid of all ghost events. DFM Purge Tool: How to Video Regards adai ... View more

Pls take a look at the history events reports which includes information events as well. dfm report view events-history Regards adai ... View more

Hi     Thats right, the bug577580 got fixed in 5.1 and now is back ported to 5.0.2P1 as well. Regards adai ... View more

Hi Reid,      Once you figure out can you post it back on the communities that what was the reason ? Regards adai ... View more

Hi Earls, Second test.  I created a brand-new dataset with an OSSV client path as the primary physical member.   The OSSV path only has about 32 KB of data in it.  I then attempt to assign the custom "Backup, then mirror" policy to my dataset.   I'm seeing something very strange in the Conformance Engine check: The planned size of the auto-provisioned Snapvault Secondary volume is 9.67 GB. The planned size of the auto-provisioned Mirror volume is 250 MB. My pmOSSVDirSecondaryVolSizeMb setting is set to 250m.  So, I'd expect my OSSV secondary volume to be 250 MB, but its 9.67 GB  ?!?!?!??!!?  What the what? My Mirror volume should be based off the size of the primary vol, which is 9.67 GB.  But its being sized at 250 MB. ????!?!?!?!?       I think I figured why the Mirror destination got created with 250mb in this case and not 9.67 GB. The Dynamic Secondary Sizing for VSM is using the projected size of the volume to create the secondary and looks like not the actual volume size returned by ONTAP. In this case the 250MB comes from the option that you have set for pmOSSVDirSecondaryVolSizeMb. Also in you first case why the Mirror failed becasue the default value for pmOSSVDirSecondaryVolSizeMb is 10GB where as the size of your aggr was only 9.67 Gb so it failed. Regards adai ... View more

Hi Jean-Christophe      Couple of questions before I can give you some solutions. Are you running OCUM 5.1 ? Is the option dpDynamicSecondarySizing turned on/enabled ? Do you have Other relationship like SV/QSM or VSM in your Environment ? Regards adai ... View more

Hi Win,      Protection Manager can only discover vFiler relatioship that are created in the context of physical filer/vfiler0 and not in vFiler context. Pls refer to this KB for more details. https://kb.netapp.com/support/index?page=content&id=3013156 Regards adai ... View more

Hi Mark,      Did you get to try SnapCreator ? They allow you to centrally manage schedule for all applications. Regards adai ... View more