In which version of DFM or OnCommand are you hitting this issue ? This is  fixed in 4.0.2D9 You are hitting bug 514679 Regards adai ... View more

Which version of DFM/OnCommand are you using ? Where and when are you seeing this warning ? Regards adao ... View more

Do note the customization of data collection is available starting 4.0 and later. Regards adai ... View more

Hi Vivek,      Can you get the  output of the following cli ? Use dfm perf threshold list to get the list of thresholds you have set. Then from that get the id of the threshold in question and run the following cli. dfm perf threshold list -x <threshold id> Your output will be like this. [root@ ~]#  dfm perf threshold list -x 105 Threshold Id: 105 Event Name: system:cpu_busy Interval: 60 Enabled: Yes Object Info:         Id: 1273         Name: sim-4-1-182-99-sf         Type: filer Counter Info:         Counter: system:cpu_busy         Threshold Type: upper         Threshold Value: 20         Threshold Unit: percent [root ~]# Similarly also get the output of the following cli to see if the values really breached. [root@ ~]#  dfm perf data retrieve -o 1273 -V "CPU_USAGE" Timestamp       1273:cpu_busy ------------------------------------------------------------------------------- 2011-09-07 05:42:38     1.085 2011-09-07 05:42:54     0.802 2011-09-07 05:44:33     1.292 2011-09-07 05:45:54     1.132 2011-09-07 05:46:08     0.521 2011-09-07 05:46:34     1.743 2011-09-07 05:47:34     1.128 2011-09-07 05:49:24     0.820 2011-09-07 05:49:53     2.020 In order to get the object id( the value for -o, use the info from threshold list -x and use the Id under object Info).Similarly for the view name( the name of the view in which this counter is used or data is being collected) use the cli below or use the name from NMC. [root ~]# dfm perf view list CPU_USAGE View Name -------------------- CPU_USAGE [root ~]# Regards adai ... View more

Hi Thomas,     BTW, Why do you want to remove the timezone setting. Can you explain the same ? Regards adai ... View more

As far as i know %T is a mandatory setting and cannot be changed. Unless you use the script to generate your snapshot names.Below is the options for the same. [root ~]# dfm options list dpSnapNameOption Option           Value ---------------- ------------------------------ dpSnapNameOption global-format [root ~]# dfm options set dpSnapNameOption=junk Error: dpSnapNameOption: junk must be global-script or global-format. [root~]# dfm options list | grep -i dpsnap dpSnapNameFormat                      %T_%R_%L_%H_%N_%A dpSnapNameOption                      global-format dpSnapNameScriptPath dpSnapNameScriptRunAs dpSnapNameOption: Naming option for snapshots in Protection Man-            ager. The value can either be global-format or global-script.  When            user sets the value as global-format, they can specify the format            in dfm global option dpSnapNameFormat. When the user sets the value            as global-script, they can specify a script path in the dfm global            option dpSnapNameScriptPath and the user account in option dpSnap-            NameScriptRunAs.            dpSnapNameScriptPath: Absolute path to the script that will gener-            ate the snapshot name to be created by protection capability of            OnCommand.  Path can only be 127 characters long.  Snapshot name            length can only be 124 characters long. Name would be truncated if            it exceeds that limit. For name collisions, numeric suffix would be            added at the end of the snapshots. Snapshot name can have ASCII            alphabets, ASCII numbers, underscore â_â, hyphen â-â, plus sign â+â            and a dot â.â. All other characters will be converted to character            âxâ.            dpSnapNameScriptRunAs: On Unix systems, user account to run the            script specified in the option dpSnapNameScriptPath. It can only be            64 characters long. Regards adai ... View more

Is your source volume dedupe enabled ? If so can you get the output of the following cli ? dfm detail <volumename-or-id> | grep -i dedup or | findstr /i dedup if the DFM server is on windows. Regards adai ... View more

Hi Paul,      The History is kept even beyond 1year. In fact the data in the year history table is unlimted. From UI you would be able to access only upto 12months worth of data. To get data  beyond 1yr, if it exist use the dfm graph cli.  Below is a link to document on DFM and capacity management. Storage Capacity Management using OnCommand Operations Manager Regards adai ... View more

This is an existing issue, pls raise a case or add your call_rec to the bug specified by francois the NetApp Global Support. Regards adai ... View more

