Release Notes P/N Rev A02

Transcription

1 EMC NetWorker Module for Microsoft Application Release 2.3 Release Notes P/N Rev A02 May 4, 2011 These release notes contain supplemental information about release of EMC NetWorker Module for Microsoft Applications release 2.3. Topics include: Revision history... 2 Product description... 2 New features and changes... 4 Fixed problems Environment and system requirements Known problems and limitations Technical notes Documentation Software media, organization, and files Installation Troubleshooting and getting help

2 Revision history Revision history Table 1 Table 1 on page 2 presents the revision history of this document. Revision history 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. A01 March 25, 2011 First revision of this document for NetWorker Module for Microsoft Applications 2.3 RA. 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. 2 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

3 Product description Important notification In October 2009, Microsoft released new guidance on Windows server 2008 system recoveries via Knowledgebase article KB 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 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 HomeBase TM 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 3

4 New features and changes 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 4 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

5 New features and changes 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 : 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 Guide provides 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 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 5

6 New features and changes 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). 6 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

7 New features and changes 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 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 7

8 New features and changes 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 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 Overwrite property 8 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

9 New features and changes 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 9

10 New features and changes 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. 10 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

11 New features and changes 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: NSR_VSS_FORCE_SYSTEM_PROVIDER=yes EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 11

12 New features and changes 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 : 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 ) 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. 12 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

13 Fixed problems 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 NW NW NW NW NW NW NW NW71167 LGTsc15889 Description NMM backup of Exchange 2007 CCR cluster using passive node does not back up index of virtual node. ITD - DPM 2007 replica backup fails in NMM 2.2. No errors or libpvssclnt logs are created. NMM system component backup is displayed as failed by savegrp when the backup is actually successful for NMM. Command nsradsave should skip corrupt object and backup should continue. NMM backup time-out for Office Search Service backup. Memory leak in nsrpsd seen with passive node CCR backups. nsrsnap_vss_save -c virt_cli -? shows no output, but 081 succeeds. NO_SUPPRESS option can cause backup operations to report failures. Application and NMM upgrades may need reinstallation after system writer recovery. LGTsc26386 Disaster recovery fails for Dell 2850 running Windows server NW NW NW LGTsc26194 Back up of SYSTEM COMPONENTS fails due to missing system writer. Directed recovery of mount point backup of a Celerra LUN is successful but the NMM.raw file displays error. If a backup was recently aborted, system takes time to detect the aborted backup and initiate backup cleanup procedure. Data cannot be recovered from multiple snapshots at a time. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 13

14 Environment and system requirements Table 2 Fixed problems (page 2 of 2) Issue number LGTsc30002 NW NW NW NW NW LGTsc21107 Description NMM does not use Backup LAN properly. CLARiiON file system backups fail with CommitSnapshots: StorRepSetListSnapControl error on ESX guest virtual machine. Need to document Exchange backups Fails with the error Error generating files and directives list for the backup. If MAPI COD version has been installed in a Microsoft Exchange 2007 standalone system environment, the NMM backup might fail. Automatic cloning, that is savegrp cloning, does not clone all the Exchange save sets in a Exchange passive node CCR backups. Databases are left in dismounted state if recovery is attempted with wrong passphrase. Recovery of multiple databases in Recovery Storage Group fails. 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 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

15 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 15

16 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. 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. 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. There is a workaround that enables you to do a full system recovery: 16 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

17 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 R clb file. The following command will prompt you to confirm the deletion of each file: del /p *.clb 5. Select N for the R 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. Do not create multiple instances of the same client in one backup group when configuring a backup. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 17

18 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. Disaster recovery should always be performed with conventional backup. 18 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

19 Backup fails when save sets are provided within inverted commas (NW ) 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. 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/ :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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 19

20 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. 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. 20 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

