Hi Hugues, What is the basis of recommending two different DFM versions for monitoring and Backup/Restore. Infact Backup/Restore depends upon monitoring. Moreover huge improvment/features are added in 3.8.1/4.0 with respect to monitoring/Backup/Restore. Regards adai
... View more
When protection manager provisions a snapmirror destination volume it creates it to the size of the containing aggregate with volume guarantee set to none. So you dont need to autogrow the volume. Regards adai
... View more
Hi Chris, To specify a preferred interface for backups. Pls specify the following options in the filer. filer> options ndmpd.preferred_interface ndmpd.preferred_interface e0b filer> Protection Manager will use the perferred interace set by the above options on the filer, for backup transfers. Below is the job snippet, which show whats the interface thats being used. Event Id: 1077646 Event Status: normal Event Type: job-progress Job Id: 50125 Timestamp: 17 Nov 2009 19:14:06 Message: Retrieving preferred interfaces Error Message: Event Id: 1077647 Event Status: normal Event Type: job-progress Job Id: 50125 Timestamp: 17 Nov 2009 19:14:06 Message: Retrieved preferred interfaces (XXX.XXX.XXX.XXX) Error Message: Regards adai
... View more
Hi Lee, Why don't you file a burt so that one of the engineers can look at it. As people in the community suggested the obvious and know issue that impacts qtree capacity/quotas. Now this needs more investigation. Regards adai
... View more
So that's where the links in the storage capacity panel comes into picture. Each of those link give details about each kind of object like, volume,qtree,lun or aggr. And further, the reports give more info on each kind of space management like, thin provisioning ie volume guarantee Overcommittment @ volume level for qtree/quotas, look at volumes-quota-committed and overcommittment @ aggr level for none guarantee volumes. look at aggregate-space-summary report So there are report for each one. So BTW is there any specific calculation you are looking for ? Regards adai
... View more
Physical space is the size of each disk, the raw capacity of the disk. The storage space and physical space will never match, as there are many things like thin provisioning,due to which you can create volume of size greater than your aggr. like raid sizing and few more. Regards adai
... View more
Hi Kevin, That's true we will soon update you on what is the approach(TR/KB/Admin guide) we are taking to give an high level info on the same. BTW can you create a similar thread in the other community ? Regards adai
... View more
Hi Kevin, The reason i havent disclosed the internal algorithms is because most of these are patentalbe or patented.So i dint want to discuss this. Can you move this thread to other closed community of StorageManagement Software ? Where we can take up this ? Regards adai
... View more
Hi David, I am not sure if you have already seen this TR. http://media.netapp.com/documents/tr-3690.pdf This completely explains how to access the dfm database views. Using third-party tools. Regards adai
... View more
The default sort order for custom reports is based on the first field of the report. Nevertheless, while viewing the report you can use the options –s to specify the sort field, when using dfm report view. with GUI you can use the column header to sort. Regards adai
... View more
Hi hill, Generally, the least used aggr is taken(which has more free space), also space balancing is done when repetitive provisioning is done. Starting DFM 3.8 we do have manual resource selection for Primary provisioning. There are also controls given to user to control/dictate how to select the best aggr within a respool by the following ways. [root@lnx/]# dfpm reslimit set Valid options are maxFlexVols Maximum number of FlexVols per storage controller maxCPUUtilThreshold Maximum CPU utilization threshold of storage controller maxDiskUtilThreshold Maximum Disk utilization threshold of an aggregate maxDedupeSizeInGB Maximum Deduplication size of a storage system model and ONTAP version (in GB) [root@lnx /]# Regards adai
... View more
No. It cant be changed.Even when you have acknowledged, the status is maintained so that when a normal event arrives for the same object(ie volume/qtree/filer etc) it can be neutralized and its status changes to green. There is one other possibility where you can change the severity of the event it self so that the color doesnt change. For example, a volume's capacity has 3 events, volume Full volume NearlyFull volume Normal. Of these full event has a status color of red, nearly full yellow and normal green. If you are not bothered by the Nearly full event you can the event severity to Information/Normal so that its status color remains green instead of yellow. so in a way the status color stays green. Regards adai
... View more
Hi srikanth, As saravanan said this report was introduced or rather made as a canned one starting DFM 3.7.But the same can be still created using custom reports infrastructure. Below are the fields for the same. [root@lnx]# dfm report view Aggr-Committed help Aggr-Committed Report (Aggr-Committed) Catalog Name: Aggregate Display Tab: Aggregates Catalog Field Field Name Format --------------------------------------------- --------------------------------------------- --------- Aggregate.Id Aggregate Id Aggregate.Name Aggregate Name Aggregate.StorageSystem Aggregate Storage System (A) Aggregate.TotalSpace Aggregate Total Space KB Aggregate.Used Aggregate Used Capacity KB Aggregate.UsedPct Aggregate Used Capacity % 1 Aggregate.BytesCommitted Aggregate Bytes Committed KB Aggregate.BytesCommittedPct Aggregate Bytes Committed % 1 Aggregate.DailyGrowthPct Aggregate Daily Growth (%) 1 Aggregate.DaysToFull Aggregate Days to Full Default sort order is Aggregate.Id. [root@lnx]# Also i installed 3.6 and i was able to see the reports. [root@lnx]# dfm report view aggregates-snapshot-capacity Object ID Aggregate Filer Snapshots Disabled Snapshot Autodelete Snap Reserve Total Snap Reserve Used Snap Reserve Used(%) --------- --------------- ----------------------------------- ------------------ ------------------- ------------------ ----------------- -------------------- 96 PUCKER_RAID4_01 bekham off on 0 0 90 aggr0 davidoff on on 0 0 94 adai_juno2 chinki on on 0 0 92 adai_juno1 chinki on on 0 0 Totals [root@lnx]# dfm version dfm 3.6 (3.6R1) [root@lnx1]# Regards adai
... View more
Yes.The download link at the end of the page does give the zip file. As you mentioned if you click on the zip file link, it leads to license agreement page at the bottom of the page once you accept it gives the download link. Regards adai
... View more
Currently no. But there is a tool written by one of our QA folks that does the same. Take a look at the link below. http://communities.netapp.com/docs/DOC-2402 Regards adai
... View more
Max records is=Collection Period/Sampling interval. In your case =604800/60=10080. This will change automatically when you change your collection period or sampling. If you reduce any of these that might reduce the max records then you must you -f options in the perf data modify. -f it forces the change of sample rate and retention period when the number of records decrease Used size is the currently used size. Projected size is the max size to which this can grow with the current sampling and collection period. this field is available starting next release. Regards adai
... View more
Will give the details of current retention. [root@lnx ~]# dfm perf data list Counter Group Host Name Sample Rate Retention Period Max Records Used Space Max Projected Space ------------------------- ---------------------------------------- --------------- ---------------- ---------- --------------- -------------------- Use dfm perf data modify to change the retention. [root@lnx ~]# dfm perf datas modify help NAME modify -- Modify the interval and collection details for a counter group SYNOPSIS dfm perf data modify [ -f ] -G <counter-group-name> [ -o <host-name-or-id> ] [ -s <sample-rate> ] [ -r <retention-period> ] DESCRIPTION Modify the interval and retention details for a counter group. Specify a positive number, optionally followed by a time period suffix to indicate seconds, minutes, hours, days, or weeks. The default time period suffix is seconds. 'host-name-or-id' is mandatory for default counter groups. Use -f option to force the change of sample rate and retention period when the number of records for the view decreases. [root@lnx ~]# Regards adai
... View more
Hi Terrance, In cli there is an options to do this. The option is -P but some how this got missed in the cli help and man pages. This is fixed in one of the upcoming release(cli help and man pages) But still the option works in 3.7 and 3.8 releases of DFM. Below is the option name and its possible values. -P time frame signifies the period to fetch performance data. Valid values are 'last, 1d, 1w, 1m, 3m and 1y'. This option is valid only in conjunction with performance reports. Below is the help of the fixed cli. [root@lnx ~]# dfm report view help NAME view -- Generate one of several reports SYNOPSIS dfm report view [ <options> ] <report-name> [ <report-arguments> ... ] DESCRIPTION The report command runs one of several pre-defined searches and presents the results. Use 'dfm report list' to get the list of reports. Use 'dfm report view <report-name> help' to see the description of a report. The options are -g <group-id or group-name> -F <output-format> -l <lines> -q (quiet) -s <sortby-field> -x (show all fields; only in perl output format) -N <repeat-for> -i <repeat-interval> -t <timeout> (in seconds; for streaming reports) -H show deleted objects -P time frame signifies the period to fetch performance data. Valid values are 'last, 1d, 1w, 1m, 3m and 1y'. This option is valid only in conjunction with performance reports. [root@lnx ~]# Regards adai Regards adai
... View more
Hi Martin, Starting DFM 3.8 while importing a VSM relationship into protection manger we don't remove the snapmirror.conf entries anymore. 1.Having said that coming to your case, if you have an compression enabled VSM relationship set in filer and import the same then we do support it, provided the hostPreferredAddr1 or hostPreferredAddr2 is not set for both the source and destination filers. So the answers is we have an workaround in 3.8 of supporting compression by the way of importing a compression enabled VSM relationship and the above said opiton not being set in the source and destination filer in operations manager. 2.If any one of the options is set on both the source and destination filer then in that case the compression is not supported even in case of imported compression enabled VSM relationships . So now suggestion with respect to 1. Create the snapmirror connection with compression enabled and scheduled set to none, as when we import and PM starts running the updates you will only have PM run schedules and not the filer run schedules.This will save you snapshots and unnecessary transfers happening other what you intended (meaning updates run by both PM and filer) though the filer run update snaphot wont be visible in your restore wizard of PM as we did not take it. Regards adai
... View more