Hi Richard,      I think there is some misunderstanding. Let me try to clarify some. PM does not support creation of compression enabled snapmirror relationships.But it interoperates PM does not make a snapmirror.conf entry for all relationship its creates, except for those that are created using preferred interface and uses connections. Case 1:Where PM creates the relationships: ================================ So if you create a normal QSM or VSM relationship using PM it neither makes a  snapmirror.conf entry nor schedules in the same as below. fas-sim-1:/vol/qsm_src/- fas-sim-2:/vol/qsm_dst/qsm_dst_non_qtree_data - 0-59/3 * * * Instead the schedule are driven by DFM server scheduler service which does the scheduling as per the policy you use in PM. If you have the option hostPreferredAddr1/2 set in DFM for the source and destination filer of Snapmirror.And create a VSM or QSM relationship using PM then PM creates a connection and make these entries in snapmirror.conf fas-sim-1_fas-sim-2_1208568606=multi(192.168.98.12,192.168.98.13) fas-sim-1_fas-sim-2_1208568606:comp_vsm_src fas-sim-2:comp_vsm_dst compression=enable - - - - - (Note if 1 is set on primary then 1 in secondary is used. Its the respective interface and not 1 in source and 2 in destination is used) Even in this case the schedule are driven by DFM server scheduler service and not ontap.This applies to both QSM and VSM. So PM is not capable of creating a compression enabled QSM or VSM relationship. The same applies to SV also where we don't create the snapvault snap schedules. In order to have the SV traffic in a preferred interface the following options in filer should be set. ndpmd_preferred.interface. Case2:Where relationships are imported. First and foremost rule: PM does not delete any snapmirror.conf or snapvault schedule when the corresponding relationships are imported into a Dataset.This enables PM to interoperate with Compression enabled snapmirror. So to have a compression enabled relationship in PM have the relationship created in the filer and the corresponding conf entries.Import them into a data and have the schedule in PM fas-sim-1_fas-sim-2_1208568606=multi(192.168.98.12,192.168.98.13) fas-sim-1_fas-sim-2_1208568606:comp_vsm_src fas-sim-2:comp_vsm_dst compression=enable - - - - - It is advised to remove the schedule in the snapmirror.conf to remove the redundant scheduling. Make sure that hostPreferredAddr1/2 are not set on the source and destination filer of the compression enabled snapmirror filers in DFM. When a relationship is imported say like below which has snapmirror.conf entry as follows fas-sim-1:/vol/qsm_src/- fas-sim-2:/vol/qsm_dst/qsm_dst_non_qtree_data - 0-59/3 * * * and hostPreferredAddr1/2 are correspondingly set on the source and destination filer then PM makes an entry in the snapmirror.conf as follows fas-sim-1_fas-sim-2_1208568606=multi(192.168.187.12,192.168.187.13) fas-sim-1_fas-sim-2_1208568606:/vol/qsm_src/- fas-sim-2:/vol/qsm_dst/qsm_dst_non_qtree_data - - - - - Still the old entry remains. The reason why hostPreferredAddr1/2 should not be set for compression enabled snapmirror is because before every transfer we rewrite the snapmirror.conf with the above two entry in this process compression options is deleted as there is no support for it in NDMP or api. Hope this clarifies. Regards adai ... View more

