Hi Renem, What is the timezone of the Linux and Windows box ? Are they in different time zone ? NMC uses the timezone of the machine on which it is running and not the DFM server time. Regards adai
... View more
HI Luca Paleari, You have hit a known issue, which is being fixed in the upcoming release version of OnCommand 5.1 expected soon. Below is the link to the public report for the same. http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=493743 Regards adai
... View more
This is what Provisioning Manager does. fas-sim-1*> snap autodelete sv_vol snapshot autodelete settings for sv_vol: state : on commitment : disrupt trigger : volume target_free_space : 5% delete_order : oldest_first defer_delete : prefix prefix : dfpm destroy_list : lun_clone,vol_clone,cifs_share But note, the prefix of dfpm is to safe guard the snapvault base snapshot, as its not locked( but only during active transfer) so there is still risk of losing your sv base snapshot. There is no problem with the snapmirror base snapshot as its always locked. Regards adai
... View more
The e0m is a low bandwidth interface and may not be suitable for data traffic(snapmirror/snapvault). Also you DFM/OC can talk to two interface. But if you are routing your data using preferred interface using connections then you can use e0m in dfm and specify other interfaces for data traffic in hostpreferredAddr1 and Addr2 for QSM and VSM connections. ndmpd_preferred_interface for SV. Regards adai
... View more
Hi I have couple of questions for you. Can you get the output of the following report for your qtrees or volume that are hosting the vm datastores ? dfm report view nfs-exports <qtree/volume name from dfm> What is the ontap version of the filers hosting your Datastore ? Is the vm datastores hosted on a vfiler volume/qtreee ? Regards adai
... View more
Hi Pedro, e0m can be blocked from having “data” traveling over it in 8.0.2 and higher: https://library.netapp.com/ecm/ecm_get_file/ECMM1277792 p36 Blocking data traffic on e0M Starting with Data ONTAP 8.0.2, you can block certain types of data traffic on the e0M interface, including SnapMirror transfers, SnapVault transfers, and data transfers that use the CIFS, NFS, and NDMP protocols. This optimizes the system performance by not allowing high-bandwidth data traffic on e0M, which is a low-bandwidth dedicated management interface. This task needs to be performed for storage systems that are upgraded to Data ONTAP 8.0.2 because the default value of the interface.blocked.mgmt_data_traffic option is off in such systems. However, in new systems installed with Data ONTAP 8.0.2, the default value of the interface.blocked.mgmt_data_traffic option is on. Step 1. To block all types of data traffic on e0M, enter the following command: options interface.blocked.mgmt_data_traffic on Or ONTAP can block certain protocols: P37 Restricting protocol access If a protocol is enabled for Data ONTAP, you can restrict the protocol's access to the storage system by specifying the host name, IP address, or network interface name. … • protocol is the name of the protocol you want to allow access to the storage system. It can be rsh, telnet, ssh, httpd, httpd.admin, snmp, ndmpd, snapmirror, or snapvault. Hope this helps and explains why NDMP is showing down.
... View more
Hi Stephen, If I read it right, you mean to say DFM 4.0.1 and not 4.1 as there is no such version. These are the version history of DFM/OC. DFM 3.4 DFM 3.5 DFM 3.6 DFM 3.7(3.7.x) DFM 3.8(3.8.x) DFM 4.0(4.0.x) OC 5.0 Regards adai
... View more
Hi As Arun, said earlier, this feature is coming in the next release of OnCommand namely5.1 if you would like to try this you can sign up for the beta. Regards adai
... View more
Hi Stephen, When you say old DFM server to new instance of OC5. Are they on different systems all together ? Old DFM Server: SERVER1 New OC5 Instance: SERVER2 If your situation is above, take a dfm backup using "dfm backup create" from SERVER1 and restore it in SERVER2 using "dfm backup restore <backupFileNameTakenInServer1> By doing this you dont have to do anything in the SMO dataset. If your situation is on the same server then you just have to run your OC5 installer and upgrade, which is seamless. Regards adai
... View more
Hi Frank, Pls read the following FAQ, from what I understand your IP address alone would change and other things like HostName and SystemID would remain the same. In that case you will have to update the following in DFM, but none of the protection relationship will be affected. dfm host set <hostname> hostPrimaryAddress=new-address Pls read the following link on headswap or changes to the settings of the filer. https://library.netapp.com/ecmdocs/ECMM1278650/html/faq/index.shtml#_9.10 Regards adai
... View more
Hi Adrian, Pls check this KB.1013796:How to rename a primary/secondary volume in a SnapVault relationship managed by PM dataset Also you may be a victim of this bug as well. To confirm on the same try to import the old relationships back into dataset and see if it throws any error as follows ? "There is no volume, qtree, LUN path, or OSSV directory named '44288'." If so pls generate/create a case and add it to bug442664 Regards adai
... View more
For version 4.0 there only exists a api and not CLI. Starting version 5.0 we have a cli as well for the same. API:dp-backup-version-delete CLI: [root@10 ~]# dfpm backup delete help NAME delete -- Delete a backup version. SYNOPSIS dfpm backup delete [ -p ] <backup-id> DESCRIPTION Delete a backup version given its id. Use the -p option to set the allow-deferred-delete flag to true. [root@10 ~]# Regards adai
... View more
Hi Scott, We would like to first understand your environment/situation. Do you have Dataset configured for the volume you are trying to migrate ? Or Are you trying to leverage Protection Manager to assist you in migrating the data from 32 to 64 bit aggr ? Now, coming to the limitation of PM esp with 32 and 64bit mirror. VSM cannot be created using any of the available DFM/OnCommand versions in NOW. But it can update a 32 to 64 bit relationship which is created outside PM and imported into a dataset. Also as per the TR doing inplace upgrade of aggr from 32 to 64 bit reduces the hassle of migration. Regards adai
... View more
When the retention is unlimited the retention setting does not apply. It can only be deleted manually by a user and not based on retention settings. Regards adai
... View more
BTW I got an update from one of our Subject Matter Expert that SnapManagerExchage does not use the above said attribute instead rely upon backup version with retention type set to unlimited and managed by SnapManager and not Protection Manager. Regards adai
... View more
If I remember correctly SME manages the snapshot retentions. It depends on what is the value of the api element "is-application-managing-primary-backup-retention" If this options is turned on while creating the application dataset, irrespective of the snapshot retention count, Protection Manager does not enforce deletion as per its count. By default its off. Even if this option is off, if the snapshot retention type is unlimited then irrespective of the retention count the snapshot are not deleted by Protection Manager. Can you run the following cli and tel me what is the retention setting ? dfpm backup list <dsid/name> Below is the snippet from the NMSDK DOC. is-application-managing-primary-backup-retention boolean optional If this input is true, Protection Manager does not enforce retention settings in the policy on the primary backups. Application is responsible for deleting primary backups, possibly by invoking dp-backup-version-delete API. If this input is false, Protection Manager deletes the primary backups according to the retention settings specified in the policy. Always present in the output. Default is false. Regards adai
... View more
The fix for this bug exist in version 5.0.1 which is already available in NOW. You are basically hitting this bug.Where even a workaround is specified. http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=541326 Regards adai
... View more
I dont know if this info is available via NMSDK, though we may try to get it via vCenter. BTW AFAIK no one has attempted this. Regards adai
... View more
Enabled or disable the alarm created for them. Alarms/alerts can be created via 2 ways namely for a particular event or based on event severity. If you have created it based on event severity then enabling or disabling the alert would affect alerts for other events too. Regards adai
... View more
Hi Michel, Can you try and get me some more details for me. Like the output of the snapmirror.conf entries from which controllers you are getting this error. Also details as to are these VSM or QSM if so are they being managed by Protection Manager or just being monitored in OC and are external relationship. Regards adai PS: I know that the logging is not specifying which controller it is, but with little work you should be able to find the filer based on the match between log error messages and snapmirror.conf.
... View more
Hi Michel, What version of DFM are you running ? I completely agree that its really poor logging as it does not say from which controllers and it looks a valid schedule as well. Regards adai
... View more
Hi Jerrod, I misunderstood you problem. Looks like you only want a list of controllers from OnCommand and add them to your System Manager. Is that right ? If that's the case you can create a db user as follows and run your query via port 2638. To access the embedded DataFabric Manager database for information rather than using the DataFabric Manager canned reports: Create a database user using the command dfm database user create. Enable access for the user created abov Run the desired SQL query for getting the LUN information using the command dfm databasquery run <SQL-Query>. This way you can get the list of host. The db views are documented under help general help of Operations Manager Console. More info on access to dfm db is available at the following TR. TR 3690 - Access to DataFabric Manager and Performance Advisor Data Using Database Access and Data Export Regards adai
... View more
In your filers you would see the snmp traphost being set as you dfm server. You will have to delete the same. fas-sim-1> snmp contact: location: adai-lxp authtrap: 0 init: 1 traphosts: 192.168.98.9 (192.168.98.9) <192.168.98.9> community: ro public fas-sim-1> After delete fas-sim-1> snmp traphost delete 192.168.98.9 fas-sim-1> snmp contact: location: adai-lxp authtrap: 0 init: 1 traphosts: community: ro public fas-sim-1> Regards adai
... View more