21 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 (NW ) Recovery fails even if the IIS Config writer is selected in the Windows Nested mount points and content of nested mount points save set are incorrectly displayed in NMM GUI (NW , 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: " /25/2010 8:53:13 PM son2k8x64.sonali2.com nsrsnap_vss_save PS: (CMTDXlator::GetCorrectFileSpec) Path component dialer.exe not on PIT path 'C:\Windows\System32\'. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 21

22 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 KB on the Microsoft website provides the current version of Windows Installer Cleanup utility. File system backup of mount points with data mover fails (NW ) 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_CLIENT xml 7167:(pid 2968): (pid 2968) completion time: 3/23/ :00:46 AM NMM.. Request the PS backup service backup the GUI presentation objects to the NetWorker saveset 'VSS:/' :nsrsnap_vss_save:NMM.. successfully completed final processing of replica :nsrsnap_vss_save:NMM.. completed commit replica with status of true :nsrsnap_vss_save:NMM backup completed successfully pensy-tom.becp.com nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with success. 0 crname: "Y:\\z-mount"; snap_sessionid: ; 25048:nsrsnap_save: Y:\z-mount\: Failed :nsrsnap_save: Backup failed :nsrsnap_save: Backup operation failed. 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. 22 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

23 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 The recovery will fail if the source NMM client machine is running Windows 2003 and the destination NMM client machine is running Windows 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\ \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\ \ProgramData \EMC\NetWorker\LG_VSS_CLIENT xml NMM.. Restored the snapshot metadata file to 'C:\temp\vssclient_ xml' NMM.. Looking for 'conventional' backup type for savetime ' '. NMM.. Found 'conventional' backup type for savetime ' '. Restoring from Conventional saveset ' ' for snapshot session ' ' Recovering 2 files within C:\ProgramData\EMC\NetWorker\ into C:\Program Files\Legato\nsr\tmp\ \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\ \ProgramData\EMC \NetWorker\LG_VSS_CLIENT xml NMM.. Restored the snapshot metadata file to 'C:\temp\vssclient_ xml' NMM.. Looking for 'conventional' backup type for savetime ' '. NMM.. Found 'conventional' backup type for savetime ' '. Restoring from Conventional saveset ' ' for snapshot session ' ' 63511:nsrsnap_vss_recover:NMM.. VSS failed to initialize the Backup Component document for restore -- 0x :nsrsnap_vss_recover:NMM.. XML file processing failed. Missing or invalid BCDocument :nsrsnap_vss_recover:NMM.. failed to process BCDoc in XML file. Cannot proceed :nsrsnap_vss_recover:NMM.. error 0x while processing XML file -- C:\temp\vssclient_ xml :nsrsnap_vss_recover:NMM.. fatal error during processing of the Metadata file for savetime :nsrsnap_vss_recover:nsrsnap_vss_recover: Recovery operation succeeded. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 23

24 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 (NW ) 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. 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 (NW ) 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 Volume shadow copy service error. Restart the COM+ Event System and the COM+ Event Application services followed by the Volume Shadow Copy Service. The article Event ID Volume Shadow Copy Service Operations on the Microsoft website provides more information. 24 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

25 If a backup was recently aborted, system takes time to detect the aborted backup and initiate backup cleanup procedure (NW ) 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 The Microsoft Knowledgebase article on the Microsoft website provides more details. Back up of multiple save sets having two partitions of the same array LUN fails (NW ) 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. After the system is restarted, manually delete the nsr_recover directory. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 25

26 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. 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. 26 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

27 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 27

28 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. 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. Add Data Domain device IP and hostname details under Hosts file on proxy machine and client machine. 28 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

29 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. 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. 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. Do not specify save set All. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 29

30 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. 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. 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. 30 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

31 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. 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 31

32 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. Clear the Data Domain option in client properties for a successful backup. 32 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

33 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. 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 Having all three roles on a single server will resolve this issue. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 33

34 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 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. 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. 34 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

35 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 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". This restriction can be overcome by changing the value in registry key. The Microsoft Knowledgebase article at 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. 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 35

36 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 when verifying existing log files in the target log file path G:\log1\ of the restore. Knowledgebase article esg on EMC Powerlink website 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 Ignore this error message. Although this error message is seen in the EventViewer, data can be recovered. 36 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

37 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. 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*/ :23:49 (9640) main. 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 message (NW125556) After a successful RDB recovery operation, NMM does not display a user mailbox if the mailbox does not contain at least one message. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 37

38 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 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. 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. 38 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

39 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. To perform an RSG recovery operation for all passive node backups that were performed with the NMM 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 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 folder that is on the same volume. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 39

40 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 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. 40 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

41 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 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. 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 41

42 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. 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. 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. 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. After the new mailbox is created, you can browse RDB. 42 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

43 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. 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. 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. Ensure that you have created the required number of DAG mailbox server client resources. You must create a client resource for each node. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 43

44 Exchange 2007 SP3 requires hotfix for NMM backups to work (NW123514, NW121777) Exchange 2007 SP3 requires the Update Rollup 1 for Exchange 2007 Service Pack 3 with NMM 2.2 SP1 or NMM 2.3. This is applicable for stand-alone, CCR, LCR, and SCC Configurations. Install this hotfix from on the Microsoft website. Exchange 2010 stand-alone hardware provider backup fails if failover cluster role is installed (NW120735) Exchange 2010 stand-alone hardware provider backups fail if failover cluster management roles are installed in stand-alone setup. Perform the following steps to remove a machine from DAG to back up 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 DAG-related Application Information parameters from the mailbox server client resource by using NMC. Recover fails if new mailbox database is created (NW120335) After backing up a storage group, create a new mailbox in the same storage group and then try to recover the storage group. The recovery fails. Dismount the newly created database, back up the storage group, and then recover. 44 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

45 Exchange 2007 and 2010 backup fails if some logs and databases are under normal path and the remaining are under volume mount path (LGTsc22968) Exchange backup fails if both mount paths and normal paths reside on the same volume (drive). For example, backup fails when the log path of both Storage Group1 and Storage Group2 is drive E\: and the database path is drive F:\: Storage Group1: Logs path: E:\logs1 Database path: F:\DB1 Storage Group2: Logs path: E:\mountpoint\logs2 Database path: F:\mountpoint\DB2 If the mount path resides on one volume and normal path resides on a different volume, backup completes successfully. For example, while the log path of Storage Group1 is drive E:\ and log path of Storage Group2 is drive G:\, the database path of Storage Group1 is drive G:\ and database path of Storage Group2 is drive H:\: Storage Group1: Logs path: E:\logs1 Database path: F:\DB1 Storage Group2: Logs path: G:\mountpoint\logs2 Database path: H:\mountpoint\DB2 Recovery of Exchange backup data in LCR setup fails when the copy status is healthy (NW113636) For storage groups, if recovery of Exchange backup data is performed when the copy status is Healthy, the recovery randomly fails for all storage groups because all the storage groups go offline or are in failed state. This results in data loss. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 45

46 Perform a Suspend Storage Group Copy prior to performing a recovery of Exchange data from a full or incremental backup to avoid data loss. Exchange storage groups must be in the same location as the Exchange server (LGTsc17699) Exchange server 2003 storage group names must be in the same location as the Exchange server. For Exchange backup, the system path and transaction log must be set to the same location (LGTpa93254) When performing a backup of Exchange, specify the same directory location (such as, E:\dir) for both the system path and the transaction log under the Storage Group properties in Microsoft Exchange System Manager. NMM installation fails with irccd failure on Exchange server 2003 (LGTsc26630) Exchange backup fails if the IRCCD.exe and nwexinfo.exe services are started manually after NMM installation. If the services are started manually after NMM installation, an additional step must be performed during Exchange installation: At the command line, run the nwexinfo.exe command to update the Exchange domain information. The EMC Module for Microsoft Applications Release 2.3 Installation Guide provides more information about how to resolve this issue. Backup fails if a logs volume and a database mount point volume are the same and in the same save set (NW113760) Backup does not work if a logs volume and a database mount point volume is the same, for example, D:\ and are in the same save set. Backup may fail, and display the following message: RM ERROR:An unexpected internal error occurred: IRD: mountrestorestate::handlefinalstatusmsg() : validatestate::runstate() failed. 46 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

47 Exchange backup fails with VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED (LGTsc26385) Attempting to perform a backup of more than 32 storage groups results in an error: VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHEDVSS_E_MAXIMUM_NUM BER_OF_VOLUMES_REACHED This is a known Microsoft error described and the Microsoft website provides details. You can back up 32 storage groups in a single save set at a time. Exchange snapshot recovery failing with ImportCopy error (LGTsc25761) For Exchange backup in NMM, it is highly recommended to avoid using persistent software shadow copy or copy-on-write backups. Due to the way data is distributed in Exchange databases, the snapshots for these backups may not remain valid long enough for the recovery to be successful. To ensure a valid and successful backup of Exchange, always use the setting backup=all when configuring the client resource. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides complete instructions for configuring a client resource. NMM does support temporary software shadow copy or copy-on-write for Exchange, which may 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' PS: (CPSImportService::ImportCopy) Error obtaining volume name (s) for snapshot; Microsoft ShadowCopy Service has no knowledge of the snapshot. Always follow these recommended practices: EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 47

48 Do not use persistent software shadow copy or copy-on-write for Exchange backup. 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. Save sets not listed in Single Copy Cluster (NW124858) nsrsnap_vss_save -c virtual_server_name -? does not list save sets in Single Copy Cluster (SCC). In Exchange 2007 SP3 SCC, if the database and logs of the storage group are on non-shared disks, the save sets are not listed. For successful backups in SCC, perform the following tasks: 1. All shared storage must be configured prior to cluster formation on each node, which will be a part of the cluster. It is mandatory that the quorum disk be configured and available to all nodes in the cluster prior to cluster formation. The cluster formation will fail if the quorum is not available. 2. After the cluster is formed, and before Exchange is installed, configure the physical disk resources for the clustered mailbox server shared storage. 3. After Exchange is installed and the clustered mailbox server is created, configure the physical disk resource dependencies. Note: The Microsoft technote provides information about planning for single copy clusters. 48 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

49 Microsoft SQL server This section lists the known problems and issues in Microsoft SQL server. When system database and user-defined database are recovered together, instance level recovery of SQL 2008 R2 Express edition fails (NW126203, NW126385) When system database and user-defined database are recovered together, and SQL Express service and SQL browser service are stopped, although the NMM GUI displays successful recovery, the recovery has actually failed. Do not recover both the system databases and user-defined databases together. Recover them separately. Stop the SQL service and SQL browser service, and recover only the system databases. Do not stop the services when recovering the user-defined databases. SQL cluster writer rollback fails (NW126030) The SQL cluster writer rollback recovery fails to rollback the data when recovery is performed with and without SQL writer service running. Default and named instance level recovery failed on SQL 2008 R2 cluster (NW123511) Default and named instance level recovery on SQL 2008 R2 cluster fails with error. For instance level recovery on SQL server cluster, perform the following steps: 1. Using Windows Cluster Management console, make the SQL Server resource under the Cluster Group of SQL Server, offline. Now the instance is down but the disk is available because the group is up. 2. Perform SQL writer recovery. 3. In the Cluster Management console, make the SQL Server resource online. Ensure that all the other SQL resources that depend on that SQL server are online. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 49

50 Recovery of database fails when the database is renamed after backup (NW115036, NW121148) If a database is renamed after backup, recovery of the database fails. This feature is not supported in NMM. To rename a database and its underlying data files, select the Tasks and Copy Database option in the context menu for the database. The wizard offers a choice to move rather than copy the database. The wizard window provides the option of renaming the data files. SQL writer restore fails when restoring a non-encrypted database to an encrypted SQL instance (NW125664) Restoring a non-encrypted SQL backup to an encrypted SQL instance puts the encrypted database in suspect mode where the encrypted database is not usable. You must restore: A non-encrypted SQL backup to a non-encrypted SQL instance. An encrypted SQL backup to an encrypted SQL instance. A directed restore of system component is not supported (NW125712) A directed restore of system component is not supported.! IMPORTANT Do not restore system component at the alternate recovery site. When databases that are kept on different partitions of the same CLARiiON disk are backed up together, the SQL writer becomes unstable [NW105481] NMM does not support backing up 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. Perform the following steps: 1. Move the SQL databases to the same partition. 2. Restart SQL VSS writer service before the next backup. 50 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

51 On a cluster with two virtual SQL instances, nsrsnap_vss_save -? -c <name> command gives SQL writer as output (NW118904) On a cluster, which hosts two virtual SQL instances, if you run the nsrsnap_vss_save e.exe -c sql2008-cluster -? command, the following outputs are displayed: For one instance, the output shows: APPLICATIONS:\SqlServerWriter APPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER APPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\master APPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\model APPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\msdb APPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\db-11 APPLICATIONS:\SqlServerWriter\SQL2008-CLUSTER\db-file grp For second instance, the output shows: APPLICATIONS:\SqlServerWriter APPLICATIONS:\SqlServerWriter\CLUSTER2003%5CCLUSTER20 03 APPLICATIONS:\SqlServerWriter\CLUSTER2003%5CCLUSTER20 03\master APPLICATIONS:\SqlServerWriter\CLUSTER2003%5CCLUSTER20 03\model APPLICATIONS:\SqlServerWriter\CLUSTER2003%5CCLUSTER20 03\msdb Although it is not possible to take a writer-level backup on the cluster hosting two or more virtual SQL instances, both the outputs show APPLICATIONS:\SqlServerWriter. Review the difference between SQL virtual server and physical client: SQL virtual server: When SQL is installed on a cluster setup, it is accessed using virtual name that is provided during installation. This virtual name is used by NMM when performing backup of the SQL instance. On cluster setup, to view the save set run the following command on active node: nsrsnap_vss_save -? -c <virtual sql server> EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 51

52 Physical client: When SQL is installed on a non-cluster setup, it does not require any virtual name or IP. On a non-cluster setup, to view the save set run the following command: nsrsnap_vss_save -? Directed recovery fails with OS version mismatch error (NW121995) Directed recovery fails with OS version mismatch error although the OS versions are the same. Install the VSS rollup patch from on the Microsoft website. This patch rectifies the XML parsing failure and ensures that the directed recovery is successful. Cannot browse folders of the database instance in SQL Management Console after a successful recovery operation (NW123542) After a successful recovery operation, instance level recovery does not allow browsing of the database instance folders in the SQL Management Console, if the credentials of database and instance are the same. When credentials of database and SQL instance are different, perform only database level restore operations. SQL database restore to a compressed location fails (NW120267) For SQL databases that are backed up from a compressed drive or folder, the recovery of the SQL databases to the same compressed location always fails. Perform a directed recovery to an alternate location. Ensure that the location is not compressed. Restore the data to a similar folder structure in a location that is not compressed. In case of writer-level backups, restore the databases one by one. 52 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

53 SQL VSS writer does not function properly when wrong passphrase is used during recovery (NW115412) The state of the SQL VSS writer becomes unstable when wrong passphrase is provided during recovery. Recovery fails with Non-retryable error. Due to instability of SQL VSS writer, successive backups also fail with the same error. Restart the SQL VSS writer service for subsequent backups to work. Directed recovery of multiple SQL databases fails intermittently if the backups are running in parallel (NW114905) Only partial data is recovered during directed recovery of multiple databases if the backups are running in parallel. For SQL directed recovery, recover one database at a time. SQL 2005 writer-level backup fails if databases have snapshots (NW113608, NW123721, NW118163) If a SQL 2005 database has snapshots that were taken through the SQL server, writer-level backup of SQL server fails. This problem does not exist in SQL To take a writer-level backup of SQL server 2005 SP3,and SQL server 2005 SP2 and earlier that has a SQL snapshot: For SQL server 2005 Service Pack 2, install the cumulative update package 10 for Knowledgebase article KB956854, available at For SQL server 2005 Service Pack 3, install the hotfix for Knowledgebase article KB983329, available at IMPORTANT Ensure to install all the updates listed in this knowledgebase article. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 53

54 For SQL directed recovery failure, manual clean up of database files is required for partially recovered SQL database files (NW112203) During SQL directed recovery, when the SQL database is being restored, the recovery process may create copies of database files (.mdf and.ldf) at the restore location depending upon the progress of recovery. If recovery fails due to any issues, NMM does not clean up these partially restored files from the restore location hard drive. Manually clean up the partially restored SQL database files from restore location. It is specially important to perform this manual clean up when performing directed recovery of large SQL database because after partial recovery, the copies of the database files will take up the available hard drive space and further recovery will fail. Microsoft Data Protection Manager This section lists the known problems and issues in Microsoft Data Protection Manager. Issue with file system automount status in DPM server with NMM 2.3 (NW126414) After installing NMM 2.3 client on DPM 2007 SP1 server and DPM protected clients, the following issues are seen: From DPM Management Console, creation of new protection group fails. From NMM 2.3 client GUI, DPM server disaster recovery operation fails. Each time you want to create a new protection group from the DPM Management or perform DPM server disaster recovery from the NMM GUI, log in to the DPM server and the DPM client, and enable automount. 54 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

55 Example: C:\Users\administrator>diskpart Microsoft DiskPart version Copyright (C) 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 disables the automount feature by default NMM disables the automount feature by default, which might affect DPM 2007 SP1 server operations. To create a protection group: 1. Enable the automount feature. 2. After creating the protection group, disable the automount feature. Note: When performing a disaster recovery operation, enable the automount feature. Replica recovery is successful but NMM logs show failure in DPM 2007 SP1 replica recovery for Exchange 2007 (NW123963) Even if DPM replica recovery is successful, as verified from DPM Management Console, NMM logs show failed recovery. Ignore the log details because recovery is successful. Backup of DPM 2007 SP1 fails in Microsoft Windows Storage server 2008 and Microsoft Windows Unified Data Storage server 2003 (LGTsc23912) DPM 2007 backup is not supported in Microsoft Windows Storage server 2008 and Microsoft Windows Unified Data Storage server 2003 (WUDSS). EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 55

56 Save of DPM data with data mover fails with import error (LGTsc12128) When performing a save operation of DPM database and replica without using data mover, save operation is successful. If the DPM database and replica is saved with data mover, the save operation fails with an error similar to the following: :52:02 (5628) main 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*/ NMM does not support hardware provider backups with dynamic disk and runs software provider backup without specifying any data mover. DPM 2007 rollup installation requires resetting account permissions (LGTsc19637) For compatibility on all supported platforms like Windows server 2003 (x86 and x64) and Windows server 2008 (x86 and 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. 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 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 56 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

57 6. Get the value of 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) Sometimes the NMC displays the DPM backup save group as failed, even though the backup was successful. 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 recover operation is performed. This file is located in the Applogs folder. For example, C:\Program Files\Legato\nsr\applogs\. Or Check the NMM GUI. If the save set is available in the DPM Recover Session window, then the save group backup was successful. Unable to recover DPM database through System Recover Session (LGTsc20971) To recover a DPM database, use DPM Recover Session. 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 selectable for recovery in System Recover Session. An attempt to recover a DPM database through System Recover Session will fail in the recovery operation. Always use the DPM Recovery Session UI to recover DPM databases. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 57

58 DPM newly allocated volumes not reported 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. Retry a replica-only recovery. It is not necessary to run the Allocate volumes utility again. Error on launching DPM Management Console after DPM disaster recovery (NW124780) Launching DPM Management Console after a DPM disaster recovery operation by using NMM 2.3 displays the following error message: Connection to SQL Server Reporting Services fails. Enable script options on default websites in DPM server: 1. To enable the scripts option for default websites. 2. Close the DPM Management Console. 3. Go to Start > Run, and then type inetmgr. 4. Launch the IIS manager. 5. Go to Default Web Site > ReportServer$systemname$ > Handler Mappings > Feature Permissions. 6. Select scripts option. 7. Run the DPM Management Console. After NMM recovery, the DPM protection groups are not in a healthy state (NW125272) During an NMM 2.3 recovery operation, 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. After an NMM recovery operation, perform a consistency check on the DPM protection groups. 58 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

59 Microsoft Hyper-V This section lists the known problems and issues in Microsoft Hyper-V. Hyper-V child partition rollback recovery fails (NW126030) Hyper-V child partition rollback recovery fails. A directed recovery of child partition recovers in a saved state (NW125795) When a directed recovery of a child partition is performed on the same Microsoft Hyper-V 2008 R2 server or in between two Microsoft Hyper-V 2008 R2 servers, the child partition is recovered in a saved state. When the child partition is started, the start operation fails. From Hyper-V Management Console: 1. Start the child partition. The start operation fails. 2. Right-click the child partition. 3. Select delete the saved state. 4. Start the child partition. The start operation succeeds. The restore operation for a child partition that was made highly available in Microsoft Hyper-V 2008 Cluster fails (LGTsc28331 and NW125169) Use the following procedures to restore a child partition for a Microsoft 2008 Hyper-V child partition that was made highly available: The child partition.vhd file is corrupt and the child partition configuration file is intact on page 60 The child partition.vhd file and the child partition configuration file are both corrupt on page 60 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 59

60 The child partition.vhd file is corrupt and the child partition configuration file is intact If the restore of a child partition fails from the NMM GUI, use the following procedure to restore a child partition with the following characteristics: The.vhd file is corrupt The child partition configuration file is intact To restore the child partition: 1. Locate the child partition (*.vhd) file path. 2. Move the corrupted.vhd file to the safe location (network share drive) for the future reference, if needed. 3. Create a dummy.vhd files that is identical to the original child partition that was created before the corruption occurred. 4. Launch the NMM GUI: a. Select the child partition. b. Perform restore to original location. 5. Start the child partition after restore operation is complete. 6. After the child partition is functional, discard the.vhd files that were placed in a safe location on the network share drive. The child partition.vhd file and the child partition configuration file are both corrupt If the restore of a child partition fails from the NMM GUI, use the following procedure to restore a child partition with the following characteristics: The.vhd file is corrupt The child partition configuration file is corrupt 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 cluster service. 4. From the Hyper-V Management Console, delete the child partition. 60 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

61 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! IMPORTANT Do not install operating system on the child partition. 7. From Failover Cluster Manager, add this dummy child partition to the Cluster Service. This makes the child highly available. 8. Launch NMM GUI: a. Select the child partition. b. Perform a restore to original location. 9. From the Hyper-V Management Console, after the restore operation: a. Observe that there are two child partitions with the same name are available. b. Note that one of the child partitions is the duplicate or corrupted instance that requires to be deleted. 10. From the Failover Cluster Manager Console, remove the child partition from the Cluster Service. 11. From Hyper-V Management Console: a. Start both instances of the child partitions. One of the instance 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 61

62 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) NMM only supports Hyper-V child partition with IDE Controller for virtual hard drives. SCSI Controllers for virtual hard drives with Hyper-V snapshots are not supported for relocated or directed recovery. For relocated or directed recovery operations, first delete or merge the Hyper-V snapshots from the Hyper-V Management Console and then take 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. After receiving a confirmation about a failed recovery operation, the Hyper-V system administrator must delete: 1. The corrupted Hyper-V child by using the Hyper-V Manager. 2. The corresponding child partition VHD files. Backup of Hyper-V fails in Microsoft Windows storage server 2008 and Microsoft Windows Unified Data Storage Server 2003 (LGTsc31734) Hyper-V backup is not supported in Microsoft Windows storage server 2008 and Microsoft Windows Unified Data Storage server 2003 (WUDSS). 62 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

