About kryan

kryan · ‎2013-07-24

Given the LUN error messages it seems that you are using LUNs. If you were using NFS, there are two help topics available that might assist you in this restore task. They can be found under "Managing virtual inventory" -> "Mounting and unmounting backups in a VMware environment". 1. Setting the preferred network interface 2. Mounting backups on remote VMware ESX server (7-Mode only) 1) If you take a new on-demand backup and transfer it to secondary are you able to restore from the older backup that already failed to restore? 2) Which versions of UM, ONTAP, and Host Package are you running?

kryan · ‎2013-07-18

DFM/UM should have detected and logged an event for an offline volume. I recommend that you open a support case to determine the cause of the monitoring failure. Troubleshooting this will require the following - it would be good to have it ready when you open the case: 1) "dfm report view events" CLI output 2) "dfm report view events-history" CLI output 3) DFMDC 4) "dfm host diag CONTROLLER" CLI output to the affected controller DFM will not log volume autosize events unless you have followed the steps in this KB: How to configure DFM Alerts for Volume Autosize, Maxdirsize Reach, or Snapshot Autodeletion Since I notice you are looking at the legacy OM UI I want to point out that all versions of DFM prior to 5.0 will go end of support as of 12/01/2013: https://support.netapp.com/info/web/ECMP1147223.html Thanks, Kevin

kryan · ‎2013-07-17

Your license key will in fact work on the new server and version of software. Theoretically the restore you plan should succeed. However, if it fails or if you notice any undesired behavior after the restore I suggest that you install 4.0.2 on the new server, restore that same backup, then upgrade as I suggested above. A particular step might still fail but we will be able to zero in on the failure at that point. Thanks, Kevin

kryan · ‎2013-07-16

Hi Siddartha, To upgrade from 4.0.1 to 5.2 I recommend that you create a backup (also if running on a VM, stop the DFM services and create a VM snapshot), upgrade to 5.0.2 to prune any excess performance data (bug 439756), then after another backup, upgrade to UM 5.2. Be aware of the following: 1) As of UM 5.1 (and higher) you will need to choose a mode upon install/upgrade - either 7DOT or cDOT. The choice will indicate the mode of controllers that UM server can manage. 2) 5.2 is 64 bit software only 3) Due to the database pruning process that occurs upon the 5.2 upgrade or db backup restore the time to complete will potentially be much longer than previous upgrades/restores. As always, I recommend that you test this process in a sandbox environment prior to performing it on the production server. As to the inodes question, I am not certain of the exact question but am hoping these KBs might be of assistance: DFM: How to create a report on volume inode utilization https://kb.netapp.com/support/index?page=content&id=1012675 Can the values for the Inodes Almost Full event be adjusted in DataFabric Manager? https://kb.netapp.com/support/index?page=content&id=3012207 Thanks, Kevin

kryan · ‎2013-07-15

I was referring to note 5521 under UM Core IMT fields discussing the versions of SDW/SDU that can be used for snapshot style UM backups (its own database/perf data) and the DR feature that can be used to mirror the UM data. I expect that the SnapDrive IMT records will state UM Core compatibility and after checking I observed that SDU lists UM 5.2 compatibility whereas SDW only shows UM 5.1. I am investigating the status of the SDW IMT records. Compatibility does indeed matter - if you do not see a particular combination of versions listed within IMT you can assume it was not tested to work.

kryan · ‎2013-07-15

The versions of SnapDrive listed in the IMT from the Unified Manager perspective are either for UM based snapshot backups (as opposed to archive) or DR style mirroring of the database location. I recommend that you will want to review the SnapDrive IMT components for integration compatibility with versions of UM.

kryan · ‎2013-07-12

Which version of Snapdrive and for which purpose? Snapshot backups or DR functionality? Kevin

kryan · ‎2013-06-26

I believe that SDU supports MPIO and iSCSI, however the SDU interactions with UM with MPIO/iSCSI configuration is currently being treated as an RFE. I have already added your support case to RFE 434447. If you can't use single path or FCP, then you will need to use archive DFM backups.

kryan · ‎2013-06-26

OnCommand UM can send SNMP traps to traphosts via triggered alarms. It can also receive traps from monitored hosts and process them. If the trap has a builtin eventtype (dfm evenettype list) UM will log a new event that can then be used for triggering alarms.

