The key to configuring snapshot backups (after ensuring all your data is present on an ONTAP LUN) is to run the command " dfm backup diag ". How to configure Operations Manager snapshot backups. https://kb.netapp.com/support/index?page=content&id=1011875 What are the DFM database backup types - file based vs. LUN? https://kb.netapp.com/support/index?page=content&id=3011237 ... View more

Mark, this KB will help you do that: How can I change the DFM severity level associated with a particular event type? https://kb.netapp.com/support/index?page=content&id=3010964 Thanks, Kevin ... View more

Peter, the only way I know to remove them is using the "dfm fcswitch delete" command.  Without a SAN license (not sold since 3.3) I am not sure how to remove them.  The SAN license was dropped in DFM 3.3 (pg 32) https://library.netapp.com/ecm/ecm_get_file/ECMM1278604 # dfm fcswitch help NAME     fcswitch -- edit and list the managed FC switches SYNOPSIS     dfm fcswitch list [ -a ] [ -q ] [ <objects> ... ]     dfm fcswitch add [ -N ] { all | <objects> ... }     dfm fcswitch delete { all | <objects> ... } DESCRIPTION     The fcswitch command manages the list of FC switches,     which determines which switches the DataFabric Manager server monitors.     Adding FC switches to the list of managed switches enables     monitoring for those switches.  Deleting them disables     monitoring. Kevin ... View more

Jeff, the nodeStats table walk failure and resulting behavior leads to to believe you are hitting bug 395154 (ONTAP bug): http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=395154 You should open up a support case and refer to this bug.  The workaround listed will most likely not help you - instead the metrics on both the ip addresses and routing groups might need to be adjusted. Thanks, Kevin ... View more

Greetings Alain, The described behavior is expected when managing vFiler relationships using OnCommand Unified Manager. You can read more about this behavior in this KB: How does OnCommand discover and display SnapVault and SnapMirror relationships with a vFiler as one or both the endpoints of a relationship? https://kb.netapp.com/support/index?page=content&id=3013156 Thanks, Kevin ... View more

OnCommand Host Package does not support Multistore.  There is no work around. There will be a public report detailing this under bug 647436. http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=647436 ... View more

Greetings Tosho Yankov, Since you stated that you are a NetApp novice, I wanted to ensure that you were aware of the technical support contact information for future issues. You can open a technical support case at any time via the phone or web: https://support.netapp.com/   =>  https://support.netapp.com/portal?_nfpb=true&_pageLabel=supportassistance Technical Support 888.4.NETAPP (US and Canada) (888.463.8277) 00.800.44.638277 (EMEA/Europe) +800.800.80.800 (Asia/Pacific) Also, this is a forum specifically for the System Setup utility that is used to perform the initial setup of the hardware.  There are a number of support forums available that are monitored by subject matter experts in those particular areas that would be a better place to seek LUN presentation documentation. https://communities.netapp.com/community/products_and_solutions Thanks, Kevin ... View more

KB on adding custom comments in 5.x: https://kb.netapp.com/support/index?page=content&id=1014110 ... View more

Thanks for the screen cap Adai.  I looked for this information in the guide and found it on pages 201-202: ================================== Snapshot copy and Protection Manager update When using Snap Creator to create a Snapshot copy, register the Snapshot copy with Protection Manager and then use Protection Manager to manage SnapVault or SnapMirror. NTAP_SNAPSHOT_NODELETE Y Note: Both Operations Manager and Protection Manager are required. Additionally, you must configure a dataset created by Snap Creator within Protection Manager and create a schedule for that dataset (secondary). Snap Creator or Protection Manager can delete primary Snapshot copies. Protection Manager manages all secondary Snapshot copies and their retentions. ================================== I also found this info not in the IAG: In the config wizard, a check box is displayed where you can select "Protection Manager responsible for deleting snapshots on primary" and if it is selected the dataset is created with is-application-managing-primary-backup-retention = false and NTAP_SNAPSHOT_NODELETE is set to Y. If it is not selected  then the dataset flag is-application-managing-primary-backup-retention = true and NTAP_SNAPSHOT_NODELETE is set to N. What I do not know is what happens if you have set the dataset flag to false and then later set the config parameter to N.  It seems to me that might lead to a build up of the primary snapshots. ... View more

Hi Michael, The design is such that that applications should control the primary backup retention (backups it creates and then registers against the primary node of the dataset) and DFM/UM controls the secondary backup retention (backups that it creates). There is no way I am aware of to modify this behavior except through unintentionally designed behavior occurring in versions of SMO/SMSAP prior to 3.3.  And even though the backups in these cases can all be deleted by DFM/UM, it is not the design and leads to errors in the applications when they look for the backups they created and expect to be available. Also of note, SC 3.6 can handle its own vaults, without the need for integration with DFM/UM, and thus can control the retention on both sides of the relationship if desired. Kevin ... View more

You might find this KB useful. How to configure DFM Alerts for Volume Autosize, Maxdirsize Reach, or Snapshot Autodeletion https://kb.netapp.com/support/index?page=content&id=1011987 ... View more

That does not appear to be a case related to this behavior.   You would want to open a case for the behavior so that specific data can be collected and analyzed. Specifically you will want to provide a DFMDC, new autosupports, and system ids of the controllers involved in addition to the controller audit logs to show the backups that are being purged and allow investigation of what is deleting them.  You might also include "dfpm job detail JOBID" for a few backups.  ... View more