63 Granular recovery of replica on Hyper-V guest leaves extra folder behind (LGTsc20357) When a granular recovery of a DPM replica is performed, NMM re-creates in the recovery folder, the exact path to the replica as it appeared when backed up from the DPM server. This path includes the installation path of the DPM application and the subfolders containing replica data similar to the following: <recovery folder>\c\program Files\Microsoft DPM\DPM\Volumes\Replica\<replica data> Following replica recovery, NMM attempts to remove the unnecessary DPM application folders, so the resulting path becomes: <recovery folder>\<replica data> When such a recovery is performed on a Hyper-V guest, NMM is unable to remove the DPM application folders. After a Hyper-V guest replica recovery, verify the recovery, and then manually delete the extra folders created in the replica path. Defaults for disaster mode and granular mode on Hyper-V guest or physical machine (LGTsc20284) The default recovery mode depends on whether it is a Hyper-V guest or physical machine: For Hyper-V guests, the default is disaster mode with directed recovery. For physical machines, the default is granular mode. Hyper-V configuration requirements for backing up a virtual machine that contains multiple volumes (LGTsc18796) When there are multiple volumes on the guest, backup may fail. When there are multiple volumes on the guest, VSS decides the shadowstorage area for the snapshots based on which volume has more space. This can lead to a condition where the snapshot of volume C and the snapshot of volume D both reside on volume D, because volume D has more space. During the snapshot revert stage in PostSnapshot, the snapshot of volume C may be lost if the snapshot of volume D is reverted first. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 63