kryan · ‎2013-06-25

Yes, HP == Host Package. The product to use as a follow on to SMVI is VSC, not OCHP. OSSV is not tied into VSC nor OCHP. UM can manage OSSV client backups and can manage the OSSV services using the NetApp Host Agent (NHA), not to be confused with the Host Package.

kryan · ‎2013-06-25

I just tested creating an alarm using the NMC against a UM 5.1 7-Mode VM with 4 hosts and default monitors (no special VM reservations) and the alarm created in seconds. Kevin

kryan · ‎2013-06-25

Todd, I see evidence under bug 434447 that the combination of MPIO and iSCSI might be causing this problem. Can you try this without MPIO or use an FCP LUN? Thanks, Kevin

kryan · ‎2013-06-25

Pre-reqs for the OnCommand Host Package include: Common Name Distributed Installer Windows 2003 SP2 WindowsServer2003-KB914961-SP2-x86-ENU.exe .NET 3.5 dotnetfx35.exe and NDP35SP1-KB958484-x86.exe Win2008 security fix WindowsServer2003-KB968730-x86-ENU.exe PowerShell 2.0 WindowsServer2003-KB968930-x86-ENG.exe There will not be any enhancements made to the HP software after the upcoming 1.3 release - this is something to keep in mind if you are just beginning to deploy it.

kryan · ‎2013-06-24

Hello, .Net 3.5 is a requirement for installing and using the OnCommand Host Package. If you are not installing that software then there is no need to install the .Net components on the server. Thanks, Kevin

kryan · ‎2013-06-24

Todd, Where are the UM binaries installed? Can you share the output of "dfm about |grep Installation"? How to configure Operations Manager snapshot backups. https://kb.netapp.com/support/index?page=content&id=1011875 Thanks, Kevin

kryan · ‎2013-06-24

Hello Ben, There are few areas to investigate when noticing slowness in the NMC. Since this is a new installation (not a restored db backup) we will rule out large perf data files as a cause of the slowness. 1) Are you observing this slowness in any other area of the NMC? Any portions of the Web UI or OnCommand Console? 2) Where is the NMC installed in regards to the UM server it is communicating to? Is it installed on the UM server? The same subnet? Across a WAN? 3) Are the CPU and memory resources for the UM VM reserved and not limited in any fashion? Thanks, Kevin

kryan · ‎2013-06-24

Hello, please share the version of Unified Manager you are using. Thanks, Kevin

kryan · ‎2013-06-21

Hi Ken, You can find a very detailed thread on this topic posted within this community: https://communities.netapp.com/message/88788 Thanks, Kevin

kryan · ‎2013-06-21

Using the default settings of UM 5.1, in order to produce a host down event/alert the host would need to be down for a significant amount of time. This behavior was changed in UM 5.2 under bug 614983 (no public report at this time). OnCommand Unified Manager Core uses five different methods to identify if a host is down: echo http snmp ndmp echo_snmp <== default The default behavior for a host down monitor run is a ping using ICMP echo and then snmpwalk. UM will retry each method a pre-configured number of times with varying timeouts, as seen below. While the ICMP retries and timeouts have remained the same over the 5.x code line, the SNMP timeouts were increased in UM 5.1 for 7DOT and even more for 5.1 cDOT installations. Due to changes under bug 614983, if pingMonTimeout is set to less than or equal to 5 seconds, then the SNMP timeout for host down (pingmon) monitoring will be 5 seconds. If the pingMonTimeout is set to a value greater than 5 seconds, then the pingMonTimeout is used as the SNMP timeout. The global MonSNMPTimeout is used for all other SNMP connections. This applies to both 7DOTand cDOT versions of UM 5.2. =============================================== UM 5.0.x default values: monSNMPRetries 4 monSNMPTimeout 5 hostPingMethod echo_snmp pingMonInterval 1 minute pingMonRetryDelay 3 pingMonTimeout 3 =============================================== UM 5.1 7DOT default values: monSNMPRetries 4 monSNMPTimeout 60 hostPingMethod echo_snmp pingMonInterval 1 minute pingMonRetryDelay 3 pingMonTimeout 3 =============================================== UM 5.1/5.2 cDOT default values: monSNMPRetries 4 monSNMPTimeout 300 hostPingMethod echo_snmp pingMonInterval 1 minute pingMonRetryDelay 3 pingMonTimeout 3 =============================================== Therefore, if a clustered ONTAP controller is down for less than 5 minutes, UM 5.1 will not report it as down as it would not have exceeded the first timeout value for the host down check. If the ping method is changed to to echo or http the node down event is logged. Changing the monSNMPTimeout to the 5.0.x default value of 5 seconds allows UM to determine the host down status with the echo_snmp method. However, it is not recommend that this value be adjusted lower than the default for cDOT UM 5.1 servers as some SNMP transactions can take a few minutes to complete and should not be sent multiple times under 5 minutes.

