NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

VMware Solutions Discussions

correct export rules are specified in the ontap_conf​ig.txt file

smokey007uk
3,810 Views

Hello All

 

Seeing this message when trying to run SRM , fun part is that the documentation , does not show me , where export rules are added to the config file

 

Am using this with ontap 8.3.1 CDOT

 

Does the actual ontap_config.txt file need to be modified or is this a misleading error msg when trying to run SRM test and it fails to create snapshots

 


########################################################################
# Copyright (c) 1996-2012 NetApp, Inc.
# All rights reserved
########################################################################

#This file mentions configurable parameters for netapp arrays
#If you want netapp api's to run over secure HTTP which uses SSL, set "ssl = on"
#If you want netapp api's to run over normal HTTP because the environment is secure set "ssl = off"
#By default ssl is disabled
#Example:
ssl = on
#ssl = off

#NFS Exporting Options
#root = yes/no (default is yes)
root = no
#By default the Disaster Recovery NAS Adapter will export all volumes with
#root access granted to the ESX hosts. If your environment does not use the
#root field on exports you can set this option to no, preventing this access.
#This is useful if you have configured your environment to use a non-root user
#to access datastores. You might want to prevent root access to Site Recovery
#Manager recovered datastores.

#nosuid = yes/no (default is no)
nosuid = no
#Specifies whether the Disaster Recovery NAS Adapter will export all volumes
#with the nosuid property.

#anon = uid (desired anon uid, default is none)
anon =
#By default the Disaster Recovery NAS Adapter will not export volumes using
#anon flag. To force volumes to be exported with an anonymous security
#identifier, enter the desired anon user id. For example, anon=0

#sec = sys (default is sys)
sec = sys
#Allows customization of the NFS export security type.


#Thin provisioning option. This options is used by the SRA only when running a
#SRM DR test. By default the NetApp SRA creates thin provisioned volumes for
#SRM DR test.

#volume_guarantee = none/file/volume (default is none)
volume_guarantee = none
#Controls the value of the volume guarantee option on all volumes created for
#DR test.

#lun_space_reservation = yes/no (default is no)
lun_space_reservation = no
#Controls whether the LUNs recovered for DR test are set with space
#reservations enabled or disabled.

#import_replication_settings=on\off(default is on)
import_replication_settings=off

#generate asup messages along with events (default is off)
enable_asup_message=off

#isIPv4 = yes/no (default is yes)
#This option will be used while resolving the hostnames. Nfs Hostname is resolved to IPv4 addresses if this option is yes else it is resolved to IPv6 addresses.
isIPv4 = yes

import_snapmirror_policy=on
replication_disruptive_test_failover=off

#maximum number of protection group per recovery plan , by default there will be one protection group per recovery plan
#modify the value of this parameter if there are more than two protection groups in a single recovery plan
num_protectiongroup_per_recoveryplan = 2

1 REPLY 1

georgevj
3,733 Views

Any reason for setting the "root=no" parameter?

 

#NFS Exporting Options
#root = yes/no (default is yes)
root = no

 

 

Also, this post seems like discussing the similiar issue. Please have a look.

http://community.netapp.com/t5/FAS-and-V-Series-Storage-Systems-Discussions/VMWare-SRM-5-1-with-NetApp-SRA-2-0-1-over-NFS-Error-Failed-to-create-snaps...

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.
Public