64 To prepare a multiple volume guest for backup: 1. Use the vssadmin command to force the shadowstorage of each volume to be on the same volume: Note: These commands must be run inside each guest, not the parent physical Hyper-V server. vssadmin Add ShadowStorage /For=C: /On=C: vssadmin Add ShadowStorage /For=D: /On=D: 2. Repeat as needed for each volume in the virtual machine. Hyper-V pass-through disks may not be backed up in a child partition backup (LGTsc28427) In the EMC NetWorker Module for Microsoft Applications Administration Guide, it is noted that 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. Hyper-V redirection support restrictions (LGTsc27630) There are a number of NMM 2.3 restrictions in the support of Hyper-V directed recover and relocated recover: NMM does not support directed recover or relocated recover of Hyper-V on a Hyper-V server cluster. Restoring Hyper-V virtual machines to non-hyper-v servers is not supported. The parent partition must be running Windows server 2008 SP2 in order to recover, with relocation of files, a virtual machine that has Hyper-V snapshots. NMM does not support relocation recover of Initial Store. When a virtual machine is redirect recovered to a second Hyper-V server, the user must update the Network Adapter settings of the virtual machine with the Hyper-V Manager before starting the VM. 64 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

65 Cannot relocate or redirect NMM Hyper-V backups taken before a NMM 2.2 upgrade. Hyper-V destination host must have NMM client installed (LGTsc29290) When using the Hyper-V Restore Wizard, the host you specify on the Destination Host page must have the NMM client installed. Otherwise, the Destination Path page browsing will not work correctly. Hyper-V recover displays the wrong time for NMM 2.1 data recover (LGTsc29563) When NMM 2.2 is used to recover a Hyper-V child backup that was created with NMM 2.1, the recovery may show as complete even though the recovery is still in progress. There are two workarounds: Upgrade the Hyper-V child machine to NMM 2.3. If an upgrade is not feasible, you can manually verify the recovery. After starting the recovery and allowing time to run, check the nmm.raw file on the Hyper-V child machine to verify that the recovery was successful. SYSTEM COMPONENT save set backups fail on Windows server 2008 Hyper-V role implementation (LGTsc30059) NetWorker backups of the SYSTEM COMPONENT:\ fail on Windows server 2008 with Hyper-V role implementation. To work around this issue: 1. Copy the slanaccel.exe file from the following location: C:\Windows\winsxs\amd64_microsoft-hyper-v-slanaccel_3 1bf3856ad364e35_ _none_1db986a6500c51a0\ 2. Save the copied slanaccel.exe file to the following location: C:\windows\system32\ Hyper-V 2008 R2 CSV child partitions are not listed as valid save sets (NW125026) NMM 2.3 does not support backup of Hyper-V child partitions in Hyper-V 2008 R2 Cluster Shared Volumes (CSV). If you run the nsrsnap_vss_save -? command on a Active node of Hyper V cluster server, CSV child partitions are not listed as valid Hyper-V save sets. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 65