You are correct in the behavior that you should be seeing. I would need to see data on the backups that are getting removed prematurely to make further comments. Did you say you have an open support case? ... View more

Counts can only be modified by the CLI, there is no manner to modify them in the NMC.  The retention behavior will be a combination of the counts and time specified. You are using a mirror protection policy so there is no "retention" for the secondary - it will be an exact copy of the primary volume when the last protection was kicked off.  Your primary retention times match the secondary policy's primary node settings, but not the counts.  The primary retention policy will be on control of the primary backups. For example, based on the below settings you will always keep 1 of each style (hourly, daily, weekly, monthly) backup no matter their age.  However you will keep every backup that is younger than the time set in the policy. c:\>dfpm policy get -q "VMware local backup policy - AMARG Name=VMware local backup policy - AMARG Description=VMware local backup, Customized for AMARG retention Type=vmware backupScript= hourlyRetentionCount=1 hourlyRetentionDuration=172800  (2 days) dailyRetentionCount=1 dailyRetentionDuration=604800  (7 days) weeklyRetentionCount=1 weeklyRetentionDuration=2419200  (28 days) monthlyRetentionCount=1 monthlyRetentionDuration=7257600  (84 days) lagWarningThreshold=129600 lagErrorThreshold=172800 Your dataset currently has 2  hourly backups, 3 daily backups, and 1 weekly primary backup.  Based on their age and your primary policy settings this appears to match. The hourly backups are both under 2 days old.  The daily backups are all under the 7 day mark - expect to lose the oldest hourly and daily backups on the next backup.  That weekly backup is only 5 days old and therefore should remain for at least 3+ weeks from today and longer if you do not make a new weekly style backup.  Backup Id Backup Version   Retention Type Retention Duration (in seconds) Node Name   --------- --------------------- -------------- ----------------------------------------------    181147 21 Dec 2012 09:00:00  hourly 172800 Primary data    180525 20 Dec 2012 13:00:00  hourly 172800 Primary data    177872 16 Dec 2012 22:00:01  daily 604800 Primary data    177168 16 Dec 2012 00:00:01  weekly 2419200        Primary data    177102 15 Dec 2012 22:00:01  daily 604800 Primary data    176335 14 Dec 2012 22:00:01  daily 604800 Primary data ... View more

It would be beneficial to see the output of the following: 1) "dfpm backup list DATASET_ID" 2) "dfpm policy node get -q SECONDARY_POLICY_ID" 3) "dfpm policy get -q PRIMARY_POLICY_ID" ... View more

The retention settings are controlled in 2 locations: 1) the OCHP/primary backup retention is controlled in by the "Local Policy" visible in the virtual dataset within the OCUM UI (not the NMC). 2) the secondary backup retention is specified by the protection policy assigned to the storage service and must be viewed edited from the OCUM server CLI or the NMC.  OCUM Core should not be deleting the OCHP primary side backups that do not meet the configured retention.  if you suspect this is the case, the controller audit logs should be inspected to determine which system is authenticating to delete the backups.  ... View more

12Gb of RAM and 6 vCPUs should be plenty to work with - are you reserving the resources or allocating them?  For a heavy ProtMgr environment plus monitoring I recommend reserving half of these resources for the VM (6Gb RAM 3vCPU) and report back. FSRM is no longer supported nor sold, and it can add a large amount of data to the db which can slow down the server.  You might also consider upgrading to 5.0.2P1 or 5.1 64 bit to take advantage of the larger addressable memory space assuming the server is x64 - this would allow the server to work more efficiently especially if the db is larger (>4Gb). ... View more

Jeremy, When you run the command "dfpm backup list DATASET_ID" on the OC UM server are there primary backups listed or no backups listed? The backups not running on the OCHP side can be resource related.  Typically this failure coincides with errors in the system/app event logs regarding resource constraints - are you seeing any such errors in your event logs? ... View more

Try IE 8 if you cannot access Firefox 3.6.  I have seen this error once but it was browser version related. ... View more

It would be good to know if a restore of the 3.8 backup to another 3.8 server produced the same results as this is not an expected outcome of a db restore as you should see exactly the same data.  Is the missing data only in certain (custom) views? ... View more

Yes, the backup contains all the existing configuration, historical trending data, and perf data. However I recommend that for any migration a backup be restored to a similar major version server (4.x to 4.x) and then upgraded in place upgrade to a newer version (OnCommand UM 5.0.2P1 or 5.1). As of OnCommand UM 5.0 the db is encrypted and as of 5.1 Sybase is upgraded.  In my opinion it always safer to restore a db backup to a similar major version.  I am not stating the restore of an older db to a newer version will always fail, but upgrading a known working server will have a better chance of succeeding. ... View more

Which browser are you using to edit the alarm? ... View more

Apologies, the hotfix is applicable to any Windows Server 2008 R2 server. There is no published documentation that I am aware of for the reserved resources, although it has been requested to be added Installation/Setup guides. It has been observed that reserving server resources has resolved "out of memory" and missed scheduled job conditions in the past, particularly on the OCHP server which kicks off the backup jobs and then registers them to UM once completed (similar to Snapmanager product integration scenarios). ... View more