Hi Richard,              I created a compression enabled relationship on the filer and imported the same into a dataset in DFM 4.0.2D1. C:\>dfm version dfbm.exe         4.0.2.7809 (4.0.2D1) dfdrm.exe        4.0.2.7809 (4.0.2D1) dfpm.exe         4.0.2.7809 (4.0.2D1) dfm.exe          4.0.2.7809 (4.0.2D1) dfmcheck.exe     4.0.2.7809 (4.0.2D1) dfmconfig.exe    4.0.2.7809 (4.0.2D1) dfmconsole.exe   4.0.2.7809 (4.0.2D1) dfmmonitor.exe   4.0.2.7809 (4.0.2D1) dfmperf.exe      4.0.2.7809 (4.0.2D1) dfmscheduler.exe 4.0.2.7809 (4.0.2D1) dfmserver.exe    4.0.2.7809 (4.0.2D1) dfmwatchdog.exe  4.0.2.7809 (4.0.2D1) eventd.exe       4.0.2.7809 (4.0.2D1) grapher.exe      4.0.2.7809 (4.0.2D1) C:\>dfm controller list ID   Type                     Host Name                           Host Address                              ProductId    Deleted ---- ------------------------ ----------------------------------- ----------------------------------------- ------------ --------   90 Active/Active Controller fas-sim-1                           192.168.98.10                             0099931871   No   91 Active/Active Controller fas-sim-2                           192.168.98.11                             0099931872   No C:\>dfm host get -q 90 host=fas-sim-1 hostLogin= hostPassword=******** hostLoginProtocol=rsh hostPreferredAddr1= hostPreferredAddr2= hostPrimaryAddress=192.168.98.10 hostRLMAddress= hostConsoleAddress= cpuTooBusyThreshold=95 cpuBusyThresholdInterval=00:15:00 hostPingMethod=echo_snmp hostAdminTransport=http hostNdmpLogin= hostNdmpPassword=******** hostAdminPort=80 perfAdvisorTransport=httpOnly prefsnmpVersion=1 useHostsEquiv=No maxActiveDataTransfers= perfDataExportEnabled=No defaultvFilerInterface= processHostIP= autoClientStatEnabled=No C:\>dfm host get -q 91 host=fas-sim-2 hostLogin= hostPassword=******** hostLoginProtocol=rsh hostPreferredAddr1= hostPreferredAddr2= hostPrimaryAddress=192.168.98.11 hostRLMAddress= hostConsoleAddress= cpuTooBusyThreshold=95 cpuBusyThresholdInterval=00:15:00 hostPingMethod=echo_snmp hostAdminTransport=http hostNdmpLogin= hostNdmpPassword=******** hostAdminPort=80 perfAdvisorTransport=httpOnly prefsnmpVersion=1 useHostsEquiv=No maxActiveDataTransfers= perfDataExportEnabled=No defaultvFilerInterface= processHostIP= autoClientStatEnabled=No C:\> Ran Multiple updates and found the conf entry to be intact. Now upgraded my dfm server to 5.0 and ran multiple update and still find my conf entry to be intact in snapmirror.conf. C:\>dfpm dataset list -x compression Id:                              392 Name:                            compression Protection Policy:               Mirror Application Policy: Description: Owner: Contact: Volume Qtree Name Prefix: Snapshot Name Format: Primary Volume Name Format: Secondary Volume Name Format: Secondary Qtree Name Format: DR Capable:                      No Requires Non Disruptive Restore: No Node details:    Node Name:           Primary data    Resource Pools:    Provisioning Policy:    Time Zone:    DR Capable:          No    vFiler:    Node Name:           Mirror    Resource Pools:    Provisioning Policy:    Time Zone:    DR Capable:          No    vFiler: C:\>dfpm dataset list -m compression Id         Node Name            Dataset Id Dataset Name         Member Type                                        Name ---------- -------------------- ---------- -------------------- -------------------------------------------------- -------------------------------------------------------        383 Primary data                392 compression          volume                                             fas-sim-1:/comp_vsm_src        386 Mirror                      392 compression          volume                                             fas-sim-2:/comp_vsm_dst C:\>dfpm dataset list -R compression Id         Name                        Protection Policy           Provisioning Policy Relationship Id State        Status  Hours Source                       Destination ---------- --------------------------- --------------------------- ------------------- --------------- ------------ ------- ----- ---------------------------- ----------------------------        392 compression                 Mirror                                                      389 snapmirrored idle    0.0   fas-sim-1:/comp_vsm_src      fas-sim-2:/comp_vsm_dst C:\>dfpm backup list compression Backup Id Backup Version        Retention Type Retention Duration (in seconds)   Node Name            Description                         Properties(Name=Value) --------- --------------------- -------------- --------------------------------- -------------------- ----------------------------------- -------------------------        12 22 Dec 2011 00:42:08  unlimited                                        Mirror        10 22 Dec 2011 00:42:08  unlimited                                        Primary data        11 22 Dec 2011 00:41:54  monthly                                          Mirror         9 22 Dec 2011 00:41:54  monthly                                          Primary data         8 22 Dec 2011 00:19:35  unlimited                                        Mirror         7 22 Dec 2011 00:19:21  weekly         3024000                           Mirror         5 22 Dec 2011 00:19:21  weekly         3024000                           Primary data         3 22 Dec 2011 00:16:51  daily          604800                            Mirror               test         1 22 Dec 2011 00:16:51  daily          604800                            Primary data         test C:\>dfm run cmd fas-sim-2 " rdfile /etc/snapmirror.conf" Job: 1 Host: fas-sim-2 Command:  rdfile /etc/snapmirror.conf Status: done Submitted: Thu Dec 22 00:45:28 2011 Attempts: 1 Login Protocol: rsh Use RLM Port: No Started: Thu Dec 22 00:45:28 2011 Completed: Thu Dec 22 00:45:29 2011 Stdout: #Regenerated by registry Tue Sep 27 08:58:29 GMT 2011 Stdout: fas-sim-1:/vol/qsm_src/qsm_qt1 fas-sim-2:/vol/qsm_dst/qsm_qt1 restart=never 0-59/3 * * * Stdout: fas-sim-1:/vol/qsm_src/qsm_qt2 fas-sim-2:/vol/qsm_dst/qsm_qt2 restart=never 0-59/4 * * * Stdout: fas-sim-1:/vol/qsm_src/- fas-sim-2:/vol/qsm_dst/qsm_dst_non_qtree_data - 0-59/3 * * * Stdout: fas-sim-1:vsm_src fas-sim-2:vsm_dst restart=never * 0-23 * * Stdout: comp_con=multi(192.168.98.12,192.168.98.13) Stdout: comp_con:comp_vsm_src fas-sim-2:comp_vsm_dst compression=enable - - - - - C:\> C:\>dfm version dfbm.exe         5.0.0.7636 (5.0) dfdrm.exe        5.0.0.7636 (5.0) dfpm.exe         5.0.0.7636 (5.0) dfm.exe          5.0.0.7636 (5.0) dfmcheck.exe     5.0.0.7636 (5.0) dfmconfig.exe    5.0.0.7636 (5.0) dfmconsole.exe   5.0.0.7636 (5.0) dfmmonitor.exe   5.0.0.7636 (5.0) dfmperf.exe      5.0.0.7636 (5.0) dfmscheduler.exe 5.0.0.7636 (5.0) dfmserver.exe    5.0.0.7636 (5.0) dfmwatchdog.exe  5.0.0.7636 (5.0) eventd.exe       5.0.0.7636 (5.0) grapher.exe      5.0.0.7636 (5.0) C:\> Can you provide the steps to reproduce  ? Regards adai fas-sim-2> rdfile /etc/snapmirror.conf #Regenerated by registry Tue Sep 27 08:58:29 GMT 2011 fas-sim-1:/vol/qsm_src/qsm_qt1 fas-sim-2:/vol/qsm_dst/qsm_qt1 restart=never 0-59/3 * * * fas-sim-1:/vol/qsm_src/qsm_qt2 fas-sim-2:/vol/qsm_dst/qsm_qt2 restart=never 0-59/4 * * * fas-sim-1:/vol/qsm_src/- fas-sim-2:/vol/qsm_dst/qsm_dst_non_qtree_data - 0-59/3 * * * fas-sim-1:vsm_src fas-sim-2:vsm_dst restart=never * 0-23 * * comp_con=multi(192.168.98.12,192.168.98.13) comp_con:comp_vsm_src fas-sim-2:comp_vsm_dst compression=enable - - - - - fas-sim-2> ... View more