66 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. 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. Microsoft SharePoint This section lists the known problems and issues in Microsoft SharePoint. Site collection lists are not recovered after Sharepoint writer restore for embedded SQL (NW126648, NW126200) After SharePoint writer restore for embedded SQL, site collection lists are not recovered. Recover the required SQL databases individually after stopping SQL Express service and SQL Browser service. In SharePoint 2010, published shared services from a farm (Farm 2) to another (Farm 1) does not list save set to back up on Farm 1 (NW122691) SharePoint 2010 writer does not report cross-farm association of a web application. Cross-farm association is established after restoring the web application. In SharePoint 2007 and 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. 66 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

67 If SQL Express is used in a stand-alone environment, use the following parameter: NSR_VSS_FORCE_SYSTEM_PROVIDER=yes NMM 2.3 does not support hardware provider backups for SharePoint 2007 and 2010, which is configured with SQL Express. Changing the 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 work 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, because of the Microsoft restriction the hardware backup fails. This happens because the backup tries to mix both hardware and software backups, which is not a supported configuration. To continue the backup with the software provider only, use the following parameter: NSR_VSS_FORCE_SYSTEM_PROVIDER=yes SharePoint 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 2.3 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 67

68 To recover the SharePoint writer, change the browse time. After a SharePoint 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. After the SharePoint writer recovery operation is complete, restore either of the following: System components Or Registry writer Because individual writers under SYSTEM COMPONENTS can be selected, the Microsoft best practices option must be cleared to restore registry writer. In SharePoint 2010, do not rollover or delete SharePoint 2007 snapshots from a remote or alternate machine (NW123590) Although SharePoint 2007 save sets are browsable in Snapshot Management view on a host with SharePoint 2010, do not perform any operation for snapshots from remote machine. SharePoint 2010 backup and recovery are not supported on Windows 2003 platforms although content is browsable in the NMM GUI (NW123591) In NMM, SharePoint 2010 backup and recovery are not supported on a Windows 2003 platform although some content is browsable in the NMM GUI: SharePoint 2010 backups are not browsable in the NMM GUI Recover Session tab on Windows 2003 (x64) R2. SharePoint 2010 backups are browsable in the NMM GUI Snapshot Management view on Windows 2003 (x64) R2. On the Windows 2003 platform, do not perform snapshot operations on backups even though the backups may be available for browsing. 68 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

