158024125 networker module for microsoft applications 2 4 sp1 release notes pdf

RELEASE NOTES

These release notes contain supplemental information about EMC NetWorker Module for Microsoft Applications release 2.4 SP1. Topics include:

◆ Revision history ........................................................................................................ 2◆ Product description................................................................................................... 2◆ New features and changes in NMM 2.4 SP1............................................................... 3◆ Fixed problems in NMM 2.4 SP1................................................................................ 5◆ Environment and system requirements ..................................................................... 5◆ Known problems and limitations............................................................................... 5◆ Technical notes ....................................................................................................... 51◆ Documentation ....................................................................................................... 53◆ Software media, organization, and files .................................................................. 54◆ Troubleshooting and getting help............................................................................ 54

EMC® NetWorker® Module for Microsoft ApplicationsRelease 2.4 SP1

Release NotesP/N 300-999-658REV 03

March 1, 2013

Revision history

Revision history

Table 1 on page 2 presents the revision history of this document.

Product description

The EMC® NetWorker® Module for Microsoft Applications (NMM) supports backup and recovery of Microsoft applications by using:

◆ Microsoft Volume Shadow Copy Service (VSS) technology — NMM uses Microsoft Volume Shadow Copy Service (VSS) technology to provide recovery services for:

• File systems

• Application data for the following Microsoft applications:

– Microsoft SQL Server

– Microsoft Exchange Server

– Microsoft SharePoint Server

– Microsoft Hyper-V Server

– Microsoft Active Directory

– Microsoft Data Protection Manager Server

• Operating system data

◆ Microsoft Virtual Device Interface (VDI) technology — NMM uses the Virtual Device Interface (VDI) technology to communicate with the SQL Server and provides backup and recovery services for Microsoft SQL Server.

Table 1 Revision history

Revision Date Description

03 March 1, 2013 Revision 03 of this document provides an important note that you must review when using NMM to backup Exchange Server. “Product description” on page 2 contains the information.

02 January 30, 2013 Revision 02 of this document contains the following updates for General Availability (GA) release of EMC NetWorker Module for Microsoft Applications Release 2.4 SP1:• “Client parallelism optimization for backups is not

supported in NMM (NW147575)” on page 8• “After BMR is performed, ReFS non-critical volumes are

online with no data but NTFS non-critical volumes are not online (NW143706)” on page 8

• “Exchange Server 2010 in hosting mode is not supported with NMM 2.4 SP1 (NW130301)” on page 20

01 December 17, 2012 First release of this document for Directed Availability (DA) release of EMC NetWorker Module for Microsoft Applications Release 2.4 SP1.

2 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Release Notes

New features and changes in NMM 2.4 SP1

IMPORTANT

When using NMM to back up the Exchange Server, review EMC Technical Alert esg133843 on http://support.emc.com for details about the NetWorker Server update required for NMM to handle Exchange save sets correctly. Information is also available in the Readme document and the Release Notes for the NetWorker Cumulative Fix release 8.0.1.1, 8.0.0.7, and 7.6.5.1.


This section lists the new features and enhancements in NMM 2.4 SP1:

◆ “Windows Server 2012 application support” on page 3

◆ “Windows Server 2012 client support” on page 4

◆ “SQL VDI multi-stream Data Domain Boost support” on page 4

◆ “SharePoint Server 2013 support” on page 4

◆ “Hyper-V 2012 support” on page 4

◆ “Windows Server 2012 Active Directory granular recovery support” on page 4

◆ “Configuration Wizard support” on page 5

◆ “Windows 32 Services Component file backup support in Windows Server 2012” on page 5

Windows Server 2012 application support

NMM 2.4 SP1 supports the following Microsoft applications on the Windows Server 2012 operating system:

◆ SQL Server 2012

◆ SQL Server 2008 R2 SP1

◆ SQL Server 2008 SP3

◆ SharePoint Server 2013

◆ Hyper-V, including Cluster Shared Volumes (CSV)

The support for these applications on Windows Server 2012 is only with Windows VSS Software Provider.

EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Release Notes 3

http://support.emc.com


Windows Server 2012 client support

Table 2 on page 4 lists the Windows Server 2012 client support provided by NMM 2.4 SP1.

NMM 2.4 SP1 does not support Windows Server 2012 deduplication volumes.

SQL VDI multi-stream Data Domain Boost support

NMM 2.4 SP1 includes client based Data Domain Boost multi-streaming support that is provided by NetWorker 8.0 SP1 or later. This support enhances the backup time and allows a backup to complete three times faster than a backup performed with Data Domain.

SharePoint Server 2013 support

NMM 2.4 SP1 supports Microsoft SharePoint 2013. This support is consistent with the support provided for SharePoint Server 2010 in the previous NMM release. NMM support for SharePoint Server 2013 is only for Windows VSS Software Provider.

Hyper-V 2012 support

NMM 2.4 SP1 supports Microsoft Hyper-V 2012. This support is consistent with the support provided for Hyper-V 2008 R2 in the previous NMM release. NMM support for Hyper-V Server 2012 is only for Windows VSS Software Provider.

Windows Server 2012 Active Directory granular recovery support

NMM 2.4 SP1 supports Active Directory granular backup and recovery for Windows Server 2012. This support is consistent with the support provided for Windows Server 2008 R2 in the previous NMM release.

Table 2 Windows Server 2012 client support

Support Windows Server version

Windows file system backup • Windows Server 2012 (x64)• Windows Server 2012 High Availability Clusters

(x64)

Windows system state backup support that is provided by NetWorker client 8.0 SP1

• Windows Server 2012 (x64)• Windows Server 2012 High Availability Clusters

(x64)

Windows Bare Metal Recovery (BMR) support that is provided by NetWorker client 8.0 SP1

Windows Server 2012 (x64)

Backup and recovery support for data stored on ReFS file system

Windows Server 2012 (x64) Datacenter and Foundation Editions

Backup and recovery support for data stored on storage spaces

Windows Server 2012 (x64)


Fixed problems in NMM 2.4 SP1

Configuration Wizard support

The configuration wizard support has been extended to include SharePoint Server 2013. Client resources can be created for SharePoint Server 2013 by using the Configuration Wizard.

Windows 32 Services Component file backup support in Windows Server 2012

NMM 2.4 SP1 provides Windows 32 Services Component file backup support in Windows Server 2012. To back up Windows Service Component files as part of file system back, you must use NSR_SYS_WRITER_WIN32_SERVCOMP_USER=YES parameter. Not specifying NSR_SYS_WRITER_WIN32_SERVCOMP_USER=YES results in this component being backed up as part of SYSTEM COMPONENTS save set.

Fixed problems in NMM 2.4 SP1

Table 3 on page 5 lists the issues in the previous NMM releases that have been fixed in this release.

Environment and system requirements

The NetWorker Software Compatibility Guide and NetWorker Module for Microsoft Applications Release 2.4 SP1 Installation Guide list hardware and software requirements for the NMM client software.

Known problems and limitations

This section describes known problems and limitations for NMM 2.4 SP1:

◆ “Unsupported NetWorker features” on page 6

◆ “Unsupported Windows features” on page 6

Table 3 Problems fixed in NMM 2.4 SP1

Issue number Description

NW145945 Mailbox RDB browsing does not show content of mailboxes.

NW144756 Unable to retrieve permissions for RDB restore intermittently in slow Active Directory environments.

NW143977 GLR recovery fails with database mount error.

NW130402 RDB data recovery fails with error “Error Determining RDB Capability:”

NW131820 Unable to browse very large mailboxes after recovering mailbox store to RDB.

NW141795 Unable to browse RDB for databases with large number of mailboxes (greater than 1300). Works for smaller number of mailboxes.

NW141365 NMM 2.4 backup fails with error: NMM .. Exchange2010 Shell interface is unavailable.

NW140167 Mailbox recovery is successful, but sub-folder recovery returns empty results.



◆ “NMM limitations” on page 6

◆ “SQL Server limitations” on page 13

◆ “Exchange Server limitations” on page 18

◆ “SharePoint limitations” on page 27

◆ “Hyper-V limitations” on page 35

◆ “Active Directory limitations” on page 41

◆ “Data Protection Manager Server limitations” on page 42

◆ “CLARiiON, Symmetrix, and provider limitations” on page 46

Unsupported NetWorker features

The following NetWorker features are not supported:

◆ Localization (L10N)

◆ Adhoc or manual VSS backups (adhoc or manual backups can be performed only for SQL Server when using VDI technology)

Unsupported Windows features

The following Windows features are not supported:

◆ BitLocker encryption

◆ LAN-based proxy client or LAN-free backups, if dynamic disks are used

◆ VSS hardware providers with Windows dynamic disks

◆ Backup of Microsoft applications, such as Exchange, configured with junction points, (mklink/J), hard links (mklink/H), and soft links (mklink or mklink/D).

◆ Windows Unique Volume GUID path for volumes. Backups that are configured using GUID path fail.

The Windows Server IA64 Edition Server version is not supported.

NMM limitations

This section lists the known problems and issues in NMM:

◆ “Client parallelism optimization for backups is not supported in NMM (NW147575)” on page 8

◆ “After BMR is performed, ReFS non-critical volumes are online with no data but NTFS non-critical volumes are not online (NW143706)” on page 8

◆ “When configuration checks are run using the NMM installer, network configuration information is not displayed correctly for Hyper-V guest virtual machine (NW128528)” on page 8

◆ “NMM 2.4 SP1 does not support cluster volumes created by storage space in Windows 2012 (NW145868)” on page 8



◆ “Incremental backups fail when run in parallel with full backups on an Avamar node (NW145239)” on page 8

◆ “When the irccd.exe command is used to change Replication Manager ports, the operation does not respond, but the changes are effective (NW115040)” on page 8

◆ “NWFS does not support write cache on Windows Server 2012 ReFS (NW143794)” on page 9

◆ “After an NMM save set is cloned, the original VSS:\ save set is not recycled until the cloned VSS:\ save set expires (NW142181)” on page 9

◆ “Backup fails with the VSS_E_UNEXPECTED_PROVIDER_ERROR error (NW143309)” on page 9

◆ “NMM applies the pool specified in the Group Properties page during client resource configuration (NW139759)” on page 10

◆ “When creating a new client resource, an error message appears if an alias already exists on the NetWorker server (NW139699)” on page 10

◆ “Back up SYSTEM COMPONENTS save set by using NMM 2.3 and restore using NMM 2.4 SP1. Observe after restore that the NMM version is reverted to 2.3 (NW137381)” on page 10

◆ “Using savegrp -e in NMM client shows failure (NW137222)” on page 10

◆ “Performance Counter Writer configuration data is not backed up in system drive (NW122499)” on page 11

◆ “NMM does not support machine names with more than 15 characters (NW126639)” on page 11

◆ “Online restore not supported for Windows Server 2008, 2008 R2, and 2012 (NW126455)” on page 11

◆ “NMM does not support Restricted Data Zone (NW145246)” on page 11

◆ “Backup of files and directories with special characters fails (LGTpa89319)” on page 11

◆ “Cannot use non-Microsoft disk management tools with software provider (NW121360)” on page 11

◆ “NMM backup fails if save sets contain special characters (LGTsc32726, NW121311)” on page 11

◆ “Nested mount points and content of nested mount points save set are incorrectly displayed in NMM GUI (NW115684, NW114120)” on page 12

◆ “Backup of SYSTEM COMPONENTS or All save set gives error due to improper uninstallation of a Microsoft application (NW115512)” on page 12

◆ “File system backup of mount points with data mover fails (NW00115510)” on page 12

◆ “Invalid temporary path created during Event Log writer recovery (LGTpa96400)” on page 13

◆ “Search results return everything from root node when searching from a subnode (LGTsc20731)” on page 13



Client parallelism optimization for backups is not supported in NMM (NW147575)

Do not use client parallelism optimization when performing backups in NMM.

After BMR is performed, ReFS non-critical volumes are online with no data but NTFS non-critical volumes are not online (NW143706)

When a combination of file system like NTFS, ReFS, and storage space volumes is used and BMR is performed, ReFS non-critical volumes are online with no data but NTFS non-critical volumes are not online. The NTFS mount points created inside NTFS critical volume is not online.

\Workaround

Microsoft does not support BMR on a host with pre-existing storage pool.

When configuration checks are run using the NMM installer, network configuration information is not displayed correctly for Hyper-V guest virtual machine (NW128528)

