EMC
®NetWorker
®Release number 8.2 and Service Packs
Release Notes
302-000-698 REV 12 June 24, 2015
These release notes contain supplemental information about the EMC NetWorker 8.2 and service pack releases.
The installed NetWorker version displays as a four digit number. For example, the initial release of NetWorker 8.2 SP1 displays as NetWorker 8.2.1.0 when installed.
Note
All new or updated software downloads and product-specific technical documentation are available on the EMC Online Support site at https://support.emc.com. From the Support by Product pages, search for NetWorker using “Find a Product.” The product page provides access to all product specific downloads and documentation, as well as additional content and tools.
Topics include:
l Revision history... 2
l Product description...3
l New features and changes... 3
l Fixed problems... 12
l Environment and system requirements... 19
l Known problems and limitations...22
l Internationalization support...150
l Localization support... 150
l Technical notes...155
l Documentation... 160
l Installation... 162
Revision history
The EMC® NetWorker® 8.2 and Service Packs Release Notes was originally published in
June, 2014. The following table presents the revision history of this document.
Table 1 Revision History
Revision Date Description
01 June 18, 2014 NetWorker 8.2 released 02 June 27, 2014 Removed limitation NW158104
03 September
26, 2014
Added section for Apache configuration file modules to Technical Notes on page 155
Revised OVA version in limitation 192213 and changed to 200234 Added knowledgebase article 192005 to 'Known Problems and Limitations" on page 22
Added 200499, 199170, 194661, 194464, 193737 and NW161099 to 'Known Problems and Limitations" on page 22
04 October 17,
2014
Added topic on the RPC Portmapper service to "Documentation corrections and additions." on page 161
Added 199027 and 197810 to 'Known Problems and Limitations" on page 22
05 October 31,
2014
Added topic on using "last" as an override value in the nsr_schedule command to "Documentation corrections and additions." on page 161
Added topic for command line changes and additions on page 8
Revised information in "New Features and Changes." on page 3
for the hotfix now available to support Avamar 7.1 with NetWorker 8.2
06 January 28,
2015
NetWorker 8.2 SP1 released . Revisions include:
l Added section New features and changes in NetWorker 8.2
SP1 on page 4
l Added section Fixed Problems in NetWorker 8.2 SP1 on page
12
l Added section Known Limitations discovered in NetWorker 8.2
SP1 on page 23
l Removed 197810 from 'Known Problems and Limitations" on
page 22
l Removed 199027 from 'Known Problems and Limitations" on
page 22 and moved information to the NetWorker and VMware Integration Guide
07 February 3,
2015
Table 1 Revision History (continued)
Revision Date Description
08 February 20,
2015
Added topic for Command line changes in NetWorker 8.2 SP1 on page 5
Added 226760 and 200743 to 'Known Problems and Limitations" on page 22
09 April 3, 2015 Added topic for New OVA files for the NetWorker 8.2 SP1 VMware Backup Appliances on page 4
10 May 4, 2015 Restored topic Hotfix to support Avamar 7.1 with NetWorker on page 11
11 June 3, 2015 Added information for ETA 196089 to Known Limitations discovered in NetWorker 8.2 SP1 on page 23
12 June 24, 2015 Added information for the issues addressed in ETA 203433 to
Known Limitations discovered in NetWorker 8.2 SP1 on page 23
Product description
The EMC NetWorker 8.2 and later releases provide significant functional enhancements, including support for the following:
l Use of https to securely communicate with the Cloud server.
l Enhancements to the VMware Protection solution, including dual network
configuration for VMware proxy backups, automated disaster recovery, VM recovery from a secondary site to a different vCenter, improved visual representation of VMware environments, VMDK-level backups, and more control of transport modes used.
l Support for NetApp SnapVault and NetApp SnapMirror operations.
l NetWorker snapshot management support for network-attached storage (NAS)
devices, including EMC Isilon, EMC VNX, EMC VNX2, EMC VNX2e, and NetApp.
l IPv6 support for NDMP backup and recovery operations and Data Domain systems. l Secure multi-tenancy (SMT) storage on DD OS 5.5 and later systems.
l Parallel save stream (PSS) support for Windows.
New features and changes on page 3 provides more information on new features and identifies the release these features were introduced.
Before installing a NetWorker 8.2 release, review the NetWorker installation guide, administration guide, and other documentation. Documentation on page 160 lists the complete NetWorker release 8.2 and later documentation set.
New features and changes
This section contains information on new features and enhancements in the following NetWorker 8.2 releases:
New features and changes in NetWorker 8.2 SP1
The NetWorker 8.2 SP1 software contains the following new features and enhancements. More detailed information on these features is provided in the core documentation set:
l OVA files for the NetWorker 8.2 SP1 VMware Backup Appliances on page 4 l Command line changes on page 5
l Recovery from a secondary site to a different vCenter when primary site is unavailable on page 6
l Dual network support for proxy backup with NetWorker VMware Protection on page 6
l NetApp SnapVault and NetApp SnapMirror replication to remote NetApp devices on page 6
l Secure HTTPS communication with the Cloud server on page 7
l Environment variable NSR_CLUSTER_LOGDIR added to change the directory location of NetWorker cluster scripts on page 7
l Starting NMC by using an SSH connection on page 7 l IPv6 support for NDMP backup and recovery on page 7
l NetWorker and Data Domain DD Boost integration enhancements on page 7 l Renaming a NetWorker server by using nsrclientfix on page 7
OVA files for the NetWorker 8.2 SP1 VMware Backup Appliances
Networker 8.2 SP1 provides the following OVA files for the 0.5 TB, 4 TB, and external proxy VMware Backup Appliances, in addition to the appliance for upgrading your OVA version.
The following table provides version information for the new OVAs.
Table 2 OVA versions for NetWorker 8.2 SP1 VMware Backup Appliances
File name Description
EBR-0.5TB-1.1.1.50.ova NetWorker 8.2.1 OVA for the 0.5 TB VMware Backup Appliance
EBR-4.0TB-1.1.1.50.ova NetWorker 8.2.1 OVA for the 4 TB VMware Backup Appliance
EBR-Proxy-1.1.1.50.ova NetWorker 8.2.1 OVA for the External proxy that supports EXT4 backup and recovery
EbrUpgradeFrom70To-7.1.61-10.iso NetWorker 8.2.1 ISO file for upgrading the OVAs
If you previously deployed OVA versions 1.1.1.46, you must apply a patch before upgrading to OVA version 1.1.1.50. When you download the OVA from https://
support.emc.com/downloads/1095_NetWorker a document displays which contains the patch links with instructions for installation. After applying the patches, you may then proceed to upgrade from OVA version 1.1.1.46 to OVA version 1.1.1.50. If you are not running OVA version 1.1.1.46, you do not need to apply the patches and can upgrade directly to OVA version 1.1.1.50.
EMC strongly recommends also upgrading your NetWorker Server and Storage Nodes to Networker cumulative build 8.2.1.3.
disks: Unable to browse as proxies are unavailable'
l Knowledge Base 201865 - Clients VMs are removed from VMware Protection Policies
OVA 1.1.1.46 fixes the following issues:
l 226264 - glibc versions vulnerability
l 226834 - Resurrect restore from Data Domain hangs in Import operation with errors l 226240 - Circular deadlock problem in rwmutex
l hfscheck failures fix detailed in Knowledgebase article 197864, available at https:// support.emc.com
Command line changes in NetWorker 8.2 SP1
NetWorker 8.2 SP1 includes the following command line additions and enhancements.
nsrrpcinfo command now used to display NetWorker daemons
Starting in NetWorker 8.2, NetWorker daemons do not register with system port mappers. NetWorker daemons register exclusively with the port mapper that the nsrexecd process manages. As a result, the OS rpcinfo command will not display NetWorker daemons. To display the NetWorker RPC processes, use the nsrrpcinfo command. The NetWorker Command Reference Guide describes how to use the nsrrpcinfo command.
mmrecov and nsrdr commands add -n option to prevent "scan needed"
flag on FTD and AFTD volumes
The mmrecov and nsrdr commands now provide an option (mmrecov -n) that allows you to disable the "scan needed" flag for any additional FTD and AFTD volumes.
nsradmin command adds -C option to perform validation checks
Running nsradmin -C allows you to perform miscellaneous validation checks on NetWorker resources.
Options added to nsrndmp_recover and nsrndmp_save commands
NetWorker 8.2 SP1 adds the following options to the nsrndmp_recover and nsrndmp_save commands:
l -O stderr file reopens the stderr descriptor on the file supplied with this
option. This option is useful on platforms that do not allow redirecting of stderr to a file.
l -f forces the use of IPv4 addresses for NDMP data connection.
Options added to nsrports command
NetWorker 8.2 SP1 adds the following options to the nsrports command:
l -a shows the state of all NetWorker socket connections.
l -f address family limits the display to connections of the provided address
family.
Recovery from a secondary site to a different vCenter when primary site is unavailable
Starting in NetWorker 8.2 SP1, when you clone a VM or VMDK backup to a secondary site with its own vCenter and VMware Backup appliance, and the secondary site shares the same NetWorker server as the primary site, you can recover data from the secondary site to a different vCenter when the primary site becomes unavailable.
You can select this option in the Restore tab of the EMC Backup and Recovery user interface in the vSphere Web Client.
Dual network support for proxy backup with NetWorker VMware Protection
The NetWorker VMware Protection solution for NetWorker 8.2 SP1 supports dual network configuration so that you can use separate networks for VM backups (for example, proxies deployed to backup VMware environments) and traditional backup data traffic. You can configure dual NIC when you deploy the VMware Backup appliance and the proxy appliance.
NetApp SnapVault and NetApp SnapMirror replication to remote NetApp devices
The following support for NetApp SnapVault and NetApp SnapMirror operations to replicate data snapshots in 7-mode or cluster-mode to remote NetApp devices is available in NetWorker 8.2 SP1:
l Support covers snapshot creation, snapshot replication, snapshot restore, and
rollover of snapshots to tape or VTL storage.
l SnapVault takes a full PiT snapshot and stores only new and changed data. l The source and destination volumes (qtrees) must exist before you configure a
replication. The volumes may be on the same or separate NetApp devices on the same or separate servers, which may be NetApp virtual machines, and both volumes must be in an online state.
l The source volume must be read-writable and the destination volume must be a data
protection type.
l You must configure SnapVault and SnapMirror replication policies on the NetApp
devices.
l Validate the replication configuration by performing an initial replication operation.
This makes the replication policies available as selections in the NetWorker client wizard.
l If the snapshot destination volume is written to, the destination becomes the new
source volume and the relationship switches.
l To enable data recovery from NetApp replications, you must specify the
NSR_MOUNTPOINT_NAME variable. NetApp devices on Linux operating systems cannot use a temporary mount point.
l In-place recoveries and out-of-place recoveries of an entire directory or save set are
not supported. You may recover one or more files, provided the files do not make up the entire contents of a directory.
l A snapshot must be restored to a unique destination volume that is not used for
other SnapMirror operations. If the same snapshot exists on the destination volume, an incremental restore is performed and the previous snapshot is overwritten.
Secure HTTPS communication with the Cloud server
NetWorker enables you to use https to securely communicate with the Cloud server. You can configure secure https communications when you configure the cloud device in NetWorker.
You will need to retrieve the SSL certificate for the Cloud server before you create a new device or modify an existing cloud device, and then provide the https address and the certificate information in the Create Device window in NMC. The sections "HTTPS
communications with the Cloud server" and "Create and label a Cloud storage device" in the NetWorker Administration Guide provide details.
Environment variable NSR_CLUSTER_LOGDIR added to change the directory location of NetWorker
cluster scripts
Log files for the NetWorker cluster scripts get placed by default in the same directory as the NetWorker scripts (/usr/bin). This is because the location of the standard NetWorker log directory (/nsr/log) may change during a cluster failover.
A new environment variable, NSR_CLUSTER_LOGDIR, allows you to specify a new location to store the NetWorker cluster script log files.
Starting NMC by using an SSH connection
You can now use SSH port forwarding to connect to the NMC server and generate reports from an NMC client. The section "Starting the Console by using an ssh connection" in the NetWorker Administration Guide provides the required steps.
IPv6 support for NDMP backup and recovery
Starting in NetWorker 8.2 SP1, you can use IPv6 for NDMP backup and recovery operations.
By default, NDMP backup and recovery will use IPv6 to create the data connection between the NDMP data server and mover server, when certain requirements are met. The section "Pre-configuration requirements for NDMP data operations" in the NetWorker Administration Guide provides more information.
NetWorker and Data Domain DD Boost integration enhancements
NetWorker 8.2 SP1 introduces the following enhancements to the Data Domain DD Boost integration:
l Support added for DD Boost backup and recovery data transport operations over IPv6
compliant networks with supported Data Domain systems.
l Support of DD Boost over fibre channel (DFC) for NetWorker storage nodes on HP‑UX
11i v3 platforms running IA-64 processors.
l Support of Client Direct backup over DFC connectivity for NetWorker clients on HP‑UX
11i v3 platforms running IA-64 processors.
Renaming a NetWorker server by using nsrclientfix
A new procedure allows you to rename a NetWorker server by modifying the /etc/hosts file to add the new name as an alias and then use nsrclientfix to move the NetWorker
instructions.
New features and changes in NetWorker 8.2
The NetWorker 8.2 software contains the following new features and enhancements. More detailed information on these features is provided in the core documentation set:
l Command line changes on page 8
l NetWorker VMware Protection enhancements on page 8 l NetWorker snapshot management for NAS devices on page 9 l DD Boost devices secure multi-tenancy on page 10
l Block-based backups enhancements on page 10
l Parallel save streams support for Windows, synthetic and virtual synthetic full backups on page 11
l Parallel cloning for clone-controlled replication (Data Domain systems only) on page 11
l Hotfix to support Avamar 7.1 with NetWorker on page 11
l Windows 2003, XP, and Change Journal Manager no longer supported on page 11 l Autoselect storage node attribute added to NMC on page 11
Command line changes in NetWorker 8.2
NetWorker 8.2 includes the following command line additions and enhancements.
New option -m <backup mode> added to nsrconsolidate command
A new option -m <backup mode> added to the nsrconsolidate command allows you to specify the backup mode, for example file system or block based backup. If you backed up the save set using block-based backup, then specify this option as "bbb". By default, the backup mode is "file system."
The nsrinfo command's -V option now includes UNIX file permissions
information
You can now use the nsrinfo command's -V option to also determine a UNIX client's file access permissions and ownership. The NetWorker 8.2 Command Reference Guide provides more information on using the nsrinfo command.
New command nsrsnap for NAS device snapshot management
NetWorker 8.2 introduces a new command, nsrsnap, which is used by savegrp to perform NAS device snapshot management related commands for file system and application backups. The NetWorker Command Reference Guide provides more information.
NetWorker VMware Protection enhancements
NetWorker 8.2 introduces many enhancements to the VMware Protection solution, which allows you to manage your VMware environment by using NMC and the EMC Backup and Recovery user interface in the vSphere Web Client.
These enhancements include the following:
Appliance registration for use in VMware view, so it is not required to manually create vCenter resources.
l Increasing the number of VM backups you can run in parallel from 24 to 48
concurrent sessions, and increasing the number of proxies per vCenter from 3 to 5.
l Instant Access restores for primary backups to Data Domain systems. Selecting an
image-level backup and clicking the Instant Access button in the EMC Backup and Recovery user interface in the vSphere Web Client launches the Recovery wizard.
l Direct to Host recovery, allowing you to restore VMs direct to an ESX host without
requiring a vCenter Server by using the Emergency Restore tab in the EMC Backup and Recovery Configure window.
l VMDK-level backup and recovery, so you can now view and select individual disks
within NMC (for backup) and the vSphere Web Client (for recovery).
l Automated disaster recovery of the VMware Backup Appliance by using the Start VBA
Recover for Checkpoints option in NMC and selecting from a list of available checkpoint backups.
l Control the transport modes used by enabling/disabling the VBA restrict transport
mode to hotadd only setting in NMC.
l Control whether backup now functionality is available in the EMC Backup and
Recovery user interface by enabling/disabling the VBA Adhoc Backups setting in NMC.
Additionally, clicking Backup Now in the EMC Backup and Recovery user interface now runs the entire policy, including backup and clone operations associated with the policy.
NetWorker snapshot management for NAS devices
The EMC NetWorker 8.2 server software includes optional features to enable NetWorker snapshot management for network-attached storage (NAS) also called NSM for NAS. Supported NAS devices are EMC Isilon, EMC VNX, EMC VNX2, EMC VNX2e, and NetApp. The NetWorker Snapshot Management for NAS Devices Integration Guide provides more information, including NAS device support and limitations.
NAS devices are configured as clients of the NetWorker server, for example, by using the Client Configuration Wizard, but you do not install NetWorker client software on a NAS device. NAS snapshot and replication features are covered by NDMP licenses.
NAS snapshot operations
NetWorker works with NAS devices to perform the following snapshot, replication, storage, and recovery operations:
l Create local snapshot save sets of specified data on the NAS device.
l Replicate specified snapshot data on a source NAS device to a different location on
the device or to a location on a different NAS device.
l Perform immediate or delayed rollover of specified snapshot save sets to secondary
storage by using NDMP.
l Apply retention policies to manage the lifecycles of snapshot, replication, and
rollover save sets.
l Recover specified data from snapshots and rollovers.
l NetWorker can roll over, recover, and report on discovered snapshots but cannot
delete them
l You can schedule discovery once per day or perform discovery manually
Types of NAS snapshot recovery
To recover NAS-based snapshots, you may use the NetWorker Recovery Wizard, the
nsrsnapadmin command, or the nsrnassnap_recover command. NetWorker mounts the snapshot volume where you can browse the snapshot save sets and select the directories or the individual files to recover. The snapshot data may be recovered as follows:
l In-place recovery restores files and directories to their original locations on the NAS
device.
l Out-of-place recovery restores files and directories to a new location you specify on
the NAS device.
l Directed recovery restores files and directories to the NetWorker host that runs the
recovery. The recovery directory may be configured as a CIFS or NFS file share, which enables recovery to a remote location, such as another client or a NAS device.
NAS snapshot lifecycle policies
The NetWorker software provides lifecycle policies for snapshot save sets. Snapshot policies specify the following information:
l The time interval between the snapshots
l The maximum number of snapshots stored on a NAS device, after which NetWorker
automatically deletes the oldest snapshots
l Which snapshots NetWorker backs up to conventional storage media
NAS snapshot monitoring and reporting
NetWorker reporting features enable you to monitor NAS snapshot operations for each NetWorker client or NAS device, including snapshots that were not created by NetWorker. NetWorker catalogs all snapshots as backup save sets. You can monitor the progress of the snapshot creation, mounting, deletion, and rollover operations. The NetWorker nwnassnap.raw log provides details of snapshot operations.
DD Boost devices secure multi-tenancy
NetWorker 8.2 supports DD Boost devices in secure multi-tenancy (SMT) storage on DD OS 5.5 and later systems. SMT is based on the model of a service provider with tenant users. A global storage administrator assigns or creates secure storage units (SU) on the Data Domain system for each tenant user. Backup administrators and other tenant users must use a DD Boost username and password to gain access to these SUs and configure DD Boost devices within them.
NetWorker supports up to 512 DD Boost devices per secure SU.
Block-based backups enhancements
Block-based backup enhancements in NetWorker 8.2 include the following:
l Support for recovering multiple save sets in a single operation, including the ability to
l Image-level recovery without mounting the backup image.
Parallel save streams support for Windows, synthetic and virtual synthetic full backups
The following Parallel save stream (PSS) enhancements have been added in NetWorker 8.2:
l Windows support
l Synthetic, and Virtual Synthetic full backups for UNIX, Linux, and Windows
Parallel cloning for clone-controlled replication (Data Domain systems only)
Parallel cloning is an enhancement to clone-controlled replication (CCR) for Data Domain systems that allows clone operations to occur concurrently, similar to save operations, so that multiple clone threads can occur in parallel for each clone process.
NetWorker enables this feature by default, and allows up to 30 parallel cloning sessions per NSR clone operation.
Note
You can modify the nsrcloneconfig file to change the number of parallel cloning sessions for CCR, however, EMC does not recommend modifying the default setting unless this setting is problematic for your system. The NetWorker Cloning Integration Guide provides more information.
Hotfix to support Avamar 7.1 with NetWorker
Increased firewall restrictions introduced in Avamar 7.1 can cause unencrypted
NetWorker backups to fail. However, a hotfix is now available that resolves this issue and allows you to use NetWorker with Avamar 7.1. FTP to the following location to download hotfix 203122: ftp.avamar.com/software/hotfixes/203122.
The knowledgebase article 193138, available from https://support.emc.com, provides more information about the issue.
Windows 2003, XP, and Change Journal Manager no longer supported
NetWorker 8.2 and later releases no longer support the following:
l Windows Client for Windows XP
l Windows Client for Windows Server 2003 l Change Journal Manager
Autoselect storage node attribute added to NMC
The Client resource and Client Configuration Wizard contain a new option, Autoselect storage node, which enables the NetWorker server to automatically select a storage node for use during a backup or recovery. When you enable this option for the NetWorker server’s Client resource, a clone operation will use this option if the clone operation cannot use the storage node specified in the Storage node resource.
The Autoselect storage node attribute is disabled by default. When enabled, NetWorker gives priority to local storage nodes and this value overrides the values specified in the “storage nodes” and “recover storage nodes” Client resource.
Fixed problems
This section provides details on fixed bugs for the NetWorker 8.2 and service pack releases. When a cumulative build is released, information on fixes included in the latest cumulative is provided in the NetWorker Cumulative Hotfixes document, available on the EMC Online Support site.
Fixed Problems in NetWorker 8.2 SP1
The following table lists customer reported defects resolved in NetWorker 8.2 SP1.
Table 3 Fixed in NetWorker release 8.2 SP1 Issue Number Description
192086 Recovery fails with block size errors 204353 nsrd cores frequently
192088 Jukebox unusable after a bootstrap save
203401 CBT incremental backup for VADP fails for Czech file name 205743 Nsrvadp_recover crashes for libasm.dll on proxy host
178806 Local user loses privileges after configuring external authentication 202166 Provide ability to restore VMs to a different vCenter
196293 Enhancement in clone framework to replicate additional VMDK files from Avamar mtree to NetWorker mtree
194236 Run nsrindexd diagnostics to understand Client performance issues during Index look-ups
193957 Change IDR maximum to 12
193893 Support for NDMPv4 Connection Address Extension to use IPv6 for data connection
193339 When snapshots are manually deleted then the corresponding mminfo entries should be removed.
192716 Update Configuration wizard messages
183909 Packaging changes to include nsrddsh in server packages
185747 Allow nsrlic to print details of NSR License resource and device licenses in addition to client licenses in a single line format
188113 Include automatic -daily- clientid report with nsrclientfix 183686 Allow NMC to work with SSH tunnels
183103 Windows Logo Certification: NetWorker Management Console Server.msi: ICE61 Errors
182025 Browsing file system from Client Properties doesn't work for NDMP client of Celerra/VNX/Isilon
Table 3 Fixed in NetWorker release 8.2 SP1 (continued) Issue Number Description
178221 LDAP enhancement
178123 NetWorker Recover.app should show active jobs in Monitoring dialog 171176 package nsrpost.exe with windows client package
158996 Enhance nsrndmp_save to use netapp NDMP cluster aware backup extension 147404 Set the scan flag by default for disk devices when running mmrecov
205347 Granular level restore fails with MAPI error "Unable to query MAPI interface" 204012 Save set "all-zfs" does not perform virtual synthetic full backups
202951 RedHat Linux on server reboot does not run NetWorker shutdown scripts. 201422 VADP: nsrvadp_recover cannot recover full VM: Error writing to VMDK: 0 bytes
written instead of n bytes
201035 Directed nsrretrieve from another host requires NSR resource administrator attribute privileges
200849 nsrarchive does not produce log/notification output in NW 8.x
200606 nsrsnmd.exe Application error on Windows - most occurrences in cloning and staging
200016 nsrd NSR critical Unable to update the volume cache for volume 199824 Lockboxes not available with every failover on Linux server cluster 198837 nsrmmd core dump
198650 BBB recovered in NMC not working while part of files are deleted in a directory 198227 Data Domain devices get unmounted during savegrp execution
197598 nsrclone command not attributing correct values to ssid's when -m, -w and -y flags specified on command line
197595 NetWorker server is unresponsive When AFTD devices passed full threshold Networker
197358 Fails to recover older save sets which are backed up using 7.6.x with the latest Build
196955 Resource Group offline sequence hangs in an AutoStart high availability environment
196900 nw_redhat script directs logs to /usr/sbin
196875 NSRserver service transitions to a failed state in an AutoStart high availability environment
195612 NSM nsrbragent dumps core during SAP restore and session hangs 195161 Unable to backup cluster drives since upgrading
194706 VADP Parser crash with heap corruption
Table 3 Fixed in NetWorker release 8.2 SP1 (continued) Issue Number Description
194573 NetWorker Cluster - bug in start-script /etc/init.d/networker 194571 NSR_DEV_BLOC_SIZE variable not honored
193861 Aborted VSS Fileset reported as competed in the media DB
193421 Savegroup completion report of an all successful restart job, wrongly reports a number of clients as failed
193944 nsrdr does not show appropriate error message when the NW software is installed on a different location during DR exercise
193551 Disable log mark display to be default in Restore Options 189545 Unable to exclude the scsi path when scanning for devices
161877 Replacing calls to logit function in libblockbased.cpp with networker logging 187852 nsrd hangs up to 1 min waiting for nsrjobd call send_ssninfo_to_jobd
hostname:bkpsrva0
153348 Provide ways to control the size of nsrmedisrv.raw file
198160 Server holds the connections to Clients leading to connection limit getting hit on the Server host(Auditlog feature).
197522 Networker client agent install on Linux using --relocate not working
197037 unable to recover CIFS save sets from the RECOVER GUI with error: "not in index" 190880 NMC on Policy group shows abort status even when Policy details shows backup
completed
190126 nsrmmd cores
187791 nsrscsi_save fails with invalid raw device path if PowerPath is not configured 192591 nwrecover does not recover all marked files on a file system, mounted within a
file system
192814 NetWorker hangs daily
192232 nsrd cores if "verify label on unload" is enabled for DD VTL 187759 Immediate clone hangs if schedule set to skip
192798 Unable to delete volumes residing on a NetWorker 7.6.5.x server via NMC version 8.1.x
193420 Allow recovery of VMs which have non ASCII characters in annotation notes 151235 Permission of some Networker directories should not be world-writable 187916 Running nsrim -X does not delete expired save sets on DD BOOST devices 189804 NMC Group status reports success despite failed NetWorker backup with input/
output error
189423 Add to repository operation in Software Distribution does not work for AIX packages
Table 3 Fixed in NetWorker release 8.2 SP1 (continued) Issue Number Description
188816 Some storage nodes no longer mount volumes after upgrading 187294 Save set all-local fails on Solaris 11 non-global zone backup
186668 Unresponsive nsrsnmd on NetWorker sever causes NetWorker server hang 189189 NMC customization not saved when closed using File > Close
186403 Nsrvba_save daemon intermittently dumps core during backup through a Linux server
Fixed Problems in NetWorker 8.2
The following table lists customer reported defects resolved in NetWorker 8.2.
Table 4 Fixed in NetWorker release 8.2 Issue Number Description
NW146642 The save set defined with multi-byte character is garbled in savegrp.log messages on Windows
NW153511 mminfo command does not display levels correctly when using report for level NW153972 Increase group name length from 32 characters to 64 characters
LGTsc20723 Incremental not saving renamed files in AIX 5.3/6.1 and MAC 10.4/5 LGTsc31384 Modify direct LDAP calls in 'ldapauth.c to use-those from CST (UNIX) NW138605 When cloning same ssid twice to the same DD Boost device, clones wait
indefinitely instead of skipping already cloned ssids NW144095 Restricted Data Zone support for NMC reporting
NW151531 Incremental backup of large XFS file systems (64-bit inode) selects all files NW152420 Add Restricted Data Zone support to jobsdb
NW152857 Put Restricted Data Zone attribute into save sets
NW152874 Encryption option required for session channels to facilitate secure remote execution through nsrjobd
NW153560 Provide run-as capabilities for NMC Recovery wizard
NW153646 Need to add policy operation calls in NetWorker WS for NetWorker VMware Protection solution
NW153672 When mtree limit is reached in Data Domain, no explicit message gets logged in NMC and NetWorker
NW154010 Make changes to savegrp process to consolidate save sets and spawn single save process for CSV backup
Table 4 Fixed in NetWorker release 8.2 (continued) Issue Number Description
NW154747 For parallel save streams send '-M' option with save command for DR and All backup
NW154883 Simplified Storage Node Selection
NW155054 Parallel save stream support for Windows deduplicated volumes
NW155218 Add support for recovery of block-based backups from Non-Windows storage nodes via NFS share
NW156112 New update enabler required for NetWorker 8.2
NW156568 Need a switch to enable/disable “auditlog” broadcast on nsrd startup NW156870 Enhanced nsrddsh debugging tool for NetWorker and Data Domain integration
issues
NW158392 Update nsravtar to Avamar version 7.0.1
NW159134 NMC Device wizard provides no error message when trying to create SMT device on a system earlier than DDOS 5.5
NW159542 Support IBM silo library for aixpower
NW159774 Discovery of Snapshots should not list Dangling NetWorker Snapshots. NW115531 Log message does not show Authentication changes
NW128960 Remove unneeded Make targets related to Fortify
NW141054 Scheduled cloning should have a notification similar to savegroup completion NW143866 Refactor libnsreva code to replace err code with NetWorker errinfo data structure NW143914 Synthetic full support for completed full/incr MBS savesets (parallel save
streams) similar to synthetic full support for CPR savesets
NW144996 Display cloned save sets in "--- Cloned Save Sets ---" section of savegroup notification email
NW145003 Dedicated Storage node attribute to be moved to storage node properties from Device properties.
NW145423 Remove obsolete recursive make framework, conversion scaffolding and recursive makefiles
NW147204 Method required to select the Internet Protocol (IP) to use IPv4, IPv6, or both NW147564 Enhance the Data Domain properties listed under the Devices tab
NW148272 Log skipped save sets by nsrclone into jobdb NW148322 Allow resizing of columns in NMC for various panels NW148596 Support FAT32 volumes with block-based backup
NW148856 Modify HP-UX ServiceGuard NetWorker monitor scripts to allow for a longer timeout period for nsrd
NW149213 Improve build performance on Windows by enabling precompiled header support
Table 4 Fixed in NetWorker release 8.2 (continued) Issue Number Description
NW150214 Backup jobs of VMware protection policy launched from vSphere Web Client do not show up in NMC policy details
NW150827 Enhance nsrvim to collect VM Container objects
NW150829 When a VBA registers (or re-registers), auto create a NSR Hypervisor resource for the vCenter
NW151228 linuxppc64 uses a bad path for bison NW151364 Bundle VDDK 5.5 with NetWorker NW151496 Decouple rapgen from liblocal headers NW152506 Add a man page for nsrclientfix
NW152802 Add aixpower32 platform to ac como date the modules NW152803 Remove AIX 5.2 support
NW153489 Provide DD boost functionality via a proxy (on NetWorker server) to NMC NW153616 Include libnsrvba.dll into NetWorker server packaging for Windows x64
platforms
NW153775 Authentication should use CST library instead of Open LDAP or CST LDAP NW153883 Display the DPN ID for the VMware Backup Appliance in NMC
NW154079 Implement file system plugins framework for the NAS client in Client Configuration wizard
NW154123 NetWorker block-based backup to include support for recovering multiple save sets in a single operation
NW154146 Support for VMware View in NMC
NW154147 Display hierarchy and the association with policy and VMware Backup Appliance in NMC
NW154193 Port nsrvim binary to Linux
NW154197 Set couple default values for the generic Client resource created for the cluster environment in NMC Client Configuration wizard
NW154227 Retrieve hypervisor statistics information using dispatcher
NW154269 Add API call to libnsrvba which will return clients of a given backup job NW154542 Adding support for nsrdisp_dd.exe in NetWorker install
NW154597 Support parallel save streams for DR and ALL workflow NW154602 Increase multi-threading
NW154664 Add NAS device backup client support to the NMC Client Configuration wizard NW154695 Provide new dispatcher APIs to update container-policy relations.
Table 4 Fixed in NetWorker release 8.2 (continued) Issue Number Description
NW154843 New NMC reporting for Snapshot save set
NW154896 Lockbox support should be separated from LDAP_AUTH feature
NW155019 Automate recover operation for disaster recovery of VMware Backup Appliance NW155047 Add hostname and retry options to nsrpolicy to support ad-hoc backups from
vCenter plug-in to run the complete policy
NW155062 Add NAS device support to the NMC Devices window
NW155065 Drop support for Windows XP and Windows 2003 NMC Clients NW155165 Recovery log files should be explicitly flushed
NW155191 Add VMware Backup Appliance save type to the action resource
NW155232 Image-level recovery directly from tape devices without involving Cloning to Disk device
NW155233 Allow callers to select a NetWorker server to use; fix threadpool performance issue
NW155279 Drop Windows server 2003 and Windows XP support for NetWorker NW155293 Enhance libnsrvba to support enabling/disabling of internal VBA proxies NW155300 Enhance libnsrvba to support checkpoint rollback of a VBA
NW155304 Enhance libnsrvba to support disabling/enabling adhoc backups on VBA NW155306 Enhance libnsrvba to support enable/disable of NBD Fallback mode NW155320 Drop NTFS Journaling Support
NW155335 Enhance libnsrvba to provide an interface to the VBA which will cause the VBA to re-register with NetWorker
NW155340 NMC Client wizard support for NAS device client
NW155376 Change getPolicy to return a type as part of the NW websvc NW155400 Remove nsrvim.exe binary from nt86 packaging
NW155457 Add change expiration function and Save sets management feature to NMC NW155496 NMC Save set Query failed receiving NAS Snapshot save sets
NW155631 NMC updates for Simplified Storage Node Selection NW155637 Man page update for simplified storage node selection
NW155769 Add nwserver as input for checkpoint save set query and also return the most recent save set times of the checkpoint backups
NW155829 Move Dedicated Storage node attribute in NMC to storage node properties from device properties
NW155932 Support two new APIs for VBA checkpoint recovery
Table 4 Fixed in NetWorker release 8.2 (continued) Issue Number Description
NW156371 Add libnsrvba.dll to client packaging
NW156442 Incorporate automated rollback operation for disaster recovery of VMware Backup Appliance
NW156815 Add support for pre-NetWorker 8.2 VMware Backup Appliance NW157129 Provide SMT support in Device wizard
NW159535 Client Configuration wizard text changes. NW159918 Add warning message for sudel command NW146411 Remove IRIX (sgi) support from NetWorker
NW150143 Duplicate hexadecimal conversion functions (hex2bin & bin2hex) need to be refactored into common functions
NW150373 Add the Oracle T10KD drive
NW152097 Add logging ability to VSS common requester library NW153331 Add ability to print log messages on stdout
NW153836 Allow parallel save stream attribute to be set for Windows Clients in NMC NW153838 Support parallel save stream backups for volumes and directories on Windows
Clients where VSS is off
NW153839 Support parallel save stream backups for VSS enabled volume and directory backups for Windows
NW154195 Remove all ifdef-MBS_USE_STDIO code from VSS/MBS/PSS code NW154595 Honor VSS directives for PSS/MBS backups
NW154776 Streamline mbs.x file so that the UNIX/Linux and Windows mbs.x code collapse into one unit
NW154926 Support BMR for parallel save stream disaster recovery backups
Environment and system requirements
This section describes specific environment and system requirements.
System configuration requirements for a dedicated NetWorker server
The tables below outline the following:
l Minimum system configuration requirements to be met when running the NetWorker
software on a dedicated NetWorker server.
l Tips when setting parameters at the operating system level.
Table 5 Minimum system requirements for a dedicated NetWorker server Minimum recommended configuration
CPU Dual Core with a minimum of 1.5 GHz speed for each CPU
RAM 2 GB
Swap space 4 GB minimum (at least twice RAM)
Table 6 Minimum system requirements for a dedicated NetWorker server Minimum recommended configuration
Kernel parameters The following plimit values for all NetWorker daemons should be set to maximum as follows:
Resource Current Maximum
Time Unlimited Unlimited
file(blocks) Unlimited Unlimited
data(Kbytes) Unlimited Unlimited
stack(Kbytes) 8192 Unlimited
coredump(blocks) Unlimited Unlimited
nofiles(descriptors) 65536 65536
vmemory(Kbytes) Unlimited Unlimited
The EMC NetWorker Performance Optimization Planning Guide provides information on tuning the operating system and is available at https://support.emc.com/.
Write access to temp folders required when using the NetWorker Software
Administration wizard or nsrpush CLI for a Windows 2008 client
Microsoft Windows 2008 restricts write access to temp folders, including the folders defined in the Windows SYSTEM user's TEMP or TMP environment variable. Write permissions must be enabled when performing software updates, add to repository operations, and inventory operations using the Software Administration wizard or the nsrpush CLI.
On the Windows 2008 client, grant the Administrator and SYSTEM users write permissions to the temp folders defined in the SYSTEM user's TEMP and TMP environment variables.
QPK1123 and PHSS_37492 patches required to run NetWorker on HP-UX RISC 11.23
The NetWorker services cannot be started on an HP-UX RISC 11.23 system until the following patches are downloaded from the HP website:
l QPK1123(B.11.23.0712.070a) 1185010 Quality Pack Depot l PHSS_37492
Go to http://itrc.hp.com and click patch database to obtain these patches. You must provide an appropriate username and login password to download the patches.
Linux st kernel max devices default configuration
By default, the Linux st kernel configures a maximum of 128 SCSI tape devices. As a result, the inquire command and the Scan for Devices operation might not detect more than 128 tape devices.
To resolve this issue, the st module of the Linux kernel must be modified and recompiled to increase the maximum number of allowable st devices created by the operating system to exceed the default value. Refer to Linux documentation for details about how to reconfigure, rebuild, and install the kernel.
Features provided with base enablers
The following table lists the features that are available as part of NetWorker base enablers.
Table 7 Features provided with base enablers
Feature Support by edition
Power Network Workgroup Business
Number of included client connections 12 10 8 8
Parallel data streams per NetWorker server 64 32 32 32
Parallel datastreams per storage node 64 32 N/A N/A
Number of physical devices included with base enabler
32 16 4 4
Increase in datazone's devices, per storage node license1
32 16 N/A N/A
Maximum number of devices 512 512 4 4
Table 7 Features provided with base enablers
1) Storage nodes available for additional cost for the Power and Network Editions only.
Additional features available with base enablers
The following table lists the features that are available for support with NetWorker base enablers.
Table 8 Additional features available with base enablers
Feature Support by edition
Power Network Workgroup Business
Additional client connections
Yes Yes No No
Table 8 Additional features available with base enablers (continued)
Feature Support by edition
Power Network Workgroup Business
NetWorker NDMP Client connections
Yes Yes No Maximum 2 NDMP
client connections Dynamic Drive Sharing
option
Yes Yes N/A N/A
NetWorker DiskBackup option
Yes Yes Yes Yes
NetWorker Archive Module Yes Yes No No
Autochanger Software Modules All All 1-9, 1-16, 1-20, 1-32 One 1-26 included in base NetWorker Application Modules
Yes Yes Yes Yes
Open File Manager Yes Yes Yes Yes
NetWorker PowerSnap Modules
Yes Yes No No
NetWorker SnapImage Module
Yes Yes No Yes
VSS Support for Windows 2003
Yes Yes Yes Yes
Simple Network Management Protocol (SNMP)
Yes Yes Yes Yes
VTL (Virtual Tape Library) Yes Yes Yes Yes
Known problems and limitations
This section describes known limitations found in the entire NetWorker family of releases:
l NetWorker 8.2 SP1 known limitations on page 23 l NetWorker 8.2 known limitations on page 27 l NetWorker 8.1 SP1 on page 36
l NetWorker 8.1 on page 46
l NetWorker 8.0 Service Pack releases on page 68 l NetWorker 8.0 on page 73
l Limitations previous to NetWorker 8.0 on page 81
Unless the entry for a known limitation indicates that it is resolved for a specific release, the limitation applies to the release in which it is identified and all subsequent releases. If a limitation is resolved, it will also be identified in the fixed bugs table for the release in
NetWorker 8.2 SP1 known limitations
The following table identifies issues and limitations discovered in NetWorker 8.2 SP1. These limitations may also apply to previous releases.
Table 9 Limitations discovered in NetWorker release 8.2 Issue
number Description of limitation Operatingsystem affected
Product feature
232125 (ETA 203433)
VMs may get removed from VMware Protection Policies
Backup 231480 (ETA
203433)
File Level Recovery (FLR) may not complete for VMs with large numbers of files on their disks, resulting in data unavailability
Recovery
ETA 196089 Recovery issue may cause deletion of original file during attempted restore of file copy to the same destination
All Recovery
226760 Save sets backed up manually are not visible during a block based backup clone recovery from tape
All CLI
224948 Successfully validated integrity check may display as "failed' in the Recent tasks pane of the vSphere Web Client
Linux GUI
224308, 224564
Instant Access and VMDK-level restore options not available after restore from a secondary VMware Backup appliance.
Linux Restore
207251 FULLVM Resurrection from AFTD and tape devices fails when the source Data Domain device is on a remote storage node
Linux Restore
204285 NetWorker installation file setup.exe does not work when you select Save instead of Run in the Windows File Download dialog
Windows Installation
200765 Intermittent backup failures when target device is Atmos Cloud device
Linux Devices and
media 200743 Changetime command fails when performing
recovery in interactive mode as a non-root user
Solaris CLI
200630 NMC's Recovery wizard cannot be used to recover files mounted within a file system that are marked for recovery
Solaris GUI
199645 Cloud device creation using secure https fails if the first certificate is invalid
Linux Devices and
media 199644 After modifying an existing cloud device with
an invalid certificate you cannot correct the certificate
Table 9 Limitations discovered in NetWorker release 8.2 (continued) Issue
number Description of limitation Operatingsystem affected
Product feature
184667 Synthetic full backup fails when rehydrated save sets occur one second apart
Linux Configuration
VMs may get removed from VMware Protection Policies
232125 (ETA 203433)During normal operations, a VMware Backup Appliance may periodically re-synchronize its list of VMs with the list of VMs in vCenter to clean up deleted VMs. During this synchronization, if lookup of a VM in vCenter does not complete (for example, due to a timeout), the VM may be removed from the VMware protection policy, leaving the VM unprotected and potentially resulting in data loss. When this issue occurs, no actual error appears. Instead, the count of protected VMs decreases when checked in NMC or the EMC Backup and Recovery user interface in the vSphere Web Client, and the log files show VMs removed from the VMware Protection Policies.
This issue occurs for the following VMware Backup Appliance OVA versions:
l 1.1.0.149 l 1.1.1.41 l 1.1.1.46 Workaround
You can avoid this issue by upgrading to the latest OVA version for the NetWorker 8.2 SP1 VMware Backup Appliance, which is currently OVA 1.1.1.50.
The knowledgebase article 203433, available at http://support.emc.com/kb/203433, provides more information.
File Level Recovery (FLR) may not complete for VMs with large numbers of files on their disks,
resulting in data unavailability
231480 (ETA 203433)
When you perform FLR from the EMC Data Protection Restore Client for the VMware Backup Appliance, FLR may not complete when the VMs contain a large numbers of files on their disks, due to the built-in timeout for browse operations. This may result in data unavailability. This issue occurs for the following VMware Backup Appliance OVA versions:
l 1.1.0.149 l 1.1.1.41 l 1.1.1.46 Workaround
You can avoid this issue by upgrading to the latest OVA version for the NetWorker 8.2 SP1 VMware Backup Appliance, which is currently OVA 1.1.1.50.
The knowledgebase article 203433, available at http://support.emc.com/kb/203433, provides more information, including errors you may encounter when this issue occurs.
Recovery issue may cause deletion of original file during attempted restore of file copy to the same
destination
ETA 196089
An issue may occur during recovery where a file copy cannot be restored, resulting in the original version of the file being deleted without prompting for a rename of the file. This occurs only if the original file exists in the same location as the recovery destination and the recovery fails.
Note
This does not occur when you redirect the recovery to a different system, relocate the file to a different location on the same host, or rename the original file before the recovery. Affected NetWorker versions include the following releases:
l NetWorker 8.0 releases up to 8.0.4.1 l NetWorker 8.1 releases up to 8.1.2.2 l NetWorker 8.2 releases up to 8.2.0.4 l NetWorker 8.2 SP1
Workaround
To address this issue, upgrade the NetWorker client software to the following versions:
l NetWorker 8.0.4.2 and later l NetWorker 8.1.2.3 and later l NetWorker 8.2.0.5 and later l NetWorker 8.2.1.1 and later
The knowledgebase article 196089, available at http://support.emc.com, provides more information.
Save sets backed up manually are not visible during a block based backup clone recovery from
tape
226760
When you attempt a block based backup (BBB) clone recovery from tape, save sets that you backed up manually will not be visible.
If you perform a scheduled backup, the cloned BBB save sets display correctly and you can select them for recovery.
Successfully validated integrity check may display as "failed' in the Recent tasks pane of the
vSphere Web Client
224948
An integrity check of the VMware Backup appliance may display as "failed" in the Recent tasks pane of the vSphere Web Client. You can verify whether the checkpoint was successfully validated in the EMC Backup and Recovery Configure window.
Instant Access and VMDK-level restore options not available after restore from a secondary VMware
Backup appliance
alternative to restore the data.
The knowledgebase article 196887, available at http://support.emc.com, provides more details.
FULLVM Resurrection from AFTD and tape devices fails when the source Data Domain device is on a
remote storage node
207251
Performing resurrection of a FULLVM backup from an AFTD or tape device requires a local Data Domain device on the NetWorker server. If you attempt a resurrection from AFTD or tape with the Data Domain device on a remote storage node, resurrection fails.
NetWorker installation file setup.exe does not work when you select Save instead of Run in the
Windows File Download dialog
204285
When you launch autorun.htm and click on the link to install NetWorker, the Windows File Download dialog prompts you to either save or run setup.exe. Always click Run in this dialog. When you save setup.exe to any location other than the original download
location, an error appears that prevents you from installing.
Intermittent backup failures when target device is Atmos Cloud device
200765Intermittent backup failures may occur with the following errors when the target device is an Atmos Cloud device:
Server returned nothing (no headers, no data) Couldn't resolve host name
Workaround
Increase the values of the Cloud device resource attributes send/receive timeout and number of retries.
Changetime command fails when performing recovery in interactive mode as a non-root user
200743When you perform a recovery in interactive mode as a non-root user, running the
changetime command fails if the current directory is a Z file system (ZFS) that does not match the save set name.
Workaround
In a command prompt, cd to the directory that matches the save set name, and then run the changetime command. You can then cd to the desired directory to mark files for recovery.
NMC's Recovery wizard cannot be used to recover files mounted within a file system that are
marked for recovery
200630
Files mounted within a file system that are marked for recovery cannot be recovered using NMC's Recovery wizard.
command or nwrecover.
Cloud device creation using secure https fails if the first certificate is invalid
199645When you create a cloud device using secure https, by default the nsrssltrust utility adds 3 certificates from the Atmos server to the device attribute Cloud CA certificate. However, NetWorker only uses the first certificate to verify the cloud device credentials. If the first certificate is invalid, NetWorker ignores the 2nd and 3rd certificates, and cloud device creation fails.
After modifying an existing cloud device with an invalid certificate you cannot correct the certificate
199644If you modify an existing cloud device with an invalid certificate, an error displays and you cannot update the device to correct the certificate.
Workaround
You must create a new cloud device with the same Atmos account, and ensure that you do not label the device or add a certificate. You can then delete the old cloud device and mount the volume to the new device.
Synthetic full backup fails when rehydrated save sets occur one second apart
184667The save time is the value in the save set record which represents the approximate time the backup occurred. When you create Avamar save sets, NetWorker reserves the next save time (the save time of the Avamar save set, plus one second) for rehydrated save sets. So, for example, if multiple rehydrated save sets get created from the same Avamar save set with a save time t1, t1+1 and t1+2 are used. If you subsequently attempt to create a synthetic full backup with this Avamar save set as the newest save set, the save times t1+1 and t1+2 are already reserved and, as a result, the synthetic full backup fails. To avoid this issue, do not rehydrate the newest incremental Avamar save set if you plan to use this save set to create the synthetic full backup.
NetWorker 8.2 known limitations
The following table identifies issues and limitations discovered in NetWorker 8.2.
Table 10 Limitations discovered in NetWorker release 8.2 Issue
number Description of limitation Operatingsystem affected
Product feature KB 192005 Non-optimized backups required for Windows
Server 2012 due to Microsoft potential data loss issue
Windows Backup
54219 No proper error message sent to user when Data Domain system reaches MTree limit
All Messaging
Table 10 Limitations discovered in NetWorker release 8.2 (continued) Issue
number Description of limitation Operatingsystem affected
Product feature 200234 Cross-sync does not occur automatically upon
disaster recovery of the VMware Backup appliance after an upgrade
All Upgrading
199170 Avamar-MOD datastore remains visible in vSphere Web Client's EMC Backup and Recovery user interface after instant access restore
Linux GUI
194661 RPC operation error displays when opening Recovery wizard after client system reboot
Windows Messaging 194464 VM backups fail with error when destination
pool contains fibre channel enabled Data Domain devices, or when external proxy has DNS issues with NetWorker server
All Backup
193737 VMware Protection Policy when stopped from NMC shows status of "Succeeded" instead of "Interrupted"
All GUI
191693 No message displays when you add a VM from an unsupported appliance to a VMware Protection Policy in NMC’s VMware View
All Messaging
189048 Client push upgrade fails when media path contains special characters
Windows Upgrading 186534 Data Domain device may not be visible to
restricted data zone user in NMC Enterprise view if the device is not added to the user’s permissions
All Security
186372 Performance of the block based backups reduces when you use the NFS protocol
Windows Block based backup 185858 Map view not available in NMC’s VMware View
when configuration for one or more VMs is incomplete
All GUI
185641 VMware Protection policy reports backup as “interrupted” in NMC and provides no
additional information when transport mode is restricted to hotadd and backup fails to meet hotadd criteria
All Messaging
185566 Incremental synthetic full backups to NetWorker File System succeed but the NMC save group completion report indicates that backups failed
All Block based
backup
185515 nsrsnapadmin reporting error message incorrectly appears during point-in-time save
Table 10 Limitations discovered in NetWorker release 8.2 (continued) Issue
number Description of limitation Operatingsystem affected
Product feature 184803 Performance of the block based File Level
Recovery is lower than the traditional NetWorker recovery
All Block based
backup NW161099 Backup and restore of powered off VM using
NetWorker VMware Protection does not work if one of the ESX clusters is in stand-by mode
All Backup
NW159203 Directed restore of NSM backup in NMC Recovery wizard incorrectly allows selection of drive that snapshot is mounted on
All GUI
NW158956 Appropriate error message does not display when you use a pre-NetWorker 8.2 VMware Backup Appliance with Networker 8.2
All Messaging
NW158170 NetWorker tasks that a userid has permission to run may fail if the user belongs to a large number of groups
Linux, Solaris Configuration
NW157710 GSTD daemon may core or become
unresponsive when logging in to NMC server on AIX
AIX Performance
NW156896 Restricted data zone savegroups hang when directing save sets to a custom pool associated with the restricted data zone
All Backup
NW156063 Unable to use the save set recovery method for a Windows PSS save point
Windows Recovery NW153845 Running nsrpolicy fails when using a VMware
Protection policy from a different NetWorker server
All CLI
Non-optimized backups required for Windows Server 2012 due to Microsoft potential data loss
issue
Knowledgebase article 192005
A defect with Windows Server 2012 introduces a potential for data loss when restoring individual files from a Windows deduplication volume backup. The issue is fixed for backups on Windows Server 2012 R2, but affected files backed up on Windows Server 2012 are still not recoverable.
The issue occurs when a re-optimization session processes clean ranges and does not update the ChunkBodySize field of the stream map entry in the SM chunk, leaving the value at 0. During the restore, the read plan is built taking into account the
ChunkBodySize, and because the ChunkBodySize from the read plan is 0, a mismatch occurs against the actual data container. This only affects files that were partially recalled and then re-optimized. Even if you upgrade to Windows Server 2012 R2, although the
Workaround
Configure non-optimized backups for new and existing Windows Server 2012 NetWorker clients. For each client with Windows deduplication volumes, add the string
VSS:NSR_DEDUP_NON_OPTIMIZED=yes to the Save Operations text box, located under the Apps & Modules tab in the NMC Client Properties window. When you set this flag, non-optimized backups will be performed for all Windows deduplication volumes, and will be recoverable.
The knowledgebase article, available at https://support.emc.com/, provides more information.
No proper error message sent to user when Data Domain system reaches MTree limit
54219When the Data Domain system reaches the MTree limit, no proper error message is sent to the user to indicate there is insufficient space. Instead, messages similar to the following display:
nsrdisp_nwbg NSR critical Could not add Data Domainhost <DD Name> to <VBA Name>, error: VBA returned status of FAILURE: details
"NW_1005:An error occurred adding DDR <DD Name>.
E30937:Description: Failed to add Data Domain system. Data: null Remedy: No action required. Domain: Publish Time: 0 Severity:
PROCESS Source Software: MCS:DPN::PS::ADD Summary: Failed to add Data Domain system. Type: AUDIT".
Check to ensure that the Data Domain system does not reach the MTree limit.
Restore to a new VM fails if two or more VMs on the same datastore share the same name but have
different SCSI controller configurations
200499
When you attempt to restore to a new VM that did not previously exist within the vCenter, and that VM shares the same name but a different SCSI controller configuration as another VM on the same datastore, the restore fails.
Workaround
Manually create a new VM in vCenter with the same SCSI configuration as the VM in the backup, and then restore to that VM.
Cross-sync does not occur automatically upon disaster recovery of the VMware Backup appliance
after an upgrade
200234
When you perform a disaster recovery of the VMware Backup appliance after upgrading from NetWorker 8.1 SP1 and OVA 1.0.1.9 to NetWorker 8.2 and OVA 1.1.0.148, cross-sync does not occur automatically. You must perform cross-cross-sync manually by using the following command on the NetWorker server:
nsrim -X -S -h <VMware Backup appliance>
Avamar-MOD datastore remains visible in vSphere Web Client's EMC Backup and Recovery user
interface after instant access restore
199170
Backup and Recovery user interface.
Workaround
To remove the Avamar_MOD datastore, you must also unmount the datastore within the EMC Backup and Recovery user interface.
RPC operation error displays when opening Recovery Configuration wizard after client system
reboot
194661
After performing a recovery of a save set that requires a client system reboot (for example, the Windows Roles and Features save set), when you restart the Recovery Configuration wizard and select the source client as the same client just used for recovery, an RPC operation error displays. This error will not appear when you close and re-open the wizard.
VM Backups fail with error when destination pool contains fibre channel enabled Data Domain
Devices or when external proxy has DNS issues with NetWorker server
194464
VM backups fail with a message similar to the following when the destination pool contains Data Domain devices configured with fibre channel connectivity, which the NetWorker VMware protection solution does not support in NetWorker 8.1.x and 8.2 releases:
NetWorker server returned an empty DDR export path.
This issue can also occur for external proxy based backups due to DNS issues with the NetWorker server.
The knowledgebase article 189499 available at https://support.emc.com provides more information, including steps on how to check the Device Properties of the Data Domain devices within the pool to determine if the devices are fibre channel enabled, and how to disable fibre channel connectivity where required.
VMware Protection Policy when stopped from NMC shows status of "Succeeded" instead of
"interrupted"
193737
When you stop a VMware Protection Policy backup in progress from NMC, the top of the VMware Protection Policy Details window incorrectly displays the status as "Succeeded" instead of "interrupted".
The Log pane in the NMC Monitoring window and the log reports show the correct status, and the bottom pane of the Policy details window also correctly shows the policy as failed with the message "cancelled by user."
No message displays when you add a VM from an unsupported appliance to a VMware Protection
Policy in NMC’s VMware View
191693
If you add a VM from an unsupported appliance to a VMware Protection Policy in NMC’s VMware View, no message displays indicating that the VM is not supported and has not been added to the policy. Also, the Properties panel incorrectly shows that the VM is now
Client push upgrade fails when media path contains special characters
189048Performing a client push upgrade fails when the media path name contains a space or any of the following special characters:
( ‘ , )
Ensure that the media path does not use any of these special characters before you run a client push.
Data Domain device may not be visible to restricted data zone user in NMC Enterprise view if the
device is not added to the user’s permissions
186534
When a Data Domain device has not been added to a restricted data zone user’s
permissions, the device will not appear to this user in the NMC Enterprise view. If the user then attempts to create this Data Domain device in the NMC Device wizard, device creation fails with the error “Host name already exists, but no permission to access host.”
Workaround
If the restricted data zone user requires Data Domain device permissions, a NetWorker administrator must add these permissions in NMC under Setup > Users.
Performance of the block based backups reduces when you use the NFS protocol
186372When you perform the block based backups on Windows 2012 client with a non-Windows NFS Data Domain device as a remote storage node, the performance of the backups reduces.
Map view does not appear in NMC’s VMware View when configuration for one or more VMs is
incomplete
185858
When using NMC’s VMware View, the map view does not appear when the configuration for one or more VMs in the vCenter is incomplete. To avoid this issue, remove incomplete VM configurations from vCenter.
VMware Protection policy reports backup as “interrupted” in NMC and provides no additional
information when transport mode is restricted to Hotadd and backup fails to meet Hotadd criteria
185641
When you enable VBA Restrict Transport Mode to Hotadd Only in NMC for the VMware Backup appliance, backups will fail for any VM that does not meet the Hotadd criteria as outlined in the VMware knowledgebase article 2048138. When such a failure occurs, the VMware Protection policy only reports that the backup was “Interrupted.” The correct status displays when you run the following command:
9139905687058209 No Eligible Proxies 0 2014-05-03 00:24 IST 00h:00m: 00s 2014-05-03 00:24 IST On-Demand Backup 0 bytes 0% VM-Local
Incremental synthetic full backups to NetWorker File System succeed but the NMC save group
completion report indicates that backups failed
185566
When you perform the block based incremental synthetic full backups to a NetWorker File System (NFS) device, the backups succeed, but the NMC save group completion report incorrectly indicates that the backups failed.
nsrsnapadmin reporting error message incorrectly appears during point-in-time save set restore
185515The following nsrsnapadmin reporting error message incorrectly appears during a point-in-time (PIT) save set restore:
nsrsnap_recover: Unable to determine jobd version, assuming version 7.3: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
The message does not affect the restore and can be ignored.
Performance of the block based File Level Recovery is lower than the traditional NetWorker recovery
184803Performance of the block based File Level Recovery from a Data Domain device is lower than the traditional NetWorker recovery.
Workaround
Perform the recovery by using the Common Internet File System (CIFS) share.
Backup and restore of powered off VM does not work if one of the ESX clusters is in stand-by mode
NW161099When you perform a backup and restore of a powered off VM, the operation does not work if one of the ESX cluster members is in stand-by mode.
The VMware knowledgebase article 1019286, available at http://kb.vmware.com/ selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1019286, provides more information.
Directed restore of NSM backup in NMC Recovery wizard incorrectly allows selection of drive that
snapshot is mounted on
NW159203
When you use the NMC Recovery wizard to perform a directed restore of a NSM backup and select the mount host as the destination host, NMC incorrectly allows you to select the drive letter that the snapshot is mounted on. This is due to the snapshot being mounted before the destination is selected.
Appropriate error message does not display when you use a pre-NetWorker 8.2 VMware Backup
Appliance with NetWorker 8.2
NW158956
An appropriate error message does not display to indicate t