69 In SharePoint 2010, the nsrsnap_vss_save -? command does not list anything to back up on the FAST Search server (NW124707) NMM 2.3 supports the backup and recovery of the following: The FAST Query Search Service Application The 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 2.3 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. An 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) gets deleted, the association cannot be manually created after NMM recovery. After installing or upgrading NMM, nsrsnap_vss_save -? does not list savesets of Microsoft Office SharePoint server backup (NW119611) If NMM is already installed and the installation is then changed from client install to storage node install, the nsrsnap_vss_save -? command does not list any save set for backing up SharePoint writer. Backup fails as no item is found. The same problem is seen when NetWorker client 7.5 SP3 is installed with NMM and then upgraded to NetWorker 7.6 SP1, although the NMM installation is not changed. After NMM is install on host, the underlying NetWorker installation should not be modified, repaired, or changed without removing NMM. The correct procedure to make such changes is: 1. Uninstall NMM Change, upgrade, or repair NetWorker client. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 69

70 3. Reinstall NMM 2.3. Directed recovery of configuration database of SharePoint 2010 fails because the SharePoint wizard cannot connect to the recovered database (NW123768) Perform directed recovery of 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 the SharePoint Foundation Search V4 program is stopped, the backup fails with an 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 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 :nsrsnap_vss_save:NMM backup failed to complete The nsrsnap_vss_save -? output also displays NULL for the dependent components. Restart the SharePoint Foundation Search V4 service and then perform a backup. The content of Admin Content database, Shared Services database, and Crawl database is browsable at the alternate host recovery site but cannot be recovered (NW123776) Although the content is available, directed recovery of these databases in SharePoint farm is not support.: Administration Content database Shared Services database Crawl database The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides detailed disaster recovery procedures for SharePoint. 70 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

