BTW what version of DFM are you using ?  Is it on a VM or a physical server ? Regards adai ... View more

Hi Peter,            Can you increase your RAM and CPU ? and tell us if you see any difference ? Also as you would have seen in the pop up during launch that only IE 8 is supported and not 9. How big is your environment ? What all functionality are you using like, Protection Performance etc ? Regards adai ... View more

Hi Peter,      What is the OS flavor of your DFM server  ? Are you seeing this sluggishness in OnCommand Console or even in Operations Manager Console and NetApp Management console too ? If its been 2 months since upgrade then its not due to what I mentioned above. Regards adai. ... View more

Short answer is there is no alternative. Either you can move to snapshot based backup using netapp lun. Or spin off a new DFM server and disable the perf data on this server. Though there is no guarantee that this will bring down the backup times to less than 5mins like a snapshots based backup as during a db backup verification and validation of the db take long time as well. ... View more

Hi Roy,      Short answer, there is no way to reduce the dfm backup time unless you go to a snapshot based backup using NetApp LUN and SnapDrive for Unix/Windows depending upon the DFM server OS flavor. If the databases are in unique locations, can the backup be restored without post-processing? Yes, but it would overwirte the perfdata and db, with whats  available in the backup. Regards adai ... View more

Yes, one can have different location for performance and database/db. You can use the following cli to move the db and perf data. [adaikkap@ /]$ dfm datastore setup help NAME     setup -- configure DataFabric Manager server data on a different location SYNOPSIS     dfm datastore setup [ -n ] [ -f ] { dfm-data-dir | [ -d dbDir ] [ -l dbLogDir ] [ -p perfArchiveDir ] [ -s scriptDir ] [ -r reportsArchiveDir ] [ -P pluginsDir ] } DESCRIPTION     -n specifies that the data present at target location will be used         without copying original data.     -f specifies that the data should be deleted from target location if it is not empty.     dfm-data-dir specifies DataFabric Manager server target root directory for data.     -d specifies the new location for database data file.     -l specifies the new location for database transaction log file.     -p specifies the new location for perf data files.     -s specifies the new location for script output data.     -r specifies the new location for report archival data.     -P specifies the new location for Storage System configuration plugins.     Example: dfm datastore setup /opt/dfmdata/              dfm datastore setup -d /opt/dfm/data/ -p /opt/dfm/perf/ -s /opt/dfm/script/. [adaikkap@ /]$ A typical db backup contains 3 things. database dir, perf data dir script pluign dir. In order for a snapshot based backup all of the above 3 should be in the lun other wise only a .ndb can be taken and not .sndb. Regards adai ... View more

Hi Peter,      There are two things that happen after upgrade to 5.0. Which were added as part of some house keeping of the database and the perfdata files. After upgrade to 5.0, the job history of protection Mgr/Backup Mgr are deleted//purge from the db beyond 90days. Which was not the case until 5.0. Same way the perfdata files are compacted on a weekly basis to remove data for stale volume in dfm db. Both these process are quite intensive on the first run due to the amount of data that needs to be purged/compacted. But once this first run finishes, it will improve your performance and recurring cleaning/house keeping will not have any impact. Regards adai ... View more

Provisioning Manager tries to prevent such things, that being the reason why it doesn't allow.Ideally this restrictions should be removed from Provisioning Manager depending the version of Data Ontap on which its fixed. Regards adai ... View more

I think you are being hit by this known issue 584186. Regards adai ... View more

Hi Reid,      Your understand is correct. Also, we are soon publishing the resource selection algorithm and  how it works. Which will help you even more. Regards adai ... View more

Hi Modi,             The priority is always for the individual aggr thresholds. Irrespective of the aggr overcommitment thresholds being modified before the aggr being added to respool or after being added to respool.When an aggr or a entire filer is added to the Resource pool all the constituent aggr get the overcommitment threshold from the respool if the "enable aggr overcommitment threshold" is checked. If the individual aggr threshold is meddled now that take precedence than the respool threshold that got set to 300 and 400 by default. If the enable aggr overcommitment threshold" is NOT checked, then the default aggr overcommitment threshold of 90 and 100 are applied. Now coming to you individual questions. Global values take effect if we leave the check-box un-ticked in the resource pool GUI (screen above) Use case would be if we don't want to micro manage each resource pool thresholds individually Not really, if respool threshold is un-checked it leave the aggr over commitment thresholds @ 90 & 100 instead of 300 and 400.Leave it unchecked if you don't wish to overcommit the aggr to 300 or 400 % Resource pool thresholds take effect if we enter the values in the resource pool GUI (screen above) overriding the global values. Use case would be if we want to have custom thresholds for aggregates that are part of that resource pool. In this case aggregates not part of the pool still rely on global values? Yes. Your absolutely correct. Aggr thresholds take effect if we set the values on the individual aggregate using "dfm aggr set .." overriding the global and resource pool values. Use case would be if we want to have custom thresholds for aggregates within a resource pool (to exclude or include from the selection criteria) ? Exactly and perfect example as to when we would want to tweak the individual aggr threshold. Regards adai ... View more

Hi  Stephen,                    The limitation if any should not be any different from what ontap support as the plugin uses Ontap API. Pls refer the ontap documentation. As far as I know and remember, Data Motion is the one that enforce volume limit per vfiler due to synchronous snapmirror limitations. Regards adai ... View more

