NMM supports the following features:
· Windows Server 2012 R2 support for applications—NMM supports the following Microsoft applications on Windows Server 2012 R2:
• SQL Server 2012
• SQL Server 2008 R2 SP2 or later
• SQL Server 2008 SP3 or later
• Hyper-V 2012 R2
· Windows Server 2012 support for application—NMM supports the following Microsoft applications on Windows Server 2012:
• SQL Server 2012 SP1
• SQL Server 2008 R2 SP1 or later
• SQL Server 2008 SP3 or later
• Exchange Server 2013 Cumulative Update 1 and Cumulative Update 2
• Exchange Server 2010 SP3 or later
• SharePoint Server 2013
• Hyper-V, including Cluster Shared Volumes (CSV’s)
· NMM support for NetWorker Restricted Data Zone—The Restricted Data Zone feature enables a privileged administrator to define restrictions for a data zone and segment existing resources (called Restricted Data Zone resources) into sub-segments.
· NMM support for immediate cloning—NMM supports the NetWorker immediate cloning feature. Immediate cloning starts the cloning operation immediately after each save set in the group is backed up. Immediate cloning operations can complete sooner because they can run in parallel instead of sequentially.
· NMM support for Client Push—NMM supports the NetWorker Client Push feature. Client Push provides the ability to distribute software and perform software updates to one or more NetWorker hosts from the NetWorker server.
· NMM only supports upgrades from NMM 3.0 to NMM 3.0 SP1 in stand-alone environments.
· Simplified backup and recovery process—The backup and recovery processes have been simplified. NMM only performs application-specific backup and recovery. For Windows file system backup and recovery, you must use the NetWorker 8.1 SP1 client.
· Exchange Server federated backup—NMM supports federated backups for Exchange Server 2013 and Exchange Server 2010 DAGs. Federated backups allow you to back up all DAG nodes with a single save set without running a separate backup of each node.
Federated backups allow you to specify the order in which NMM backs up the DAG nodes. NMM backs up the first DAG server specified in the priority list that has an active or passive database copy. The first database found using the priority list is backed up, and all other active or passive copies of the same database are excluded.
For the preferred option, the active database is backed up only if no passive copies are available. There are no special considerations for the recovery of federated backups. You can recover federated backups by using the same recovery methods used for any other Exchange backup.
· Exchange mailbox level recovery to alternate mailbox—NMM supports mailbox level granular recovery to an alternate mailbox for Exchange Server 2013, Exchange Server 2010, and Exchange Server 2007. Recovering to an alternate mailbox is similar to recovering mailboxes, folders, and messages to the original mailbox. You can perform these recoveries from the NMM graphical user interface (GUI).
· Exchange default install—NMM supports default installation for Exchange Server 2013, Exchange Server 2010, and Exchange Server 2007. The databases and logs can be in the same directory on the same volume.
· Circular logging-enabled Exchange Server database backups—NMM supports non-federated backups of circular logging- enabled databases. Exchange Server 2013 and Exchange Server 2010 can contain a mixture of databases that may or may not be enabled for circular logging.NMM does not support federated backups of circular logging-enabled databases.
· SQL Server 2012 VDI AlwaysOn federated backups—NMM supports SQL Server 2012 federated backups, and gives priority to AUTOMATED_BACKUP_PREFERENCE and BACKUP PRIORITY settings for a SQL Server 2012 AlwaysOn database during the backups.
· SQL Server VSS directed recovery to the original server—NMM supports directed recovery of SQL Server VSS backups to the original server but at a different location.
· SQL Server VDI multiple stream with Data Domain Boost—NMM provides the Data Domain multiple stream support for SQL Server VDI with the NetWorker 8.1 client.
· NetWorker SQL VDI Adhoc Backup Plug-in—NMM provides a NetWorker SQL Adhoc Backup Plug-in for SQL Server Management Studio (SSMS) that a SQL database administrator can use to run manual SQL VDI backups directly from SSMS. Local SQL instances are supported. This support is available for SQL Server 2012, SQL Server 2008 R2, and SQL Server 2008.
· Client Direct to a Data Domain or AFTD device—NMM provides Client Direct backup support provided by the NetWorker 8.1 client.The NetWorker client enables clients with network access to an AFTD or Data Domain device to send their backup data directly to the device, bypassing the NetWorker storage node.
The storage node manages the device for the NetWorker clients, but does not handle the backup data. The Client Direct feature reduces bandwidth usage and bottlenecks at the storage node, and provides highly efficient backup data transmission.
The Device Access Information attribute must specify the complete pathname of the destination device. If the Client Direct backup is not available, a traditional storage node backup is performed instead. The Client Direct feature is enabled by default, but can be disabled on each client by clearing the Client Direct attribute.
· Hyper-V over CSV federated backup—Windows Server 2012 supports a Hyper-V over CSV federated backup, changing the way that Hyper-V servers in a CSV work by eliminating the I/O Redirection Mode requirement. Additionally, NMM provides support for proxy node backups for Hyper-V CSV servers by using the Windows VSS System Provider, offering impact-free backups. NMM also provides parallel backups through this feature.
· Hyper-V Continuous Availability support for Windows CSV—Windows Server 2012 provides Hyper-V Continuous Availability support for Windows CSV, changing the way that Hyper-V servers in a CSV work by eliminating the I/O Redirection Mode requirement. Additionally, NMM provides support for proxy node backups for Hyper-V CSV servers by using the Windows VSS System Provider, offering impact-free backups.
· Hyper-V over SMB-3 support—Windows Server 2012 provides support for Hyper-V over SMB-3 shares.
· Hyper-V support for Windows Server 2012 features—NMM supports the following Windows Server 2012 features:
• Deduplicated data can be recovered on Windows Server 2012 and later. To recover deduplicated volume data, you must enable the Deduplication role.
• Windows Server 2012 provides Hyper-V support for VHDX hard disks.
• ReFS volume data can be recovered on Windows Server 2012 and later.
• NMM supports granular level recovery for virtual machines (VMs) stored in the Following Windows Server 2012 deployments:
· Hyper-V VMs over SMB-3
· VHDX hard disk
· Hyper-V VMs excluded from backups—NMM allows you to exclude Hyper-V VMs that have data stored on SMB file servers.
· Hyper-V in-guest copy or full backup options—NMM allows you to perform VSS full or VSS copy backups in guest VMs.
· Hyper-V configuration wizard—NMM provides a configuration wizard that allows you to easily configure scheduled backups for NMM clients for Hyper-V servers.
· Active Directory granular backup and recovery on Windows Server 2012—NMM provides support for granular backup and recovery for Active Directory on Windows Server 2012.
· Backup and recovery in a multihomed setup—NMM supports VSS-based and VDI-based backup and recovery in a multihomed setup.
· Dedicated storage node for LAN-free backups.
· Deduplication of data using Avamar and Data Domain—Deduplication segments an incoming data stream, uniquely identifies data segments, and then compares the segments to previously stored data. If a segment is unique, then the segment is stored on disk. However, if an incoming data segment is a duplicate of what has already been stored, a reference is created to the segment, and the segment is not stored again.
You can use NMM with Avamar or Data Domain to perform deduplication backups.
· Adhoc (manual) backups for SQL VDI—You can start a manual backup of SQL data at any time. You can use NMM to back up the following combinations of data objects:
• • The entire SQL Server storage hierarchy
• • One or more entire databases
• • One or more file groups
• • One or more files in a file group
• • A heterogeneous collection of files, file groups, and databases
• • Transaction log backups
· Internationalization (I18N) — NMM includes the NetWorker support for I18N. NetWorker supports language packs, which can be installed during NetWorker installation, or can be installed separately after NetWorker has been installed.
I18N support in NetWorker is dependent on the underlying operating system’s I18N support. If you plan to use non-English data in NetWorker, ensure that the appropriate support for that language has been installed and configured on the operating system.
· NetWorker cloning and staging to create and manage additional copies of save sets—NMM uses NetWorker snapshot management technology to perform a backup, which creates multiple save sets regardless of the client involved. The backup differs from a traditional NetWorker file system backup, which creates one save set for each file system.Cloning is a NetWorker feature that allows for secure offsite storage and the transfer of data from one location to another. Cloning provides the ability to create a copy of a save set from one volume to another volume. A NetWorker clone operation can be performed at the save set, volume, or pool level.NetWorker staging is a separate process that relies on the cloning mechanism. Save set staging is the process of transferring data from one storage medium to another medium, and then removing the data from its original location. Staging is only supported for data that resides on disk-type devices.
· Bare Metal Recovery (BMR)—NMM supports NetWorker Windows BMR, which provides an automated BMR solution by using the Windows ASR writer and other Microsoft VSS writers to identify critical volumes that are needed to perform a recovery on a disabled computer. Windows BMR is performed offline, while the Windows operating system is inactive. This offline operation removes the requirement to reinstall Windows manually and prevents problems that can occur when you restore operating system files to a running version of Windows.To support Windows BMR, NetWorker provides a bootable Windows BMR image that contains NetWorker binaries and a wizard to control the recovery process.
· IPv4 and IPv6—NMM supports the use of IPv4 and IPv6. If the host on which NMM is installed uses IPv4 or IPv6, then the NetWorker server, NetWorker storage node, or NetWorker client node must be within the IPv4 or IPv6 network infrastructure. In an IPv6 environment, update the hosts file in C:WindowsSystem32driversetc with the IPv6 client and FQDN names. This operation helps in resolving the IPv6 enabled clients quickly and starts the NetWorker User for Microsoft GUI faster.
· NMM support for these applications on Windows Server 2012 R2 is for Windows VSS Software Provider only. There is no support for VSS Hardware Provider implementations.
· You must upgrade both NetWorker and NMM by selecting them together during installation.
· Client Push is not supported in clustered environments or for NMM GLR installation.
· NMM no longer supports Data Protection Manager backup and recovery.
· NMM does not include localization (L10N) support and is available in English only.
· NMM supports Client Direct backups to a Data Domain or AFTD device for all applications.
Supported types of backup and recovery
NMM supports the following types of backups:
◆ Scheduled backup—
Scheduled backups are available for all Microsoft applications. The NetWorker server backs up client data regularly by using scheduled backups. You scheduled a backup to start at any time.
◆ Federated backup—
Federated backups are available for Hyper-V Server VSS, Exchange Server VSS, and SQL Server VDI.
◆ Manual backup—
Manual backups are only available for Microsoft SQL Server when using the VDI technology. Manual backups are also known as adhoc backups. You can start a manual backup at any time. Manual backups are always full backups.
◆ Granular backup—
Granular backups are available for Active Directory and Active Directory Application Mode (ADAM). A granular backup does not use snapshot technology (non-VSS). Instead, the backup is routed directly to a granular backup medium. A traditional granular Active Directory backup enables you to recover individual objects and object attributes. A granular ADAM backup enables you to recover individual application partitions.
NMM supports the following types of recovery:
◆ Conventional recovery—The entire volume or database is recovered as a whole.
◆ Granular level recovery—
Granular level recovery (GLR) lets you recover specific items, such as files and folders, from a single full backup without having to recover the full backup. This type of recovery reduces the recovery time and the space requirements on local system storage.
◆ Windows BMR—
NetWorker provides an automated BMR solution by using the Windows ASR writer and other Microsoft VSS writers to identify critical volumes that are needed to perform a recovery on a disabled computer.
There are two types of directed recovery:
In a pull directed recovery:
the control role and destination role are run on the same computer. The control role running on the destination computer pulls the recovery data to itself. Backup data from the source client is restored to the destination client.
In a push directed recovery:
the control role can run on the source client or a different client. Backup data from the source client is restored to the destination client. The control client computer pushes the data out to another computer, the destination client. The destination client is a different computer than the source client and control client.