71 If SPSearch is enabled on more than one server, the SharePoint Services writers are not reported by the vssadmin application (NW124249) If SPSearch is enabled on more than one server, the nsrsnap_vss_save -? command does not report the SharePoint 2010 save sets and the backup fails. Configure only a single SPSearch for a SharePoint farm. In SharePoint 2010, the nsrsnap_vss_save -? command does not display the name of the search application in the Search Application index save sets (NW120617) The nsrsnap_vss_save -? command lists valid save sets that contain the Search Application ID instead of the Search Application Name: This makes it difficult to verify the related component and Search Application. However, this limitation does not impact the backup. To identify the Search Application, use the following: SharePoint Administration GUI Powershell commands If the SharePoint 2010 VSS writer is unregistered, the SPSearch4 and OSearch14 writers are not reported by vssadmin and VSS applications (NW120615) The backup of the following SharePoint search save set fails if the VSS writer is unregistered: APPLICATION:\Microsoft Office Search APPLICATION:\Microsoft Office SharePoint Search Register SharePoint Services Writer by using the stsadm.exe -o registerwsswriter command. Recovery fails when hardware and software backups are performed at the same time (NW115573) System components recovery fails with following error if components are configured on both local software LUN and hardware LUN, like CLARiiON or Symmetrix: NMM.. Starting Recovery. This operation may take a long time depending on the size of the data requested. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 71

72 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 SharePoint server hosting search services on hardware LUN. When full system components are recovered, some components reside on C:\ and Microsoft Office SharePoint Search on hardware LUN. 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 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 correctly 63778: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 although all dependent services and search services are running. Restart the search services for backup to be successful. Web front-end backup fails (NW115362) Web front-end backups fail and the following error message appears: 3331:nsrsnap_vss_save:NMM.. No items identified to replicate. Try to resolve the issue by using the first workaround. Use the second workaround only if the issue is not resolved by using the first: 1. Re-register the VSS writer by using the command: 72 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

