SnapProtect^™ Backup - Support

Initial SnapProtect Setup

Deployment and a successful initial run of an SnapProtect backup in some complex environments may require customization, due to specific dependencies in your environment. The following parameters are known to affect the deployment and initial run and hence need a thorough evaluation:

• Firmware versions on the array
• Device types
• Mode of access
• Security configuration
• Operating Systems interacting with the storage array
• Application layout on the storage array LUNs

License Requirements

The SnapProtect feature requires the NetApp Snap Management license. This license is consumed when SnapProtect is enabled for a client.

Backup Types

The following table lists the Agents supporting the SnapProtect backup and provides information about the various options supported by each of these Agents.

Agents	Full Backup	Incremental Backup	Differential Backup	Notes
Virtual Server (VMware)				Backup of VM Templates is not supported. Virtual Server instances configured with ESX server are not supported. Instances should be configured using Virtual Center.
Exchange Database
Oracle				Incremental backups are applicable for Backup copies. See Backup Copy Operations for more information.
Microsoft SQL Server				Transactional Log backups always use the traditional backup method. Log backups are stored in the Primary (classic) copy.
Microsoft SharePoint Server				Snap Mining operations from a snapshot on the computer hosting the snapshot or from a proxy computer are supported.
MySQL				Only supported in UNIX configurations.
NAS
Virtual Server (Hyper-V)				SnapProtect backups support online virtual machines.
DB2				Backup of partial databases is not supported. Log files always use the traditional backup method.
Lotus Notes Database
Unix File System				On Demand Backup Set is not supported for SnapProtect Backup. Raw partitions in Unix are supported. Mirrored LVM configuration is not supported.
Windows File System				On Demand Backup Set is not supported for SnapProtect Backup.

Platforms

The following table lists the platforms supported for SnapProtect backup. The latest updates should be installed on all the platforms.

• ** To enable Red Hat and CentOS 7.x support:

  1. Disable and stop the lvm2-lvmetad service. To do this, run the following command:

  systemctl disable lvm2-lvmetad
  systemctl stop lvm2-lvmetad

  2. Disable lvmetad in to the LVM config file. To do this, run the following command:

  edit /etc/lvm/lvm.conf to include use_lvmetad = 0

Note that the above list does not provide a comprehensive list of supported platforms for each agent. See System Requirements for information on the platforms supported by the individual Agents.

See List of Deprecated Applications and Platforms for more details.

SnapProtect for Open Systems

Deployment and a successful initial run of an SnapProtect backup in some complex environments may require customization, due to specific dependencies in your environment. The following parameters are known to affect the deployment and initial run and hence need a thorough evaluation:

• Firmware versions on the array
• Device types
• Mode of access
• Security configuration
• Operating Systems interacting with the storage array
• Application layout on the storage array LUNs

The following table lists the Agents supporting Block Level Replication and provides information about the various options supported by each of these Agents.

Agents	Full Backup	Incremental Backup	Differential Backup	cluster support	WORKFLOW	Notes
Exchange Database					Full, Incremental or Differential	Exchange 2013 is supported. No DAG support. Only database level backups are supported with SPOS enabled storage policy. Backup of individual mailboxes to a SPOS enabled storage policy is not supported. Data mining is supported only with a target storage policy that is not SPOS enabled. To perform single mailbox restore, do an out-of-place restore of the Exchange Database and then using the DB mining tool (setup should have x32 Microsoft Outlook) to get mailboxes/messages list and restore them as MSG/PST format.
Microsoft SQL Server		Incremental backups will be transaction log backups and can only be run from the subclient level			Workflow will only start FULL backup jobs for SQL subclients that are associated with it.	MS SQL 2012 is supported. Transactional Log backups always use the traditional backup method. Log backups are stored in the Primary (classic) copy.
Oracle					Workflow will start a SPOS job for a Oracle subclient only if the data storage policy is the same as the storage policy on which the workflow is running or if no data is selected at the subclient level but the log storage policy is set to the storage policy from which the work flow is running.	Incremental backups are applicable for Backup copies. See Backup Copy Operations for more information. Log and data on the same volume is not supported. No support for partial table backups, i.e., no support for online subset backup option. RAC and ASM are not supported.
Unix File System					Full, Incremental or Differential	On Demand Backup Set is not supported for SnapProtect Open Systems Backup. Raw partitions in Unix are not supported Mirrored LVM configuration is not supported. Root Volume snap is supported with LVM.
Windows File System					Full, Incremental or Differential	On Demand Backup Set is not supported for SnapProtect Backup. Default subclient is not supported for SPOS

The following table lists the platforms supported for SnapProtect for Open Systems.

Release Notes

• Storage policy reassociation will cause a baseline for some or all the volumes in the subclient.
• No support for NetApp C Mode or OnCommand Unified Manager 6.x1.
• No support for filtering of pagefile.sys and hiberfile.sys on Windows 2003. Please refer to Skipping Files for Backup for more information.