OnCommand Plug-in is not same as oncommand 5.0 ... View more

Hi Tony,      That sounds bizzare, and we have never heard this. Can you give us more information on the following details. What was your old version. To which version you migrated ? Is there any timezone change between the two system ? Currently what version of  OC are you. This sounds like a bug or config issue and needs more investigation. Regards adai ... View more

Hi J,      I tried it with first level group also, but works fine in my case. I suggest you to open a case with Netapp support as it may need more back and forth information, or a copy of  your db will help solve this. As the operation you are trying to do is simply going to update the db tables in dfm sybase. Regards adai ... View more

Hi J,      I tried this in OnCommand 5.0, with group two level down( Global/Group/Sub_Group).In my case the controllers were direct members of the group did what you said and this is what i got.So more details from your end will help is this regard. Changed volume snapshot count threshold for volume sim735rtp1:/vol0 (322) to 255. Changed volume full threshold (%) for volume sim735rtp1:/vol0 (322) to 95. Changed volume too old snapshot threshold  for volume sim735rtp1:/vol0 (322) to 80weeks. Changed volume snapshot count threshold for volume sim735rtp1:/vol0.snapshot (323) to 255. Changed volume full threshold (%) for volume sim735rtp1:/vol0.snapshot (323) to 95. Changed volume too old snapshot threshold  for volume sim735rtp1:/vol0.snapshot (323) to 80weeks. Changed volume snapshot count threshold for volume sim735rtp1:/nfs_ds_demo_1 (324) to 255. Changed volume full threshold (%) for volume sim735rtp1:/nfs_ds_demo_1 (324) to 95. Changed volume too old snapshot threshold  for volume sim735rtp1:/nfs_ds_demo_1 (324) to 80weeks. Changed volume snapshot count threshold for volume sim735rtp1:/nfs_ds_demo_1.snapshot (325) to 255. Changed volume full threshold (%) for volume sim735rtp1:/nfs_ds_demo_1.snapshot (325) to 95. Changed volume too old snapshot threshold  for volume sim735rtp1:/nfs_ds_demo_1.snapshot (325) to 80weeks. Changed volume snapshot count threshold for volume sim735rtp1:/iscsi_ds_demo_3 (326) to 255. Changed volume full threshold (%) for volume sim735rtp1:/iscsi_ds_demo_3 (326) to 95. Changed volume too old snapshot threshold  for volume sim735rtp1:/iscsi_ds_demo_3 (326) to 80weeks. [additional messages trimmed...] Regards adai ... View more

Hi Balbeer,      I doubt if this will solve, AFAIK the lag monitor in  a local backup policy is based on success or failure of the the local backup job and not on creation of snapshots. Since in this case the schedule is set to none jobs wont be triggered by PM so lag time will not drop based on snapshot creation. As its only based on jobs success or failure. A Dataset lag can in a protection policy can define 2 things: The lag time between the current and the previous local backup The lag between the primary and the secondary Regards adai ... View more

Hi J,      Couple of questions to you. What version of DFM are you using ? Do all the nearstore belong to the group as direct members ? What version of ONTAP are your nearstores running ? Do Volume also belong to the group ? What is the hierarchy level of this group, ?( ie from Global how many levels down ?) Is it possible to past a screen shot of the error when you try to push it to all member of the group ? Regards adai ... View more

Hi Subramaniam,                          I am not clear on your question. Is your question why the lun was provisioned under testDS_11 and not testDS or how to list the members of a dataset  uisng API. The following iter api will get you the members of a dataset. dataset-member-list-info-iter-end dataset-member-list-info-iter-next dataset-member-list-info-iter-start esp the iter-next output array element dataset-member-info will give you the information you are looking for. The reason for testDS_11 instead of testDS could be one of the following. Provisioning Manager, creates a volume and keeps creating qtrees/lun inside the volume as long as the containing aggr has space or maxqtree/lun per volume count is not exceeded. In you case you may have created 10 volume before you created the FCP lun thats why the volume name is 11. or you may have deleted object information in your dfm db thats why you are still getting 11. Regards adai ... View more

Hi,      I have not seen this issue before. Issue like this are better handled by support as it may require some amount of debugging and logs to figure out whats happening. Regards adai ... View more

Hi Mark,             By default for any SnapVault/Qtree SnapMirror/Volume SnapMirror/OSSV relationship OC/DFM monitors and reports lag. The default values are 1.5days for lag warning threshold and 2.0days for lag error threshold. a) Fudge Protection Manager so that it WILL monitor the lag times of SnapShots created on the filer, or in a SnapManager If I understand correctly you want to monitor the lag time for relationship in that case use the thresholds that I specified. b) Figure out how to get SnapManagers like SM for Exchange to initialize it's dataset properley if it ISN'T one being used for SnapVault! AFAIK, only snapvault integration is supported with SME and PM. If you are looking for just snapshot monitoring then OC itself can report on the list of snapshots created on each volume. Regards adai ... View more

Hi Steve,               The option you mentioned is a hidden option. In order to see it you will have to first set it using the below cli. dfm option set pmMaxQsmRelsPerSecondaryVol=20. The default value for this options is 50. Regards adai ... View more

Hi Alfonso, We have a FAQ on how to with HP Open View but no experience with CA spectrum. See if this helps. https://library.netapp.com/ecmdocs/ECMM1278650/html/faq/index.shtml#_7.12 Regards adai ... View more