kryan · ‎2013-06-21

Hello, Per the UM 5.1RC1 Admin Guide page 66 https://library.netapp.com/ecm/ecm_download_file/ECMP1153167 , Active Directory groups can be added as DFM admins. Active Directory user group accounts The DataFabric Manager server recognizes two types of users namely Administrator and User, thereby allowing domain administrators the ability to define roles based on a company’s organizational hierarchy. To set up administrator accounts as a user group, use the following naming convention: <AD domain>\group_dfmadmins . In this example, all administrators who belong to group_dfmadmins can log in to the DataFabric Manager server and inherit the roles specified for that group. Thanks, Kevin

kryan · ‎2013-06-21

Hi Graeme, I would not expect that to be a configuration problem within UM since the hostPassword is only entered once for the entire cluster and if works one time it should continue to work. This might be indicative of a node configuration problem or network access to a particular node(s). Does the warning only occur for one node (SEN_SAN_CLU01) or all of them? Kevin

kryan · ‎2013-06-21

Greetings Graeme, can you provide us the version and mode of UM you are using as well as specifically where you are observing the warnings? Thanks, Kevin

kryan · ‎2013-06-06

No, UM 5.1 does not remove the ONTAP schedules upon import, so the schedules should be intact unless someone removed them. Kevin

kryan · ‎2013-06-06

Hello, you did not mention the version of DFM/UM you are using, however all recent versions of the software will not modify the existing SV schedule on the controllers when importing a relationship into a dataset. Therefore, if there is/was an existing schedule on the controllers driving the updates (regardless if DFM/UM was managing them), they should be manually removed to avoid firing off extra/unplanned backups. I am not sure why you did not see those BizConn/Backup Manager based backups continuing to occur, but I would have expected them along with the Protection Manager based backups. Kevin

kryan · ‎2013-06-05

There is no eventtype defined for such a condition in UM (dfm eventtype list). If a trap is triggered/sent via ONTAP for that condition then you could configure the UM server as a traphost in the controller(s) to have an informational event logged in UM. However you will need to write a script to parse the contents of those events (scheduled to run via an alarm) and then take further actions.

Re: Host service can not mount backup snapshot from remote site

Re: DFM is not picking all the events from Filer

Re: How to upgarde the DFM Version from 4.0.1. to 5.2

Re: How to upgarde the DFM Version from 4.0.1. to 5.2

Re: Changing DFM Installation Path Before Upgrading

Re: Changing DFM Installation Path Before Upgrading

Re: Changing DFM Installation Path Before Upgrading

Re: Unable to set up Snapshot backups: Data not present on LUN

Re: Quota notification email

Re: When installing OnCommand Core 5.0 what .Net components do you need?

Re: DFM so s...l...o...w....when working with alarms

Re: Unable to set up Snapshot backups: Data not present on LUN

Re: When installing OnCommand Core 5.0 what .Net components do you need?

Re: When installing OnCommand Core 5.0 what .Net components do you need?

Re: Unable to set up Snapshot backups: Data not present on LUN

Re: DFM so s...l...o...w....when working with alarms

Re: importing qsm external relationship into dataset with no protection schedule wipes snapmirror co...

Re: Using AD security groups when defining user roles

Re: Intermittent Host Login Failed warnings

Re: Using AD security groups when defining user roles

Re: Intermittent Host Login Failed warnings

Re: Intermittent Host Login Failed warnings

Re: OnCommand Backup Manager and Protection Manager

Re: OnCommand Backup Manager and Protection Manager

Re: Is there an alert/event for Max Volume Count per controller reached or almost reached?