73 STSADM -o registerwsswriter 2. Restart SQL browser services on the SQL server of farm, and then re-register the VSS writer by using the command: STSADM -o registerwsswriter Manual steps required for SharePoint writer after recovery to associate web application to original SSP (NW105541) The original association of web application to original SSP is not restored when the association of the web application to original SSP is changed after backup. However, the data is recovered successfully. 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. Now 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. Required Volumes information is not displayed correctly in Microsoft SharePoint Services node (LGTsc13670) In NMM, when you select and right-click the Microsoft Office SharePoint Services node or an item within that node, and then click Required Volumes, the volume information is not displayed. Instead, a message box appears: NetWorker was not able to display required volumes information for the selected Microsoft Office SharePoint Services component. Please query the following node(s): EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 73

74 SharePoint disaster recovery fails with SQL database recovery failure (LGTsc20972) Failure of SQL master database recovery leads to failure in SharePoint disaster recovery. An error, similar to the following, is displayed: 63688:nsrsnap_vss_recover: NMM Cannot replace file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf in comp master in writer SqlServerWriter. Database must be put into overwrite state. When this error occurs, the specified files database must be moved, renamed, or deleted, and the recovery steps must be performed again from that point. The associated files are the master database file master.mdf and master log file mastlog.ldf. Microsoft Office SharePoint server 2007 VSS writer backup and recovery fails for Windows server 2008 R2 (NW118982, NW120044, and NW118258) Microsoft Office SharePoint server 2007 VSS writer backup on Windows server 2008 R2 fails when no components are configured. The SharePoint writer crashes during recovery. Install the following Knowledgebase hotfixes (full server cumulative update packages) released in April 2010 from the Microsoft website: KB at for Windows SharePoint Services. KB at for MOSS. Note: These hotfixes are only required for Windows server 2008 R2 and not mandatory for Windows server 2008 SP2. Error occurs on restoring SSP and unregistering SharePoint writer (NW124776) The VSS_E_WRITER_INFRASTURE error occurs when the following steps are performed: 1. Running the backup on a FARM. 2. Deleting the SSP and restoring the SSP. 3. Unregistering the SharePoint writer and running the nsrsnap_vss_save -? command. 74 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

75 Register the SP writer. This provides the correct save sets for nsrsnap_vss_save -?. In SharePoint 2007 SP2, recovery of the web application and SSP fails when the OCT CU patch is applied (NW125432) In SharePoint 2007 SP2, a recovery of the web application and SSP fails when the OCT CU patch is applied and the SQL named instance is used. To recover the web application and SSP: 1. Install the following software: SharePoint 2007 SP2 software October 2010 CU 2. Run the backup for the SP writer. For example: C:\inetpub SYSTEM COMPONENTS:\ SQL writer 3. Restore the WS 2008 R2 SharePoint server: a. Delete a web application. For example: iis _ db b. Restore the following: SYSTEM COMPONENTS:\ c. Restore the following: C:\inetpub d. Restore SQL. 4. Clear the SharePoint Configuration Cache: a. Stop the Windows SharePoint Services Timer service. b. Delete all the XML file in the following directory: C:\ProgramData\Microsoft\SharePoint\Config\<G UID> Note: Only delete the XML files. Do not delete the.ini file. EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 75

76 Technical notes 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. 5. Restore the SharePoint Writer. Technical notes In addition to the EMC Module for Microsoft Applications Release 2.3 Administration Guide, review the following for more information about NMM 2.3: EMC NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups 2.3 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.3 Technical Notes provides details on how to deploy NMM in a proxy backup configuration with EMC Symmetrix. Documentation Related documents include: EMC Module for Microsoft Applications Release 2.3 Installation Guide EMC Module for Microsoft Applications Release 2.3 Administration Guide EMC Module for Microsoft Applications Release 2.3 Application Guide EMC NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups 2.3 Technical Notes EMC NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups 2.3 Technical Notes EMC NetWorker Licensing Guide EMC Information Protection Software Compatibility Guide EMC NetWorker License Manager Seventh Edition Installation and Administration Guide 76 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes

77 Software media, organization, and files EMC Solutions Enabler Symmetrix CLI Version Quick Reference EMC NetWorker Release 7.5 Service Pack 3 documentation EMC NetWorker Release 7.5 Service Pack 4 documentation EMC NetWorker Release 7.6 Service Pack 1 documentation EMC NetWorker Release 7.6 Service Pack 2 documentation! IMPORTANT The PDF versions of the guides provide the most current information on NMM 2.3. Check the EMC Powerlink website to ensure that you are using the latest version of this document. Software media, organization, and files Information on software media, organization, and files is provided in the EMC Module for Microsoft Applications Release 2.3 Installation Guide. Installation The EMC Module for Microsoft Applications Release 2.3 Installation Guide provides information about installing and uninstalling NMM 2.3, Microsoft hotfixes required for NMM 2.3, preinstallation checklists, postinstallation configurations, and other details. Troubleshooting and getting help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes 77

78 Troubleshooting and getting help Technical support For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Contact your EMC Sales Representative for details about obtaining a valid support agreement or to answer any questions about your account. Copyright 2011 EMC Corporation. All rights reserved. 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. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 78 EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes