These release notes contain supplemental information about release of EMC NetWorkerModule for Microsoft Applications release 2.3. Topics include:
◆ Revision history ... 2
◆ Product description ... 2
◆ New features and changes ... 4
◆ Fixed problems ... 13
◆ Environment and system requirements ... 14
◆ Known problems and limitations ... 14
◆ Technical notes ... 76
◆ Documentation ... 76
◆ Software media, organization, and files... 77
◆ Installation ... 77
◆ Troubleshooting and getting help ... 77
Module for Microsoft Application
Release 2.3
Release Notes
P/N 300-011-102 Rev A02 May 4, 2011
Revision history
Table 1 on page 2 presents the revision history of this document.
Table 1 Revision history
Product description
The EMC® NetWorker® Module for Microsoft Applications Release 2.3 (NMM) uses Microsoft Volume Shadow Copy Service (VSS) technology to provide backup and recovery services for: ◆ File systems
◆ Application data — The Microsoft applications whose data can be backed up are:
• SQL
• Data Protection Manager • Hyper-V
• Active Directory • SharePoint • Exchange
◆ Operating system data
The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide and the EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provide details about NMM. The EMC Information Protection Software Compatibility Guide provides more information on the supported hardware, software, and
operating systems for NMM. Revision Date Description
A02 May 4, 2011 Second revision of this document. This document contains updates and revisions for NetWorker Module for Microsoft Applications 2.3 RA Refresh.
Important notification
In October 2009, Microsoft released new guidance on Windows server 2008 system recoveries via Knowledgebase article KB249694. This knowledgebase article states that Microsoft will support System State Recovery to the same instance of Windows Server 2008, but will not support System State Recovery after full server restore (without Windows Bare Metal Recovery) to the same or different hardware, or after a new installation of Windows Server 2008 on new hardware or same hardware.
The NMM 2.3 release is compatible with the NetWorker 7.6 SP2 client, which provides a true Windows Bare Metal Recovery (BMR) capability for Windows server 2008 R2 and Windows server 2008. This capability is built-into the NetWorker client and provides BMR support to the same or similar hardware. For Windows Disaster Recovery (DR), a Windows DR ISO image is supplied with
NetWorker 7.6 SP2, which provides a wizard driven BMR recovery for Windows. The NetWorker 7.6 SP2 Windows DR wizard
automatically formats disks, recovers Windows critical volumes from backup, and reboots to bring server back online.
NMM 2.3 can support this Windows DR capability and the
configuration and integration of this is fully explained in the NMM 2.3 documentation. This method of Windows DR is highly
recommended for all NetWorker customers and you are encouraged to use the NetWorker 7.6 SP2 client with NMM 2.3 for seamless NetWorker Windows DR solution. Upgrades to NetWorker 7.6 SP2 server or storage nodes are not compulsory to gain this functionality. Due to the additional features and support that NetWorker 7.6 SP2 provides, you are encouraged to review the documentation and consider a future upgrade of the server and storage nodes. Enhanced BMR can also be realized by utilizing the HomeBaseTM product. This together with NetWorker 7.6 SP2 and NMM 2.3 adds further capability by allowing recovery to different hardware, as well as detailed configuration monitoring and automation.
“NetWorker 7.6 SP2 client Windows Disaster Recovery support in NMM 2.3” on page 10 provides an introduction to Windows DR.
New features and changes
This section lists the new features and enhancements in NMM 2.3: Note: The NMM 2.3 documentation provides details about these new features and enhancements. It is recommended that you also refer the EMC NetWorker Release 7.6 Service Pack 1 Administration Guide for a better understanding of some of these features and enhancements.
◆ “Changes in installation procedure for NMM 2.3” on page 5 ◆ “Additional application support in NMM 2.3” on page 5 ◆ “NMM dedicated storage node support” on page 6 ◆ “Windows server 2008 R2 support” on page 6
◆ “Windows server 2008 R2 VSS Express Writers support” on page 7
◆ “Backup and restore support for Boot Manager (BCD) data on unmounted volumes with Windows server 2008 R2” on page 7 ◆ “Windows DFS-R granular recoveries support” on page 7 ◆ “Microsoft Exchange 2010 and 2010 SP1 support” on page 7 ◆ “Microsoft Exchange server 2007 support” on page 8
◆ “NetWorker and Data Domain integration support in NMM” on page 9
◆ “Microsoft SQL server support” on page 9
◆ “Microsoft Hyper-V 2008 R2 virtualization support” on page 9 ◆ “Microsoft SharePoint server support” on page 10
◆ “Granular backup of Microsoft Active Directory support on Windows server 2008 R2” on page 10
◆ “Multihomed environment support for Microsoft applications” on page 10
◆ “NetWorker 7.6 SP2 client Windows Disaster Recovery support in NMM 2.3” on page 10
◆ “Changing Exchange 2007 and 2010 credentials after installation” on page 10
◆ “Ability to suppress missing System Writer file errors in NMM 2.3” on page 11
◆ “Improved CMTDXlator error message if System Writer file is not found” on page 11
◆ “For unsupported hardware providers, use the
NSR_VSS_FORCE_SYSTEM_PROVIDER=yes parameter to back up data” on page 11
◆ “NMM pre and post script feature support for automating the Windows Server Backup image creation and configuring the backup to a NetWorker server” on page 12
◆ “nsrsnap_vss_savepnpc command with a customized backup program” on page 12
◆ “ESA-2011-012: Security update for EMC NetWorker Module for Microsoft Applications” on page 12
◆ “NMM 2.3 does not support SharePoint granular backup and recovery” on page 12
Changes in installation procedure for NMM 2.3
It is required that you install NetWorker 7.5 SP3 or later, or NetWorker 7.6 SP1 or later before installing NMM 2.3. The EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guideprovides details.
Additional application support in NMM 2.3
In addition to the Microsoft applications supported in the previous releases of the NMM software, NMM 2.3 provides support for: ◆ Exchange 2010 SP1
◆ Exchange 2007 SP3 ◆ SQL server 2005 SP4 ◆ SQL server 2008 SP2 ◆ SQL server 2008 R2
◆ Data Protection Manager 2007 SP1 ◆ Windows 2008 Hyper-V SP2 ◆ Windows 2008 R2 Hyper-V ◆ SharePoint server 2007 SP2 ◆ SharePoint server 2010
NMM dedicated storage node support
The support for dedicated storage node in NMM 2.3 enables you to: ◆ Perform LAN-free backup from NMM client without the need to
configure NMM proxy node and VSS hardware provider-based backups for LAN-free backups.
◆ Perform LAN-free backups while running VSS software provider-based backups.
◆ Migrate easily from the NetWorker Module for Exchange (NME) to the NMM software without major architectural changes on application server host.
Dedicated storage nodes are supported for all the NMM supported applications. NMM 2.3 dedicated storage node support enables you to perform LAN-free backups without configuring a separate proxy node for all the supported applications.
You can perform LAN-free backups for: ◆ Exchange 2010 database
◆ Exchange 2007 CCR node ◆ Windows File System ◆ SQL server
◆ SharePoint server ◆ DPM server ◆ Hyper-V server
◆ Active Directory server
Windows server 2008 R2 support
NMM 2.3 provides support for Windows server 2008 R2 x64 (Web, Standard, Enterprise, and Datacenter editions).
Windows server 2008 R2 VSS Express Writers support
NMM 2.3 provides support for all the new VSS Express Writers for Windows server 2008 R2:
◆ VSS Performance Counters Writer ◆ VSS Task Scheduler Writer ◆ VSS Express Writers ◆ VSS Metadata Store Writer
Backup and restore support for Boot Manager (BCD) data on unmounted volumes
with Windows server 2008 R2
While installing Windows 2008 R2 on an unpartitioned disk,
Windows 2008 R2 creates a separate partition to keep all the boot files on an unmounted partition. The location of the boot files can be used by the ASR writer BCD component.
NMM 2.3 supports backup of BCD data on unmounted partition, and restore of BCD data to an alternate recovery location to avoid system crashes. You can then import BCD data by using Microsoft utility BCDEDIT. BCD component can be recovered to C:\ drive only if proper time stamp and the location is added correctly in nmm.raw file.
Windows DFS-R granular recoveries support
NMM 2.3 supports granular recoveries of DFS-R folders on Windows server 2008 and Windows server 2008 R2.
Microsoft Exchange 2010 and 2010 SP1 support
In NMM 2.3 provides the following:
◆ Qualification of Exchange 2010 and 2010 SP1 on Windows server 2008 R2 and Windows server 2008 SP2.
◆ New GUI for Exchange 2010 recovery. ◆ Support for:
• Exchange 2010 VSS writer-based backups • Exchange 2010 full and incremental backups
• Exchange 2010 stand-alone and DAG environment backups • Exchange server 2010 DAG passive database backups from a
local backup server
• Exchange server 2010 DAG database backups by backing up one of the following on a DAG server:
– All active databases – All passive databases – All databases
• Exchange 2010 backup by using proxy node • Exchange server 2010 directed recoveries • Recovery to alternate mailbox database • Remote database recovery
• Granular mailbox item recoveries for Exchange 2010 using the Recovery Database (RDB) management console to:
– Create – Delete – Mount – Unmount
– Overwrite property
Note: Rollback recovery is not supported for Exchange 2010.
Microsoft Exchange server 2007 support
NMM 2.3 provides support for the following:
◆ Backup and recovery of Exchange server 2007 SP3 with Windows server 2008 R2.
◆ Recovery Storage Group (RSG) options: • Create
• Delete • Mount • Dismount
NetWorker and Data Domain integration support in NMM
NMM 2.3 provides support for:◆ Client-side deduplication support for: • Exchange 2010 (x64)
• SQL server 2008 R2 (x86, x64) • SharePoint 2010 (x86, x64)
◆ Data Domain optimized cloning (replication) for backup-to-disk through standard cloning workflow for all Microsoft applications supported by NMM
◆ Storage node deduplication for Data Domain for all Microsoft applications supported by NMM
Microsoft SQL server support
NMM 2.3 provides support for:
◆ SQL server 2008 on Windows server 2008 R2 (x64) ◆ SQL server 2008 R2 on:
• Windows server 2008 R2 (x64) • Windows server 2008 SP2 (x86, x64)
Microsoft Hyper-V 2008 R2 virtualization support
NMM 2.3 is qualified with Hyper-V 2008 R2 virtualization. NMM 2.3 provides the same level of support for Hyper-V 2008 R2 as it did in previous release.
To perform backup operation:
◆ Hyper-V 2008 R2 must be enabled.
◆ Child partitions (virtual machine) must be installed on Windows server 2008 R2.
The recovery steps to recover Hyper-V 2008 R2 server are the same as the steps to recover a Hyper-V 2008 SP2 server.
Note: NMM 2.3 does not support backup on Clustered Shared Volumes (CSV) enabled child partitions.
Microsoft SharePoint server support
NMM 2.3 provides support for:
◆ SharePoint server 2007 SP2 backup and recovery on Windows server 2008 R2.
◆ SharePoint server 2010 VSS writer backup and recovery on Windows server 2008 R2 and Windows server 2008 SP2.
Granular backup of Microsoft Active Directory support on Windows server 2008 R2
NMM 2.3 is qualified for granular backup of Active Directory on Windows server 2008 R2.Note: NMM 2.3 provides the same level of backup and recovery for Active Directory on Windows server 2008 R2 as it did in previous release.
Multihomed environment support for Microsoft applications
NMM 2.3 supports backup and recovery for all Microsoft
applications in a multihomed environment, for example, Exchange, SQL, SharePoint, Hyper-V, and DPM.
NMM backs up the data by using VSS technology and writes to a backup device, like Avamar® or Data Domain by using dedicated backup LAN instead of production LAN. Performing backups in a multihomed environment helps avoid contention between the application traffic and backup traffic in a production environment.
NetWorker 7.6 SP2 client Windows Disaster Recovery support in NMM 2.3
NMM 2.3 leverages the support provided in EMC NetWorker 7.6 SP2 for Windows Disaster Recovery (WDR) for NetWorker clients and provides support for Windows offline system state recoveries.
Changing Exchange 2007 and 2010 credentials after installation
In NMM 2.3, you can change the credentials for Exchange 2007 and Exchange 2010 after NMM installation is complete.
Ability to suppress missing System Writer file errors in NMM 2.3
In previous releases of NMM software for Windows 2008, sometimes the System Writer listed files that were no longer a part of the writer or in the system. This caused backup to fail when a file was not found.
In NMM 2.3, the following parameter in the Application Information field of the client resource can be set to ignore the missing system files and proceed with the backup:
NSR_IGNORE_MISSING_SYSTEM_FILES=Yes
When the Application Information field is set, a warning message is displayed on the NetWorker Management Console (NMC) and in the NMM logs. The warning message states that the missing system files or folders will be ignored, and will not be backed up. A separate message that provides details about each missing file or folder is also displayed.
Improved CMTDXlator error message if System Writer file is not found
In releases prior to NMM 2.3, if any of the System Writer files was missing, the backup failed and the CMTDXlator code displayed a generic error message “error generating files.”
In NMM 2.3, the error message now includes the name of the missing file.
For unsupported hardware providers, use the
NSR_VSS_FORCE_SYSTEM_PROVIDER=yes parameter to back up data
In releases prior to NMM 2.3, backups failed for LUNs managed by hardware providers that were not supported by NMM, for example, the NetApp hardware provider.
In NMM 2.3, you can set the following parameter in the Application Information field of the client resource to force the NMM software to use the Microsoft System Provider:
NMM pre and post script feature support for automating the Windows Server
Backup image creation and configuring the backup to a NetWorker server
The following scripts and files have been created to automate the Windows Server Backup image creation and to configure the backup to a NetWorker server:
◆ precmd.bat script ◆ postcmd.bat script ◆ nsrsnapvsssavepnpc file
nsrsnap_vss_savepnpc command with a customized backup program
As an alternative to using the nsrsnap_vss_save command, use the nsrsnap_vss_savepnpc command with a custom script for backup. The nsrsnap_vss_savepnpc command does the following:
◆ Performs any preprocessing commands listed for the precmd attribute in the <group-name>.res file.
◆ Save by using the options specified for the nsrsnap_vss_savepnpc command itself.
◆ Performs any postprocessing commands listed for the pstcmd attribute.
ESA-2011-012: Security update for EMC NetWorker Module for Microsoft
Applications
To resolve the vulnerability issue that was identified in Replication Manager, a fix is now included in NMM 2.3. The EMC Security Advisory (ESA-2011-012) provides more information.
NMM 2.3 does not support SharePoint granular backup and recovery
NMM 2.3 does not support SharePoint granular backup and recovery, including SharePoint optimized backup and SharePoint granular (non-optimized) backup. If you require SharePoint granular recoveries of SharePoint sites and site components, you can use the NMM 2.3 SharePoint VSS farm level backup capability.
Content databases from the SharePoint VSS farm backup can be recovered to alternate locations for data mining by third-party SharePoint granular recovery tools, such as Kroll Ontrack
PowerControls. However, if you do not want to use third-party tools, it is recommended that you continue to use the NMM 2.2.x version that you are currently using.
Fixed problems
Table 2 on page 13 lists the issues fixed in this release.
Table 2 Fixed problems (page 1 of 2) Issue number Description
NW115355 NMM backup of Exchange 2007 CCR cluster using passive node does not back up index of virtual node.
NW112473 ITD - DPM 2007 replica backup fails in NMM 2.2. No errors or libpvssclnt logs are created.
NW118086 NMM system component backup is displayed as “failed” by savegrp when the backup is actually successful for NMM.
NW117831 Command nsradsave should skip corrupt object and backup should continue.
NW115429 NMM backup time-out for Office Search Service backup. NW105181 Memory leak in nsrpsd seen with passive node CCR backups. NW113807 nsrsnap_vss_save -c virt_cli -? shows no output, but 081 succeeds. NW71167 NO_SUPPRESS option can cause backup operations to report failures. LGTsc15889 Application and NMM upgrades may need reinstallation after system
writer recovery.
LGTsc26386 Disaster recovery fails for Dell 2850 running Windows server 2008. NW127015 Back up of SYSTEM COMPONENTS fails due to missing system writer. NW113866 Directed recovery of mount point backup of a Celerra LUN is successful
but the NMM.raw file displays error.
NW114153 If a backup was recently aborted, system takes time to detect the aborted backup and initiate backup cleanup procedure.
Environment and system requirements
The EMC Information Protection Software Compatibility Guide and EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide list hardware and software requirements for the NMM software.
Known problems and limitations
This section describes known problems and limitations for this release.
◆ “Unsupported NetWorker features” on page 15 ◆ “Unsupported Windows features” on page 15
◆ “Microsoft Windows server and clustering” on page 16 ◆ “Installation” on page 17
◆ “NetWorker Module for Microsoft Applications” on page 17 ◆ “CLARiiON, Symmetrix, and providers” on page 28
◆ “Microsoft Active Directory” on page 32 ◆ “Microsoft Exchange server” on page 33
LGTsc30002 NMM does not use “Backup LAN” properly.
NW114989 CLARiiON file system backups fail with CommitSnapshots: StorRepSetListSnapControl error on ESX guest virtual machine. NW119114 Need to document Exchange backups Fails with the error “Error
generating files and directives list for the backup.”
NW120149 If MAPI COD version 1.2.1 has been installed in a Microsoft Exchange 2007 standalone system environment, the NMM backup might fail. NW115584 Automatic cloning, that is savegrp cloning, does not clone all the
Exchange save sets in a Exchange passive node CCR backups. NW115411 Databases are left in dismounted state if recovery is attempted with
wrong passphrase.
LGTsc21107 Recovery of multiple databases in Recovery Storage Group fails.
Table 2 Fixed problems (page 2 of 2) Issue number Description
◆ “Microsoft SQL server” on page 49
◆ “Microsoft Data Protection Manager” on page 54 ◆ “Microsoft Hyper-V” on page 59
◆ “Microsoft SharePoint” on page 66
Unsupported NetWorker features
The following NetWorker features are not supported: ◆ Localization (L10N)
◆ Adhoc/manual backups
Unsupported Windows features
The Windows IA64 editions server version is not supported. 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. ◆ Windows Automated System Recovery (ASR).
◆ Windows Storage Server Single Instance Storage (SIS) — SIS is supported, but recoveries will recover file data for all duplicate file. Data will not be lost if there is sufficient disk space to hold the duplicate copies.
The EMC Information Protection Software Compatibility Guide contains additional and the most up-to-date information about NMM compatibility.
Microsoft Windows server and clustering
This section lists the known problems and issues in Microsoft Windows server and clustering.
Failed cluster database recovery of legacy VSS backups may fail without displaying error message (LGTsc06190)
The NMM client can recover legacy VSS backups of the cluster database (VSS SYSTEM SERVICES) created prior to an upgrade or installation of the NMM client. The Cluster Writer Service files may be successfully recovered, but the cluster database recovery fails without displaying a recovery failure message.
Workaround
When recovering the cluster database, ensure that the cluster is not running on the other node.
Installation of Microsoft Windows server 2008 does not grant correct permissions to nsr\tmp directory (LGTsc15258)
During installation of the NMM client on Windows server 2008, the networker_install_dir\tmp directory does not have correct
permissions. The Administrator account requires write permissions to this directory.
Workaround
Manually change the permissions to the networker_install_dir\tmp directory:
1. In Windows Explorer, right-click the networker_install_dir\tmp directory and select Properties.
2. Click the Security tab.
3. Temporarily change the ownership to the Administrators group. 4. Grant Read\Write permissions to the Administrators group. 5. Change the ownership back to the system.
Windows server 2008 COM+ Registry database is not recovered correctly (LGTsc15380) NetWorker System State restores on Windows server 2008 do not correctly recover the COM+ Registry database.
Workaround
1. Log in to the system as a local system administrator. 2. Open a command window:
Click Start > Run, type cmd, and then press Enter.
3. Change the working directory to the COM+ catalog files folder: cd %windir%\registration
4. Delete all the COM+ catalog files that are not in use, except for the R000000000001.clb file. The following command will prompt you to confirm the deletion of each file:
del /p *.clb
5. Select N for the R000000000001.clb file, if it exists.
Installation
This section lists the known problems and issues in installation, uninstallation, and silent installation of NMM.
Silent uninstall of NMM and PowerSnap with qn option shows progress bar (NW124252) If the \networkr\setup.exe /s /v "/qn " /x command is run to uninstall NMM, the progress bar should not show. Currently, the progress bar is displayed.
When the same option is used during installation, the installation proceeds as expected without the progress bar.
NetWorker Module for Microsoft Applications
This section lists the known problems and issues in NMM. Backup of multiple instances of a client in the same backup group fails (NW126817, NW119295)
NMM recovers the wrong mega.xml if a backup group contains more than one instance of a client.
Workaround
Do not create multiple instances of the same client in one backup group when configuring a backup.
Online restore not supported for Windows 2008 and Windows 2008 R2 (NW126455)
Successful recovery of system state to the same or a similar hardware, can only be achieved through offline disaster recovery. Disaster recovery backup needs to be taken after SYSTEM COMPONENTS are changed. This includes adding, changing, removing roles, and features, or installing Windows updates.
Online restore of SYSTEM COMPONENTS save set is generally not supported. Improper restore of the SYSTEM COMPONENTS save set online could lead to inconsistent state of the system. They can only be restored to the same Windows OS instance.
NMM 2.3 does not support machine names with more than 15 characters (NW126639) In NMM 2.3, on a machine which has SQL installed, when the machine name contains more than 15 characters, nsrsnap_vss_save -? does not provide any output.
When using NMM with Data Domain, DDCL backup fails without generating the media waiting alert (NW126320)
Media waiting event alert is not generated when the Data Domain device is not available. Ideally, the media waiting event should occur and an alert should be generated.
NMM with Windows Disaster Recovery: Snapshot recovery fails for file system data after reimaging the client machine with disaster recovery saveset (NW125710)
Details of this defect:
◆ Snapshot recovery fails for file system data after reimaging the client machine with disaster recovery saveset.
◆ Manual rollover of the snapshot fails.
◆ When performing backup of saveset with snapshot policy as 1/1/day/none, retention is applied and the stale snapshot entry gets deleted.
Workaround
Disaster recovery should always be performed with conventional backup.
Backup fails when save sets are provided within inverted commas (NW00124454)
When you run the command nsrsnap_vss_save -? on a NMM client, a valid save set is displayed. All the save sets are displayed within inverted commas. If you copy and paste the save set including the inverted commas in NMC and start a backup, the backup fails without displaying an error message.
Workaround
Ensure that you have removed the inverted commas when you copy the save set name from the output.
Proxy server fails to roll over data to dedicated storage node device (NW120269) When using data mover host, data flows from proxy host to the storage node. If Dedicated Storage Node is set to “Yes,” the storage node host does not allow any data from any other host.
The NSR_VSS_FORCE_SYSTEM_PROVIDER=yes parameter does not work with the NSR_DATA_MOVER parameter (NW122123)
In stand-alone data mover setups, when both NSR_VSS_FORCE_SYSTEM_PROVIDER=yes and
NSR_DATA_MOVER=clientname.domain.com parameters are used in the Application Information field of the client resource, backup fails.
A wrong report message appears when a file system directed recovery operation completes successfully (NW120376)
The following error messages appear in the Monitor tab of the target client, although a file system directed recovery completes
successfully:
session id: 1, User defined message not understood. Message type: 50, request type: 0
nsrsnap_vss_recover complete time: 11/30/2009 12:32:25 PMsession id: 1, User defined message not understood. Message type: 50, request type: 0
Recover program exited with status: 0session id: 1, User defined message not understood.
Performance writer should back up configuration data located in system drive as per writer information (NW122499)
NMM does not back up the Performance Counter Writer
configuration distributed on non-system drives on Windows 2008 R2 (x64) setup. According to Performance Writer Information, the data in the perf*.dat file, located in system drive, should be backed up as per writer information.
The other non-system performance data is backed up with regular file system and it is recovered as part of file system recover. Windows operating system issue — French character is not printed in the command window (NW114758)
Backup fails when the component string, generated using the nsrsnap_vss_save.exe -? command, is used for French character database name. This is because the component is not found in a valid component list.
This is a Windows OS issue, and the special character is not printed on the command window.
Workaround
Successful backups of database are possible when the database name in the save set is entered manually.
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. Note: Some extended ASCII characters that are not symbol related may not display properly.
◆ Unicode characters. These characters are often used in Asian languages.
Cannot use non-Microsoft disk management tools with software provider (NW121360) A disk management system that replaces Microsoft’s Disk Management tool cannot use NMM with Microsoft’s system provider. For example, the VERITAS Volume Manager.
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.
Select IIS Config Writer in NMM GUI in Windows 2008 to recover the deleted IIS sites (NW00113269)
Recovery fails even if the IIS Config writer is selected in the Windows 2008.
Nested mount points and content of nested mount points save set are incorrectly displayed in NMM GUI (NW00115684, NW114120)
Nested mount point is not supported in NMM 2.3.
Recovery of Terminal Services Gateway writer does not recover the deleted connection authorization policies in the Terminal Services management console (NW115682)
Terminal Services Gateway writer is not supported in NMM 2.3. Improper uninstallation of NMM gives error when SYSTEM COMPONENTS or All save set is backed up (NW115512)
If uninstallation of NMM is not carried out properly on the NMM client machine, NMM backup with save set SYSTEM COMPONENTS or ALL fails with the “missing file” error in 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
After uninstalling NMM, perform the following steps: 1. Install the Windows Installer Cleanup utility to clean an
application completely from the NMM client machine.
2. Start the NMM backup with SYSTEM COMPONENTS:\ or All save set.
The Microsoft Support website provides details about the Windows Installer Cleanup utility. Knowledgebase article KB290301 on the Microsoft website provides the current version of Windows Installer Cleanup utility.
File system backup of mount points with data mover fails (NW00115510)
The following false error message appears in NMC for conventional file system backup of mount points with data mover:
savegrp: suppressed 24 lines of verbose output
43705:(pid 2968): Save Operations value is ignored on this OS platform.
C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT2223549555.xml 7167:(pid 2968): (pid 2968) completion time: 3/23/2010 12:00:46 AM
NMM .. 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. 0
crname: "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 backup is successful. Cross-platform directed recovery operations are not supported (NW110270)
NMM does not support cross-platform recovery. A directed recovery operation might fail if the source and the destination NMM client machines are not running the same operating system.
For example, to perform a directed recover operation of a Exchange Mailbox, both the source and the destination NMM client machines must be running the same version of the operating system. For example, both NMM client machines must be running either Windows 2003 or Windows 2008. The recovery will fail if the source NMM client machine is running Windows 2003 and the destination NMM client machine is running Windows 2008.
Because a directed recovery operation is performed at the application level, the underlying differences between the operating system might not be apparent. The error that appears with this failure might not specify the cause, for example:
Recovering 1 files within C:\ProgramData\EMC\NetWorker\ into
C:\Program Files\Legato\nsr\tmp\4091571676\ProgramData\EMC\NetWorker Received 1 matching file(s) from NSR server `dc100.ccs.local' Recover completion time: 10/28/2009 2:14:09 PM
C:\Program Files\Legato\nsr\tmp\4091571676\ProgramData \EMC\NetWorker\LG_VSS_CLIENT22103515764.xml
NMM .. Restored the snapshot metadata file to 'C:\temp\vssclient_2814145890.xml'
NMM .. Looking for 'conventional' backup type for savetime '1256222175'.
NMM .. Found 'conventional' backup type for savetime '1256222175'. Restoring from Conventional saveset '4108348882' for snapshot session '1256222063'
Recovering 2 files within C:\ProgramData\EMC\NetWorker\ into
C:\Program Files\Legato\nsr\tmp\4091571676\ProgramData\EMC\NetWorker Received 1 matching file(s) from NSR server `dc100.ccs.local' Recover completion time: 10/28/2009 2:14:14 PM
C:\Program Files\Legato\nsr\tmp\4091571676\ProgramData\EMC \NetWorker\LG_VSS_CLIENT22103515764.xml
NMM .. Restored the snapshot metadata file to 'C:\temp\vssclient_28141413796.xml'
NMM .. Looking for 'conventional' backup type for savetime '1256222175'.
NMM .. Found 'conventional' backup type for savetime '1256222175'. Restoring from Conventional saveset '4108348882' for snapshot session '1256222063'
63511:nsrsnap_vss_recover:NMM .. VSS failed to initialize the Backup Component document for restore -- 0x80042311.
63867:nsrsnap_vss_recover:NMM .. XML file processing failed. Missing or invalid BCDocument.
63849:nsrsnap_vss_recover:NMM .. failed to process BCDoc in XML file. Cannot proceed.
63847:nsrsnap_vss_recover:NMM .. error 0x80042310 while processing XML file -- C:\temp\vssclient_28141413796.xml.
63421:nsrsnap_vss_recover:NMM .. fatal error during processing of the Metadata file for savetime -- 1256222175.
50325:nsrsnap_vss_recover:nsrsnap_vss_recover: Recovery operation succeeded.
nsrsnap_vss_recover complete time: 10/28/2009 2:14:24 PM Recover program exited with status: 0
Restore destination has been reset for storage group W2k8DC-SG The options specified in the Recover Options Dialog have been reset back to their safe default values.
Recover end time: 10/28/2009 2:14:24 PM Recover elapsed time: 0 minutes, 24 seconds.
Error messages displayed during clean up of RMagentPS on client (NW00110192) When NMM is uninstalled, some times RMAPI binaries are not deleted. This might happen when there is access to any file or directory in RMAPI installation location.
For example:
◆ The command prompt or an Internet Explorer window is open, and the RMAPI folder is accessible.
◆ Any RMAPI log file is open. ◆ The event viewer is open. Workaround
Ensure that any file or directory that is open is first closed before uninstallation.
If the RMAPI binaries are not deleted, restart the machine so that the files are deleted and a clean installer base is obtained for the next NMM installation.
Restarting COM services may sometimes put the Volume Shadow Copy Service in an inconsistent state (NW00114460)
Restarting COM+ Event System and COM+ Event Application in a Windows 2008 setup may sometimes leave the Volume Shadow Copy Service in an inconsistent state, such that in the services console, the Volume Shadow Copy Service will show the status as “started” on the right side, but on the left side the status will be shown as “start” and not “stop.” Also, vssadmin list writers will return the command prompt without throwing any “waiting for...” message, and the event viewer will show the error as “Event 12347 - Volume shadow copy service error.”
Workaround
Restart the COM+ Event System and the COM+ Event Application services followed by the Volume Shadow Copy Service.
The article “Event ID 12347 — Volume Shadow Copy Service Operations“on the Microsoft website provides more information.
If a backup was recently aborted, system takes time to detect the aborted backup and initiate backup cleanup procedure (NW00114153)
If a backup is recently aborted, it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures. The following message may be generated if an attempt is made to back up a storage group before a previous backup attempt is fully terminated:
An attempt to prepare the storage group 'sg2' for backup failed because the storage group is already in the process of being backed up. The error code is -2403. The Microsoft Knowledgebase article 930800 on the Microsoft website provides more details.
Back up of multiple save sets having two partitions of the same array LUN fails (NW00112227)
Back up of multiple save sets having two partitions of the same array LUN (for Symmetrix, CLARiiON, or Celera) fails with error.
Application logs in Event Viewer display the following error. Conventional incremental backup does not save renamed files (LGTsc00665)
After performing a conventional full backup of a drive, if you rename files and then perform a conventional incremental backup of the drive, the renamed files are not saved and are not browsable for recover in the NMM client window.
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 recover operation. The creation of this subdirectory does not create any performance issues, but the nsr_recover directory is not removed after restarting the system.
Workaround
After the system is restarted, manually delete the nsr_recover directory.
Unable to browse save sets created by NMM client after downgrading from NMM client software to non-NMM client (LGTpa96395)
After installing the NMM software, if you perform a save or rollover save operation and then decide to downgrade to a non-NMM client, you cannot browse the save sets created by the NMM client on the downgraded client software. This is because the format of the client file index entries changed with the NMM client, and the previous NetWorker clients do not recognize this format.
Mounting one volume will mount all volumes in snapshot (LGTpa94348)
When mounting a volume for restore, all volumes included in that snapshot are also mounted. For example, if drives C:, D:, and E: are included in the snapshot and then you mount a directory from drive C: for restore, drives D: and E: also get mounted. The mounting of all volumes in the snapshot causes drive letters to be used up.
Local directives in nsr.dir file cannot refer to nested directory (LGTpa94805)
Local directives specified in nsr.dir file cannot refer to a nested directory.
Workaround
Place the nsr.dir directive file in the nested directory to which the directive applies.
For example, the following directive specifies that all files with a .dll extension must be skipped when a backup is performed:
<<"C:\Windows\system32">> skip: *.dll
To enable the this directive, place the nsr.dir file in the
C:\Windows\system32 directory. If the directive is placed in the root of C: drive, it is not executed during backup.
Celerra snapshot failure due to inadequate file system size (LGTsc12292)
The file system size needs to be set correctly to accommodate snapshots.
Configuring iSCSI Targets on Celerra describes how to set the file size correctly.
When GUI is minimized during rollover, the GUI does not open again (LGTsc06558) If a rollover is started from the GUI and the GUI is minimized, the GUI cannot be opened to check monitoring status. The GUI may appear to be hung.
Workaround
Wait until rollover is complete, and then open the GUI. 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, several levels deep in the navigation tree, the search operation displays results from the root node down. This may occur when you right-click a sub-node in the Browse pane and then click Search for. NMM switches to the Search tab, and the search path correctly displays the selected sub-node. But when a search is performed, the results are displayed from the root node down, and not from the selected sub-node.
At least one drive letter must be available for rollover of a snapshot (LGTsc27316)
When performing a rollover of a snapshot of the drive that contains the NMM binaries, at least one drive letter must be available to use as the temporary location for the mounted snapshot.
Clock skew between NetWorker server and NMM client can cause recovery error (LGTsc29650)
NMM clients must be kept in sync with the NetWorker server. If the clock times are not in sync and differ more than 5 minutes, problems will occur when recovering Full + Incremental backups.
Note: Note that the clock times for client, server, and data mover must match for backups to work without an issues.
NMM GUI does not list dependency of web front- ends that are not hosting SQL or search (NW123337)
NMM GUI lists dependency for SQL databases and hosts that have SharePoint search services. However, it does not list dependency of other web front-ends, which are to be restored.
CLARiiON, Symmetrix, and providers
This section lists the known problems and issues in EMC CLARiiON®, EMC Symmetrix®, and providers.
Limit on the number of shadow copies in a single session with EMC 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.
Backups fail if VSS 4.4 is installed on Windows 2008 R2 French OS (NW125474)
EMC hardware provider snapshot backups fail on Windows 2008 R2 French OS, if VSS 4.4.x is installed on the machine with
VSS_E_UNEXPECTED_PROVIDER_ERROR. Workaround
For EMC hardware provider backup:
◆ Clear the option in the Security tab of EMCVSSProvider COM+ service properties on Windows 2008 R2 French OS.
Or
◆ Force the backup with Microsoft System VSS Provider by using NSR_VSS_FORCE_SYSTEM_PROVIDER=Yes Application Information parameter.
Data Domain backup fails sometime with Data Mover configuration (NW126009) You may come across this issue only some times.
If Data Domain device host details are not added under the Hosts file in data mover and if the Data Domain device resides in the client, then backup fails and an error message is displayed.
Workaround
Add Data Domain device IP and hostname details under Hosts file on proxy machine and client machine.
Backup of save set All runs successfully on machine with hardware LUNs (NW120308) Backup of save set All is not supported on machines that have hardware LUNs on them, because the backup includes both software and hardware snapshots during the same backup.
In a normal scenario, when LUNs are assigned to machines and the save set All backup is run, the backup fails. But if the LUNs are created as mount points then the backup passes. Software snapshots are taken for the local drives and 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, 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 will fail.
Workaround
If NMM 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 save set All in any of the client resources for the NMM.
EMC VSS provider cannot take a snapshot of the volume on which Solutions Enabler is installed (LGTpa90841)
A CLARiiON or Symmetrix volume supported with the EMC VSS provider cannot take a snapshot of the volume on which Solutions Enabler is installed. Additionally, the volume on which Solutions Enabler is installed cannot be included in the same client resource and backup group with a CLARiiON or Symmetrix volume. The EMC Solutions Enabler documentation provides more information about this issue.
Workaround
To protect a NMM by using CLARiiON or Symmetrix storage: ◆ Install Solutions Enabler on a local volume (a volume that is not a
CLARiiON or Symmetrix volume). When Solutions Enabler is installed on a local volume, the snapshot is taken with the software-based VSS System provider.
◆ Create at least two client resources for the NMM. Create one client resource for the local volume on which Solutions Enabler is installed and 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 may fail to import when QLogic SanSurfer running (LGTpa90724)
Snapshots supported with a hardware provider may 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.
Hardware import failures and freeing up LUN resources (LGTpa88834)
When an import operation succeeds, LUN resources reserved for the import operation are freed automatically. When an import operation fails, the NMM cannot free resources when the snapshot is deleted through 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 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 process or procedure. The product documentation provides more detailed steps and information to perform these on your system.
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 then click Stop Session.
4. Select the snapshot, and then 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.
Backups of CLARiiON volumes when connected to the storage array through iSCSI not supported (LGTsc29782)
NMM does not support backups of CLARiiON volumes that connect to the storage array through iSCSI.
Microsoft Active Directory
This section lists the known problems and issues in Microsoft Active Directory server.
Restoring attributes of a domain local group to a global group with same name generates exception (NW124804, NW120949)
In Active Directory, users can create objects with the same names as previously existing objects. This can be done after deleting the previously existing objects. For example, you can create a domain local security group object, back up the object, and delete the object. Then create another global security object with the same name and try to restore the attributes of the group over the user object. However, this 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. Active Directory object backup fails when Data Domain is selected (NW124314)
Backing up an Active Directory object fails when you select the Data Domain option in client properties.
Workaround
Clear the Data Domain option in client properties for a successful backup.
Group Policy Object data cannot be recovered after Active Directory granular backups (LGTsc31471)
Recovery of Group Policy Object is done by using NMM after doing granular backups of Active Directory. Although the recovery is successful, the Group Policy Object cannot be viewed by using Active Directory Users and Computers (ADUC) and Group Policy
Management Console (GPMC).
In a directed recovery scenario, the ADAM writer of the source machine is visible (NW102761)
In a directed recovery scenario, the ADAM writer of the source machine is visible under “Snapshot Management” in the NMM GUI of the target machine.
Microsoft Exchange server
This section lists the known problems and issues in Microsoft Exchange server.
Mailbox role installation required on any one of the CAS machines for RDB item level recovery in Exchange 2010 DAG (NW127118)
RDB items are not browsable in NMM UI > Exchange 2010 plug-in > RDB Restore in DAG mailbox server, when only mailbox role or Client Access role (CAS) is installed on DAG member server. Workaround
At least one Exchange Server in your Exchange domain must have all three of the following roles installed:
◆ CAS
◆ Mailbox
◆ Hub
The mailbox role on this server does not require any mailboxes assigned to it. The mailbox role only needs to be installed because of a known RDB browsing issue with Microsoft Exchange 2010. Having all three roles on a single server will resolve this issue.
Recovery of Exchange 2007 fails with an index retrieval error (NW127387, NW127344) This problem can be identified by the following line in the NMM client GUI output window or in the NMM raw log:
nsrsnap_vss_recover: NMM … Index retrieval of metadata key failed for index path
APPLICATIONS:\Microsoft Exchange 2007\... with savetime 1234567891.
The problem could be seen on a Windows 2008 or Windows 2008 R2 system that is running Exchange 2007, either as a stand-alone server or the passive, or active node in a CCR environment.
The restore problem might occur if the following sequence occurred over a period of time during previous backups: If a single NMM save set list includes multiple databases or storage groups, and one or more of these databases or storage groups are dismounted or suspended during a backup, and then are put back online and additional backups take place. After such a sequence, the most recent backup for these databases or storage groups may fail during the recovery.
Workaround
Back up the registry before making these changes. Perform the following steps:
1. Open the Windows registry. 2. Locate and open
HKEY_LOCAL_MACHINE\SOFTWARE\Legato\NetWorker\V SSClient.
3. Create a registry value named RetrieveAllTimesMethod. 4. For the registry value RetrieveAllTimesMethod, modify the
value to true.
5. Close the registry key. 6. Rerun the restore.
By default, a MAPI session allows creation of only 500 Exchange 2007 folder objects (NW126557, NW126351)
By default, MAPI allows creation of only 500 folder objects per session in Exchange 2007.
During RSG item level recovery for 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
This restriction can be overcome by changing the value in registry key. The Microsoft Knowledgebase article at
http://technet.microsoft.com/en-us/library/aa997425%28EXCHG.8 0%29.aspx provides the procedure that must be followed.
IMPORTANT
!
After making the changes specified in the Microsoft
Knowledgebase article, restart Microsoft Exchange Information Store service for the changes to take effect.
“Attempted to Read or Write Error Protected Memory” message seen during RSG item level recovery (NW126347)
When performing RSG item level recovery, while browsing through the user mailboxes an error is observed.
Workaround
Restart the Exchange System Attendant Service, and then perform the RSG item level recoveries.
In Exchange 2010 DAG, refresh required to load the Exchange plug-in (NW126319)
The Exchange 2010 recovery plug-in does not display recovery items unless one of the following is done:
◆ A refresh by using the F5 key. ◆ Selecting a client from the menu. ◆ Changing the browse time.
In Exchange 2010 DAG, rollback recovery fails on DAG with error message (NW126030, NW125274)
Rollback recovery is not supported on Exchange 2010 DAG node. Exchange IS error messages in Event Viewer for successful Exchange PIT recovery (NW126021, NW122170)
Exchange VSS writer fails to restore a backup with error code -4001 when verifying existing log files in the target log file path G:\log1\ of the restore.
Workaround
Knowledgebase article esg119099 on EMC Powerlink website http://Powerlink.EMC.com provides details for this issue. In Exchange 2010, NMM 2.3 does not support the archive mailbox feature (NW122331, NW122339)
The NMM 2.3 software does not support the Microsoft Exchange 2010 archive mailbox feature.
In Exchange 2003, restore not permitted error is seen in EventViewer during the recovery of a storage group (NW124845, NW123043)
The following error message appears in the EventViewer during recoveries performed in Exchange 2003:
Restore not permitted because storage group
/DC=com/DC=TeamNMM/CN=Configuration/CN=Services/CN=Micro soft Exchange/CN=First Organization/CN=Administrative Groups/CN=First Administrative
Group/CN=Servers/CN=EVS/CN=InformationStore/CN=STG02 is online. Error is -2147467259.
Workaround
Ignore this error message. Although this error message is seen in the EventViewer, data can be recovered.
In Exchange 2010, the RM_ExchangeInterface.exe service is disabled when nwexinfo.exe program is run with wrong credentials (NW123443)
The RM_ExchangeInterface.exe service is disabled when the nwexinfo.exe program is run with wrong credentials.
Workaround
1. Close the Services.msc user interface. 2. Reopen the Services.msc user interface.
3. Run nwexinfo.exe and provide the correct credentials. The RM_ExchangeInterface service runs successfully. In Exchange 2007 and 2010, ensure that NSR_ALT_PATH is empty before performing a backup (NW124652)
When the alternate path is not cleared, the backup fails with an error similar to the following:
SS_mount_controller::ExposeSnapshot failed to mount C:\mount2\Idrive\ for snapshot id
922b939c-209f-4d98-bdae-6df7c1e94b73, VSS error is E_INVALIDARG, device may already be mounted /*1*/ 2010 11 17 04:23:49 (9640) main.
Workaround
Before performing a backup in Exchange 2007 and 2010, clear the alternate path that was specified for the NSR_ALT_PATH attribute. In Exchange 2010 RDB, in the NMM GUI only the first RDB user is browsable (NW125623)
After a successful RDB recovery operation, you can use the NMM GUI to browse the first RDB user item. However, subsequent RDB user items are not browsable.
In Exchange 2010, a user mailbox do not appear in the RDB recovery window unless the mailbox contains at least one e-mail message (NW125556)
After a successful RDB recovery operation, NMM does not display a user mailbox if the mailbox does not contain at least one e-mail message.
In Exchange 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 the following error message might appear:
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 2010 DAG, the Exchange Replication writer moves to a “retryable error” mode (NW119287)
When DAG client resources are created in the NetWorker
Management Console, the DAG machine entries might have been wrongly included in the hosts file. This results in the Exchange Replication writer moving to “retryable error” mode.
Workaround
Correct the host files entries and perform either of the following steps:
◆ Delete the existing NetWorker client resource and then recreate it. Or
◆ In NMC, select DAG client properties > Globals (1 of 2) and then ensure that both of the following are correctly listed:
• Shortname • FQDN name
If the shortname and the FQDN names are incorrectly listed, correct the names.
In Exchange 2007, NMM supports only mailbox recovery to RSG if the Logs Path and SysPath are in different folder but on the same volume (NW125367)
In a Microsoft Exchange 2007 CCR passive node backup scenario, the NMM 2.3 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.
In this type of configuration, the NMM 2.3 software supports mailbox recovery to RSG. RSG item level recovery can also be performed. Note: The NMM 2.3 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 Microsoft Exchange logs path and system path are on 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 EMC NetWorker Module for Microsoft Applications Release 2.3
Administration Guide provides information on how IPv6 might cause browsing issues on RSG mailboxes.
4. Ensure that a public folder appears on the Exchange Domain server.
5. Create a RSG for the required Storage Group by selecting the storage group to link with the Recovery Storage Group. 6. Change the Log Path and the System Path to point to the same
7. Use the NMM 2.3 software to start the RSG recovery: a. Launch the NMM 2.3 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 from which the RSG was created. f. Select Restore to - Recovery Storage Group.
g. Click OK.
h. Click RECOVER to start the RSG recovery. Moving from Networker support for Exchange 2010 interim solution to NMM 2.3 (NW125249)
The upgrade option from interim solution to NMM 2.3 is not available.
Perform the following steps:
1. Use the interim solution to recover all data that was previously backed up by the interim solution.
2. Uninstall the interim solution.
3. Install the appropriate version of NetWorker. 4. Install NMM 2.3.
5. Now, by using NMM 2.3, perform a full backup of the data. In Exchange 2010, RDB items are not browsable when the Mailbox database is not mounted (NW122293)
When the Mailbox database is not mounted, you cannot use the NMM 2.3 GUI to browse RDB items. This is the mailbox that was used to log in to the Microsoft Exchange server.
For example:
The Microsoft Exchange server named exchsrv was logged in to by using e2k10\administrator. This administrator user mailbox was created for the Mailbox Database MB1.
To use the NMM client GUI to browse RDB user mailbox items, always mount the mailbox database named MB1. Otherwise, the following message appears in the NMM GUI:
Insufficient permissions for user mailbox to browse RDB items
NMM does not support DAG with cross-domain servers (NW123275)
Microsoft Exchange 2010 is not supported to build DAG with cross-domain servers. NMM does not support backup with such configurations due to this Microsoft limitation. The Microsoft technote at
http://technet.microsoft.com/en-us/library/dd979802.aspx provides more information about this limitation.
In Exchange 2010 DAG, remote recover to DAG node is failing with “Error starting Restore” pop-up (NW121462)
In Exchange 2010, DAG remote restore to another DAG node may fail with ‘Error starting Restore’ error because of either of the following reasons:
◆ Fire wall is enabled in remote node. Or
◆ Name resolution is not configured properly. Workaround
◆ Disable the firewall.
◆ Configure both forward and reverse lookup zones properly, and ensure that name resolution is working correctly for all DAG nodes.
Exchange 2010 database level incremental backup fails if the save set contains both passive and active copy databases (NW122668)
Exchange 2010 DAG database level incremental backup fails if the save set contains both active and passive copy databases with attribute NSR_EXCH2010_BACKUP=passive and
NSR_EXCH2010_BACKUP=active. The NetWorker server forces a full backup.
In Exchange 2010, the user can browse only the first RDB item (NW122233)
In Exchange 2010, only the first RDB item is browsable in the RDB View window of the NMM UI. Subsequent RDB items do not appear in the RDB View window and are therefore not browsable.
RDB item-level recovery fails when opening an Exchange 2010 message store (NW123687) A RDB item-level recovery fails with an error message when opening a Exchange 2010 message store.
Workaround
Press F5 to refresh the NMM UI.
Exchange 2010 RDB item-level recovery fails with “Insufficient permissions to access mailbox” error (NW122293)
RDB item-level recovery fails due to insufficient permission to access mailbox.
Workaround
Perform the following steps: 1. Close the NMM UI.
2. Restart the Microsoft Exchange System Attendant service. 3. Open NMM UI.
4. Perform a RDB item-level recovery.
Cannot browse Exchange 2010 RDB on a stand-alone server (NW125038)
Exchange 2010 must have an administrative mailbox to browse a RDB with NMM. This mailbox is created by default. Sometimes, the Active Directory entry for this mailbox becomes corrupt and leads Exchange to believe that:
◆ The mailbox does not exist.
◆ The user (administrator) already has a mailbox and will not let you create a mailbox.
Workaround
Perform the following steps:
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.
In Microsoft Exchange 2010, cannot create a new RDB if existing RDB logs and database path are selected (NW125119)
A new RDB cannot be created if RDB logs and database path of an existing RDB are selected during the creation process. Also, no error message is displayed.
For example, if the RDB logs for an existing RDB named RDB-check reside on database path G:\RDB, a new RDB named RDB-666 cannot be created using the existing RDB logs and G:\RDB. The new RDB is not created.
Note: This is Microsoft Exchange 2010 restriction. Microsoft Exchange 2010 does not support the ability to create new RDB using the RDB logs and database path location of an existing RDB.
Workaround
When creating a new RDB, always use new RDB logs and database path location.
Alternate Storage Group directed recovery with different versions of Exchange displays error message while mounting the database (NW105628)
If you back up an Exchange database using one version of Exchange and perform 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 versions of the Exchange databases are the same. Incremental backup is prompted to full backup for Exchange 2010 DAG mailbox server (NW123550)
An incremental backup is prompted 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 DAG mailbox server client resources. You must create a client resource for each node.
