About creating backup policies for Clustered Data ONTAP with Replication Director — NetBackup 11.1 | Cohesity Documentation

Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

About creating backup policies for Clustered Data ONTAP with Replication Director — NetBackup 11.1 | Cohesity Documentation

About creating backup policies for Clustered Data ONTAP with Replication Director

Keep in mind the following considerations when you configure backup policies for Clustered Data ONTAP with Replication Director.

Table: Backup policies for Clustered Data ONTAP

Policy type	Considerations
Standard	For a Standard policy, make sure that the Storage Virtual Machine (SVM) can resolve the NetBackup client's host name by running the following command on the cluster shell: network ping -lif-owner vserver -lif lif-name -destination Netbackup-client When you create a mount point, you should keep the following in mind: If the SVM name is used to create a mount point for a volume that is exported by an SVM on the NetBackup client, you should enter the name of the SVM exactly as the OnCommand Unified Manager sees it. If the SVM name in the OnCommand Unified Manager is a fully qualified domain name, you must use the SVM's fully qualified domain name when you create the mount point. The name is case-sensitive. Alternatively, you can use the IP address of the SVM LIF to specify a mount point instead of the SVM name. Consider the following examples: When you create a mount point on the NetBackup client for volume "vol_nfs" that is exported by an SVM named "vs1", the nfs volume name must be specified as "vs1:/vol_nfs". You would use the command "mount vs1:/vol_nfs /mnt/vol_nfs". If you specify the nfs volume name as "VS1:/vol_nfs" or "vs1.example.com:/vol_nfs" then the snapshot job fails. When you create a mount point on the NetBackup client for volume "vol_nfs2" that is exported by an SVM named "VS2.example.com", the nfs volume name must be specified as "VS2.example.com:/vol_nfs2". You would use the command "mount VS2.example.com:/vol_nfs2 /mnt/vol_nfs2". If you specify the nfs volume name as "vs2.example.com:/vol_nfs2" or "VS2:/vol_nfs2" then the snapshot job fails. When you create a mount point on the NetBackup client for volume "vol_nfs3" that is exported by an SVM with the LIF "10.67.212.20", the nfs volume name must be specified as "10.67.212.20:/vol_nfs3". You would use the command "mount 10.67.212.20:/vol_nfs3 /mnt/vol_nfs3". See Configuring a Standard or MS-Windows policy to protect NAS volumes or SAN-connected devices. Note: Replication Director for NetApp Clustered Data ONTAP supports NAS only at this time.
MS-Windows	For a MS-Windows policy, make sure that clocks are in sync for the following: the domain controller that is used for the Storage Virtual Machine's (SVM) CIFS server and the cluster hosting the SVM. Make sure that the NetBackup Client Service and the NetBackup Legacy Client Service are running under an account which has read and write access to the shares that the SVM exports. When you create a mount point, you should keep the following in mind: If the SVM name is used to specify a share that is exported by an SVM in a policy, you should enter the name of the SVM exactly as the OnCommand Unified Manager sees it. If the SVM name in the OnCommand Unified Manager is a fully qualified domain name, you must use the SVM's fully qualified domain name when you create the mount point. The name is case-sensitive. Alternatively, you can use the IP address of the SVM LIF to specify a share instead of the SVM name. Consider the following examples: When you select a share "vol_cifs" that is exported by an SVM named "vs1" as a backup selection, the selection must be entered as "\\vs1\vol_cifs". If you enter the backup selection as "\\VS1\vol_cifs" or \\vs1.exqample.com\vol_cifs" then the snapshot job fails. When you select a share "vol_cifs2" that is exported by an SVM named "VS2.example.com" as a backup selection, the selection must be entered as "\\VS2.example.com\vol_cifs2". If you enter the backup selection as "\\VS2\vol_cifs2" or "\\vs2.example.com\vol_cifs2" then the snapshot job fails. When you select a share "vol_cifs2" that is exported by an SVM with the LIF "10.67.212.20" as a backup selection, the selection must be entered as "\\10.67.212.20\vol_cifs3". See Configuring a Standard or MS-Windows policy to protect NAS volumes or SAN-connected devices. Note: Replication Director for NetApp Clustered Data ONTAP supports NAS only at this time.
Standard or MS-Windows with NDMP Data Mover enabled	For a Standard policy with NDMP Data Mover enabled: The Storage Virtual Machine (SVM) must be added as an NDMP host in NetBackup. You should keep in mind the following naming conventions: The junction name cannot be different from the volume name. When you mount the volume in the SVM's namespace, make sure that the junction name is the same as the volume name. For example, if you have a volume "vol_nfs" on the SVM "vs1", you should use the junction name "vol_nfs" when you mount the volume. The mount path must use the host name as the SVM name. The SVM name must be spelled out exactly as it appears in the OnCommand Unified Manager. You cannot use the IP address of a data LIF when you mount an SVM's volumes. For example, the mount point "/mnt/vol_nfs" on the NetBackup client refers to "vs1:/vol_nfs", where vs1 is the SVM name and "vol_nfs" is the junction path for the volume "vol_nfs". For a Windows policy with NDMP Data Mover enabled: The SVM must be added as an NDMP host in NetBackup. You should keep in mind the following naming conventions: Any share that is created as an export volume must have the same name as the volume name. For example, the volume "cifs_vol" on SVM "vs1" must be exported using the share name "cifs_vol". The name is case-sensitive. The share name must use the host name as the SVM name. The SVM name must be spelled out exactly as it appears in the OnCommand Unified Manager. You cannot use the IP address of a data LIF as the share name. For example, the share "cifs_vol" on the SVM "vs1", must be specified as "\\vs1\cifs_vol". See Configuring a Standard or MS-Windows policy to protect clients using NDMP with Data Mover.
NDMP	Make sure that the node-scoped NDMP is disabled: system services ndmp node-scope-mode off system services ndmp node-scope-mode status To generate a password for the NDMP user, run the following command: vserver services ndmp generate-password - vserver vserver_name -user user Remote NDMP and three-way NDMP backups are supported for Clustered Data ONTAP Backup From Snapshot operations. To perform three-way backup operations, any devices and storage units must be configured for the tape devices that are attached to the clustered storage system. You must add the NDMP host using the cluster-management LIF in NetBackup. After the storage units are configured for the cluster storage system, they can be used as the destination in an SLP for three-way backups. Refer to the NetBackup NDMP Administrator's Guide for more information. Add the Storage Virtual Machine (SVM) as an NDMP host in NetBackup. You must enter the SVM name exactly as the OnCommand Unified Manager sees it when you create the policy. For example, if the SVM name in the OnCommand Unified Manager is a fully qualified domain name, you must use the SVM's fully qualified domain name when you create the policy. The entry is case-sensitive. When you select a volume named "vol_nfs" that is on an SVM named "vs1" as a backup selection, the selection must be entered as "/vs1/vol_nfs". Alternatively, you can use the IP address of a LIF belonging to the SVM to configure a backup policy for NDMP. For the Backup From Snapshot operation to work correctly, make sure that an Intercluster LIF is created on each node of the cluster. You should enable a firewall policy for NDMP service on the Intercluster LIF: You can use following NetApp command to verify that the firewall policy is enabled for NDMP: system services firewall policy show-policy intercluster Make sure that the NDMP services are allowed for the "intercluster" policy. If the "Allowed" column displays "0.0.0.0/0", it means that the firewall policy is enabled and that all clients can connect to the NDMP service on the Intercluster LIF. If the firewall policy is not enabled for NDMP, use the following NetApp command to enable it: system services firewall policy modify -vserver cluster1 -policy intercluster -service ndmp 0.0.0.0/0 The destination SVM must be added as an NDMP host in NetBackup for Backup From Snapshot to work from a replica. For a Live Browse to work, enable the following extension on Clustered ONTAP 8.3: set advanced vserver services ndmp extensions modify -is-extension-0x2050-enabled true If you use the ALL_FILESYSTEMS directive in an NDMP policy for Clustered Data ONTAP, you must exclude the SVM's root volume using the VOLUME_EXCLUDE_LIST directive. For example, to exclude the root volume "root_vs1" of the SVM "VS1" you would use the following directive: VOLUME_EXCLUDE_LIST=/VS1/root_vs1 ALL_FILESYSTEMS For more information, refer to the following topic: See ALL_FILESYSTEMS and VOLUME_EXCLUDE_LIST directives. To enable indexing, you must add a disk array host to NetBackup. Complete the steps in the following procedure: See Configuring indexing for an NDMP policy. See Configuring an NDMP policy to protect a NAS host.
VMware	When you create an NFS datastore on a VMware ESX host and the datastore refers to a volume that the SVM exported, the server name must be entered exactly as it appears in the OnCommand Unified Manager. The server name entry refers to the SVM name. This entry is case-sensitive. If the server name is not entered correctly, the NetBackup snapshot job fails. Alternatively, you can use the IP address of the SVM LIF to specify a server name instead of the SVM name. If the NetBackup VMware host is a Windows computer, make sure that the appropriate name-mapping rule is created on the SVM that exports the volume for the VMware datastore. The name-mapping rule should map the user under which the NetBackup Client Service is running to the UNIX user "root". For example, SVM1 is a storage virtual machine that exports a volume to the ESX NFS datastore. You should create a Windows-UNIX name-mapping rule on SVM1 that maps the Windows user "DOMAINAME1\Administrator" to the UNIX user "root", where "DOMAINAME1\Administrator" is the account for NetBackup Client service on the VMware backup host. You should create similar name-mapping rules on any other peer SVMs where replicated volumes are created. Refer to the following NetApp document for more information: https://kb.netapp.com/support/index?page=content&id=1013831&actp=RSS Refer to the following topic for more information about configuring VMware backup policies: See Configure a policy for virtual machines to use Replication Director.
Oracle	Oracle provides specific requirements for the mount commands that you use when you mount Oracle database components to NetApp filers. Refer to your Oracle documentation for more information. When you create a mount point for Oracle operations, you must use an NFS version 3 volume. Make sure that the volume is created using the parameters that are specified in the Oracle documentation. Oracle backup policies may only include any data files that exist on the filer mount point. Backup selections can include tablespaces, individual data files, or whole databases so long as they exist on the filer mount point. If backup selections include any file other than a data file or any files that do not exist on the mount point, the backup operations fail. Refer to the following topics for more information about configuring Oracle backup policies: See Configuring an Oracle Intelligent Policy. See Configure a script-based Oracle policy.

See Using NetApp Clustered Data ONTAP with Replication Director.

See Protecting volumes with nested junctions for Clustered Data ONTAP.

See Limitations to using Clustered Data ONTAP with Replication Director.

Feedback

Was this page helpful?

Feedback

Was this page helpful?