This issue is specific to Hyper-V virtual machines and there is no issue with physical and VMware virtual machines.

In the results page that is displayed after the configuration checks are run from the NMM installer, the check for NETWORK_ADAPTER_STATUS is displayed as “Fail” and a message that no adapter is found during check appears, although the network adapter is present.

Workaround

Perform a manual check for the Hyper-V network adapter.

NMM 2.4 SP1 does not support cluster volumes created by storage space in Windows 2012 (NW145868)

Cluster volumes created by storage space in Windows 2012 is not supported by NMM 2.4 SP1.

Incremental backups fail when run in parallel with full backups on an Avamar node (NW145239)

When incremental backups and full backups are performed simultaneously on an Avamar node, the incremental backups fail.

When the irccd.exe command is used to change Replication Manager ports, the operation does not respond, but the changes are effective (NW115040)

When Replication Manager’s (RM) control and data ports are changed by using the irccd -p command, the operation does not respond. Also, the new control and data ports are not updated in the rmps.res file in the C:\Program Files\Legato\nsr\rmagentps\client\bin path.

But when the irccd -s command is used to check, the new control and data ports are displayed.



Workaround

To make sure that the irccd.exe command responds:

1. Stop the RM service from services.msc.

2. Go to C:\Program Files\Legato\nsr\rmagentps\client\bin and open the rmps.res file.

3. Change the control and data ports in the rmps.res file.

4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\EMC\RMService\RMAgentPS\Client location in the registry, and change the ports by changing the following parameters:

• CC_DEFAULT_DATA_PORT

• CC_DEFAULT_PORT

5. Restart the RM service.

NWFS does not support write cache on Windows Server 2012 ReFS (NW143794)

NMM installation allows the NWFS cache directory to be placed on an ReFS drive. NWFS uses sparse files for writing cache files, but ReFS does not support sparse files.

After an NMM save set is cloned, the original VSS:\ save set is not recycled until the cloned VSS:\ save set expires (NW142181)

After an NMM save set is cloned, until the cloned VSS:\ save set expires the original VSS:\ save set is not recycled.

Backup fails with the VSS_E_UNEXPECTED_PROVIDER_ERROR error (NW143309)

Backups fails with “VSS_E_UNEXPECTED_PROVIDER_ERROR” when Microsoft iSCSI Target VSS Hardware Provider is not configured properly on a Windows Server 2012.

Workaround

Perform any one of the following steps:

◆ Configure Microsoft iSCSI Target VSS Hardware Provider by following the instructions provided in http://technet.microsoft.com/en-us/library/hh848268.aspx#BKMK_Step4

◆ Uninstall Microsoft iSCSI Target VSS Hardware Provider. In the Remove Roles and Features Wizard, select Remove server roles > Server Roles > File And Storage Services > File and iSCSI Services > iSCSI Target Storage Provider (VDS and VSS).

◆ Use the Application Information variable NSR_VSS_FORCE_SYSTEM_PROVIDER=yes to perform backups using the system provider. This workaround does not work for Hyper-V federated backups, where NSR_FEDERATED_BACKUP=yes is specified.

Data backup using Avamar storage device and IPv6 fails with Saverc -1 error (NW137696)

When IPv6 protocol and an Avamar storage device is used to back up data, the backup fails with an error.


http://technet.microsoft.com/en-us/library/hh848268.aspx#BKMK_Step4


NMM applies the pool specified in the Group Properties page during client resource configuration (NW139759)

Although a pool is specified in the Client Properties page during a client resource configuration, NMM applies the pool specified under Group Properties.

Workaround

Do not specify the pool in the Client Properties page to configure NMM backups.

When creating a new client resource, an error message appears if an alias already exists on the NetWorker server (NW139699)

When creating a new client resource either manually or by using the Client Configuration Wizard, if the alias being used already exists on the NetWorker server, an error message appears. For example:

Found alias: libho188 map using client id: <Client ID>. If renaming client :libho188 to libho188.sp2010.com specify this client ID. Otherwise, re-apply to create a new client id.

Here, a client resource was created using client ID libho188, and then a new client resource was created using client ID libho188.sp2010.com.

Workaround

Do either of the following:

◆ Create a new client ID by clicking Back and then Finish.

◆ If you do not want to create a new client ID, then use the same shortname to create the client resource each time when configuring backups. For example, if you have created the client resource with the shortname libho188, continue to use the same client ID for each client resource that is created. You cannot use the shortname once and the FQDN name the next time when creating client resources.

Back up SYSTEM COMPONENTS save set by using NMM 2.3 and restore using NMM 2.4 SP1. Observe after restore that the NMM version is reverted to 2.3 (NW137381)

After backing up the SYSTEM COMPONENTS save set with NMM 2.3 and then restoring using NMM 2.4 SP1, the NMM version is reverted back to 2.3.

Workaround

After restoring SYSTEM COMPONENTS using NMM 2.4 SP1, you must uninstall NMM 2.3 and reinstall NMM 2.4 SP1.

Using savegrp -e in NMM client shows failure (NW137222)

Although the -e option can be used in NetWorker to set the retention time for backup, using the -e option with the savegrp command for the same function in the NMM software shows failure. The -e option is invalid in NMM.



Performance Counter Writer configuration data is not backed up in system drive (NW122499)

NMM does not back up the Performance Counter Writer configuration distributed on non-system drives on Windows Server 2008 R2 (x64). According to Performance Writer Information, the data in the perf*.dat file, located in the system drive, should be backed up as per writer information.

The other nonsystem performance data is backed up with the file system and is recovered as part of file system recovery.

NMM does not support machine names with more than 15 characters (NW126639)

In NMM, when the machine name contains more than 15 characters, nsrsnap_vss_save -? does not provide any output.

Online restore not supported for Windows Server 2008, 2008 R2, and 2012 (NW126455)

Successful recovery of the system state to the same or a similar hardware can only be achieved through offline disaster recovery. A disaster recovery backup needs to be performed after SYSTEM COMPONENTS are changed. This includes adding, changing, removing roles and features, or installing Windows updates.

Online recovery of the SYSTEM COMPONENTS save set is not supported. Improper restore of the SYSTEM COMPONENTS save set online could lead to an inconsistent system state. The SYSTEM COMPONENTS save set can only be restored to the same Windows operating system instance.

NMM does not support Restricted Data Zone (NW145246)

Restricted Data Zone (RDZ) or multi-tenancy support is not supported by NMM.

Backup of files and directories with special characters fails (LGTpa89319)

The backup fails if the file and directory names contain:

◆ Extended ASCII characters such as those in French or Spanish. Some extended ASCII characters that are not symbol related may not display properly.

◆ Unicode characters. Details about unicode characters are provided in the NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide.

Cannot use non-Microsoft disk management tools with software provider (NW121360)

A disk management system that replaces Microsoft’s Disk Management tool, for example, the VERITAS Volume Manager, cannot use NMM with Microsoft’s system provider.

NMM backup fails if save sets contain special characters (LGTsc32726, NW121311)

If a save set contains the following special characters, the backup fails:

◆ <

◆ >

◆ $



◆ '

◆ "

◆ &

◆ /

◆ \

These special characters are not supported for NMM backup operations.

Nested mount points and content of nested mount points save set are incorrectly displayed in NMM GUI (NW115684, NW114120)

Nested mount point is not supported in NMM.

Backup of SYSTEM COMPONENTS or All save set gives error due to improper uninstallation of a Microsoft application (NW115512)

When uninstallation of a Microsoft application is not performed properly on the NMM client machine, backup with save set SYSTEM COMPONENTS or ALL fails with the “missing file” error in the nmm.raw file:

" 48488 3/25/2010 8:53:13 PM 1 0 0 6508 4892 0 son2k8x64.sonali2.com nsrsnap_vss_save PS: (CMTDXlator::GetCorrectFileSpec) Path component dialer.exe not on PIT path 'C:\Windows\System32\'.

Workaround

Specify the variable NSR_IGNORE_MISSING_SYSTEM_FILES=yes in the Application Information field when creating the client resource before performing backup of the SYSTEM COMPONENTS:\ or All save set. The backup is successful.

File system backup of mount points with data mover fails (NW00115510)

The following error message appears in NMC for a conventional file system backup of mount points with a data mover:

savegrp: suppressed 24 lines of verbose output43705:(pid 2968): Save Operations value is ignored on this OS platform.C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT2223549555.xml7167:(pid 2968): (pid 2968) completion time: 3/23/2010 12:00:46 AMNMM .. Request the PS backup service backup the GUI presentation objects to the

NetWorker saveset 'VSS:/'.76958:nsrsnap_vss_save:NMM .. successfully completed final processing of replica.77175:nsrsnap_vss_save:NMM .. completed commit replica with status of true.63334:nsrsnap_vss_save:NMM backup completed successfully.68150 1269327686 2 0 0 4272 2968 0 pensy-tom.becp.com nsrsnap_vss_save 39

nsrsnap_vss_save: Exiting with success. 0crname: "Y:\\z-mount";snap_sessionid: 1269327056;25048:nsrsnap_save: Y:\z-mount\: Failed.53294:nsrsnap_save: Backup failed.20123:nsrsnap_save: Backup operation failed.

Workaround

Ignore the error message because the backup is successful.



Invalid temporary path created during Event Log writer recovery (LGTpa96400)

When you recover a writer such as the System Components Event Log writer, an empty subdirectory is created at C:\temp\nsr_recover\timestamp\...\ ServiceState\EventLogs, where timestamp indicates the time and date of the recovery operation. The creation of this subdirectory does not create any performance issues, but the nsr_recover directory is not removed after the system is restarted.

Workaround

After the system is restarted, manually delete the nsr_recover directory.

Search results return everything from root node when searching from a subnode (LGTsc20731)

In the NMM System Recover Session window, if you use the context menu to search from within a folder that is located several levels deep in the navigation tree, the search operation displays results starting from the root node. This may occur when you right-click a subnode in the Browse pane and then click Search for. NMM switches to the Search tab, and the search path correctly displays the selected subnode. But when a search is performed, the results are displayed from the root node, and not from the selected subnode.

SQL Server limitations

This section lists the known problems and issues that involve SQL Server:

◆ “SQL Server 2012 cluster writer-level recoveries prompt for reboot after recovery (NW145309)” on page 14

◆ “For SQL Server (VDI), there is no correlation between the Change Browse Time entries and Backup Version entries in the Database Properties window (NW135919)” on page 14

◆ “Databases with AlwaysOn functionality are grayed out and can not be selected for recovery in the NMM GUI (NW134538)” on page 14

◆ “When migrating from NMSQL to NMM 2.4 SP1, use nsrsnap_vss_save.exe instead of the file system backup command save.exe (NW137458)” on page 15

◆ “Only SQL database log files are recovered when wrong data pass phrase is specified during recovery (NW136815)” on page 15

◆ “For SQL Server (VDI), the point-in-time GUI does not restrict the user from specifying time within the first full backup interval, but the restore fails (NW133696)” on page 15

◆ “For SQL Server backup, incorrect size is shown when full striped backup of a database is performed (NW133916)” on page 15

◆ “NMM does not support SQL compression for SQL 2005 SP4, although this support is provided from SQL Server 2005 SP2 onwards by Microsoft (NW131385)” on page 16

◆ “For SQL VSS, recovery of database fails when the database is renamed after backup (NW115036, NW121148)” on page 16

◆ “For SQL VSS, SQL Writer fails to recover a nonencrypted database to an encrypted SQL instance (NW125664)” on page 16



◆ “On a cluster with two virtual SQL Server instances, nsrsnap_vss_save command gives SQL writer as output (NW118904)” on page 17

◆ “Cannot browse folders of database instance in SQL Management Console after a successful recovery (NW123542)” on page 17

◆ “SQL database restore to compressed location fails (NW120267)” on page 18

◆ “For SQL VSS, directed recoveries of multiple SQL databases when run in parallel fail intermittently (NW114905)” on page 18

◆ “NMM fails to clean up files after failure of SQL directed recovery (NW112203)” on page 18

SQL Server 2012 cluster writer-level recoveries prompt for reboot after recovery (NW145309)

Although the recovery of SQL Server cluster writer-level is successful, you are prompted to restart the SQL Server.

Workaround

Restart the SQL Server when prompted.

For SQL Server (VDI), there is no correlation between the Change Browse Time entries and Backup Version entries in the Database Properties window (NW135919)