you may want to delete the OLD FAS 3040(using dfm host delete -f) which still exist in the DFM db as deleted item.Also can you check if you are getting any host identity conflict event ? Also can you get us the output of dfm diag <hostid> Regards adai ... View more

Hi Richard, Can you get the output of the following command for your source and destination filers of snapmirror ? dfm host get -q <filerid/name> Regards adai ... View more

AS of now no. The only other work around I can think of is to create application data set and register the backups, but instead of registering the backup manually you can say dfm is responsible for primary backup. This need to be done using the SDK. Regards adai ... View more

Hi Erik,      During this head swap what all did you change ? IP address ? Host name ? Check the following FAQ. https://now.netapp.com/NOW/knowledge/docs/DFM_win/rel402/html/faq/index.shtml#_9.10 Regards adai ... View more

Check this link for all doc related to OnCommand/DFM OnCommand(DFM) and its related Technical Reports and specifically the link below for MSCS TR 3767-High-Availability Support forDataFabric Manager Server Regards adai ... View more

Hi Mark,      I have passed on this to my product manger thanks for your description and explanations. Regards adai ... View more

Is your question how to monitor the sybase service status in dfm ? If that's the case you should go for MSCS or VCS, which will take care of this. Regards adai ... View more

Hi Jeff,            Does the primary directories have space in between the names ? can you get the output of the following cli ? dfpm dataset list -R <dsname/id> Regards adai ... View more