SnapProtect - NetApp - Frequently Asked Questions
- What are the maximum number of snapshots created for each volume?
- Can I create additional provisioning policies for secondary copies and use them for SnapProtect?
- Can I use a non root user to configure an array or NDMP?
- What account types and roles should I set for Cluster-Mode?
- How do I verify that the destination Filer has SnapMirror access to the source filer?
- How does the SnapMirror process work?
- How does data aging work with SnapMirror?
- Can I disable tunneling for a storage virtual machine?
- How do I select vFiler as the destination for secondary (vault or mirror) copy?
- Can the data on SharePoint Server be restored from the content databases on the SQL Server configured to use NetApp SnapProtect?
The maximum number of snapshots created for each volume is 255.
Yes, you can create additional provisioning policies for secondary copies to the OnCommand Unified Manager. Any provisioning policy with a name starting with “SnapProtect_” (case in-sensitive) will be displayed in the SnapProtect console for use in storage policy copies.
You can use a non-root user for array configuration and NDMP configurations. To configure the array with a non-root user, execute the following commands:
- To create SnapProtect role with proper rights:
NetApp1> useradmin role add SnapProtectrole -c ”[ SnapProtect Management Role]" -a login-ndmp,login-http-admin,api-*
NetApp1> useradmin role add SnapProtectrole -c ”SP Mgmt Role" -a login-ndmp,login-http-admin,api-*
- To add a role to the newly created SnapProtect group:
NetApp1> useradmin group add SnapProtectgroup -c ”[ SnapProtect Management Group]" –r SnapProtectrole
NetApp1> useradmin group add SnapProtectgroup -c ”SP Mgmt Group" –r SnapProtectrole
- To create a user for the array credential in the SnapProtect Control Panel.
NetApp1> useradmin user add SnapProtectuser -c ”[ SnapProtect Management Account]" -n ”S Admin" –g SnapProtectgroup
NetApp1> useradmin user add SnapProtectuser -c ”SP Mgmt Account" -n ”S Admin" –g SnapProtectgroup
Use the Same Credentials for NDMP
You can use the same credentials for NDMP that you use for the array.
To configure NDMP with the same credentials, enter the encrypted password in the following command, and then execute it:
NetApp1> ndmpd password [ SnapProtectuser]
NetApp1> ndmpd pswd1 SnapProtectuser
Add a user in the Array Management credentials with ontapi and ssh roles. Add the cluster in Array Management and then SVMs are detected and added from the cluster client.
For more information on the configuration of NetApp clusters, see Configuring Storage Virtual Machines on NetApp Arrays.
To ensure that SnapMirror jobs run, the destination filer must have SnapMirror access to the source filer. If the name or IP address of the SnapMirror filer appears in "/etc/snapmirror.allow", then the destination filer has access.
For more information on SnapMirror options, refer to the NetApp Support documentation - SnapMirror options.
Alternatively, you can go into each of the hosts in OnCommand Unified Manager and configure the proper security rights for source and destination in the Fabric-Attached Storage settings.
- To get the full, detailed Snap Management plan so that SnapMirror/SnapVault can run, NetApp runs a conformation check during the first auxiliary copy job.
- During each SnapMirror auxiliary copy job, SnapMirror creates a “BackupVersion," which is a new Snapshot of the entire volume that requires replication.
- Once a new Snapshot for SnapMirror is available, the Snapshot is listed under the volume on the Primary Filer.
- The new Snapshot also appears in the current SnapMirror session.
- On the destination filer site, the same Snapshot appears. In addition, if there were any previous SnapMirror on-demand jobs run, only the very last one remains on the target box.
NetApp calls this a “Swizzling Process”. That is, the primary Fabric-Attached Storage (FAS) creates a delta set between the original snapshot used from the previous SnapMirror job and the new snapshot created for the current SnapMirror job. Only the details of the snapshot and the deltas are sent to the destination FAS, and refer to the previous snapshot, which was formerly the target SnapMirror session. The volume is updated to match what is in the primary FAS. The previous snapshot is not deleted because the entire process is a background job.
In SnapProtect, if an SnapProtect job on a storage policy copy with SnapMirror capabilities is data-aged, the job is removed from the snapshots list. For information on viewing the snapshots for an agent, or snapshot copy, see List Snapshots.
The data-aging process does not physically delete the snapshot taken by the SnapProtect job from the SnapMirror volume on the file server. Snapshots from jobs that have been data-aged are physically deleted only when you perform an auxiliary copy to the SnapMirror node.
Yes. If you want to disassociate a particular Storage Virtual Machine from a NetApp array, then you can turn off the tunneling option.
All jobs scheduled through the array no longer run for the disassociated Storage Virtual Machine.
To turn off tunneling:
- Log into CommCell Console.
- Click the Storage tab, and then click Array Management.
- Select the Storage Virtual Machine for which you want to enable tunneling, and then click Edit.
- Click the Snap Configuration tab, clear Use Tunneling, and then click OK.
- Click the General tab, and then under Credentials, click Change.
- In the User Name and Password boxes, enter the NDMP credentials, and then click OK.
- Click OK to close the Filer Properties dialog box.
- Click OK to close the Array Management dialog box.
- Create resource pool with physical filer and not aggregate as resource pool member.
- When creating secondary snapshot copy, then
Select the resource pool(s) created in (1), and
Enable the "Select vFiler" option and select the required vFiler from the dropdown list.
Can the data on SharePoint Server be restored from the content databases on the SQL Server configured to use NetApp SnapProtect?
Offline browse and restore for SharePoint 2010 and later is supported on NetApp by using SnapProtect- SQL Server iDataAgent. The following are the prerequisites to using this feature:
- The source client machine must have Microsoft SQL Server with an attached Content Database. This can be configured using any one of the following methods:
- The destination client machine must have SharePoint Server iDataAgent installed.