There is no correlation between the Change Browse Time (CBT) entries and the Backup Version entries in the Database Properties window. The backup time that is displayed is different in the two lists. And even if interleaving full and incremental backups are performed, CBT cannot be used to change the Browse Time to the backup version specified in the Backup Versions entry in the Database Properties window.

Workaround

You can change the CBT to the last backup when the database was available for restore and use the Point-in-Time (PIT) option to specify the exact time.

When performing a Copy restore and the last available backup of the database is a full backup, the PIT option cannot be used. PIT can only be specified with incremental or transaction log backups. You must change the CBT to the last incremental backup before the last full backup and then use the PIT option.

For example, full backup A has been performed, followed by incremental backup B, followed by full backup C. Copy restore of C with PIT cannot be performed. You must change the CBT to B and then use the PIT option.

Databases with AlwaysOn functionality are grayed out and can not be selected for recovery in the NMM GUI (NW134538)

During SQL Server 2012 recovery, you are not allowed to mark databases that are configured with the AlwaysOn functionality and a message “Cannot mark fake item” appears. The databases with AlwaysOn functionality are grayed out and can not be selected.



Workaround

To be able to mark a database for restore, you must break the AlwaysOn relationship.

When migrating from NMSQL to NMM 2.4 SP1, use nsrsnap_vss_save.exe instead of the file system backup command save.exe (NW137458)

Using the save.exe command when backing up the ALL save set or performing file system backup leads to error.

Workaround

Do the following:

◆ Use the nsrsnap_vss_save.exe command instead of save.exe command when backing up the ALL save set or file system.

◆ Update the client configurations for VSS based backup:

• Use Application Information variable NSR_SNAP_TYPE=VSS.

• Ensure that the group running the file system backup is snapshot enabled. The group can be a new or existing group.

Only SQL database log files are recovered when wrong data pass phrase is specified during recovery (NW136815)

When a recovery of a SQL database is performed by specifying an incorrect data pass phrase, the recovery fails. However, a partial .log file is recovered to the hard drive location. The SQL database in inconsistent state can be viewed in the SQL Management Studio.

Workaround

To prevent this problem, perform the recovery by specifying the correct pass phrase.

If an incorrect data pass phrase is specified and recovery has failed, perform the following steps:

1. Manually clean up the SQL database in inconsistent state from the SQL Management Studio by deleting the database from SQL Management studio.

2. Delete the .ldf file from the hard drive location to which the recovery was performed.

For SQL Server (VDI), the point-in-time GUI does not restrict the user from specifying time within the first full backup interval, but the restore fails (NW133696)

The restore fails when a time is specified within the first full backup interval from the point-in-time GUI.

For SQL Server backup, incorrect size is shown when full striped backup of a database is performed (NW133916)

The incorrect size of the striped backup is shown in the NMC for SQL Server VDI.



Workaround

To find the correct size of the striped backup, run the mminfo command:

mminfo -c nmmda184 -r "volume,client,savetime(26),sumsize,level,name”

For example, for a striped backup of a database size 1431 KB, the output of the command will be:

nmmda223.multinic.com.001 nmmda184 1/6/2012 4:36:30 PM 668 KB full MSSQL:test_db_2 nmmda223.multinic.com.001 nmmda184 1/6/2012 4:36:29 PM 798 KB full MSSQL:test_db_2

These entries represent two stripes. The cumulative size of these two stripes is 668+798 = 1466 KB.

NMM does not support SQL compression for SQL 2005 SP4, although this support is provided from SQL Server 2005 SP2 onwards by Microsoft (NW131385)

SQL compression is not supported in SQL Server 2005 SP4 by NMM.

For SQL VSS, recovery of database fails when the database is renamed after backup (NW115036, NW121148)

If a database is renamed after a backup, VSS recovery of the database fails. This feature is not supported in NMM.

Workaround

To rename a database and its underlying data files, select the Tasks and Copy Database options in the SQL Management Studio menu for the database. The wizard offers a choice to move rather than copy the database. The wizard also provides the option of renaming the data files.

For SQL VSS, SQL Writer fails to recover a nonencrypted database to an encrypted SQL instance (NW125664)

Restoring a nonencrypted SQL database to an encrypted SQL instance puts the encrypted database in a suspect mode where the encrypted database is not usable.

Workaround

Restore the following:

◆ A non-encrypted SQL database to a non-encrypted SQL instance.

◆ An encrypted SQL database to an encrypted SQL instance.



On a cluster with two virtual SQL Server instances, nsrsnap_vss_save command gives SQL writer as output (NW118904)

On a cluster that hosts two virtual SQL Server instances, the nsrsnap_vss_save -c sql2008-cluster -? command displays the following output:

◆ For one instance:

APPLICATIONS:\SqlServerWriterAPPLICATIONS:\SqlServerWriter\SQL2008-CLUSTERAPPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\masterAPPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\modelAPPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\msdbAPPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\db-11APPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\db-filegrp

◆ For a second instance:

APPLICATIONS:\SqlServerWriterAPPLICATIONS:\SqlServerWriter\CLUSTER2008%5CCLUSTER2008APPLICATIONS:\SqlServerWriter\CLUSTER2008%5CCLUSTER2008\masterAPPLICATIONS:\SqlServerWriter\CLUSTER2008%5CCLUSTER2008\modelAPPLICATIONS:\SqlServerWriter\CLUSTER2008%5CCLUSTER2008\msdb

Although it is not possible to perform a writer-level backup on the cluster that hosts two or more virtual SQL instances, both the outputs include APPLICATIONS:\SqlServerWriter.

Workaround

Review the requirements between SQL virtual server and physical client:

◆ SQL virtual server:

When a SQL Server is installed in a cluster setup, it is accessed using the virtual name that is provided during installation. This virtual name is used by NMM when performing a backup of the SQL Server instance.

In a cluster setup, to view the save set run the following command on an active node:

nsrsnap_vss_save -? -c <virtual sql server>

◆ Physical client:

When a SQL Server is installed in a noncluster setup, it does not require any virtual name or IP.

In a noncluster setup, to view the save set run the following command:

nsrsnap_vss_save -?

Cannot browse folders of database instance in SQL Management Console after a successful recovery (NW123542)

Although the database instance is visible in the SQL Management Console after successful recovery, the folders of the database instance cannot be browsed.

Workaround

If the database and SQL instance credentials are different, perform only database-level restore operations.



SQL database restore to compressed location fails (NW120267)

When SQL databases are backed up from a compressed drive or folder, the recovery of the SQL databases to the same compressed location fails.

Workaround

Perform a directed recovery to an alternate location. Restore the data to a similar folder structure in the location that is not compressed. In the case of writer-level backups, restore the databases one by one.

For SQL VSS, directed recoveries of multiple SQL databases when run in parallel fail intermittently (NW114905)

Only partial data is recovered during directed recovery of multiple databases that were recovered in parallel.

Workaround

For SQL directed recovery, recover one database at a time.

NMM fails to clean up files after failure of SQL directed recovery (NW112203)

When the SQL database is being restored during an SQL directed recovery, the recovery process might create copies of database files (.mdf and .ldf) at the restore location. If recovery fails due to any issues, NMM does not clean up these partially restored files from the restore location hard drive.

Workaround

Manually clean up the partially restored SQL database files from restore location. It is especially important to perform this manual cleanup after the failure of the directed recovery of a large SQL database because the copies of the database files will take up the available hard drive space and subsequent recovery will fail.

Exchange Server limitations

This section lists the known problems and issues that involve Exchange Server:

◆ “Exchange Server 2010 in hosting mode is not supported with NMM 2.4 SP1 (NW130301)” on page 20

◆ “In Exchange Server 2007 and 2010, manually mount database if mount fails (NW142346)” on page 20

◆ “EMC Reports is not functioning in Exchange Server 2007 and 2010 environments (NW146275)” on page 20

◆ “In Exchange Server 2010 DAG, the Back and Next buttons in the Client Configuration Wizard are not functioning correctly when modifying a client instance (NW144185)” on page 20

◆ “The NMM GUI stops responding when an empty folder is opened on Exchange Server (NW146162)” on page 21



◆ “The transaction log files of Exchange Server must not be present at the root level of a mount point (NW146056)” on page 21

◆ “In Exchange Server 2010, unhandled exception occurs when mounting RDB after failed recovery (NW139317)” on page 21

◆ “In Exchange Server 2010, retention policy 4, 2, or All is not working properly when multiple client backups are performed using the same group at the same time (NW139706)” on page 21

◆ “For Exchange Server 2007 and Exchange Server 2010, CPb entries are not deleted from volumes after retention (NW139117)” on page 22

◆ “NMM 2.4 SP1 MAPI requirements are not compatible with Microsoft Outlook/Office (NW135007)” on page 22

◆ “In Exchange Server 2010, recovery of a deleted database to RDB cannot be performed (NW133385)” on page 22

◆ “RSG item recoveries fail if more than 500 Exchange Server 2007 folder objects are created per MAPI session (NW126557, NW126351)” on page 22

◆ “In Exchange Server 2010, only the first RDB user item can be browsed in NMM GUI (NW125623)” on page 23

◆ “In Exchange Server 2010, user mailbox does not appear in RDB recovery window unless the mailbox contains at least one email message (NW125556)” on page 23

◆ “In Exchange Server 2010, RDB item level recovery fails with “insufficient permissions to access mailbox” error (NW122293)” on page 23

◆ “In Exchange Server 2007, NMM supports only mailbox recovery to RSG if Logs Path and SysPath are in different folder but on same volume (NW125367)” on page 23

◆ “In Exchange Server 2010 DAG, database-level incremental backup is promoted to full backup, if the save set list includes database that has never been backed up before (NW122668)” on page 25

◆ “Cannot browse Exchange Server 2010 RDB on a stand-alone server (NW125038)” on page 25

◆ “Alternate storage group directed recovery with different Exchange versions displays error message while mounting the database (NW105628)” on page 25

◆ “Incremental backup is promoted to full backup for Exchange Server 2010 DAG mailbox server (NW123550)” on page 25

◆ “Exchange Server 2007 SP3 backup with NMM requires hotfix (NW123514, NW121777)” on page 26

◆ “Exchange Server 2010 stand-alone hardware provider backup fails if failover cluster role is installed (NW120735)” on page 26

◆ “Recovery fails if new mailbox database is created (NW120335)” on page 26

◆ “For Exchange Server 2010, backup fails if a logs volume and a database mount point volume are the same and in the same save set (NW113760)” on page 27

◆ “Exchange snapshot recovery fails with ImportCopy error (LGTsc25761)” on page 27



Exchange Server 2010 in hosting mode is not supported with NMM 2.4 SP1 (NW130301)

NMM 2.4 SP1 does not support Exchange Server 2010 in hosting mode.

In Exchange Server 2007 and 2010, manually mount database if mount fails (NW142346)

When performing a database recovery of Exchange Server 2007 and 2010, the following error appears:

NMM .. Failed to mount Mailbox Store "<database name>". Client will not attempt any further mounts.

Where “<database name>” is the name of the database.

Workaround

Manually mount the database using the Exchange Management Shell command:

Mount-Database "<database name>"

EMC Reports is not functioning in Exchange Server 2007 and 2010 environments (NW146275)

In Exchange Server 2007 and 2010, EMC Reports is not functioning correctly.

Workaround

Perform the following steps:

1. Go to Start > Programs > EMC NetWorker > NetWorker Tools, and expand to locate NMM EMC Reports.

2. Right-click on NMM EMC Reports, select Properties. Locate and copy the following path from Target column:

C:\Windows\system32\cmd.exe /c ""C:\Program Files\EMC NetWorker\nsr\support\nmm log collector\emcrpt.cmd" -nmm -path "C:\Program Files\EMC NetWorker\nsr\support\nmm log collector\reports""

3. Delete \reports from the path.

4. Go to Start > Run and copy the updated path in the field:

C:\Windows\system32\cmd.exe /c ""C:\Program Files\EMC NetWorker\nsr\support\nmm log collector\emcrpt.cmd" -nmm -path "C:\Program Files\EMC NetWorker\nsr\support\nmm log collector\

5. Click OK to run NMM EMC Reports.

In Exchange Server 2010 DAG, the Back and Next buttons in the Client Configuration Wizard are not functioning correctly when modifying a client instance (NW144185)

When trying to modify a dummy client instance by using the Client Configuration Wizard for Exchange Server 2010 DAG, the Back or Next buttons do not display the relevant page.

Workaround

Click the hyper-links on the left of the wizard window to go to the respective pages.



The NMM GUI stops responding when an empty folder is opened on Exchange Server (NW146162)

From the NMM GUI, if you browse and open an empty folder on Exchange Server, the GUI stops responding.

Workaround

Do the following:

1. Start Windows Task Manager.

2. Under the Processes tab, end the winclient.exe process.

The NMM GUI exits.

3. Open the NMM GUI.

4. Ensure that you browse and open a folder that contains data.

The transaction log files of Exchange Server must not be present at the root level of a mount point (NW146056)

NMM 2.4 SP1 does not back up the transaction log files if they are present at the root level of a mount point.

Workaround

Ensure that the transaction log files of Exchange Server are not present at the root level of a mount point.

In Exchange Server 2010, unhandled exception occurs when mounting RDB after failed recovery (NW139317)

Sometimes, after an RDB recovery failure, when the RDB is dismounted and the NMM GUI is left open for a few days without use, and the RDB is then remounted, unhandled exception occurs.

Workaround

Close and reopen the NMM GUI.

In Exchange Server 2010, retention policy 4, 2, or All is not working properly when multiple client backups are performed using the same group at the same time (NW139706)

When more than one node is being used for backup, and all these nodes are using the same backup group, retention policies 4, 2, or All is not working.

Workaround

When using snapshot policy 4, 2, or All, perform only one Exchange Server 2010 client backup at a time with a particular backup group. Multiple Exchange 2010 client backups using same backup group must not be performed.



For Exchange Server 2007 and Exchange Server 2010, CPb entries are not deleted from volumes after retention (NW139117)

After passive node backups are performed with 1/1/Day All policy, CPb entries are not properly deleted from volumes after retention. Although the snapshots are deleted based on the snapshot policy, at least one extra CPb entry is present apart from the CPb entries for the snapshots.

Workaround

Clean up snapshots and associated flags properly after successful retention.

RM_ExchangeInterface service does not start if a long password is used during user login, and backups fail (NW137569)

If a long password or a password with space, for example B@chup Lottery Network, is used during user login, the RM_ExchangeInterface.exe service does not start and backups fail.

Exchange Server 2010 DAG backups fail when the Dedicated Storage Node option is selected under Device Properties (NW137550)

Exchange Server 2010 DAG backups fail when the Dedicated Storage Node option is selected under Device Properties.

Workaround

Use a regular storage node (RSN) license for an Exchange Server 2010 DAG backup.

NMM 2.4 SP1 MAPI requirements are not compatible with Microsoft Outlook/Office (NW135007)

The MAPI server version of Microsoft Outlook/Office is not compatible with the MAPI server version that is part of the MAPI/CDO kit being used by NMM. This is a known Microsoft restriction.

Workaround

Microsoft Outlook/Office cannot be installed on the Exchange Server when NMM is being used. If access to mail is desired, install Microsoft Outlook/Office on a client machine.

In Exchange Server 2010, recovery of a deleted database to RDB cannot be performed (NW133385)

NMM does not support recovery of a deleted Exchange 2010 database to RDB.

RSG item recoveries fail if more than 500 Exchange Server 2007 folder objects are created per MAPI session (NW126557, NW126351)

By default, MAPI allows the creation of only 500 folder objects per session in Exchange 2007.



During RSG item-level recovery for a bulk number of users, recoveries fail with the following error messages if more than 500 folder objects per session are created:

Calendaring agent failed with error code 0x8000ffff while saving appointment.

Mapi session "Microsoft System Attendant" exceeded the maximum of 500 objects of type "objtFolder".

Workaround

Follow the procedure in this Microsoft Knowledgebase article to change the value in the registry key: http://technet.microsoft.com/en-us/library/aa997425%28EXCHG.80%29.aspx

After making the changes specified in the Microsoft Knowledgebase article, restart Microsoft Exchange Information Store service for the changes to take effect.

In Exchange Server 2010, only the first RDB user item can be browsed in NMM GUI (NW125623)

After a successful RDB recovery operation, you can use the NMM GUI to browse only the first RDB user item. Subsequent RDB user items cannot be browsed.

In Exchange Server 2010, user mailbox does not appear in RDB recovery window unless the mailbox contains at least one email message (NW125556)

After a successful RDB recovery in Exchange 2010, NMM does not display a user mailbox in the RDB recovery window if the mailbox does not contain at least one e-mail message.

In Exchange Server 2010, RDB item level recovery fails with “insufficient permissions to access mailbox” error (NW122293)

If the mailbox database where the currently logged-in user mailbox resides is not mounted, then an RDB item-level recovery might fail with the following error message:

Insufficient permissions to access mailbox

Workaround

To be able to browse the contents in RBD, ensure that the mailbox database where the currently logged-in user mailbox resides is mounted. MAPI communicates with the RDB mailbox through the currently logged-in user mailbox.

For example, if the user is logged in as Administrator, the mailbox database that contains the Administrator mailbox should be mounted.

In Exchange Server 2007, NMM supports only mailbox recovery to RSG if Logs Path and SysPath are in different folder but on same volume (NW125367)

In a Microsoft Exchange 2007 CCR passive node backup scenario, the NMM software only supports restores from mailbox recovery to a RSG item-level recovery if the storage groups where LogsPath and SysPath are in different folders but on the same volume have been backed up.


http://technet.microsoft.com/en-us/library/aa997425%28EXCHG.80%29.aspx


In this type of configuration, the NMM software supports mailbox recovery to RSG. RSG item-level recovery can also be performed.

The NMM software does not support point-in-time mailbox recovery in this configuration.

Workaround

To perform an RSG recovery operation for all passive node backups that were performed with the NMM 2.2.1 software prior to build 123 where the Exchange logs path and system path are in different folders but are on the same volume:

1. On the Microsoft Exchange Server, select Start > All Programs > Exchange Management Shell - Enable Send-As and Receive-As permission.

For example:

get-ExchangeServer <Exchange Server name> |Add-AdPermission -user <username> -extendedrights Receive-As, Send-As

2. Ensure that the following MAPI/CDO kit is installed:

Microsoft Messaging API and Collaboration Data Objects 1.2.1

3. For Windows Server 2008, ensure that IPv6 is disabled. The NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide provides information on how IPv6 might cause browsing issues on RSG mailboxes.

4. Create an RSG for the required storage group by selecting the storage group to link with the Recovery Storage Group.

5. Change the log path and the system path to point to the same folder that is on the same volume.

6. Use the NMM software to start the RSG recovery:

a. Start the NMM GUI.

b. Select the virtual Exchange Server by using the client menu list.

c. Select the storage group for which you created the RSG.

d. Select View Versions to mark the required recovery date.

e. Select the storage group for which the RSG was created.

f. Select Restore to - Recovery Storage Group.

g. Click OK.

h. Click Recover to start the RSG recovery.



In Exchange Server 2010 DAG, database-level incremental backup is promoted to full backup, if the save set list includes database that has never been backed up before (NW122668)

In Exchange 2010 DAG, database-level incremental backup is promoted to a full backup, if the save set contains both active or passive copies of databases with the attributes NSR_EXCH2010_BACKUP=passive and NSR_EXCH2010_BACKUP=active, and one of the databases has never been backed up.

If all databases listed have been backed up at least once, this does not occur.

Cannot browse Exchange Server 2010 RDB on a stand-alone server (NW125038)

Exchange Server 2010 must have an administrative mailbox to browse an RDB with NMM. This mailbox is created by default. Sometimes, the Active Directory entry for this mailbox becomes corrupt and leads Exchange to believe the following:

◆ The mailbox does not exist.

◆ The user (administrator) already has a mailbox and will not let you create a mailbox.

Workaround


1. Manually remove all Exchange Active Directory entries for the administrator by using ADSI edit.

The administrator is visible.

2. Recreate a mailbox for the administrator.

After the new mailbox is created, you can browse the RDB.

Alternate storage group directed recovery with different Exchange versions displays error message while mounting the database (NW105628)

If you back up an Exchange database using one version of Exchange and perform a recovery using another version of Exchange, the recovery is successful. However, while mounting the database, the following error message is displayed:

Database "<Storage Group\Database>" is too new to be upgraded.

Workaround

Ensure that the same version of Exchange database is used for both backup and recovery.

Incremental backup is promoted to full backup for Exchange Server 2010 DAG mailbox server (NW123550)

An incremental backup is promoted to a full backup for a DAG mailbox server that does not have a client resource.

Workaround

Ensure that you have created the required number of Exchange Server 2010 DAG mailbox server client resources. You must create a client resource for each node.



Exchange Server 2007 SP3 backup with NMM requires hotfix (NW123514, NW121777)

Exchange 2007 Service Pack 3 Update Rollup 1 is required with NMM 2.2 SP1 or NMM 2.4 SP1. This is applicable for stand-alone, CCR, LCR, and SCC configurations.

Workaround

Install this hotfix from http://support.microsoft.com/kb/982118/ on the Microsoft website.

Exchange Server 2010 stand-alone hardware provider backup fails if failover cluster role is installed (NW120735)

Exchange Server 2010 stand-alone hardware provider backups fail if failover cluster management roles are installed in the stand-alone setup.

Workaround

Perform the following steps to remove a machine from Exchange Server 2010 DAG to enables backup of the machine as a stand-alone server:

1. Stop replication for all replicated databases from the mailbox server.

2. Remove all of the replicated databases from the mailbox server.

3. Remove the mailbox server from DAG by using the following command:

Remove-DatabaseAvailabilityGroupServer -Identity DAG3 -MailboxServer NMMDA189.NMMEXCH2010.com

4. Open the Server Manager and select Features.

5. Select Remove Features.

6. Remove the failover clustering role and reboot the machine.

7. Remove the DAG-related Application Information variables from the mailbox server client resource by using the NMC.

Recovery fails if new mailbox database is created (NW120335)

After backing up a storage group, if you create a new mailbox in the same storage group and then try to recover the storage group, the recovery fails.

Workaround

Dismount the newly created database, back up the storage group, and then recover the backup.


http://support.microsoft.com/kb/982118/


For Exchange Server 2010, backup fails if a logs volume and a database mount point volume are the same and in the same save set (NW113760)

Backup fails if a logs volume and a database mount point volume are the same (for example, D:\) and are in the same save set.

Backup fails with the following message:

RM .. 026420 ERROR:An unexpected internal error occurred:IRD:mountRestoreState::handleFinalStatusMsg() :validateState::runState() failed.

Exchange snapshot recovery fails with ImportCopy error (LGTsc25761)

For Exchange, do not use persistent software shadow copy or copy-on-write backups. Due to the way the data is distributed in Exchange databases, the snapshots for these backups might not remain valid long enough for the recovery to be successful.

The NMM software supports temporary software shadow copy or copy-on-write backups for Exchange, which might be necessary if your system does not use a CLARiiON or similar hardware storage array. For persistent snapshot support in an Exchange environment, use a hardware storage array in your Exchange backup and recovery strategy.

If a persistent software copy or copy-on-write backup is performed on an Exchange database, recovery may fail with an error message similar to the following:

%sERR: Error calling importCopy, status=%d:'%s' 3 0 35 PS: (CPSImportService::ImportCopy) 1 2 15 24 107 Error obtaining volume name (s) for snapshot; Microsoft ShadowCopy Service has no knowledge of the snapshot.

Workaround

Always follow these recommended practices:

◆ Do not use persistent software shadow copy or copy-on-write for Exchange backups.

◆ Configure the NMM backup client resource snapshot policy to use the backup=all setting.

◆ Use a hardware storage array to handle backup, recovery, and storage operations. This minimizes the load on the Exchange Server storage and resources by moving these operations to separate hardware.

The NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide provides instructions for configuring a client resource.

SharePoint limitations

This section lists the known problems and issues in Microsoft SharePoint:

◆ “New features in SharePoint Server 2013 are not supported by NMM 2.4 SP1 (NW143356)” on page 29

◆ “When using the Configuration Wizard to create client resources for SharePoint, a client resource with more than 30 SQL save sets can be created, however backup fails (NW139739)” on page 29



◆ “The SharePoint GLR mount option is inconsistently enabled and disabled when SYSTEM COMPONENTS:\ and SharePoint Writer are backed up together (NW137841)” on page 29

◆ “Sometimes the NMM GUI does not enable the mount SharePoint GLR option during SQL Server directed recovery (NW137547)” on page 29

◆ “Creation of client resource fails with error message “Group already exists - first create client using shortname” (NW135727)” on page 29

◆ “Although one SQL instance is selected for GLR, there is inconsistency in mounting (NW135722)” on page 30

◆ “Sometimes unwanted NMM SharePoint Shell messages are displayed in nmm.raw (NW132359)” on page 30

◆ “SharePoint Configuration Wizard fails with error “... is longer than the maximum size [64 bytes] allowed” on simplified Chinese setup (NW137732)” on page 30

◆ “In SharePoint Server 2010, published shared services between two farms does not list save set for the first farm backup (NW122691)” on page 30

◆ “In SharePoint Server 2007 and SharePoint Server 2010, if SQL Express is used in stand-alone environment and hardware providers are used, the backup fails (NW123598)” on page 30

◆ “Restriction on Admin component of search in SharePoint 2010 (NW123480)” on page 30

◆ “SharePoint Server 2010 writer backup is not browsable when multiple instances of same client are backed up by using different save sets (NW125218)” on page 31

◆ “After a SharePoint Server 2010 recovery, the Search Application is in an unprovisioned state (NW123624)” on page 31

◆ “In SharePoint Server 2010, NMM does not support backup and recovery of FAST Search Server (NW124707)” on page 32

◆ “Administration site host cannot be linked to its original Shared Service Provider after NMM recovery (NW114300)” on page 32

◆ “Directed recovery of SharePoint Server 2010 configuration database fails because the SharePoint wizard cannot connect to the recovered database (NW123768)” on page 32

◆ “If SharePoint Foundation Search V4 program is stopped, backup fails with error (NW122193)” on page 32

◆ “Directed recovery fails for Administration Content database, Shared Services database, and Crawl database (NW123776)” on page 33

◆ “Recovery fails when hardware and software backups are performed at the same time (NW115573)” on page 33

◆ “Intermittent backup failure seen on farm node where search services are hosted (NW115363)” on page 33

◆ “Manual steps required for SharePoint writer after recovery to associate web application to original SSP (NW105541)” on page 34



◆ “SharePoint Server 2007 VSS writer backup and recovery fail on Windows Server 2008 R2 (NW118982, NW120044, and NW118258)” on page 34

◆ “In SharePoint Server 2007 SP2 and SharePoint Server 2007 SP3, recovery of web application and SSP fails when the October CU patch is not applied (NW125432, NW137564)” on page 34

New features in SharePoint Server 2013 are not supported by NMM 2.4 SP1 (NW143356)

NMM 2.4 SP1 does not support backup and recovery of SharePoint Server 2013 applications, for example SharePoint Server 2013 application store.

When using the Configuration Wizard to create client resources for SharePoint, a client resource with more than 30 SQL save sets can be created, however backup fails (NW139739)

When the Configuration Wizard is used to create a SharePoint client resource with more than 30 save sets, and the clients resource is created successfully, but the backup fails with a non-retryable error.

Workaround

For successful backup, ensure that fewer than 30 SQL save sets are used when creating a client resource by using the Configuration Wizard for SharePoint.

The SharePoint GLR mount option is inconsistently enabled and disabled when SYSTEM COMPONENTS:\ and SharePoint Writer are backed up together (NW137841)

The SharePoint GLR mount process hangs when backups of SYSTEM COMPONENTS:\ and SharePoint Writer are performed.

Workaround

Backup only the SharePoint Writer. This backs up the SQL Embedded databases as dependent components. Backup of SYSTEM COMPONENTS:\SQL Embedded cannot be performed.

Sometimes the NMM GUI does not enable the mount SharePoint GLR option during SQL Server directed recovery (NW137547)

The mounting option for SharePoint GLR is sometimes unavailable during SQL Server directed recovery.

Workaround

Restart the NMM GUI.

Creation of client resource fails with error message “Group already exists - first create client using shortname” (NW135727)

If a client resource is created using the short name but later the Configuration Wizard is used to make modifications and the FQDN name of the client is used, the Configuration Wizard will not create the client resource.



Although one SQL instance is selected for GLR, there is inconsistency in mounting (NW135722)

For SharePoint GLR, only one database can be selected for granular recovery. If the SQL Server is backed up at the writer level and the SQL instances are on multiple volumes, then NMM generates multiple save set IDs and all the databases contained in the given save set ID are mounted.

Workaround

You are able to see the database that was selected and this database is available for granular recovery. Ignore the other databases that are not selected but are mounted.

Sometimes unwanted NMM SharePoint Shell messages are displayed in nmm.raw (NW132359)

Sometimes when SharePoint 2010 SP1 backup is performed, a number of unwanted NMM SharePoint Shell messages appear in the nmm.raw file.

Workaround

Ignore these messages.

SharePoint Configuration Wizard fails with error “... is longer than the maximum size [64 bytes] allowed” on simplified Chinese setup (NW137732)

On simplified Chinese setup, the SharePoint Configuration Wizard fails with error:

MICROSOFT OFFICE SHAREPOINT SERVICES\309BEA3B-64DB-4517-9612...' is longer than the maximum size [64 bytes] allowed.

In SharePoint Server 2010, published shared services between two farms does not list save set for the first farm backup (NW122691)

A SharePoint 2010 writer does not report a cross-farm association of a web application. A cross-farm association is established after restoring the web application.

In SharePoint Server 2007 and SharePoint Server 2010, if SQL Express is used in stand-alone environment and hardware providers are used, the backup fails (NW123598)

In SharePoint 2007 and 2010, if SQL Express is used in a stand-alone environment and hardware providers are used, the backup fails.

Workaround

If SQL Express is used in a stand-alone environment, use the following parameter:

NSR_VSS_FORCE_SYSTEM_PROVIDER=yes

NMM does not support hardware provider backups for SharePoint 2007 and 2010, which is configured with SQL Express.

Restriction on Admin component of search in SharePoint 2010 (NW123480)

There is a Microsoft restriction that the Admin component of Search cannot be changed or moved inside the same SharePoint Server after installation.



For hardware backups to succeed for SharePoint 2010, all SharePoint search components should be installed only on the hardware LUN.

For example, if SharePoint is installed on a local drive, such as C:\, and the index location and query component are moved to a hardware LUN but the Admin component of search is not moved, the hardware backup fails due to the Microsoft restriction. This happens because the backup tries to mix both hardware and software backups, which is not a supported configuration.

Workaround

To continue the backup with the software provider only, use the following parameter:

NSR_VSS_FORCE_SYSTEM_PROVIDER=yes

SharePoint Server 2010 writer backup is not browsable when multiple instances of same client are backed up by using different save sets (NW125218)

The SharePoint writer backup is not browsable in the NMM GUI when multiple instances of the same client are backed up by using different save sets.

For example:

◆ Backup1 runs the SharePoint writer data backup:

ClientA.sharepoint.com APPLICATIONS:\Microsoft Office SharePoint Services

◆ Backup2 runs the SQL writer data backup:

ClientA.sharepoint.com APPLICATIONS:\SqlServerWriter

After Backup2 completes, the Backup1 data of SharePoint writer cannot be browsed.

Workaround

To recover the SharePoint writer, change the browse time.

After a SharePoint Server 2010 recovery, the Search Application is in an unprovisioned state (NW123624)

In SharePoint 2010, after a restore operation:

1. The Search Application is unprovisioned.

2. The event ID (6482) is generated.

3. The successive backup fails with a NULL appearing in the nsrsnap_vss_save -? command under the search save sets.

Workaround

After the SharePoint writer recovery operation is complete, restore either of the following:

◆ System components

◆ Registry writer

Because individual writers under SYSTEM COMPONENTS can be selected, the Microsoft best practices option must be cleared to restore the registry writer.



In SharePoint Server 2010, NMM does not support backup and recovery of FAST Search Server (NW124707)

NMM supports the backup and recovery of the following:

◆ FAST Query Search Service Application

◆ FAST Content Search Service Application

These applications crawl and index the contents to the FAST Search server. The backup and restore operations of the FAST Query Search Service Application and the FAST Content Search Service Application are similar to the default search applications.

NMM does not support backup and recovery of the FAST Search Server. The FAST Search sever is a different product and has its own backup and restore scripts. The FAST Search server consists of index data and a configuration database. This content should be backed up by using the FAST Search Applications scripts. The Microsoft documentation provides more information.

Administration site host cannot be linked to its original Shared Service Provider after NMM recovery (NW114300)

If there are two Shared Service Providers (SSP), and the association for an administration site host (the web application) is deleted, the association cannot be manually created after NMM recovery.

Directed recovery of SharePoint Server 2010 configuration database fails because the SharePoint wizard cannot connect to the recovered database (NW123768)

If you perform a directed recovery of a SharePoint 2010 configuration database and try to browse the data by using the SharePoint Configuration Wizard, the SharePoint Configuration Wizard cannot connect to the recovered database.

If SharePoint Foundation Search V4 program is stopped, backup fails with error (NW122193)

If the SharePoint Foundation Search V4 service is configured in a SharePoint farm and this service is stopped in services.msc, the backup fails with the following error:

APPLICATIONS:\Microsoft Office SharePoint Services is valid63778:nsrsnap_vss_save:NMM .. ERROR..Writer SharePoint Services Writer with local dependent writer id { comp ContentIndex_SPSearch4 cannot be found. CONTINUE PROCESSING.

63335:nsrsnap_vss_save:NMM backup failed to complete

The nsrsnap_vss_save -? output also displays NULL for the dependent components.

Workaround

Restart the SharePoint Foundation Search V4 service and then perform a backup.



Directed recovery fails for Administration Content database, Shared Services database, and Crawl database (NW123776)

Although the content of the following databases is browsable at the alternate host recovery site, directed recovery of these databases in SharePoint farm is not supported:

◆ Administration Content database

◆ Shared Services database

◆ Crawl database

The NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide provides detailed disaster recovery procedures for SharePoint.

Recovery fails when hardware and software backups are performed at the same time (NW115573)

A SYSTEM COMPONENTS recovery fails with the following error if components are configured on both local software LUN and hardware LUN, such as CLARiiON or Symmetrix:

NMM .. Starting Recovery. This operation may take a long time depending on the size of the data requested.

77108:nsrsnap_vss_recover:NMM .. Operation unit failed with error 'No such file or directory'.Possible cause: 1)Unsupported file system or 2)write-protected disc or 3)No space on disc

This error is commonly seen for a SharePoint Server that hosts search services on a hardware LUN. When full system components are recovered, some components reside on C:\ and Microsoft Office SharePoint Search components reside on a hardware LUN.

Workaround

Recover SYSTEM COMPONENTS:\Microsoft Office Search or SYSTEM COMPONENTS:\Microsoft Office SharePoint Search independently and other system components separately.

Intermittent backup failure seen on farm node where search services are hosted (NW115363)

Intermittent backup failure is seen on the farm node where search services are hosted. Backup fails and the following error message appears:

Format string Save set name %S is valid cannot be rendered correctly63778:nsrsnap_vss_save:NMM .. ERROR..Writer SharePoint Services Writer

with local dependent writer id { comp ContentIndex_SPSearch cannot be found. CONTINUE PROCESSING.

This error is generally expected when search services or dependent services are not running. However, it is also seen in some cases when all dependent services and search services are running.

Workaround

Restart the search services to ensure a successful backup.



Manual steps required for SharePoint writer after recovery to associate web application to original SSP (NW105541)

The original association of a web application to an original SSP is not restored when the association of the web application to the original SSP is changed after backup. However, the data is recovered successfully.

Workaround

You must perform the following steps to associate the original SSP with the appropriate web application after such a restore has been performed:

1. Under Central Administration, select Shared Services Administration.

2. In the Manage this farm’s shared services page that appears, select Change association.

3. Assuming that you have already restored the SSP on a site, complete the required fields. Ensure that you specify the restored web application and database that the SSP site has already been restored to.

SharePoint Server 2007 VSS writer backup and recovery fail on Windows Server 2008 R2 (NW118982, NW120044, and NW118258)

A SharePoint Server 2007 VSS writer backup on Windows Server 2008 R2 fails when no components are configured. The SharePoint writer crashes during the recovery.

Workaround

Install the following Microsoft Knowledgebase hotfixes (full server cumulative update packages) released in April 2010 from the Microsoft website:

◆ KB981043 at http://support.microsoft.com/kb/981043 for Windows SharePoint Services.

◆ KB981042 at http://support.microsoft.com/kb/981042 for MOSS.

These hotfixes are only required for Windows Server 2008 R2 and not mandatory for Windows Server 2008 SP2.

In SharePoint Server 2007 SP2 and SharePoint Server 2007 SP3, recovery of web application and SSP fails when the October CU patch is not applied (NW125432, NW137564)

In SharePoint Server 2007 SP2 and SharePoint Server 2007 SP3, a recovery of the web application and SSP fails when the October CU patch is not applied and the SQL named instance is used.


http://support.microsoft.com/kb/981043

http://support.microsoft.com/kb/981042


Workaround

To recover the web application and SSP:

1. Install the following software:

• SharePoint Server 2007 SP2 or SharePoint Server 2007 SP3 software

• October 2010 CU

2. Run the backup for the SharePoint writer. For example, back up of the following:

• C:\inetpub

• SYSTEM COMPONENTS:\

• SQL writer

3. Restore the Windows Server 2008 R2 SharePoint Server.

4. Delete a web application. For example: iis _ db

a. Restore the following:

SYSTEM COMPONENTS:\

b. Restore the following:

C:\inetpub

c. Restore SQL.

5. Clear the SharePoint Configuration Cache:

a. Stop the Windows SharePoint Services Timer service.

b. Delete all the XML files in the following directory:

C:\ProgramData\Microsoft\SharePoint\Config\<GUID>

Only delete the XML files. Do not delete the .INI file.

c. In Notepad, open the cache.ini file and reset the number to 1. Save and close the file.

d. Start the Windows SharePoint Services Timer service and wait for the XML files to begin to reappear in the directory.

6. Restore the SharePoint Writer.

Hyper-V limitations

This section lists the known problems and issues that involve Hyper-V:

◆ “In Hyper-V Server 2012, backup of Hyper-V VMs configured in SMB file share is not supported (NW142816)” on page 36

◆ “A virtual machine does not start after a directed recovery of Windows Server 2012 Cluster Shared Volume Virtual Machine to Windows Server 2012 standalone (NTFS volume) is performed (NW143887)” on page 36



◆ “After Hyper-V CSV disaster recovery, application data recovery fails and unable to browse CSV mount point (NW137842)” on page 37

◆ “When the Encryption Directives option is enable, federated backup of Hyper-V CSV fails with error (NW139411)” on page 37

◆ “Through Advanced Recovery option, recovery of online VM to other node in same cluster setup completes (NW137205)” on page 37

◆ “In Hyper-V recovery, the AVHD file is not recovered to the alternate location path (NW138368)” on page 37

◆ “For Hyper-V image recovery, in the differencing disk type configuration, recovery to the alternate location fails with error (NW137115)” on page 38

◆ “Recovery fails for a child partition in Hyper-V Server 2008 cluster (LGTsc28331, NW125169)” on page 38

◆ “SCSI controllers for virtual hard drives with Hyper-V snapshots are not supported for relocated or directed recovery (NW114872)” on page 40

◆ “NMM registers corrupted Hyper-V child partition to Hyper-V Server (NW113595)” on page 40

◆ “Hyper-V pass-through disks may not be backed up in a child partition backup (LGTsc28427)” on page 40

◆ “Backup of Hyper-V child partitions using EMC VSS hardware providers (NW125025)” on page 41

In Hyper-V Server 2012, backup of Hyper-V VMs configured in SMB file share is not supported (NW142816)

NMM does not support backup of Hyper-V VMs configured in Server Message Block (SMB) file share for Hyper-V Server 2012.

A virtual machine does not start after a directed recovery of Windows Server 2012 Cluster Shared Volume Virtual Machine to Windows Server 2012 standalone (NTFS volume) is performed (NW143887)

When you perform a directed recovery of a Windows Server 2012 Cluster Shared Volume (CSV) virtual machine (VM) to a Windows Server 2012 stand-alone, the virtual hard disk (VHDX) is recovered. However, the VHDX points to the old location instead of the new location that is defined in the NMM GUI, and when the VM is started after the recovery, it does not start and displays the following error: VM failed to start.

Workaround

After completion of the directed recovery, do the following:

1. Start the Hyper-V manager.

2. Select Settings.

3. Change the .vhdx location to the correct location.

4. Start the VM.



After Hyper-V CSV disaster recovery, application data recovery fails and unable to browse CSV mount point (NW137842)

After disaster recovery, if NMM is used to restore Hyper-V data, the following issues are observed:

◆ Hyper-V recovery of VMs located in a shared disk (but non-CSV volume) fails.

◆ The CSV volumes are not browsable, and recovery of VMs located in CSV volume fails.

Workaround


1. Remove stale entries from the cluster resource.

2. In the Domain Controller, start the Active Directory Users and Computers Snap-In, and cross-check that the failover cluster virtual network name account of Hyper-V Virtual Server is enabled.

3. Restart the cluster service on both nodes.

4. Perform the restore.

The VM is restored and its status is shown as online.

When the Encryption Directives option is enable, federated backup of Hyper-V CSV fails with error (NW139411)

When the Advanced Encryption Standard (AES) option is enabled during a federated backup in an Hyper-V CSV setup, the backup fails with an error.

Through Advanced Recovery option, recovery of online VM to other node in same cluster setup completes (NW137205)

In a Hyper-V CSV setup, when a child partition is up and running, the same child partition can be recovered to another node by using the Advanced Recovery option. This creates multiple virtual machines in different CSV nodes.

Workaround

If the virtual machine is online or active, recover the virtual machine to the same node.

In Hyper-V recovery, the AVHD file is not recovered to the alternate location path (NW138368)

Recovery of an Automatic Virtual Hard Disk (AVHD) file to an alternate path of VM is not supported.

During a Hyper-V image recovery, an .AVHD file is not recovered to the alternate location path. The recovery is performed to the original volume path, if available. If the original volume is not available, the recovery fails with an error message similar to the following:

Node2\Node2VM_FF182268-033D-474D-BF72-316D55E0ADDC.avhd 0 0 0 0 5054 1331904175 0 0 2 5908 6012 0 nmm-csv-node1.nmm24perf.com nsrbragent 33 Failed

to create directory %s: %s 2 23 25 C:\ClusterStorage\Volume2 0 18 Access is denied.



16294 1331904248 0 0 2 5908 6012 0 nmm-csv-node1.nmm24perf.com nsrbragent 34 Encountered an error recovering %s 1 0 81 C:\ClusterStorage\Volume2\Node2\Node2VM_FF182268-033D-474D-BF72-316D55E0ADDC.avhd

53363 1331904248 2 0 0 5908 6012 0 nmm-csv-node1.nmm24perf.com nsrbragent 30 Recover of rsid %lu failed: %s 2 2 5 16464 49 83 16253 43 Error receiving files from NSR server `%s' 1 12 22 nmm-ds02.nmm24perf.com

73724 1331904248 0 0 2 5908 6012 0 nmm-csv-node1.nmm24perf.com nsrbragent 55 One or more recover threads failed to exit successfully 0

52973 1331904248 0 0 2 5908 6012 0 nmm-csv-node1.nmm24perf.com nsrbragent 32 Didn't recover requested file %s 1 23 127 C:\ClusterStorage\Volume2\Node2\N2_VM01\Snapshots\40917A20-DDD1-4786-8352-820DAA2F454A\40917A20-DDD1-4786-8352-820DAA2F454A.bin

52973 1331904248 0 0 2 5908 6012 0 nmm-csv-node1.nmm24perf.com nsrbragent 32 Didn't recover requested file %s 1 23 127 C:\ClusterStorage\Volume2\Node2\N2_VM01\Snapshots\40917A20-DDD1-4786-8352-820DAA2F454A\40917A20-DDD1-4786-8352-820DAA2F454A.vsv

For Hyper-V image recovery, in the differencing disk type configuration, recovery to the alternate location fails with error (NW137115)

In the differencing disk type configuration, image recovery of child partition to the alternate location fails with error.

Workaround

Follow the example solution provided:

If the source of the backup is:

◆ D:\VMDiff\Diff\VMdiff01\diff.vhd

◆ D:\VMDiff\Base\SA_Gold\SA_Gold.vhd

During the recovery, if the alternate location is P:\, then manually create the following path in P:\ and then perform the recover:

◆ P:\VMDiff\Diff\VMdiff01

◆ P:\VMDiff\Base\SA_Gold

The recovery completes without any error.

Recovery fails for a child partition in Hyper-V Server 2008 cluster (LGTsc28331, NW125169)

Recovery of a child partition that is available in Hyper-V Server 2008 cluster fails.

Workaround

Use the following procedures to recover a child partition in a Hyper-V Server 2008 cluster:

◆ “The child partition .vhd file is corrupt and the child partition configuration file is intact” on page 39

◆ “Both the child partition .vhd file and the child partition configuration file are corrupt” on page 39



The child partition .vhd file is corrupt and the child partition configuration file is intact

If the recovery of a child partition fails from the NMM GUI, use the following procedure to restore the child partition:

1. Locate the child partition (*.vhd) file path.

2. Move the corrupted .vhd file to a safe location (network share drive) for future reference, if needed.

3. Create a dummy .vhd file that is identical to the original child partition that was created before the corruption occurred.

4. Use the NMM GUI to select the child partition and perform a restore to the original location.

5. Start the child partition after recovery is complete.

6. After the child partition is functional, discard the .vhd file that was placed in a safe location on the network share drive.

Both the child partition .vhd file and the child partition configuration file are corrupt

If the recovery of a child partition fails from the NMM GUI, use the following procedure to restore the child partition:

1. Locate the child partition .vhd file and configuration file .xml path.

2. Copy the child partition .vhd file path and the configuration file to a safe location on a network share drive.

3. Remove the child partition from the cluster service.

4. From the Hyper-V Management Console, delete the child partition.

5. Delete the corrupted .vhd files from the local hard drive.

6. Create a dummy child partition that has the identical details to the original child partition that was created before the corruption occurred. This includes the following:

• Child partition name

• .vhd file location

Do not install the operating system on the child partition.

7. From the Failover Cluster Manager Console, add this dummy child partition to the cluster service. This makes the child highly available.

8. Use the NMM GUI to select the child partition and perform a restore to the original location.

9. From the Hyper-V Management Console, after the restore operation:

a. Observe that two child partitions with the same name are available.



b. Note that one of the child partitions is the duplicate or corrupted instance that needs to be deleted.

10. From the Failover Cluster Manager Console, remove the child partition from the cluster service.

11. From the Hyper-V Management Console:

a. Start both instances of the child partitions. One of the instances will start successfully and the other will fail.

b. Identify the corrupted instance, the one that fails to start.

c. Delete the corrupted instance.

d. Shut down the working instance of the child partition.

12. From the Failover Cluster Manager Console, make the child partition highly available.

13. Start the child partition after the restore operation is complete.

14. After the child partition is functional, discard the .vhd files and the configuration file that were placed in a safe location on the network share drive.

SCSI controllers for virtual hard drives with Hyper-V snapshots are not supported for relocated or directed recovery (NW114872)

The NMM software only supports a Hyper-V child partition with an IDE controller for virtual hard drives. The SCSI controllers for virtual hard drives with Hyper-V snapshots are not supported for relocated or directed recovery.

Workaround

For relocated or directed recovery operations, first delete or merge the Hyper-V snapshots from the Hyper-V Management Console and then perform a backup.

NMM registers corrupted Hyper-V child partition to Hyper-V Server (NW113595)

Even if a recovery operation for a Hyper-V child partition fails, NMM still registers the corrupted Hyper-V child partition to the Hyper-V Server.

Workaround

After receiving a confirmation about a failed recovery operation, the Hyper-V system administrator must delete the following:

1. The corrupted Hyper-V child by using the Hyper-V Manager.

2. The corresponding child partition .vhd files.

Hyper-V pass-through disks may not be backed up in a child partition backup (LGTsc28427)

For Hyper-V backups, the child partition pass-through disks are skipped in Hyper-V parent partition backup, and child partition pass-through disks are supported by backups within the child partition.



However, in some cases, Hyper-V parent partition backup of a child partition with a pass-through disk may fail completely. If this occurs, contact Microsoft support for assistance because the problem may be with the hardware configuration or the Microsoft Hyper-V writer.

Backup of Hyper-V child partitions using EMC VSS hardware providers (NW125025)

NMM does not support backup of Hyper-V child partitions by using EMC VSS hardware providers, if the child partition configuration file is placed on local drives (non-SAN) and the child partition hard disk files (.vhd) files are placed in SAN drives.

Workaround

To back up Hyper-V child partitions by using EMC VSS hardware providers, place the child partition configuration file and child partition hard disk providers files (.vhd) in SAN drives.

Additionally, if child partition files are placed in SAN drives and the Hyper-V Manager or Hyper-V Initial Store configuration file is backed up with APPLICATIONS:\Microsoft Hyper-V and APPLICATIONS:\Microsoft Hyper-V\Initial Store save sets, then NSR_VSS_FORCE_SYSTEM_PROVIDER=yes parameter must be provided in the Application Information field of the client resource in the NMC. This ensures that all child partitions are backed up by using Microsoft VSS software provider.

Active Directory limitations

This section lists the known problems and issues that involve Active Directory Server:

◆ “Restoring attributes of a domain local group to a global group with same name generates exception (NW120949)” on page 41

◆ “Active Directory object backup fails when Data Domain is selected (NW124314)” on page 42

◆ “Group Policy Object cannot be viewed if recovery occurs after Active Directory granular backups (LGTsc31471)” on page 42

Restoring attributes of a domain local group to a global group with same name generates exception (NW120949)

In Active Directory, users can create objects with the same names as existing objects after deleting the existing objects. For example, you can create a domain local security group object and then back it up. Creating another global security object with the same name and trying to recover the attributes of the group over the user object, generates an exception.

The same issue is seen when a user object is created with a specific name and then a group object is created with the same name.

Workaround

Take a full backup.



Active Directory object backup fails when Data Domain is selected (NW124314)

An NMM backup of an Active Directory object fails when you select the Data Domain option in the client properties.

Workaround

Clear the Data Domain option in the client properties to ensure successful backup.

Group Policy Object cannot be viewed if recovery occurs after Active Directory granular backups (LGTsc31471)

A recovery of Group Policy Object is performed by using NMM after doing granular backups of Active Directory. Although the recovery is successful, the Group Policy Object cannot be viewed by using the Active Directory Users and Computers (ADUC) and Group Policy Management Console (GPMC).

Data Protection Manager Server limitations

This section lists the known problems and issues that involve Data Protection Manager:

◆ “DPM writer application information parameter NSR_PS_FIRST_SAVESET_SAVE is not considered in NMM backups (NW129271)” on page 43

◆ “For DPM, the nmm.raw log file displays success messages even though backup fails (NW129436)” on page 43

◆ “Issue with file system automount status in DPM Server with NMM (NW126414)” on page 43

◆ “NMM logs incorrectly show failure of DPM Server 2007 SP1 replica recovery for Exchange 2007 (NW123963)” on page 44

◆ “Save of DPM data with data mover fails with import error (LGTsc12128)” on page 44

◆ “DPM Server 2007 rollup installation requires reset of account permissions (LGTsc19637)” on page 44

◆ “After successful DPM backup, NMC occasionally displays the save group as failed (LGTsc20732)” on page 45

◆ “Unable to recover DPM database through System Recover Session (LGTsc20971)” on page 45

◆ “DPM does not report newly allocated volumes as “Allocated” (LGTsc29911)” on page 45

◆ “Error on starting DPM Management Console after DPM disaster recovery (NW124780)” on page 45

◆ “After NMM recovery, DPM protection groups might not be in healthy state (NW125272)” on page 46

◆ “In DPM guest VM, by default, disaster mode is selected during directed recovery (LGTsc20284)” on page 46



DPM writer application information parameter NSR_PS_FIRST_SAVESET_SAVE is not considered in NMM backups (NW129271)

A DPM database is backed up after a DPM replica backup is complete. This backup sequence is against Microsoft recommendations.

Workaround


1. Disable automount before the backup operation.

2. Set client retries to zero (0).

The subsequent backup that is performed will follow the correct sequence and the DPM database will be backed up first.

Follow the procedure provided in “Issue with file system automount status in DPM Server with NMM (NW126414)” on page 43 if automount is enabled.

For DPM, the nmm.raw log file displays success messages even though backup fails (NW129436)

For a failed DPM backup, you may find that the nmm.raw log on the DPM Server displays success messages. This behavior is intermittent.

Issue with file system automount status in DPM Server with NMM (NW126414)

After installing NMM software on a DPM Server 2007 SP1 and DPM protected clients, the automount feature is disabled by default, which causes the following issues:

◆ From the DPM Management Console, creation of a new protection group fails.

◆ From the NMM client GUI, a DPM Server disaster recovery operation fails.

Workaround

To create a new protection group from the DPM Management Console or to perform a DPM Server disaster recovery from the NMM GUI, log in to the DPM Server:

To create a protection group or perform a disaster recovery operation:

1. Enable the automount feature.

2. Create the protection group or perform the disaster recovery operation.

3. Disable the automount feature.

The following example shows the procedure to enable the automount feature:

C:\Users\administrator>diskpart Microsoft DiskPart version 6.1.7600

Copyright (C) 1999-2008 Microsoft Corporation. On computer: HOSTNAME

(check the automount status) DISKPART> automount Automatic mounting of new volumes disabled.

(check that automount is enabled) DISKPART> automount enable Automatic mounting of new volumes enabled.



NMM logs incorrectly show failure of DPM Server 2007 SP1 replica recovery for Exchange 2007 (NW123963)

If a DPM Server 2007 SP1 replica recovery for Exchange Server 2007 is successful, as verified from the DPM Management Console, the NMM logs show failure of the DPM replica recovery.

Workaround

Ignore the log details because the recovery is successful.

Save of DPM data with data mover fails with import error (LGTsc12128)

When you perform an NMM backup of DPM database and replica without using a data mover, the save operation is successful.

When you perform an NMM backup of the DPM database and the replica is saved with a data mover, the save operation fails with an error similar to the following:

2007 12 12 16:52:02 (5628) main. 000551 ERROR:Import of dynamic disk group(s) cannot proceed because

Replication Manager was unable to determine the existing dynamic disk groups on this system (Call to vxdg list failed). Check to make sure that Volume Manager is installed properly. /*e*/

Workaround

Because NMM does not support hardware provider backups with dynamic disk, NMM runs a software provider backup without specifying a data mover.

DPM Server 2007 rollup installation requires reset of account permissions (LGTsc19637)

For compatibility on all supported platforms like Windows Server 2008 (x86 and x64) and Windows Server 2008 R2 SP1 (x64), NMM requires that the initial installation of DPM 2007 be followed by installation of the DPM 2007 rollup “System Center Data Protection Manager 2007 Feature Pack (x86),” available from the Microsoft website. However, installing the rollup also removes account permissions essential for recovery of the DPM configuration database, resulting in failed recoveries.

Workaround

Currently, Microsoft has no service pack or hotfix available to fix this issue. The following steps are required to manually restore the permissions:

1. Install Data Protection Manager 2007.

2. Install the DPM 2007 Rollup.

3. Back up the Windows registry.

4. Open the Windows registry.

5. Locate the registry key:

HKLM/Software/Microsoft/Microsoft Data Protection Manager/Setup/DatabasePath

6. Obtain the database path.



For example:

C:\Program Files\Microsoft DPM\DPM\DPMDB\

7. Close the Windows registry.

8. Go to the folder obtained from the registry entry. For example, the DPMDB folder at:

C:\Program Files\Microsoft DPM\DPM\DPMDB\

9. Assign a full control permission to the folder for the user Microsoft$DPM$Acct.

After successful DPM backup, NMC occasionally displays the save group as failed (LGTsc20732)

Occasionally, the NMC displays the DPM backup save group as failed, when the backup was actually successful.

Workaround

You can verify whether the save group backup succeeded or failed by either of the following methods:

◆ Check the nmm.raw file. This is the NMM log file and it is cumulative, so it is appended each time a backup or recovery operation is performed. This file is located in the applogs folder for example, \nsr\applogs.

◆ Check the NMM GUI. If the save set is available in the DPM Recover Session window, the save group backup was successful.

Unable to recover DPM database through System Recover Session (LGTsc20971)

In the NMM GUI, when you select a DPM Server and then select Recover, the submenu lists both System Recover Session and DPM Recover Session. Because the DPM database is a SQL database, it may appear that you can select it for recovery in System Recover Session. An attempt to recover the DPM database using System Recover Session fails.

Workaround

Use the DPM Recover Session option to recover DPM databases.

DPM does not report newly allocated volumes as “Allocated” (LGTsc29911)

When performing a DPM replica recovery, the dpmsync -reallocatereplica command runs successfully, but sometimes in the subsequent procedure a recently allocated volume is not reported by DPM to be in the “Allocated” state, causing it to be skipped.

Workaround

Retry a replica-only recovery. It is not necessary to run the Allocate Volumes utility again.

Error on starting DPM Management Console after DPM disaster recovery (NW124780)

When you start the DPM Management Console after DPM disaster recovery by using NMM, the console displays the following error message:

Connection to SQL Server Reporting Services fails.



Workaround

Enable the script options for the default websites in the DPM Server:

1. Close the DPM Management Console.

2. Go to Start > Run, and then type inetmgr.

3. Launch the IIS manager.

4. Go to Default Web Site > ReportServer$systemname$ > Handler Mappings > Feature Permissions.

5. Select scripts option.

6. Start the DPM Management Console.

After NMM recovery, DPM protection groups might not be in healthy state (NW125272)

During an NMM recovery, the DPM database and replicas are recovered. However, the protection groups in the DPM console might not be in a healthy state after the recovery.

Workaround

After an NMM recovery operation, perform a consistency check on the DPM protection groups.

In DPM guest VM, by default, disaster mode is selected during directed recovery (LGTsc20284)

In a DPM guest VM, when directed recovery is performed, by default the disaster mode gets selected and you are able to browse further. This is not an expected behavior.

However, in the physical machine, by default, the granular mode is selected, which is the expected behavior.

CLARiiON, Symmetrix, and provider limitations

This section lists the known problems and issues that involve EMC CLARiiON, EMC Symmetrix®, and providers:

◆ “Mount point data is not recovered when the entire mount point is selected in NMM GUI (NW135787)” on page 47

◆ “File System mount point data is not browsable in NMM GUI after backup (NW132588)” on page 47

◆ “Hardware provider backups are failing with iPdevShowVM: StorUIDdevShow: Failed to obtain device information message (NW136307)” on page 47

◆ “Data mover successful backups generate VSS errors in event viewer (NW133229)” on page 48

◆ “Backup fails when databases on different partitions of the same CLARiiON disk are backed up together (NW105481)” on page 48

◆ “Backup of multiple save sets having two partitions of the same array LUN fails (NW112227)” on page 48

◆ “Backup fails for VSS shadow copy storage on target LUN (NW128149)” on page 48



◆ “Limit on the number of shadow copies in a single session with CLARiiON (NW126388)” on page 48

◆ “Data Domain backup fails with data mover configuration (NW126009)” on page 49

◆ “Backup of save set All fails on machine with hardware LUNs (NW120308)” on page 49

◆ “Snapshot cannot include both CLARiiON and Symmetrix volumes (LGTpa91221)” on page 49

◆ “EMC VSS provider cannot take a snapshot of a volume with Solutions Enabler installed (LGTpa90841)” on page 49

◆ “Snapshot might fail to import when QLogic Management Suite Java Agent service is running (LGTpa90724)” on page 50

◆ “NMM cannot free LUN resources after hardware import failures (LGTpa88834)” on page 50

◆ “Reclaiming array storage after an import failure (LGTsc03522)” on page 50

◆ “NMM cannot back up CLARiiON volumes connected to the storage array through iSCSI (LGTsc29782)” on page 51

Mount point data is not recovered when the entire mount point is selected in NMM GUI (NW135787)

When the entire mount point is selected in the NMM GUI, the mount point is not recovered.

Workaround

Select individual files in the mount point and perform recovery. Recovery is successful.

File System mount point data is not browsable in NMM GUI after backup (NW132588)

When backups of file system mount point path using data mover configuration with hardware provider is performed, the content is not browsable in the NMM GUI.

Workaround

Backup file system mount points using software provider and forcing the NSR_VSS_FORCE_SYSTEM_PROVIDER=yes parameter. The data is visible in the NMM GUI.

Hardware provider backups are failing with iPdevShowVM: StorUIDdevShow: Failed to obtain device information message (NW136307)

Hardware provider configured with VNX backups may stop working after reinstalling NMM.



Workaround

To re-enable the hardware based backup, perform following steps after reinstalling NMM:

1. Run the Symcfg discover -clar command.

2. Stop the EMC VSS Provider Service.

3. Start the EMC VSS Provider Service.

Data mover successful backups generate VSS errors in event viewer (NW133229)

VSS errors are displayed in the event viewer on the data mover even after data mover backups are successful.

Backup fails when databases on different partitions of the same CLARiiON disk are backed up together (NW105481)

The NMM software does not support the backup of multiple partitions on a single hardware LUN on any array.

In this configuration, the backup fails and the SQL writer or any other application writer state becomes unstable.

Workaround


1. Move the SQL databases to the same partition.

2. Restart the SQL VSS writer service before the next backup.

Backup of multiple save sets having two partitions of the same array LUN fails (NW112227)

Backup of multiple save sets having two partitions of the same array LUN (for EMC Symmetrix or EMC CLARiiON) fails with error.Application logs in Event Viewer display the following an error:

"Event viewer - VSS - Volume Shadow Copy Service error: Error calling a routine on a Shadow

Copy Provider {bd3e52cd-c89b-4a26-828b-7668c6f8d783}. Routine details EndPrepareSnapshots({b50f068d-7e39-4529-a30f-d5266c73880f}) [hr = 0x80010105]."

Backup fails for VSS shadow copy storage on target LUN (NW128149)

When VSS shadow copy storage settings are configured for a LUN that is being backed up, the backup fails at the rollover stage.

Limit on the number of shadow copies in a single session with CLARiiON (NW126388)

There is a limitation on the number of shadow copies in a single session with CLARiiON.

The SnapView release notes on the EMC Powerlink website provides details on this limitation.



Data Domain backup fails with data mover configuration (NW126009)

If Data Domain device host details are not added under the Hosts file in the data mover and if the Data Domain device resides in the client, then the backup fails with an error message.

Workaround

Add the Data Domain device IP and hostname details under the Hosts file on the proxy machine and the client machine.

Backup of save set All fails on machine with hardware LUNs (NW120308)

A backup of the save set All is not supported on machines that have hardware LUNs, because the backup includes both software and hardware snapshots. When LUNs are assigned to machines and a backup is performed for the save set All, the backup fails.

Workaround

You can create the LUNs as mount points to ensure that the backup succeeds. Software snapshots are then taken for the local drives, and a hardware snapshot is taken for the LUN.

Snapshot cannot include both CLARiiON and Symmetrix volumes (LGTpa91221)

A client resource cannot include both CLARiiON and Symmetrix volumes in the same save set. Additionally, the save set All cannot be specified for such a client resource. If both CLARiiON and Symmetrix volumes are included in a save set, the backup fails.

Workaround

If the NMM client has both CLARiiON and Symmetrix volumes, create at least two client resources, one for CLARiiON volumes and another for Symmetrix volumes. Additionally, do not specify the save set All in any of the client resources for the NMM client.

EMC VSS provider cannot take a snapshot of a volume with Solutions Enabler installed (LGTpa90841)

A CLARiiON or Symmetrix volume cannot take a snapshot of a local volume on which Solutions Enabler is installed. Additionally, the local volume on which Solutions Enabler is installed cannot be included in the same client resource and backup group as a CLARiiON or Symmetrix volume.

The EMC Solutions Enabler documentation provides more information about this issue.

Workaround

To protect an NMM client client by using CLARiiON or Symmetrix storage:

◆ Install Solutions Enabler on a local volume (a volume that is not a CLARiiON or Symmetrix volume). The snapshot is taken with the software-based VSS system provider.

◆ Do not specify the save set All.



◆ Create at least two client resources for the NMM client client:

• Create one client resource for the local volume on which Solutions Enabler is installed.

• Create another client resource for the CLARiiON or Symmetrix volumes.

◆ Local volumes without Solutions Enabler installed can be included in any client resource.

◆ Ensure that the client resource for the local volume on which Solutions Enabler is installed and the client resource for the CLARiiON or Symmetrix volumes are not assigned to the same backup group.

Snapshot might fail to import when QLogic Management Suite Java Agent service is running (LGTpa90724)

Snapshots supported with a hardware provider might fail to import if the QLogic Management Suite Java Agent service is running and returns a getoperation error.

Workaround

Use the QLogic SanSurfer utility to stop the QLogic Management Suite Java Agent service. Manually start the service only when required and then manually stop the service. The Primus eServer Solution article, emc129473, provides more information.

NMM cannot free LUN resources after hardware import failures (LGTpa88834)

When an import operation succeeds, LUN resources reserved for the import operation are freed automatically. When an import operation fails, NMM client cannot free resources when the snapshot is deleted through the retention policy on hardware storage systems such as CLARiiON or Symmetrix.

Workaround

Free the LUN resources manually by using the Microsoft vshadow utility or vendor-supplied utilities.

The Microsoft vshadow utility is available in the Microsoft Volume Shadow Copy Service SDK 7.2, which is available for download from the Microsoft website.

Information about freeing resources with vendor utilities is available in the array of management utilities provided with your hardware storage systems.

Reclaiming array storage after an import failure (LGTsc03522)

When there is an import failure in CLARiiON snapshots or clones or in Symmetrix BCVs or VDEV, the snapshot session must be destroyed, synchronized, or terminated, depending on the hardware type, prior to the next backup.

Use the following examples as general descriptions of the recommended procedures. The product documentation provides more detailed steps and information for your system.


Technical notes

Workaround

For CLARiiON snapshots (DIFF):

1. In Navisphere Manager, locate the snapshot name and session, based on the timestamp.

2. If the snapshot belongs to a storage group, remove the snapshot from the storage group.

3. Select the session, and click Stop Session.

4. Select the snapshot, and click Destroy Snapshot.

The Navisphere Manager online help provides more detailed steps and information.

For CLARiiON clones (PLEX):

1. In Navisphere Manager, locate the clone group for the source LUN.

2. Right-click the clone group that you want to synchronize, and then click Synchronize.

The Navisphere Manager online help provides more detailed steps and information.

For Symmetrix BCVs (PLEX):

Make the BCVs not ready by using EMC Solutions Enabler Symmetrix CLI (SYMCLI).

For example:

symdev -sid SymmID [not_ready] BCV#

The EMC Solutions Enabler Symmetrix CLI Command Reference and the EMC Solutions Enabler Symmetrix TimeFinder Family CLI Product Guide provide detailed information about using the symdev command and options.

For Symmetrix VDEV (DIFF):

Terminate the snap session by using the symsnap command with the terminate option.

The EMC Solutions Enabler Symmetrix CLI Command Reference and the EMC Solutions Enabler Symmetrix TimeFinder Family CLI Product Guide provide more information about using the symsnap command and options.

NMM cannot back up CLARiiON volumes connected to the storage array through iSCSI (LGTsc29782)

NMM does not support backups of CLARiiON volumes that connect to the storage array through iSCSI.

Technical notes

This section provides some important information that you must review when using NMM 2.4 SP1.


Technical notes

Using EMC VSS hardware providers with NMM 2.4 SP1

The NetWorker Software Compatible Guide contains information about the EMC VSS hardware providers and the various versions that can be used with NMM 2.4 SP1.

In addition to the EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide, review the following for more information:

◆ EMC NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups 2.4 Technical Notes provides details on how to deploy NMM in a proxy backup configuration with EMC CLARiiON.

◆ EMC NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups 2.4 Technical Notes provides details on how to deploy NMM in a proxy backup configuration with EMC Symmetrix.

Using NMM 2.4 SP1 to back up and recover SQL Server data

You must remember:

◆ To use:

• The NetWorker User for NMM program when backing up a SQL Server by using the VSS technology.

• The NetWorker User for SQL program when backing up a SQL Server by using the VDI technology.

◆ Not to use both the NetWorker User for NMM program (for VSS backup and recovery) and NetWorker User for SQL program (for VDI backup and recovery) together.

◆ When migrating from NMSQL, SQL snapshot data backed up by using NMSQL is not supported by NMM 2.4 SP1.

The NetWorker Module for Microsoft Applications Release 2.4 SP1 Applications Guide provides details.

Migrating from VSS solution to VDI solution for SQL Server data protection

If you have been using a previous NMM release to recovery SQL Server data with VSS technology, and would now like to use NMM 2.4 SP1 to back up and recover SQL Server data with VDI technology, take care of the following:

◆ Clear the Snapshot checkbox under Backup Group Properties.

◆ Specify the Backup Command as nsrsqlsv. For SQL virtual server in a cluster environment, specify nsrsqlsv -A <virtual sql server>.

◆ Keep the Application Information field blank.

◆ Change the save set to MSSQL: for instance level backup or MSSQL:dbname for database level backup.


Documentation

Documentation

Table on page 53 lists the EMC publications that provide additional information.

The PDF versions of the guides provide the most current information on NMM 2.4 SP1. Check EMC Online Support (http://support.emc.com) to ensure that you are using the latest version of this document.

Table 4 EMC publications for additional information (page 1 of 2)

Guide names Description

NetWorker Module for Microsoft Applications Release 2.4 SP1 Installation Guide

Contains preinstallation, installation, silent installation, and post installation information about NMM 2.4 SP1.

NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide

Contains information common to all the supported Microsoft applications that can be backed up and recovered by using EMC NetWorker Module for Microsoft Applications.

NetWorker Module for Microsoft Applications Release 2.4 SP1 Applications Guide

Contains information needed to back up and recover the supported Microsoft applications.

NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups Release 2.4 Technical Note

Contains supplemental information about using EMC NetWorker Module for Microsoft Applications release 2.4 with EMC CLARiiON.

NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups Release 2.4 Technical Note

Contains supplemental information about using EMC NetWorker Module for Microsoft Applications Release 2.4 with EMC Symmetrix.

NetWorker Cloning Integration Guide Contains planning, practices, and configuration information for using the NetWorker, NMM, and NMDA cloning feature.

Simplified Windows Bare Metal Recovery Solution for Microsoft Applications by using EMC NetWorker Module for Microsoft Applications Release 2.4 Technical Notes

Contain supplemental information about performing Windows Bare Metal Recovery by using NMM.

SharePoint Granular Recovery by using EMC NetWorker Module for Microsoft Applications and Kroll Ontrack PowerControls Release 2.4 Technical Notes

Contain information about how to perform granular recovery of Microsoft SharePoint with NMM release 2.4 and third-party software Kroll Ontrack PowerControls.

Protecting Virtual Machine Manager Environments Using EMC NetWorker Module for Microsoft Applications Release 2.4 Technical Notes

Provide a data protection strategy for Microsoft System Center Virtual Machine Manager (VMM) using EMC NetWorker Module for Microsoft Applications release 2.4 (NMM) and the EMC NetWorker Windows Disaster Recovery feature.

NetWorker Procedure Generator (NPG) The NPG is an executable download that can be used to generate precise, user-driven steps for high demand tasks carried out by customers, support, and the field.

NetWorker Licensing Guide Provides information about licensing NetWorker and its modules.

NetWorker Software Compatibility Guide Includes a list of supported client, server, and storage node operating systems for the following software products: NetWorker and NetWorker application modules and options (including deduplication and virtualization support), AlphaStor, Data Protection Advisor, and HomeBase.



Software media, organization, and files

Software media, organization, and files

Information on software media, organization, and files is provided in the NetWorker Module for Microsoft Applications Release 2.4 SP1 Installation Guide.

Troubleshooting and getting help

EMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to EMC online support (http://support.emc.com).

Technical support — For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Your comments

Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: [email protected]

NetWorker Data Domain Deduplication Devices Integration Guide

Provides planning and configuration information on the use of Data Domain devices for data deduplication backup and storage in a NetWorker environment.

NetWorker Avamar Integration Guide Provides planning and configuration information on the use of Avamar in a NetWorker environment.

NetWorker documentation set Provides the documentation that is available with NetWorker.

Table 4 EMC publications for additional information (page 2 of 2)

Guide names Description




Troubleshooting and getting help

Copyright © 2007 - 2013 EMC Corporation. All rights reserved. Published in the USA.

Published March, 2013

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Connectrix, CopyCross, CopyPoint, CX, Dantz, Data Domain, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, VMAX, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and the RSA logo, are registered trademarks or trademarks of EMC Corporation in the United States and other countries. Vblock is a trademark of EMC Corporation in the United States.

All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.


158024125 networker module for microsoft applications 2 4 sp1 release notes pdf

Documents

microsoft applications

microsoft applicationsrelease

backup exchange server

nmm nw147575

sp1 nw130301

recovery services

critical volumes

file systems application