CU00610B Configurar Java en Windows Variables Entorno Java - Home y Path

Release Notes
EMC® Avamar®
Release number 7.1
Release Notes
302-000-836
10
October, 2015
These release notes contain supplemental information about EMC Avamar release 7.1.
Topics include:
l Revision history......................................................................................................... 2
l Product description....................................................................................................3
l New features and changes......................................................................................... 3
l Security updates........................................................................................................ 8
l Fixed problems.......................................................................................................... 9
l Environment and system requirements.................................................................... 34
l Known problems and limitations..............................................................................35
l International language support................................................................................ 50
l Technical notes........................................................................................................54
l Documentation........................................................................................................ 60
l Installation.............................................................................................................. 66
l Troubleshooting and getting help.............................................................................69
Release Notes
Revision history
The following table presents the revision history of this document.
Table 1 Revision history
Revision Date Description

10 October 28, l Added snapshot_max_change_percent flag on page 8
2015
09 July 21, 2015 l Added fixed bugs for the SP2 release to Fixed problems on page 9.
08 June 15, 2015 l Updated all references to supported Data Domain operating system version to 5.4.1.1.
07 May 5, 2015 l Added Avamar Downloader Service feature changes to Documentation errata on page 62, and
a workaround regarding Microsoft Office XML file restores to the Windows client area of Avamar
Virtual Edition known problems and limitations on page 37.
06 March 25, 2015 l Added fixed bugs for the SP1 refresh build 145 release to Fixed problems on page 9.
l Updated Avamar Virtual Edition known problems and limitations on page 37.
05 January 20, l Added fixed bugs for the SP1 release to Fixed problems on page 9.
2015
l Added information about uninstalling a cluster client in IBM Lotus Domino plug-in known
problems and limitations on page 40.
l Updated New features and changes for the Avamar 7.1 SP1 release on page 7.
04 December 15, l Added RHEL7 and Ubuntu 14.04 support to New features and changes for the Avamar 7.1 GA
2014 release on page 7.
l Added New features and changes for the Avamar 7.1 SP1 release on page 7.
l Updated the client/server support information in Microsoft Windows features and
enhancements on page 5.
l Added fixed bugs for the SP1 release to Fixed problems on page 9.
l Updated Known problems and limitations on page 35.
03 September 18, l Added details on the new vCloud Director plug-in in VMware features and changes on page
2014 6.
l Added information on default security hardening and firewall packages installed with Avamar
7.1 in Security updates on page 8.
l Added fixed bugs for the GA release to Fixed problems on page 9.
l Updated Known problems and limitations on page 35.
l Changed the number of concurrent connections from 80 to 72 in Maximum number of
concurrent connections for each storage node on page 54.
l Removed the Avamar Administration Guide item regarding the outbound rule to unblock port 22
on Windows 7 computers from Documentation errata on page 62. This issue has been
corrected in the Avamar Administration Guide.
02 July 2, 2014 l Updated supported client operating systems in Client, server, and platform compatibility on
page 34.
2 EMC Avamar 7.1 Release Notes

Release Notes
Table 1 Revision history (continued)
Revision Date Description
l Added Avamar Data Store Gen4x performance expectations on page 55.

l Added information on Data Domain system upgrade requirements and required Microsoft
updates for Avamar and Hyper-V on CSV in Upgrade requirements for Avamar 7.1 on page 66.
01 June 18, 2014 Initial release of Avamar 7.1.
Product description
EMC® Avamar® is backup and recovery software with integrated data deduplication
technology. Avamar solves the challenges associated with traditional backup, enabling
fast, reliable backup and recovery for remote offices, VMware® environments, and data
center LANs. Unlike traditional solutions, Avamar reduces the size of backup data at the
source — before it transfers across the network and stores to disk. As a result, Avamar
delivers fast, efficient daily full backups despite slow or congested infrastructure, and
data encryption for added security. Avamar uses patented RAIN technology for high
availability, and a scalable grid architecture enables you to upgrade capacity and
performance when necessary.
New features and changes

The following topics provide details on the new features and changes in Avamar 7.1 for
each product component.
NOTICE
If you are upgrading to Avamar 7.1 from an earlier release to take advantage of new
features and changes, review the information in Upgrade requirements for Avamar 7.1 on
page 66 before the upgrade.
New features and changes for the Avamar 7.1 DA release

The following topics provide details on the new features and changes that are available
starting with the DA release of Avamar 7.1.
Avamar server features and changes

The following sections list the new features and changes for the Avamar server in release
7.1.
Unencrypted backups require unblock of port 27000
The Avamar server firewall setting in release 7.1 blocks port 27000 by default, which
causes all unencrypted backups to fail. To enable unencrypted backups to continue,
manually unblock port 27000 on the Avamar server.
External key management for data-at-rest encryption keys
In this release you can manage data-at-rest encryption keys externally, as an alternative
to Avamar's existing internal key management. After you enable this feature, data-at-rest
®
encryption key management tasks are handled through your existing installation of RSA
Data Protection Manager.
Product description 3
Release Notes
New location for client log files on the Avamar server

Files generated by client process are now located in the /usr/local/avamar/var/
client directory on a single-node server or on the utility node of a multi-node server. In
earlier releases, the files were located in the /usr/local/avamar/var directory.
The change applies only to client log files on the Avamar server. The location for log files
on the client remains the same.
Removal of support for remote login as root
You can no longer log in to the Avamar server remotely as root. Instead, you must log in
remotely as admin and then switch user to root.
Avamar Extended Retention features and changes

Avamar Extended Retention 7.1 supports Avamar 7.1. When you use Avamar Extended
Retention 7.1, the Media Access node and all Avamar servers with backups to export to
tape must use version 7.1.
Data Domain system support

Avamar 7.1 supports version 5.4.1.1 of the Data® Domain® Operating System (DD OS).
In addition, Avamar support for Data Domain systems includes IPv6 support, network
throttling improvements, improved efficiency for restores, and support for encryption in
flight.
You can also specify the encryption method for data transfer between a client and a Data
Domain system by setting plug-in options during a backup or restore.
Backup clients features and changes

Avamar clients and plug-ins were updated in release 7.1 to include several new features
and enhancements.
Details on new and existing platform and environment support is available in the EMC
Avamar Compatibility and Interoperability Matrix on EMC Online Support at https://
support.EMC.com.
IBM DB2 features and changes

Release 7.1 of the Avamar Plug-in for DB2 supports restore and recover operations from
the DB2 Command Line Processor (CLP) for all database partitions at the same time.
IBM Lotus Domino features and changes

Release 7.1 of the Avamar Plug-in for Lotus Domino supports multi-stream restores from
either an Avamar server or a Data Domain system by using Avamar Administrator or the
CLI.
Microsoft Exchange VSS features and changes

The Avamar Plug-in for Exchange VSS supports multi-stream restore from a Data Domain
system for release 7.1.
Microsoft Hyper-V VSS features and changes

There are no significant new features or changes for the Avamar Plug-in for Hyper-V VSS
in release 7.1.

Release Notes
Microsoft SharePoint VSS features and changes

The Avamar Plug-in for SharePoint VSS includes the following new features and changes
for release 7.1:
l Support for multi-stream restore from a Data Domain system.
l Improved GLR process, where users can initiate GLR by using the GLR icon on the
Backup, Restore and Manage window in Avamar Administrator.
l Support for backup and restore of SharePoint databases on the primary replica in
SQL Server AlwaysOn availability groups.
Microsoft SQL Server features and changes

The Avamar Plug-in for SQL Server includes the following new features and changes for
release 7.1:
l Support for SQL Server 2014
l Support for Windows Server 2012 R2
l Support for storage of SQL Server databases and log files in a Windows Server 2012
R2 active/passive cluster on shared disks, clustered shared volumes (CSVs), and
shared virtual hard disk (VHDX) files. Shared VHDX files must be located on either a
CSV or on a Server Message Block (SMB) 3.0 file share.
l Backup option to skip log gap detection for transaction log (incremental) backups.
Log gap detection ensures that there is a valid chain of SQL Server transaction logs so
that point-in-time restore can occur, but log gap detection may require as many as 20
to 30 seconds to complete for each database. Transaction log backups may take an
excessive amount of time to complete in environments with a significant number of
databases.
If the performance issues outweigh the risk of possible log gaps, then you can
disable log gap detection by selecting the Skip log gap detection option in the
backup plug-in options to improve performance. You can also use the --skip-log-
gap-detection option in the avsql command line interface (CLI).
Microsoft Windows features and enhancements

The Avamar Client for Windows includes the following new features and changes for
release 7.1:
l Support for multi-stream restore from a Data Domain system.
l Support for Windows Server 2012 R2 and Windows 8.1. This includes support for the
following Microsoft applications running on Windows Server 2012 R2:
n SQL Server 2012
n SQL Server 2008 R2 SP2 or later
n SQL Server 2008 SP3 or later
n Exchange Server 2013 SP1 or later
n SharePoint Server 2013 SP1
n Hyper-V, including Cluster Shared Volumes (CSVs)
l Dropped support for Windows Server 2003 and Windows XP. For these operating
systems, use Avamar 6.x and 7.0.x clients and application plug-ins. The EMC Avamar
Compatibility and Interoperability Matrix on EMC Online Support provides details on
client/server compatibility requirements.
New features and changes for the Avamar 7.1 DA release 5

Release Notes
The Windows VSS plug-in for System State backups includes the following new features
and changes for release 7.1:
l Support for backup and restore of the "Work folders" role in Windows Server 2012 R2.
l Support for storing backups on a Data Domain system.
The Windows BMR process includes the following new features and changes for release
7.1:
l Support for physical to virtual (P2V) restores for Hyper-V and VMware.
l Support for WinPE 5 instead of WinPE 3 and WinPE 4.
l Dropped support for ESX 4.x.
NDMP Accelerator features and changes

The Avamar NDMP Accelerator includes the following new features and changes for
release 7.1:
l On-demand and scheduled backups of an entire Isilon® cluster to a Data Domain
system.
l Support for snapshot-based incremental backups in Isilon OneFS 7.1 and later.
l Support for recovering NetApp data to a Windows or Linux host file system.
l Support for include and exclude lists for NetApp backups.
l Support for running scripts during backups and restores.
Oracle features and changes

Release 7.1 of the Avamar Plug-in for Oracle supports the Oracle multisection backup
feature from the RMAN CLI.
SAP with Oracle features and changes

Release 7.1 of the Avamar Plug-in for SAP with Oracle includes the following new features
and changes:
l Support for Oracle operating system authentication for the database connection
during backup browse operations in Avamar Administrator.
l Support for BR*Tools secure storage password and role-based secure storage in
Avamar Administrator and the SAP plug-in CLI.
Sybase ASE features and changes

Release 7.1 of the Avamar Plug-in for Sybase ASE includes enhancements of the Sybase
backup behavior that keep the backups synchronized and prevent any data loss. The
Sybase plug-in now recognizes when an incremental backup of a Sybase database is
cancelled before its completion. The next incremental backup from a GUI or CLI of the
same database is promoted to a full backup.
VMware features and changes

The following sections list Avamar 7.1 features and changes for VMware backup, restore,
and integration.
VMware image backup and restore features and changes
Avamar for VMware image backup and restore includes the following new features and
changes for release 7.1:
l Improved multitenancy support for service providers.
l File-level restore now supports extended LVM partitions.

Release Notes
l Automated backup validation, which enables you to validate image backups on a

regular basis by using validation groups and schedules.
l Intelligent automated proxy selection for backup and restore operations, with the
ability to manually specify a proxy as needed.
l Support for running scripts during backups and restores.
l Support for mounting VMDKs from VMware image backups of Windows virtual
machines to support third party tools such as Kroll OnTrack PowerControls to perform
data mining and advanced data recovery.
New vCloud Director plug-in
Avamar 7.1 for vCloud Director is a new plug-in that brings Avamar-based data protection
to clouds built using vCloud Director. The plug-in allows vCloud Director system
administrators to manage backup, restore, and replication operations for cloud
organizations, Org VDCs, and vApps. It is targeted primarily at Service Providers, and can
also be used by enterprises using vCloud Director. Avamar 7.1 has embedded backup
services into vCloud Director so that they can be shared and distributed in a multi-tenant
model as a managed resource in vCloud Director. In addition, Avamar 7.1 has extended
the vCloud Director APIs with REST APIs that enable backup, restore, and monitoring,
allowing Service Providers to connect their portals directly to these services.
Discontinuation of Avamar Enterprise Manager

EMC intends to discontinue Avamar Enterprise Manager (EM) in future releases starting in
2015. EMC introduced a comparable but more robust tool that replaces EM called EMC
Backup and Recovery Manager (BRM). BRM provides centralized enterprise monitoring
capabilities for multiple EMC Avamar, NetWorker, and Data Domain systems in a single,
simple, easy-to-deploy virtual appliance application. BRM also has a mobile app for
Android and iOS tablets, job restart capabilities, and search and filtering capabilities. All
customers are encouraged to deploy BRM. The EMC Backup and Recovery Manager User
Guide, available on EMC Online Support, provides details.
The discontinuation of EM will not impact existing EM deployments up to and including
Avamar 7.1. Existing EM customers will continue to receive the same customer support
that they have been receiving based on their EMC Customer Support Agreement.
New features and changes for the Avamar 7.1 GA release

The following new features and changes are available starting with the GA release of
Avamar 7.1:
l IPv4/IPv6 dual stack support for backups that are stored on a Data Domain system.
l Update of the Data Domain Boost software to version 3.0.0.3 to address
incompatibility with DD OS 5.5.1.
l Support for NetApp cluster mode.
l Support for Red Hat Enterprise Linux (RHEL) 7.
Details on application plug-in support for RHEL7 are available in the EMC Avamar
Compatibility and Interoperability Matrix on EMC Online Support.
l Support for Ubuntu 14.04.
Backups of Ubuntu 14.04 must be stored on the Avamar server. Backup storage on a
Data Domain system is not supported in this release.
New features and changes for the Avamar 7.1 SP1 release
The following new features and changes are available starting with the SP1 release of
Avamar 7.1:
New features and changes for the Avamar 7.1 GA release 7

Release Notes
l Web servers on Avamar systems specify stronger default cipher suites

l Avamar Virtual Edition support on Microsoft Hyper-V Server and Microsoft Azure
l NDMP Accelerator support for NetApp clusters
l VMware file-level restore (FLR) support for FAT16 and FAT32 virtual disks
l New instructions for generating an Avamar server license key
l Supports VMware vSphere 6.0 including ESXi 6.0 with Avamar Data Store, Data
Domain OS 5.4.x, and Data Domain OS 5.5.x backup targets.
Note
A hotfix is required for this support. Contact EMC Tech Support for the hotfix. The
hotfix is not expected to be required for the next service pack of Avamar 7.1.
snapshot_max_change_percent flag
The "snapshot_max_change_percent" flag tells the proxy to pre-evaluate free datastore
space to ensure that there is enough storage for the VM snapshot. The default value is set
to 5%. If the proxy incorrectly fails the backup due to the perceived lack of storage, the
value can be overridden by either changing the percentage to "0" by the user of the
policy, or by permanently overriding the value in the proxy command file.
To permanently override this check in the proxy, log into each proxy, modify the file
"/usr/local/avamarclient/avvcbimageAll.cmd" to include the line:
-- snapshot_max_change_percent=0
This will disable this feature.
Security updates
The following sections discuss security updates in Avamar 7.1.
Avamar 7.1 security features
Installation of or upgrade to Avamar 7.1 software installs, by default, hardening and
firewall packages that improve security capabilities on the Avamar server. Installation of
these packages does not restrict supported server functionality, and the packages cannot
be uninstalled. In some cases, such as future upgrades, EMC Customer Support
personnel will provide the steps and tools to enable necessary procedures (for instance,
FTP capabilities for downloading packages to the server).
Security fixes
Avamar 7.1 contains security fixes for common vulnerabilities and exposures (CVEs)
based on security advisories from major operating system vendors.
The GNU C Library and associated internationalization files have been updated to resolve
the following vulnerabilities:
l CVE-2013-1914
l CVE-2012-3406
l CVE-2012-3405
l CVE-2011-2483
l CVE-2011-1089
l CVE-2009-5029

Release Notes
Fixed problems
This section provides details on fixed problems for Avamar 7.1.
Fixed problems for the Avamar 7.1 DA release

The following table lists fixed problems for the Avamar 7.1 DA release.
Table 2 Fixed problems for the Avamar 7.1 DA release
Issue Product feature Problem summary

number
54080 Administration guide DOCS: bug 52001-CLONE: bug 51998-Escalation 5883:Popup message has returned post
Hotfix 41951 but only on one of three Avamar Servers
54386 Administration guide DOCS: bug 54240-CLONE: bug 54239-Escalation 6515:Avamar 7.0 DA - Backups that
timeout do not show in MC GUI start-page
59949 Administration guide Escalation 7251:Need clarification on Solaris restore documentation
60890 Administration guide Escalation 7235:Documentation: LDAP Maps over SSL
61085 Avamar Client Manager CLONE: bug 61084-Escalation 7428 - Since upgrade to 7.0.1-61, Client Manager's "User
Name" query fails to complete when run under Server Summary pane.
50769 Avamar Desktop/ CLONE: bug 50766-Escalation 5931:DTLT browse shows no backups although there are
Laptop backups.
50964 Avamar Desktop/ CLONE: bug 50317-Escalation 6018:Avamar 7.0 Beta >> German Help Menu in English &
Laptop German
52001 Avamar Desktop/ CLONE: bug 51998-Escalation 5883:Popup message has returned post Hotfix 41951 but
Laptop only on one of three Avamar Servers
54680 Avamar Desktop/ CLONE: bug 54237-Escalation 6519:CVE-2013-2251 -Apache Struts 2.0.0 through 2.3.15
Laptop allows remote attackers to execute arbitrary OGNL expressions
56747 Avamar Desktop/ Escalation 6798:Application-Level Security Vulnerabilities

Laptop
58471 Avamar Desktop/ CLONE: bug 58469-Escalation 7029:Browse for redirecting a restore in DTLT shows SQL
Laptop instance as destination
59857 Avamar Desktop/ Escalation 7266:Web restore interface 'indexing' functionality - popup message does not
Laptop match the button selections offered to the user
60921 Avamar Desktop/ CLONE: bug 60920-Escalation 7381:DTLT Write in protect directory
Laptop
50065 Avamar Downloader Escalation 5978:ER: File adsinfo.txt does not contain enough information from the
Service Downloader Service
59041 Avamar Enterprise Escalation 6918:EM is not updating server status for days. Similar to Esc 6753
Manager
59241 Avamar Enterprise Escalation 7159:Missing required Permissions manifest attribute in main jar
Manager
186201 Avamar Installation Password security setting in Avamar Installation Manager fails to enforce password
Manager requirements during Avamar server installation
Fixed problems 9
Release Notes
Table 2 Fixed problems for the Avamar 7.1 DA release (continued)

number
22225 Avamar server Escalation 1773: Improvement on hfscheck requested to checking persistent datastripe
cxormismatch
26198 Avamar server Escalation 2436 - On indexstripe split child left with two parents
35260 Avamar server Escalation 3940:Avamar server reports Event Code 1: kernel error: Dec 21 02:53:46
svaksa69901m37 kernel: [5301943.941516] MaserInfo[28409]: segfault at 0 ip (null) sp
00000000ffef2e5c error 14 in MaserInfo[8048000+5f000]
37664 Avamar server RFE: Escalation 4456:Missing MC_BACKUPS & EM_BACKUPS between the maintenance
times and other times it works fine. Customer receiving the message
38241 Avamar server Escalation 4524:Avamar server goes readonly when single disk gets suspended
44281 Avamar server Escalation 5099:refcheck errors on node 0.3 after that node was restarted
47728 Avamar server CLONE: bug 39472-Escalation 4720:NAT configuration for 6.1
49356 Avamar server Escalation 5881: index caches stuck unloading if forced to unload during GC
49773 Avamar server Escalation 5458:Customer has reported several "Security Audit Vulnerabilities"
49992 Avamar server Escalation 5944:HFSCheck failed with MSG_ERR_TIMEOUT during waitcomplete phase
50409 Avamar server Escalation 6019:avsysreport Command Required to Identify Gen4S Node Types
50849 Avamar server Escalation 6048:The stripe in OFFLINE_MEDIA_ERROR on the single node Gen4 system
due to
50973 Avamar server Escalation 5982:Insecure permission errors when logrotate runs
50978 Avamar server Escalation 6080 - node offline caused HFSCheck issues - Add more debug info for write
locks
50980 Avamar server Escalation 6099 - node offline - [cprecovery:3163] FATAL ERROR: <0001> tabfile::read out
of range
51266 Avamar server Escalation 6129:Meaning of 'syncthread::commit timed-out waiting for map.commit()'
Error
51426 Avamar server Escalation 6110:RCA REQUEST | gsan deadlock
52388 Avamar server Escalation 6279:Avamar server in Admin Mode Due to removehashes
52515 Avamar server CLONE: bug 43202-Escalation 5066:Axionfs not updated in Proxy after restart Avamar
server
52619 Avamar server Escalation 6294:checkpoint::validate file error
52861 Avamar server CLONE: bug 51517-Escalation 6167: Avamar 7.0 Beta: Hash referenced but not defined
following concurrent backup + GC
53877 Avamar server CLONE: bug 53776-Escalation 6452:Degraded HFScheck performance after upgrade to
7.0.0-396 - we are checking ALL stripes during a rolling HFSCheck
54467 Avamar server Escalation 6463:userdatastripe::cmdMovGetLink Namelistrec is already marked for

'move in progress'
54650 Avamar server Escalation 6575 - Balancing an empty stripe causes tchunklist::init to be called twice
without unloading chunklist

Release Notes

number
54927 Avamar server Escalation 6535: checkpoint fails with MSG_ERR_TIMEOUT due to stripe stuck MIGRATING
55463 Avamar server Escalation 6688 - gsan should better account for free space during crunch operations
55528 Avamar server Escalation 6683 - catch various UNIX errors when attempting to devices that don't exist
using ioctl
56104 Avamar server Escalation 6703 - logscan doesn't work as expected in Avamar 7.0
57028 Avamar server Escalation 6820: RFE: Allow checkpoints to be locked similar to the "keep last backup"
functionality
57244 Avamar server Escalation 6790:2 cxor compare errors on 7.0.0-427 after stripes were balanced
27327 Avamar server Escalation 6870:Full hfscheck failed on single node 3.3TB
57387 Avamar server Escalation 6868: maintenance window skipped due to failed negotiation
57486 Avamar server Escalation 6909: hfscheck did not report errors in a stripe, preventing it from being auto-
repaired
57498 Avamar server Escalation 6879 - improved syncing behavior when recovering from offline node
situations
57700 Avamar server Escalation 6923:RCA multiple nodes offline
57739 Avamar server Escalation 6926:Hfscheck fails with MSG_ERR_TIMEOUT due to thread exhaustion
58185 Avamar server Escalation 6799:hotspot on stripe 0.0-1551 causing degraded performance performance
on a replication target
58340 Avamar server Escalation 6971:failure to start DTLT web interface from Linux client to perform restore
58478 Avamar server Escalation 7073 - reset parent index stripe split state if we fail to create child index stripe
during splitting
58759 Avamar server Escalation 7021:Multiple nodes throwing "diskinfo::update invalid disk space
parameters" errors never having run Avamar 7.0 DA
59089 Avamar server Escalation 6993: refcheck errors when user accounting block splits during GC refcount
59292 Avamar server Escalation 7124 - "workertask::run caught uexception tcp timeout exception" errors are
reported as critical events in v7.0 administrator console dashboard
186879 Avamar server CLONE: bug 186630-Escalation 7465:Re-occurrence of messages "invalid disk space
parameter" described in Esc 7021 and 7315 after hotfix 59848 is applied
187739 Avamar server Escalation 7518 - gsan should protect itself from invalid XML
188350 Avamar server ESC 7548: Improve NetApp dirmap conversion to reduce update time
189622 Avamar server Escalation 7639 - invalid connection reference used with killwaiter when attempting to
force close stalled connection
25776 Client Escalation 2338:backup tries to follow symlink folder and cannot back up open files
45972 Client Escalation 5430:RFE:brbackup is putting ALL tablespaces in hot backup mode when
using -d util_file_online
49065 Client Escalation 5786:SQL transaction Log backups randomly fail with 'Dropped Session'
Fixed problems for the Avamar 7.1 DA release 11

Release Notes

number
50362 Client Escalation 5991:Cannot restore Win files if it is long file name and there is a file which
has same MS-DOS file name.
50533 Client Escalation 5843:avtar command hanging and causing AER node to hang ( cpus usage
going ot 99% )
50865 Client Escalation 6055:Avamar does not preserve attributes timestamp with milliseconds
precision
51242 Client CLONE: bug 50786-Escalation 6036: (Avamar 7.0 Beta) During the restore no progress
bytes reported
51481 Client CLONE: bug 49607-Escalation 5786:SQL transaction log backups randomly fail with
'Dropped Session'
51606 Client CLONE: bug 50145-Escalation 4955:HP-UX backup Network errors and reconnection to
Avamar
52450 Client Escalation 6094:Backups failing with Internal Error: backtree: bad response - hotfix
50046 is installed
52953 Client CLONE: bug 52658-Escalation 6253:Slow exports, avdto using 100% CPU
53392 Client Escalation 6287:Functionality relating to backup and browsing of removable disks on a
Windows client
54480 Client CLONE: bug 54468-Escalation 6546:Avamar 7.0 Client backups fail if the pre-7.0 server
goes readonly during maintenance operations
54609 Client Escalation 6506:Scheduled replication (dpn) jobs are unable to use hash cache files if
initial replication job is run from the MCS/EMS GUI (user admin)
55093 Client Escalation 6351:avtar: fails to restore large amount of data
55319 Client CLONE: bug 55158-Escalation 6198:Slow backup Performance | Multiple ACL's set on 5
million files in user home directories and folders beneath
55352 Client Escalation 6672:Failed to rename backup dir DD - Issue 2: Avtar should NOT be sending
"Seal" messages for an incomplete backup
57268 Client Escalation 6853:Is Avamar 7. supposed or expected to remove snapshots after a job has
been canceled?
58254 Client Esc 6951: Certain cancellations can cause a cascade of asserts that appears to have no
end
58333 Client Escalation 6836:Lotus Domino Backup performance for DAOS folder highly degraded to
DD backend
59020 Client CLONE: bug 58585-Escalation 6952:Exchange 2010: Exchange Backups using Parallel
streams and By Target fails to restore
59249 Client CLONE: bug 58832-Escalation 7059:2 Group Policies from 2 Avamar Grids Failing Exports
w/ avtar Warning <7542>: Internal Warning: Very large amount of pending data in filepipe
59437 Client Escalation 7167: Multi-stream backups to DD does not throttle the max number of
streams

Release Notes

number
60497 Client Escalation 7344:MCS database does not store ddrid or ddrhostname for on demand
backups
60820 Client Escalation 7386:Export failed - Issue occurred during restore from Windows to Linux OS
60916 Client CLONE: bug 60914-Escalation 7097:fatal error when f_cache2.dat reach more than 2 GB
50979 Client Escalation 7413:AER Exports are failing during restore after upgrade to v7
60993 Client Escalation 7334:AIX backup hanging when dealing with mandatory locking
187154 Client Escalation 7302:Windows 2k8R2 backups intermittently complete with exceptions
188399 Client Escalation 7451:Avagent should not access generic adhoc requests from any process
except the local avscc
51909 Data Domain Escalation 6216:RFE Procedure for swapping out a DDR in AVE+DDR config is
integration unnecessarily high impact on Avamar backups.
55042 Data Domain CLONE: bug 55039-Escalation 6628:hfscheck failed with result MSG_ERR_DDR_ERROR
integration because of missing container files
55594 Data Domain RFE: Escalation 6679:Checkpoint Restore For v7.x Single Nodes with DD Integration >>
integration Restore Requirements (cprestore)
57312 Data Domain Escalation 6877:unable to do DD instant access while replication is running
integration
189935 Data Domain CLONE: bug 189217-Esc 7626: vm Instant access cannot handle non-sequential scsi ids
integration
52722 DB2 plug-in CLONE: bug 52721-Escalation 6302:DB2 backup fail - check_dpf_options error
56628 DB2 plug-in CLONE: bug 56624-Escalation 6796:db2 restores from offline backup complete OK
without ERRORS but the database is left in rollforward pending state
61242 DB2 plug-in Escalation 7444:DB2 backups failing with: [avdb2ctlplugin_assist] ERROR: <0001>
xml_message::validname('') invalid xml name
186183 DB2 plug-in Escalation 7450:DB2 DPF backups failing if there is one remote database with the same
name of the one we need to backup and that name shows up first in db2 list db directory
188312 DB2 plug-in Escalation 7513:DB2 restore failed : SQLO_PROG_ERR "Unknown"
59601 DB2 user guide CLONE: bug 59600-Esc 7218: Documentation request for redirected_restore_target flag
50291 Exchange VSS plug-in Browsing backups by using the command line interface on Exchange 2013 hangs.
50724 Exchange VSS plug-in DAG client is still registered to the Avamar server after uninstall.
51075 Exchange VSS plug-in CLONE: bug 51072-Escalation 6046:Exchange 2010:(Avamar 7.1)GLR Browse Failure :
Unable to read mailbox information from PowerShell
51174 Exchange VSS plug-in CLONE: bug 51172-Escalation 6112:(Avamar 7.1)Restore to RDB hangs if debug is used
51495 Exchange VSS plug-in CLONE: bug 51493-Escalation 6029:(Avamar 7.1)Exchange 2010: GLR Browse works but
fails to restore Complete Inbox
52091 Exchange VSS plug-in CLONE: bug 52088-Escalation 5213:(Avamar 7.1)Exchange backups failing with VSS
errors

Release Notes

number
53773 Exchange VSS plug-in Cannot browse Exchange Information Store after upgrade to Exchange 2013 CU2.
53958 Exchange VSS plug-in CLONE: bug 53955-Escalation 6258: (Avamar 7.1) -- Allow for a GLR proxy server that is
not a member of a DAG.
54558 Exchange VSS plug-in CLONE: bug 54555-Escalation 6512:(Avamar 7.1)Exchange 2010: Restore to RDB fails for
Non-DAG member
55600 Exchange VSS plug-in CLONE: bug 53678-Escalation 6430 - Backup User CFG Tool does not complete MAPI
profile creation in EX 2013
56334 Exchange VSS plug-in Escalation 6481:(Avamar 7.1)Exchange Incremental backups failing due log gap error
57591 Exchange VSS plug-in Escalation 6757:(Avamar 7.1)avexvss: RDB restore behavior inconsistency and fails with
avexvss Error <0000>: One or more selected databases do not have the "This database
can be overwritten by a restore" flag set
593111 Exchange VSS plug-in Escalation 6935:(Avamar 7.1)GLR restore is showing browse result empty
60049 Exchange VSS plug-in Escalation 7212:(Avamar 7.1)Exchange 2013 VSS backup not working as the backup
agent is not running as Avamar backup User
61255 Exchange VSS plug-in Escalation 7392:(Avamar 7.1)cannot restore to RDB from a DAG
187093 Exchange VSS plug-in Escalation 7478:(Avamar 7.1)Exchange 2010: Mailbox Database Restore Fails because of
GUID check (both 6.1 & 7.1)
190392 Exchange VSS plug-in Escalation 7454:(Avamar 7.1)Exchange GLR browse "result is empty"
54199 Exchange VSS user Escalation 6457: Exchange2010:Incremental federated backup promoted to full if "list"
guide changes
56922 Exchange VSS user DOCS: Document "--use-ps-displayname", "--remote-ps-server" flags to be used in
guide avmapi.cmd file (see escalation 6046)
53012 Extended Retention CLONE: bug 52966-Escalation 6319:AER export client s00sql01 fails: MCS timeout
getting info on 20 years of backups
58090 Extended Retention Escalation 6991:Export job hang at 0% after upgrade to version 7.0-1.2.1
58212 Extended Retention Escalation 7025:Error: Error reading volume label: cannot set record size: block size ioctl
failed
59035 Extended Retention Escalation 7153:Error on AER Upgrade when Postgres password has changed from the
original install
59113 Extended Retention Escalation 7155:TaskException: Could not create MBackupRetention object
59130 Extended Retention Escalation 7164:AER 2.1 timeout running MDomain Query via webservices
60185 Extended Retention CLONE: bug 59918-Escalation 7234:AER export did not export domain if vapp or
container client exists in that domain
187632 Extended Retention Escalation 7443:AdaGridTrace log fills root partition
186324 Hyper-V GLR plug-in CLONE: bug 186316-Escalation 7400:(Avamar 7.1)HyperV GLR Proxy does not mount
Windows 2008 & 2008 R2 VM backups taken on Windows 2012 R2 HyperV server
186198 Hyper-V VSS plug-in Escalation 7438:Hyper-V 2012 VM restore for manual provisioning not working

Release Notes

number
186547 Hyper-V VSS plug-in Escalation 7107:(Avamar 7.1)Hyper-V CSV cluster backup first install with proxy
configuration, no VMs appear in the Avamar GUI when browsing the Hyperv-Vss plugin
45520 Linux client Push upgrade for 32 bit CentOS 5 upgrades to the wrong version of the RHEL binary.
60521 Lotus Domino plug-in Escalation 7342:pm times are being translated to am times when Domino recover is
requested
49578 Management Console CLONE: bug 49577-Escalation 5925:"Failed User Login" on MC GUI via LDAP/AD
Authentication method
52494 Management Console CLONE: bug 52489-Escalation 6280:set destination window is blank while restoring the
folder which has >50000 files.
53738 Management Console RFE: Escalation 6440:Using lower version Avamar Administration console on a 6.1.1-87
Utility grid causes clients to be removed from a Domain group.
53808 Management Console Escalation 6451 - VM client move between the groups moves non-desired clients after a
sort in v7.0.0-396
54233 Management Console Escalation 6518:VMware image level backups special character in the datastore name
cause the snapshot to fail
54240 Management Console CLONE: bug 54239-Escalation 6515:Avamar 7.0 DA - Backups that timeout do not show
in MC GUI start-page
54696 Management Console CLONE: bug 54695-Escalation 6585:Avamar 7.0 build 421 - Couldn't reserve 1 ddr
stream(s) for ddrIndex:
54733 Management Console CLONE: bug 54732-Escalation 6595:Avamar 7.0 DA MC GUI shows Red X icon for
replication status when cron-based replication is still used
56831 Management Console CLONE: bug 48414-Escalation 5774:Getting error configuring Avamar with AD
57390 Management Console CLONE: bug 57330-Escalation 6888:Policy Window - sorting table causes functions to use
wrong client
57961 Management Console CLONE: bug 57960-Escalation 6748:6.1 to 7.0 Upgrade workflow fails updating MCS
58392 Management Console Escalation 7054:RCA - Unable to start MCS port replicate restore from the target. MCS
start failing with rollbacktime mismatch with gsan
59126 Management Console CLONE: bug 59122-Escalation 7125: Activities Client Filter List is not sorted
alphabetically after upgrade to version 7.0
59187 Management Console CLONE: bug 58932-Escalation 7127:Hotfix Request for 7.0.0-427 for Bug 58812 - Activity
Monitor very slow or unresponsive with large number of activities.
59189 Management Console Escalation 6661:RFE: Make manual maintenance failsafe or remove the maintenance
options from the GUI
60408 Management Console MCGUI Replication - encrypt flag is not being updated until the group is run (see
escalation 7297)
60660 Management Console CLONE: bug 60601-Escalation 7353:Post install HF 58932, Activity monitor pane doesn't
show the activities for a long time
61147 Management Console Escalation 7439:Avamar vsphere web client logins fail due to maxHttpHeaderSize tomcat
configuration

Release Notes

number
186173 Management Console CLONE: bug 186171-Escalation 7457:Plus (+) in password breaks MCGUI LDAP
authentication
186941 Management Console Escalation 7501:Emergency Virtual Center restore in Avamar 7.0.x
188914 Management Console DOCS: bug 59189-Escalation 6661:RFE: Make manual maintenance failsafe or remove
the maintenance options from the GUI
188971 Management Console Escalation 7584:The Admin GUI freezes while trying to open a large session log. The
session log is never opened.
190411 Management Console Escalation 7678:exported Activity Report file is 0 bytes
50754 Management Console CLONE: bug 50592-Escalation 6050:Avamar 7.0 Beta - Passwords for plug-in based
Server replication destinations are stored in plain text
51010 Management Console Escalation 6091:Avamar 7.0 Beta - Vcenter Delete issue - Unable to delete directory
Server because it contains groups
51017 Management Console CLONE: bug 50975-Escalation 5982:Insecure permission errors when logrotate runs
Server
51603 Management Console CLONE: bug 51508-esc 5891:Communications module scanner encountered an error
Server
51865 Management Console CLONE: bug 51861-Escalation 6199:6.1.1.-87 Upgrade workflow fails updating MCS -
Server Update Failed: Error processing preferences file merge
52115 Management Console CLONE: bug 27819-Escalation 2982:Backup browsing performance related to bug 17637
Server
53365 Management Console Escalation 6398:Randomly and Intermittently, physical clients failing backup with
Server
54714 Management Console CLONE: bug 54513-"No Vm" workorder is not generated. Escalation 6526:Avamar 7
Server Scheduled backups not running
54734 Management Console CLONE: bug 54451-Escalation 6539:7.0 Plug-in based replication jobs were stuck in
Server
54990 Management Console CLONE: bug 54420-CANCEL jobs at group level no longer works (from Escalation 6526)
Server
55013 Management Console Escalation 6596:Domain and clients are not visible in MC GUI
Server
55114 Management Console CLONE: bug 55109-Escalation 6610:cannot edit vm client's policy settings when the vm
Server is inside a static container
55786 Management Console Escalation 6597:Avamar 7.0 DA - Replication reports inconsistent number of clients
Server succeeded in source vs target MCGUI Dashboard
55931 Management Console CLONE: bug 55829-Encounter javax.xml.rpc.JAXRPCException while cloning connection.
Server Escalation 6526:Avamar 7 Scheduled backups not running
56161 Management Console Escalation 6332:Scheduled backups fail seemingly at random with "TCP timeout on
Server receive ack (seconds 300)" followed by "avagent Warning <5473>: Null message received
from MCS"

Release Notes

number
56256 Management Console Escalation 6767:Different rollbacktime across nodes will cause MCS restore to fail
Server
57441 Management Console Escalation 6905:Adding vCenter fails with error message pop-up: "Unexpected exception
Server occurred"
57709 Management Console Escalation 6917:Cannot restore VM after upgrade to 7.0 -- restore is reject because ESX is
Server not in vCenter
57730 Management Console Escalation 6827:BRSIL: Avamar 7 VMware backups hanging

Server
57754 Management Console Escalation 6958:Backups for VMs protected with dynamic inclusion are incorrectly tagged
Server with yearly retention
58178 Management Console Escalation 7014:new vms discovered in dynamic containers have CBT disabled
Server
58261 Management Console Escalation 6996:Running 2 scheduled backups of the same client at the same time failed
Server one of them with the lock error rather than waiting for the first one to complete
58325 Management Console "Ghost" VMs emerge after VMs are relocated. Escalation 6774:Avamar Schedule image
Server backup is running but does not backup all VMs in policy>
58457 Management Console CLONE: bug 58456-Escalation 7044:WC | Restore | SQL | RESDTCvAP59 - SQL browse
Server restore takes long
58797 Management Console Escalation 7114:Vmimage Restore sits in waiting queued state for 7 SP1
Server
58923 Management Console Escalation 7095:failed avtar backup shows 30000 success in Activity Report
Server
58926 Management Console Escalation 7112:Vm's disabled in a dynamic container still show failed in activity window
Server
59302 Management Console Escalation 7130:The user has insufficient privileges to access the system resource
Server
59464 Management Console Escalation 7206:The backup completion email is not sent for the container clients
Server
60527 Management Console Escalation 7351:Java process using 12,000+ threads

Server
187036 Management Console Escalation 7416:When replicating internal Avamar system accounts AVI_BACKUPS,
Server EM_BACKUPS and MC_BACKUPS fail after 15 minutes.
187882 Management Console Escalation 7540:Activity Monitor/Summary don't show any activities after installing MCS
Server hotfix# 60601
188455 Management Console Escalation 7594:MCS crashed due to lack of jdbc connections
Server
52997 MCCLI Escalation 6338:next run time show incorrect date after export / import group by mccli
59260 MCCLI Escalation 7177:RFE: mccli dataset show to display dataset type in Avamar 7.0
59475 MCCLI Escalation 7176:Datasets with Type Unknown after being imported from Avamar 6.1

Release Notes

number
187657 MCCLI Escalation 7541:mccli command line does not allow restore of replicated virtual machine
after Avamar 7.0 upgrade
39833 NDMP Accelerator RFE - Escalation 4705:NDMP backup failing with: NDMP: Medium error (Speed up the
merge process)
50433 NDMP Accelerator After rebooting the accelerator, push upgrades do not work until the accelerator has been
re-registered with the Avamar server.
53439 NDMP Accelerator Escalation 6413:Avamar 6.1 SP1 + Isilon Username/Password visibility
59846 NDMP Accelerator RFE: Escalation 7264:NDMP failing with:Unable to find a matching entry in prevlist for
historytable ('3353713:OTC7KUIT.txt (RFE)
60566 NDMP Accelerator CLONE: bug 60447-Escalation 7105:Progress bytes are not reported correctly for all
Netapp backups sent to DD
61259 NDMP Accelerator CLONE: bug 61257-Escalation 7448:NDMP backups failing daily with NDMP file history
errors
190051 NDMP Accelerator CLONE: bug 190045-Escalation 7677:Avamar MCS Browse is not able to see the
contained files inside a directory that is using a special character "space".
191911 NDMP Accelerator Escalation 7695:NDMP data restored to different folder not accessible by cifs user
57599 NDMP Accelerator user Escalation 6938:restoring NDMP backup to a CIFS share is corrupted if compression is
guide enabled
59053 NDMP Accelerator user CLONE: bug 58417-Escalation 7031:Modify "EMC Avamar 7.0 NDMP Accelerator user
guide guide" manual to reflect modify introduced to avndmp script to resolve BUG 30164
48451, Oracle plug-in Escalation 5707: The avoracle SQL files creating in vardir should not have file names
48452 ending in '.cmd'.
52244 Oracle plug-in CLONE: bug 52222-Escalation 6186:oracle backups failure due to communication
between avamar oracle library and avoracle and avoracle failing with mutex errors
55183 Oracle plug-in CLONE: bug 55136-Escalation 6618:Oracle restores fails when using --nohist and hotfix:
Bug 50191 - Escalation 5923:request a hotfix that combines HF48405, HF47185 and
HF47109
59336 Release notes DOCS: bug 48465-Escalation 5779:VMimage restore fail with invalid snapshot
configuration due to storage DRS
60565 Release notes Escalation 7364:The number of concurrent connections per data node is not documented
in the customer facing documentation
50723 Replicator Escalation 5871:Escalation Review 53188020 Replication will intermittently hang
52111 Replicator Escalation 6184:Several backups should not have been removed from Data Domain
during GC
54185 Replicator CLONE: bug 54183-Escalation 6508:Avamar v7.0.0-396 replicate script changes behavior
for --force-move use - Causing replication to fail
55933 Replicator Escalation 6714:7.0 Plug-in based replication is applying incorrect expiration to
replicated backups

Release Notes

number
188154 Replicator Escalation 7311:Replication does not replicate all backups after timing out the previous
day
42270 SAP with Oracle plug-in Display issue for SAP restore with Avamar server release earlier than 7.0
49507 SAP with Oracle plug-in CLI backup of an online database fails if any of the datafiles use UNC pathnames or
directory junctions.
50746 Security Escalation 6020:SSLCertificateChainFile directive is commented out in the default

installation (Workflow Update)
54600 Security CLONE: bug 54306-Escalation 6503:Avamar 7.0 DA: Config files are browseable on the
utility node.
54748 Security Escalation 6557:Orange Business Service - SSL-cipher and apache security
customization
57319 Security CLONE: bug 52976-Escalation 6370:Hotfix Request for Bug 39329 - (NAT and cannot
access the browse local hard drive)
59391 Security Escalation 7192:6.1.2-47 Upgrade workflow resets custom passwords to "changeme"
when avhardening is installed
61010 Security CLONE: bug 60966-Quick Fix (workaround) for esc 7322:Keystore password needs to be
hidden - request hotfix
56813 SharePoint VSS plug-in CLONE: bug 56785-Escalation 6791:(Avamar 7.1)SharePoint Browse Failure Due to SQL
Alias Being Truncated
58523 SharePoint VSS plug-in Escalation 6911:(Avamar 7.1)SharePoint Backup failure after SQL Back-end Migration
60513 SharePoint VSS plug-in Escalation 6882:SharePoint 2013 Backup authentication issue
187874 SharePoint VSS plug-in Escalation 7066:(Avamar 7.1)Unable to successfully backup SharePoint Environment
188484 SharePoint VSS plug-in Escalation 7471:Escalation 7489:Escalation 7461:(Avamar 7.1)Unable to backup
sharepoint farm | SQL & Sharepoint Alias Names | alias > itself contains .'s
188529 SharePoint VSS plug-in Escalation 7511:(Avamar 7.1)SharePoint VSS unable to backup SQL back-end
189718 SharePoint VSS plug-in Escalation 7655:(Avamar 7.1)Sharepoint VSS backups fails if SQL Alias has FQDN
190389 SharePoint VSS plug-in CLONE: bug 190119-Escalation 7564:(Avamar 7.1)SharePoint VSS Backup Failing
50501 SQL Server plug-in CLONE: bug 50500-Escalation 5912:(Avamar 7.1)SQL DB Restore with FILE STREAM data
Failing
50730 SQL Server plug-in FILESTREAM datafiles appear as Rows Data in Avamar Administrator.
50779 SQL Server plug-in Differential or incremental backups are incorrectly forced to full after previous backup
was forced to full.
51406 SQL Server plug-in CLONE: bug 51352-Escalation 5291:(Avamar 7.1)Failed to browse SQL instances,
pbg1sql01v312, pbg1sql01v305
52144 SQL Server plug-in CLONE: bug 48581-Escalation 5789:(Avamar 6.1 GA HOTFIX)SQL server detecting
SQL2012 while SQL Browse Function
55655 SQL Server plug-in Redirected restore to a different instance with existing database fails.

Release Notes

number
57248 SQL Server plug-in Escalation 6691:(Avamar 7.1)SQL 2008 browsing failure on Windows 2012
57610 SQL Server plug-in Escalation 6824:(Avamar 7.1)MSI SQL Plugin Installation Fails -: Setup Premature ended
187150 SQL Server plug-in Escalation 7474:(Avamar 7.1)In-House Repro: Esc 7372: "avsql Error <9072>:
System.NullReferenceException: Object reference not set to an instance of an object
54197 SQL Server user guide Escalation 6484: Cannot recover data in mixed SQL versions
56300 Sybase ASE user guide DOCS: bug 56299-Escalation 6771:Sybase using encrypted password need to pass
through correctly
51042 Tools Escalation 6102:Time sync issue on one node
52516 Tools Escalation 6291 - mapall parallel issues
52808 Tools Escalation 6328 - avi directory is grabbed twice when running getnodelogs
55456 Tools Clone: Bug 51074 - Escalation 6015:RFE: Add the systemid to status.dpn.
59038 Tools Escalation 7146:system_time_zone.pm doesn't work on SLES
59657 Tools Escalation 7137: switch monitoring "is running, detected 6 instances" false alarm
188408 Tools CLONE: bug 60696-Escalation 7009:hfscheck failed with hash reference after node 0.5
was put offline by other nodes
48287 Upgrade Escalation 5749:Upgrade Workflow does not verify GSAN shutdown is clean
49226 Upgrade Escalation 5887:Disable avfirewall during Upgrade Workflow to Allow Switch Firmware
Update
54887 Upgrade CLONE: bug 54886-Escalation 6615:7.0.0-423 Upgrade workflow fails -- Creating 12GB
Swap File Failed - timeout error
55268 Upgrade Escalation 6666:Upgrade61To6.1.2-47 Workflow failure - Validating Node Database

failed
61265 Upgrade Escalation 7452:RFE: Request option to skip hard stop for metadata in Upgrade
Workflow. for Avamar 7.0 SP2
30681 VMware Special characters in datastore, folder, or datacenter names prevent the .vmx file from
being backed up.
35331 VMware Windows-based proxies from previous versions of the Avamar software are unable to
browse backups for file level recovery.
51992 VMware Escalation 6133:P2Ved vm is not bootable in vmware after avamar restore
52705 VMware Escalation 6185:VM image backup fail due to the Host <esxserver> is in a state that
cannot perform snapshot operations
53208 VMware Escalation 6379:After node offline on July 10th - large number of VM backups failing with
TIMED OUT messages
55142 VMware Escalation 6617:Avamar 7 is restoring thin vms as thick.
57737 VMware Escalation 6894:The file with extension '.vmx' could not be located on the VM" when VM
folder is not in the root of the datastore.

Release Notes

number
58135 VMware Escalation 6989:avvcbimage crash during the backup causing the snapshots to be left on
the DS, and reports as successful in MCS.
58377 VMware RFE: Add tcpdump to the VMware Combined Proxy Appliance (Esc 6826)
58676 VMware Escalation 7084: FLR fails with error "Failed to generate session handle" if the filename
contains "%20s"
58837 VMware Escalation 7122:vm image backups show completed successfully but log shows they
failed.
59435 VMware CLONE: bug 59288-Escalation 7160:If vCenter becomes unavailable during EBR backup,
the backups halt
60652 VMware CLONE: bug 60499-Escalation 7345:HOTFIX:Avamar 7.0 SP1 proxy are NOT clearing stale
migration reservation
188144 VMware Large Number of ESX Hosts in vCenter Server Cause Proxy to Run Out of Memory (see
escalation 7573)
188523 VMware Esc 7310: EBR: VDDK crash and CTL race condition issue cause failures
190010 VMware Escalation 7690:vmimage plugin does not remove snapshot due to NotAuthenticated
soap message
192117 VMware Escalation 7571: Do Multiple retries for HTTP PUT/GET for the VMX file
60803 VMware user guide Escalation 7394:Retiring the container from Avamar does not retire the VM which was
previously added as an static/standalone entry
189359 VMware user guide Escalation 7656:restore rehearsal fails with the documented privileges for the Avamar
user in vSphere
190117 VMware user guide DOCS: bug 186941-Escalation 7501:Emergency Virtual Center restore in Avamar 7.0.x
190564 VMware user guide Escalation 7717:DOC-BUG - FLR progress byte not visible in Avamar GUI, the
documentation does not reflect it.
54642 Windows client Unable to ping DNS addresses in a mixed IPv4/IPv4 environment when Bare Metal
Recover wizard is used to configure the addresses.
57811 Windows client Escalation 6933:(Avamar 7.1)Icon is not hidden when using UICOMPONENT=0 after a
push install.
187613 Windows Cluster Escalation 7470:(Avamar 7.1)WCCW: Unable to Config Cluster if Disk Drive has "path" in
Configuration Tool it
51198 Windows VSS plug-in CLONE: bug 50387-Escalation 6024:(Avamar 7.1)Unable to restore a critical volume X:
through WinPE
54915 Workflow Escalation 6616:7.0.0-423 sysctl_helper script failing due to hostname problem
55581 Workflow CLONE: bug 55561-Escalation 6695:logrotate cannot rotate apache logs after applying
the OS Security Rollup.
57413 Workflow CLONE: bug 57409-Escalation 6798:Application-Level Security Vulnerabilities
186737 Workflow DOCS: bug 61266-Escalation 7452:RFE: Request option to skip hard stop for metadata in
Upgrade Workflow. for Avamar 7.0 SP2

Release Notes
Fixed problems for the Avamar 7.1 GA release

The following table lists fixed problems for the Avamar 7.1 GA release.
Table 3 Fixed problems for the Avamar 7.1 GA release
Issue number Product feature Problem summary

195384 Backup and Recovery esc 7890:PGP Signature for BRM fails on RHEL
Manager
199161 ConnectEMC CLONE: bug 199063-esc 7837:Stripes did not come online after rollback with node
offline
191317 Hyper-V VSS plug-in Virtual machine appears to be available for restore even though the backup of the
virtual machine failed
193088 Lotus Domino plug-in Escalation 7809:Domino database is restored OK but the job fails due to not being
able to delete the temp folder
193393 Management Console CLONE: bug 193392-Escalation 7822:Similar errors as mentioned in Esc7810,
Server however, in our scenario, the MCS remains in hung state when clicked on Policy tab
190088 MCCLI Escalation 7657:Export/import of SAP groups using MCCLI results in clear-text
passwords in DATASET+group does not work
188255 NDMP Accelerator Escalation 7555:RFE support for NetApp cluster mode
188207 Oracle plug-in Escalation 7498:Oracle plug-in leaking file descriptors
59856 Replicator Cron-based replication setup from an Avamar 6.1 source server to an Avamar 7.1
destination server fails
192829 Security Enabling two-way authentication after enabling external key management causes
failed key rotation
193184 Security OpenSSL vulnerabilities
193213 Security Escalation 7821:Security - CVE-2014-0224 is affecting GA versions of Avamar
193918 Security CLONE: bug 193805-Escalation 7850:SECURITY: customer demonstrated exploit to

retrieve MCUser password from any grid
193960 SharePoint VSS plug-in Incorrect error message that the username or password is missing during an on-
demand backup
191688 Windows client Windows client installation requires reboot
Fixed problems for the Avamar 7.1 SP1 release

The following table lists fixed problems for the Avamar 7.1 SP1 release.

Release Notes
Table 4 Fixed problems for the Avamar 7.1 SP1 release

number
191140 Avamar Administrator CLONE: bug 188969-Escalation 7584:The Admin GUI freezes while trying to open a large
session log. The session log is never opened.
197722 Avamar Administrator Escalation 8038:SR 64620286 - instant access button not available for back up/restore
Operator
194305 Avamar Client Manager CLONE: bug 194190-Escalation 7732 - ACM UI performace degradation in v7
196623 Avamar Desktop/ Escalation 7932 -Tomcat vulnerabilities for Jsessionid, error handling and version
Laptop updates
205293 Avamar Desktop/ CLONE: Escalation 8420:Request a hotfix on top of HF 203549 to allow linux clients to
Laptop use avamar authentication when the DTLT user-login-module=mix
198734 Avamar Rest API Escalation 8096:Need REST-API RPM for RHEL
200811 Avamar Rest API CLONE: bug 193832-Name attribute's description of JobType is not correct
56295 Avamar server CLONE: bug 51786-Escalation 5744:USB errors in the logs - kernel: [12984306.731685]
usb 5-2: device descriptor read/64, error -71
57769 Avamar server Escalation 6972:7.0.1 - During Checkpoint Maintenance "ERROR: <0001>
stripe::unsafestripewrite readonly iogroup size=1..."
60453 Avamar server Escalation 7254:Upgrade from 6.x to 7.x breaks replication as the replication interface is
not correctly defined in probe.xml
60851 Avamar server Escalation 7370:ASCD killed node 0.0 after node 0.3 became isolated.
187047 Avamar server Escalation 7494:MSG_ERR_HFSCHECKERRORS "<detail kind="writelog"/>"
188273 Avamar server Escalation 7577:Stripe corrupted due to "fileimpl::write pwrite returned errno 9 (Bad file
descriptor)" error (RCA)
194298 Avamar server Escalation 7854 - Improved stripe creation handling during checkpoint operations
197024 Avamar server Esc 8015 - avsysreport pdisk status should add Status of "Online with errors"
197535 Avamar server Escalation 7830:GSAN crashed twice with FATAL 11 on a single node server
201536 Avamar server Escalation 8231 - Excessive number of packet errors for dropped frames
203866 Avamar server Escalation 8323:7.1.0-370 upgrade, Gsan will not restart -- FATAL ERROR: <0001>
tatrestencryption::initrestencryption cannot load EAR salts
203932 Avamar server CLONE: bug 203615-Escalation 8294:Four bytes in chd of parity stripe fails cxor
comparison after crunching
205610 Avamar server CLONE: bug 205374-Escalation 8408: attempt to repair chunk from checkpoint causes
fatal errors
205682 Avamar server Escalation 8425: comparechunk errors in persistent store due to empty chunklist
195537 Backup and Recovery CLONE: bug 195384-Escalation 7890:PGP Signature for BRM fails on RHEL
Manager
197640 Backup and Recovery Escalation 8012:BRM reporting false replication information before and after upgrading
Manager to 1.2-123
186816 Client Escalation 7415:avtar is not able to browse directories with 64bits inodes
Fixed problems for the Avamar 7.1 SP1 release 23

Release Notes
Table 4 Fixed problems for the Avamar 7.1 SP1 release (continued)

number
192651 Client Escalation 7668: Avamar datadomain backups take longer in version 7.0 than 6.x
193177 Client Escalation 7790:BUG: Avagent holding an exclusive lock on C:\ClusterStorage
194232 Client CLONE: bug 194230-Escalation 7565:Avtar process stalling on random directories
196182 Client CLONE: bug 187942-Escalation 7547:Backup to Data Domain is sealed on Avamar, but
not committed to DDR.
196516 Client Escalation 7894:Backups unable to generate VSS snapshot
197200 Client CLONE: bug 53647-Escalation 6361 - plugins should exit with error if "--parallel" flag is
used
199219 Client Escalation 7072:(7.1 SP1)System State backup should detect avtar exit status
EXIT_OK_WITH_OPENFILES
200349 Client CLONE: bug 200252-Escalation 8104:Unable to run pre-script after upgrade to v7 -
FileSystem backup on windows 2012
200930 Client Escalation 8107:VBA backup failures. Avtar got killed unexpectedly
202083 Client CLONE: bug 202082-Escalation 8142:Incorrect 'Progress Bytes' reported for archived/
stub files
202179 Client CLONE: bug 202150-Escalation 8254:avtar dumping core in HPUX 11.31
202279 Client CLONE: bug 189788-CSV with SMB: multi-stream by-target backup to DD failed with error
"avtar FATAL <18129>: DDRIO_Write::Shutdown: ddp_close() failed: DDR result code:
5057, desc: File handle is stale"
202531 Client esc 8278 avtar -tv or --list with --after and --before and --labelnum causes lot of invalid
entries in avtar output
199162 ConnectEMC CLONE: bug 199063-Escalation 7837:Stripes did not come online after rollback with node
offline
187942 Data Domain Interrupted backups cause hfscheck failures

integration
202523 Data Domain CLONE: bug 199542-Escalation 8063:Hyper-V 2012 R2 : Slow Backups | Data Domain |
integration High number of TODO list | Avamar works fine
198043 DB2 plug-in Escalation 8020:Warning <16837>: Unable to load /usr/db2inst1/sqllib/lib64/

libdb2.a(shr.o): Error: 0509-022 Cannot load module /usr/db2inst1/sqllib/lib64/
libdb2.a(shr.o).
190843 Exchange VSS plug-in CLONE: bug 190569-Escalation 7653:(7.1)Failed exchange backups with "unable to
enumerate exchange databases"
190943 Exchange VSS plug-in Escalation 7580:(7.1)Second Exchange VSS incremental backup always fails with Log file
gap detected between current backup and last backup
192008 Exchange VSS plug-in Escalation 6953:(7.1)Exchange 2013 GLR Failing with "Backup Browse Result is Empty"
193012 Exchange VSS plug-in Escalation 7544:(7.1 SP1)Canceling an Exchange DAG backup from the Avamar GUI it
does not stop the avtar process in the physical server.

Release Notes

number
193017 Exchange VSS plug-in Escalation 7422:(7.1 SP1)Exchange 2010 : RDB restore is successful but marked as
Failed in MCGUI (Progress Avtar Issue)
196766 Exchange VSS plug-in Escalation 7964:RFE:(7.1 SP1)Exchange VSS Plugin Need way to toggle the permission
and\or Group Membership check change introduced in 7.0
199190 Exchange VSS plug-in CLONE: bug 199167-Escalation 7595:(7.1 SP1)Exchange database reported in dirty shut
down state during GLR.
199392 Exchange VSS user DOCS: bug 199190-CLONE: bug 199167-Escalation 7595:(Indio SP1)Exchange database
guide reported in dirty shut down state during GLR.
59918 Extended Retention Escalation 7234:AER export skipped vms under resource pool/vapp
188377 Extended Retention Escalation 7592:The issue with the clients that have expired or no longer in dns so we
can't see it in the Import & Restore.
193822 Extended Retention Escalation 7838:avtar exports causing OOM on AER man node (GSAN failures result
because of no memory and swap).
203945 Extended Retention CLONE: Escalation 8351:AER 2.6 does not show exports whose browse policy has expired
204330 Extended Retention Escalation 8274:Unable to save data required for partial import for <Client>. while running
export Job
186776 Hyper-V VSS plug-in Escalation 7466:(7.1 SP1 RFE) Multi-Proxy Backup should fallback to regular mechanism
if "--change-csv-volume" flag doesn't work
191317 Hyper-V VSS plug-in Escalation 7712:Bug/RFE : Hyper-v Multi-Node backup failed to backup 1 VM but VM is
available for Restore
197263 Hyper-V VSS plug-in Escalation 8010:RFE: Hyperv2012/R2: Multi-Proxy: Complete Backup is marked as Failed
if there is a missing Virtual Machine
197265 Hyper-V VSS plug-in Escalation 8011:RFE/BUG: Hyper-v2012/R2: Few of the Failed VM's are available for
Restore (Snapview Bug)
193817 Lotus Domino plug-in Escalation 7785:AVLOTUS not able to backup files bigger than 2GB
201245 Lotus Domino plug-in Escalation 8103:Avtar failure handling by avlotus
60497 Management Console Escalation 7344:MCS database does not store ddrid or ddrhostname for on demand
Server backups
188478 Management Console Escalation 7460:Utility node errors with no resources available (can't fork)
Server
189117 Management Console Escalation 7604:5 Apache Tomcat Vulnerabilities

Server
189803 Management Console CLONE: bug 188533-Escalation 7589:SR 62316300 - setting locale to fr_FR@euro on
Server RHEL client causes java exception in MCS when browsing for restore
192840 Management Console CLONE: bug 192819-Escalation 7683:Unable to run replication (PLUG-IN based) and
Server backup of VMware Image client at the same. One job can be in a "running" state and the
other stays in "waiting-client" state
193810 Management Console CLONE: bug 192005-Escalation 7076:(esc 7063) Restore of SQL db's with large backup
Server label numbers is slow

Release Notes

number
195533 Management Console CLONE: bug 188630-Escalation 7551:Unable to Retire Client from Dynamic container
Server
196367 Management Console CLONE: bug 196365-Escalation 7992:SNMP statistics error messages between Avamar
Server and dd
197436 Management Console CLONE: bug 194504-Escalation 7862:Avamar times out SNMP get requests from Data
Server Domain
197963 Management Console Escalation 7999:Cannot add avamar 7.1 to BRM(1.2)., fails with certificate error
Server
199551 Management Console Escalation 8111:Installing an MCS hotfix caused stripeUtilizationCapacityFactor to be set
Server back to default (1.05)
200084 Management Console CLONE: bug 198006-Escalation 8058:GUI based replication authentication fails if user
Server account exists in a sub-folder
201806 Management Console CLONE: bug 201805-Escalation 8232:After applying MCS patch HF197495, backups to
Server DD stalled on Waiting Queued unless we change ddr_stream_management_enabled in
mcserver.xml to false >
201970 Management Console CLONE: bug 200311-Escalation 7888:Activity Summary page shows groups ran for 50
Server hours under "Time Active" column while they ran for only 2 hours.
203550 Management Console CLONE: Escalation 8311:DTLT backup/restore showing session expired for all clients in
Server NAT environment after upgrade to version 7.1
203757 Management Console CLONE: bug 203756-Escalation 8322:After rollback in ESC 8306, backups and restores
Server through MCS are stuck in waiting-queued
203842 Management Console CLONE: bug 203820-Escalation 8343:unable to load client list on the AER export policy
Server
204254 Management Console CLONE: bug 202460-Escalation 8202:DTLT : load issue on the utility node since
Server upgrading to v7
205671 Management Console esc 8436 - DPN event code 35 not showing from MCGUI, user cannot opt not to receive
Server notification.
205705 Management Console CLONE: Escalation 8427:unable to set expiration to "no end date"
Server
205795 Management Console CLONE: bug 205491-Escalation 8374:Cannot view clients via the mcs GUI or mccli after
Server an attempt to move any client from one group to another or change made in any schedule
61107 MCCLI Escalation 7411:RFE: Improve mccli dd show-prop --xml output
61269 NDMP accelerator UTF-8 character sets do not appear correctly in Avamar Administrator for restores on EMC
VNXe NAS devices
200150 NDMP Accelerator Escalation 8178:avtar Error <15168>: Stream error: Invalid file type:55 on socket files
200993 NDMP Accelerator Escalation 8165:NDMP backup fails to save hard links path for stub files
202614 NDMP Accelerator Escalation 8268:PR 944: NC - NDMP Netapp - SR66103994 - cannot browse the backup
203575 NDMP Accelerator Escalation 8327:All Avamar restores from Isilon backup to Isilon fail.

Release Notes

number
198245 Oracle plug-in Escalation 8040:Backup fails with: avoracle Error <17358>: An incremental backup was
requested but there is no previous full backup. Please perform a full backup before any
subsequent full backups
202484 Oracle plug-in CLONE: bug 202480-Escalation 8131:Oracle backup completed successfuly, but the
control file was missing in backup content
203972 Oracle plug-in CLONE: bug 202422-Escalation 7943 (HOTFIX):Oracle 9.2 "out of process memory" errors
205910 Oracle plug-in Escalation 8431:oracle restore --nohist not working anymore and possible dataloss
202072 Replicator CLONE: bug 201238-Escalation 8034:Replication in not replicating a group that has more
than 100 clients in the list of members for the group after upgrading to 7.0.2-47
202394 Replicator CLONE: bug 200379-Escalation 8076:Selecting parent domain, always includes all sub-
domains in policy based replication even when sub-domains are deselected
202476 Replicator Escalation 8266:Kernel Error from avtar.bin during replication
203269 SAP with Oracle plug-in CLONE: bug 200986-Escalation 7852:WC - SAP - db restore not finding current database
control file
196620 Security Escalation 7932 -Tomcat vulnerabilities for Jsessionid, error handling and version
updates
202093 Security esc 7349: harden ciphers in sshd configuration
202875 Security Esc 8303 -7.1.0-302 upgrade workflow installed avfirewall on NDMP accelerator, backups
failed because port 28001 was blocked
203849 Security ESC 8325 -PR 1102: SER - Network - SR 66522028 - Avamar firewall blocks traffic to ftp
server used by connectEMC
204008 Security CLONE: bug 204006-ESC 8308: Disable SSLv3 support in apache
196169 SharePoint VSS plug-in Escalation 7796:(7.1 SP1)SharePoint VSS Restore Failing with "Writer-file map is empty"
198817 SharePoint VSS plug-in Escalation 7897:(7.1 SP1)SharePoint 2013 with 2 named instances for SQL cluster back-
end results in backup failure.
201014 SharePoint VSS plug-in Escalation 8177:(7.1 SP1)PR 788: WC - SharePoint VSS - SR<65390172> - SharePoint VSS
restore error "Failed to parse Search Service Applications metadata file"
204588 SharePoint VSS plug-in CLONE: Escalation 8234:(7.1 SP1)SharePoint farm backup error "RegQueryInfoKey failed
with error 0"
205793 SharePoint VSS user Escalation 8418:Doc RFE : Improve documentation to clarify supportability for SharePoint
guide 2010 Farms with multiple Search Service Applications
186775 SQL Server plug-in Escalation 7361:(7.1 SP1 RFE)SQL client installer checks for .NET installed but not SMO or
other required components
189394 SQL Server plug-in Restore fails when an availability group database name includes an apostrophe
189507 SQL Server plug-in Restore fails when an availability group database name includes Unicode characters
194978 SQL Server plug-in Escalation 7909:(7.1 SP1)SQL 2005 Cluster failing to backup
197437 SQL Server plug-in Restore fails when the transaction log on the secondary replica is not synchronized
during the backup

Release Notes

number
200280 SQL Server plug-in Escalation 8159:(7.1 SP1)SQL Cluster incremental backups getting progressively slower
over time
200286 SQL Server plug-in Escalation 8120:(7.1 SP1)WC - SQL - AppSync SQL Copy is Forcing Avamar to Take Full
Backups
191589 Tools Esc 7774 - Create New Symptom Codes for Dell Hardware Events (and Intel Gen4S events)
190984 Upgrade Error code appears during push upgrade of NDMP accelerator, but upgrade succeeds
196795 Upgrade Guide DOCS: bug 22982-Escalation 4049 - RFE show status if avinstaller is able to connect to
ADS and show ADS info
57015 VMware CLONE: bug 54233-Escalation 6518:VMware image level backups special character in the
datastore name cause the snapshot to fail
59940 VMware Escalation 7211: RFE:VM Non-quiesced snapshots are not cbt base backup candidates
203065 VMware Guide DOCS: bug 203063-Escalation 8307:Image backup fail when user square brackets in vm
name
191991 Windows Cluster Escalation 7389:(7.1)Unable to register cluster after Avamar 7.0 SP1 upgrade
Configuration Tool
199594 Windows Cluster CLONE: bug 197271-Escalation 8017:RFE: Hyperv2012/R2: Multi-Proxy : Cluster Config
Configuration Tool tool should state "The Current Proxy Node" and Stop
22982 Workflow Escalation 4049 - RFE show status if avinstaller is able to connect to ADS and show ADS
info
187765 Workflow Escalation 7543:Upgrade from 6.1 to 7.0.1-61 does not remove older
dpnserverhotfix-6.1.1-87_HF45974.rpm
194664 Workflow Escalation 7868:UpgradeClientDownloads-6.1.2-47.avp PACKAGE REJECTED. REASON:

REQUIRES DIFFERENT AVAMAR VERSION
195298 Workflow CLONE: bug 195297-[REGRESS] - "Description + and -" icons are missing in avi page after
upgrade
197060 Workflow NewInstallRhel failed at "AvamarInstallRhel:: Installing Client Download RPMs" step with
Bad file descriptor ERROR
197329 Workflow Escalation 8031:V602hf46907-6.0.2-153.avp MCS Hotfix workflow fails at 53% updating
mcs configuration failed
198414 Workflow RFE: Escalation 8045:Cannot install UpgradeClientPluginCatalog-7.1.0-302.avp on 7.x

Avamar servers only on 6.x
202092 Workflow esc 7349: harden ciphers in apache and tomcat servers
Fixed problems for the Avamar 7.1 SP1 refresh build 145 release
The following table lists fixed problems for the Avamar 7.1 SP1 refresh build 145 release.

Release Notes
Table 5 Fixed problems for the Avamar 7.1 SP1 refresh build 145 release

number
206481 Client CLONE: bug 206471-Escalation 8241:Windows 2012 server
backups for directories with 1.2 million SYMLINKS get stalled
225045 Client CLONE: bug 225043-Escalation 22763:the files are shown for
restore on Admin GUI and avtar --list even though the files
were failed to backup.
225738 Client CLONE: bug 225736-Escalation 22780:Large NetApp backups

in Indio use excessive memory when "Preparing tables for
backup"
226183 Client CLONE: bug 225779-Escalation 22818:Backup to Data Domain

is sealed on Avamar, but not committed to Data Domain.
226434 Client Manager CLONE: bug 225900-ESC 8129 - Client manager initiated client
upgrade fails intermittently
226277 Data Domain CLONE: bug 226000-Escalation 22818:ddrmaint patch:

Integration Backup to Data Domain is sealed on Avamar, but not
committed to Data Domain.
222358 DB2 Plug-in CLONE: bug 207249-Escalation 8422:memory leak in avdb2

and db2vend
226366 Management CLONE: bug 224527-Escalation 22878:Cannot use web-

Console restore(configured with new ldap method) and ldap
login(configured with legacy method) together.
222303 Management CLONE: bug 222302-Escalation 8453:Replications randomly

Console Server fail with avtar Error <8609>: Connection killed from GSAN
222791 Management CLONE: bug 222297-Escalation 8526:After upgrade to 1.2

Console Server BRM reports activity as Failed. Same activity on Avamar GUI is
successful
226368 Management CLONE: bug 225349-Escalation 22809:MC fails to initate

Console Server restore job when restore to new virtual machine option is
selected
223293 NDMP NetApp CLONE:Bug 223292 - Escalation 22780: Large NetApp backups
in Indio use excessive memory when "Preparing tables for
backup"
188594 Security CLONE: bug 188588-Escalation 7601:CVE
226439 Security CLONE: Escalation 23028:CVE-2015-0235
207069 Sharepoint CLONE: Escalation 8482:(Indio SP2)The component "****" was

not found in the writer components list!
206565 Web Restore CLONE: bug 206561-Escalation 8479:Customer created user

at client level. But while login to web-restore, we see error â
€œuser authentication failed. could not find an active client
associated with this account
Fixed problems for the Avamar 7.1 SP1 refresh build 145 release 29
Release Notes
Fixed problems for the Avamar 7.1 SP2 release

The following table lists fixed problems for the Avamar 7.1 SP2 release.
Table 6 Fixed problems for the Avamar 7.1 SP2 release

234486 Avamar Client Manager CLONE: bug 228062-esc 23268 - Customer doesn't
want to manually set subprocesstimeoutsecs for client
upgrades using client manager
202137 Avamar Desktop/ CLONE: esc 8239:Web Restore - SCO plugin backups
Laptop not listed after login
234525 Avamar Desktop/ CLONE: bug 188780-esc 7451:Security Vulnerability

Laptop Issue with token authorization on dtlt - Add avamar
client level authentication
234524 Avamar Desktop/ CLONE: bug 229062-esc 23154 - AD user has DTLT
Laptop browse message "Indexing the backed up data is
taking a long time"
234522 Avamar Desktop/ CLONE: bug 231778-esc 23563:DTLT restore fails avtar
Laptop Error <5195> Path not found
234523 Avamar Desktop/ CLONE: bug 231904-esc 23628:DTLT Restore not

Laptop working when using Internet Explorer v11
226436 Avamar Hardware CLONE: bug 225015-megaraid_sas bug in version

00.00.05.38; esc 8516:Tracking: Gen4s node crashed
with no visible hardware errors with page_fault
followed by megasas_reset_timer and scsi_times_out
226275 Avamar server CLONE: bug 203827-esc 8294:Four bytes in chd of

parity stripe fails cxor comparison after crunching
222550 Avamar server Esc 8471:Tracking esc for: Four bytes in chd of parity
stripe fails cxor comparison after crunching
186351 Avamar server CLONE: bug 58940-esc 7140: ERROR:

datastripe::traversebuffer:: during refcount phase of
GC
234604 Avamar server Esc 23786: update gsan backup locking code to
accommodate new client behavior for DD backups
226182 Avamar server CLONE: bug 199899-esc 8150 - Allow checkpoints to

retry or hold off if hashrefcheck is active
235525 Avamar server CLONE: bug 235146-esc 23910:hfscheck fails with

MSG_ERR_CGSAN_FAILED after an upgrade to
7.1.1-145
58362 Avamar server CLONE: bug 58361-esc 7033:backups cannot run

because metadata capacity is showing up as "∞"
234366 Avamar server CLONE: bug 231291-esc 23580:fscheck failed with

MSG_ERR_NODE_DOWN without any node offline issue

Release Notes

227005 Client CLONE: bug 227004-esc 23011: avtar may stall for up
to 10 minutes after DDR error in the final stages of a
backup
230344 Client CLONE: esc 23360:backup job cause Oracle 12c

database to crash
235010 Client CLONE: bug 234957-ESC23845: (Indio SP1 Refresh

HOTFIX) Avamar 7.1.101-145 SQL Plugin Failing to
Install
234854 Client CLONE: bug 234852-esc23824:(Indio SP2) Generic

service 'EMC Avamar Backup Agent resource for SQL-
US-P-MES019' could not be brought online (with error
'1060') during an attempt to open the service. Possible
causes include: the service is either not
198277 Client Esc 7973:(Indio SP1)Unable to view all cluster

resources in Avamar Cluster Wizard
204440 DB2 Plug-in CLONE: bug 203587-esc 8300:Restore are failing

because avamar queries looking for backup images are
taking too long
206097 DB2 Plug-in CLONE: bug 206092-esc 8087:Db2 CLI backups do not
show up in DPNsummary report
231391 Data Domain CLONE: bug 226000-esc 22818:ddrmaint patch:

Integration Backup to Data Domain is sealed on Avamar, but not
committed to Data Domain
224696 Data Domain Griffin4 - Update DDBoost Libraries to v3.0.2.0 build

Integration 480717 for DDOS 5.5.2.X and Avamar 7.1 Indio SP2
226339 Data Domain CLONE: bug 226271-esc 23082:Completed backups

Integration fail to write ddr_files.xml due to Data Domain stream
limits
225942 Exchange VSS Plug-in CLONE: Esc 22729: (Indio SP2) - avexvss , Avamar
Exchange incremental backup is causing wrong TX logs
to be truncated resulting in log gap error during next
incr backup
235087 Exchange VSS Plug-in CLONE:(Indio SP2) bug 235084-esc23821: WC -

Exchange VSS - SR 71012654 - Restore into RDB and
Flat File EDB restores fail with Avtar Error <5195>: Path
"ohcinmail06_00000000\N:\MAILBOX\DB9.edb" not
found in backup
230480 Exchange VSS Plug-in Esc 23221: (Indio SP2) Exchange 2013 backups failing
for servers hosting a 'suspended' copy of a database
228226 Exchange VSS Plug-in Esc 23259:(Indio SP2) Exchange GLR Browse taking
1hr 1/2

Release Notes

222494 Exchange VSS Plug-in CLONE: esc 7209:(Indio SP2)Exchange GLR operation
will mount the RDB but the operation never proceeds
to the browse phase and hangs
231284 Exchange VSS Plug-in CLONE(Indio SP2): bug 231283-esc23038: Exchange

GLR Browse for 2 mbxs gets avmapi error 0x80005010
224780 Exchange VSS Plug-in CLONE: bug 224778-esc 8495:(Indio SP2)Exchange

GLR fails to browse avmapi not starting
232579 Extended Retention Esc 23546:Assert errors in windows filesystem export

jobs after upgrade to 7.1.1-145
195705 MCCLI Guide DOCS: bug 61107-esc 7411:RFE: Improve mccli dd

show-prop --xml output
235259 Management Console Esc 23884 - Discrepancy between EM and MC GUI

Server Dashboard for total successful backups in "last 24
hours"
234142 Management Console CLONE: bug 234138-esc 23506:MCS crashing at initial

Server backups
231727 Management Console Esc 23476:Failed to initiate on-demand backups of

Server virtual clients
234999 Management Console CLONE: bug 234998-esc 23903 - why one client
Server schedule backup didn't start
234470 Management Console CLONE: bug 234466-esc 23871:Restore of individual

Server disks to “different existing VM” with “restore as new
disks” option fails with "no proxy" when target is a
different VC
234694 Management Console CLONE: bug 231964-esc 23220:"Clients - Unprotected"

Server report produces results which do not reflect its stated
purpose
236060 Management Console CLONE: esc 24030:Filter from Avamar GUI not working
Server properly for group, display replication jobs as well
206134 Management Console CLONE: bug 205494-esc 8087:Db2 CLI backups do not
Server show up in DPNsummary report
235397 Management Console CLONE: bug 234040-esc 23395:vAPP VM restore fails

Server with " VM creation failed during restore,create virtual
machine mcServiceResponse abort
230056 Management Console CLONE: bug 228692-esc 23220:"Clients - Unprotected"

Server report produces results which do not reflect its stated
purpose
224732 Management Console CLONE: bug 224731-esc 8152:NC - AER -

Server SR<65026826> - <Export of Avamar backup
proddb01scan.adweag.local/ Daily 4 30 AM-
proddb01scan_AEITP_AL_M-1409531400 from client /
Oracle/proddb01scan.adweag.local failed. Error
starting export task >

Release Notes

227450 NDMP Isilon Esc 23210: Isilon rollup - New bytes over 100% with
DD backend
229390 NDMP NetApp CLONE: esc 23374:NDMP restore completes without

error but files are missing "NDMP: RESTORE: cannot
create file"
228535 Replicator CLONE: bug 228527-esc 23244:Slow VMware Restore

Performance
229829 Replicator CLONE: bug 229827-esc 22903:Hyper-V GLR from DD

fail with - "Failed to Browse into the Virtual Machine"
pop-up message
231544 Replicator CLONE: bug 230995-esc 23527:Replication is

replicating a lot of clients with 0 progress bytes after
upgrading to 7.1.1-145
201274 Replicator CLONE: bug 201273 - esc 7745:SR 62628936 - /home

local folder is being excluded from the backup as soon
as an NFS mount is mounted as /HOME
229183 Replicator CLONE: bug 229181-esc 23278:replication will not run

with no encryption enabled
232184 Replicator CLONE: esc 23438:Replication Activity Progress Bytes

and New Bytes are ~10 x the values in Replications
logs
227527 Replicator CLONE: esc 23140:Oracle restore failing intermittently
223157 Replicator CLONE: esc 22740:Oracle backups failing on windows

if the service is started with double quotes in it
230573 Replicator CLONE: bug 230571-esc 23136:Assert errors with

export jobs of Mac OSX 10.10
226151 Replicator CLONE: bug 226148-esc 22973:SAP backups failing

when avtar connects to CTL port
233025 Replicator CLONE: esc 23702:Oracle backup failing with Warning

<0000>: [ctl_spawn] Workorder
"Oracle_Daily-1429122487077" non-zero exit status
code 255: The extended attributes are inconsistent
228054 Replicator CLONE: esc 23113:backend capacity report

discrepancy using "backendreport" command
223287 SQL Server Plug-in CLONE: esc 8500:(Indio SP2)Cluster Virtual Agent 7.1
spawns avtar using physical vardir instead of cluster
vardir
223343 SQL Server Plug-in CLONE: esc 8481:(Indio SP2)Cannot backup / browse
SQL 2005 32 bit instance on Windows 64 bit OS by
Avamar 7.1 (Provider load failure) 7.0 and older client -
work

Release Notes

229355 Security CLONE: esc 23297 -OpenSSL Vulnerabilities for 2015
CVE's
224249 VMware CLONE: bug 223186-esc 22772:All backups fail

problem with vcenter session id
Environment and system requirements

This following topics describe specific environment and system requirements.
Client, server, and platform compatibility

Details on client, server, and platform compatibility is available in the EMC Avamar
Compatibility and Interoperability Matrix on EMC Online Support at https://
support.EMC.com.
Support for the following operating system clients has been removed in this release:
l Windows XP
l Windows Server 2003
l RHEL Linux 4 x86 and x64
l SuSE Linux 9 x86 and x64
l Ubuntu Linux 11.04 and 11.10
l Debian Linux 5
l Mac OS X 10.6
For these operating systems, use Avamar 6.x clients and application plug-ins.
Client hardware requirements

Client hardware requirements are listed in each client user guide, such as the EMC Avamar
for Oracle User Guide, EMC Avamar for Windows Server User Guide, or EMC Avamar for SQL
Server User Guide. A full list of Avamar documentation is available in Documentation on
page 60.
Avamar Downloader Service operating system requirements

The Avamar Downloader Service is supported on Windows operating systems, including
Windows Server 2012 (64-bit), Windows Server 2008, Windows 8, Windows 7, and
Windows Vista.
Starting with release 7.1, the Avamar Downloader Service is no longer supported on
Windows XP or Windows Server 2003.
The EMC Avamar Administration Guide provides a list of supported operating systems for
the Avamar Downloader Service.
Server dependencies for client features

The following client features require specific versions of Avamar server software:

Release Notes
l Granular Level Recovery (GLR) with the Exchange VSS plug-in requires build 6.0.0-580
or later.
l The SharePoint VSS plug-in requires build 6.0.0-580 or later.
l The SQL Server plug-in requires release 6.1 or later.
l To store backups on a Data Domain system, you must use build 6.0.0-580 or later.
Data Domain system requirements

The EMC Avamar Compatibility and Interoperability Matrix provides details on supported DD
OS and DD Boost versions.
Avamar supports the Data Domain with Extended Retention feature on DD OS version
5.0.2.3 through 5.4.x, subject to the supported DD OS versions listed in the EMC Avamar
Compatibility and Interoperability Matrix.
Known problems and limitations

The following topics discuss known issues and limitations in this release of Avamar.
Temporary solutions are provided if they are available.
Avamar server known problems and limitations

The following list describes known problems for this release of the Avamar server.
46224 — Scheduled backups are missed during daylight savings time transitions
During days when Daylight Saving Time transitions occur, if you have backups
scheduled to run during the following times, the backups do not occur:
l For the Spring Daylight Saving Time transition, daily backups scheduled during
the hour from 2:00 a.m. through 2:59 a.m. do not occur.
l For the Autumn Daylight Saving Time transition, daily backup scheduled during
the hour from 1:00 a.m. through 1:59 a.m. do not occur.
The interim solution to this problem is to avoid scheduling backups during these
time ranges, or to perform an ad-hoc backup if the scheduled backup does not
occur.
58895 — Client disabled after restoring a replicated backup

When restoring a client's backup after a cascading replication, the client becomes
disabled even after activating the client from the Avamar system tray icon. Because
the client is disabled, the restore fails with the following error:
Cannot select a disabled or deactivated client
The client was originally attached to server _A. After a replication from server_A to
server_B and another replication from server_B to server_C, the client was moved to
server_C and activated from the Avamar system tray icon. A restore to the client now
attached to server_C failed because the client is disabled. Activation from the
Avamar system tray icon did not activate the client.
To resolve this issue, activate the client by using the Policy window in Avamar
Administrator.From the Policy Management tab, right-click the client and clear the
checkmark for Disable backups.
Avamar Administrator known problems and limitations

The following list describes known problems for this release of Avamar Administrator.
Data Domain system requirements 35

Release Notes
52801 — Progress Bytes column in the Activity Monitor displays different values from one
Level 0 backup to the next
The value that appears in the Progress Bytes column in the Activity Monitor for
backups with the Windows File System plug-in is different from one Level 0 backup
to the next for an unchanged backup set. The issue is a display issue only and does
not affect the validity of the backup itself.
57448 — Avamar appears in the Server column of the Activity Monitor during replication
of backup data on a Data Domain system
When you use Avamar replication to replicate backup data from a source Data
Domain system to a destination Data Domain system, Avamar appears in the Server
column in the Activity Monitor for the replication activity even though the backup
data is on a Data Domain system.
Avamar Client Manager known problems and limitations

There are no significant known problems for this release of Avamar Client Manager.
Avamar Config Checker known problems and limitations

The following list describes known problems and limitations with the Avamar Config
Checker.
57968 — Configuration check fails on an Exchange Server when the AvamarBackupUser
is the Exchange GLR service account
If you run the Avamar Config Checker on an Exchange Server and the Exchange GLR
service is running on the server as the AvamarBackupUser account, then the
configuration check fails.
To work around this issue, temporarily assign a different service account to the
Exchange GLR service while you run the Config Checker, and then reset the service
account to the AvamarBackupUser account after the check completes.
60806 — Config Checker exits unexpectedly during a SharePoint configuration check

when SharePoint is not installed
If you run a SharePoint configuration check on a server where SharePoint is not
installed, then the Avamar Config Checker exits unexpectedly.
To avoid this issue, run a SharePoint configuration check only on servers where
SharePoint is already installed.
Avamar Data Store Gen4 known problems and limitations

The following list describes known problems for Avamar Data Store Gen4.
Limitations when rerunning dpnnetutil
You cannot add or change replication and management parameters when rerunning
dpnnetutil on ADS Gen4 systems.
If you rerun dpnnetutil, the following prompt appears: Use existing
dpnnetutil configuration file? If you click Yes (the proper response),
then management and replication prompts are excluded in successive screens.
To work around this issue, delete the probe.xml file in the /usr/local/
avamar/var directory before you rerun dpnnetutil.

Release Notes
Changing subnets is not allowed on single-node servers

You cannot use dpnnetutil to change subnets in a postinstallation single-node
server environment. The dpnnetutil utility initially allows you to change the
subnet IP address, but an error message appears later that directs you to return the
configuration to its original state. To work around this issue:
l Run a nodedb update if command in the following form:
nodedb update if --addr=old_ip_address --new-
addr=new_ip_address --new-nwgrp=network_id
l Manually update the configurations of network interfaces, such as /etc/
sysconfig/network/ifcfg-eth0.
l Manually edit the contents of /etc/hosts.
l Update the configurations of the Avamar subsystems (that is, gsan, mcs, ems).
Avamar Desktop/Laptop known problems and limitations

The following list describes known problems for this release of Avamar Desktop/Laptop.
39138 — Some Mac and Linux users cannot restore an entire directory structure to the
original location
Restore fails when all of the following are true:
l A user logs in to a Mac or Linux computer with a user account that does not have
administrative privileges on that computer.
l The user logs in to the Avamar Desktop/Laptop web UI using Avamar
authentication.
l On the Browse page, the user selects the entire directory structure for restore.
l The user does not select a new restore location.
To work around this problem, do either of the following:
l Restore to a new location.
l Restore less than all of the directory structure. For example, in the restore set,
clear one file from the lowest directory.
Avamar Installation Manager known problems and limitations

The following list describes known problems for this release of Avamar Installation
Manager.
200207 — "Configuring Website if required Failed" error appears occasionally during
installation
When you are performing a new installation of the Avamar server software, a failure
error sometimes occurs during the Configuring Website if required task in Avamar
Installation Manager.
To work around this issue, click Retry Current Task to retry the installation. The task
completes successfully upon the retry.
Avamar Virtual Edition known problems and limitations

The following list describes known problems for this release of the Avamar Virtual
Edition.
Avamar Desktop/Laptop known problems and limitations 37

Release Notes
228100 — Workflow fails at validating Linux root password

The workflow will fail intermittently at validating root password when the user does
NOT select the Save button at the User Input Page for avinstaller.
To workaround this problem, select Save before continuing with the workflow.
Avamar Plug-in for vSphere Web Client known problems and limitations
There are no significant known problems for this release of the Avamar Plug-in for the
vSphere Web client.
Avamar Web Restore known problems and limitations

The following list describes known problems for this release of Avamar Web Restore.
55314 — Restore of files with special characters in file name fails when Avamar server
LANG variable is not set
When the LANG variable is not set on an Avamar server, using Avamar Web Restore to
restore a file with special characters in the file name fails. To fix this issue, set the
LANG variable in /etc/locale.conf and reboot the Avamar server.
58788 — UI does not render properly on Internet Explorer 11 browser
High Security setting in Internet Explorer 11 prevents rendering of JavaScript
commands in the Avamar Web Restore pages. To workaround this issue add the
Avamar Web Restore server to the trusted sites list in Internet Explorer.
59001 — Restore of large number of files fails
Users cannot restore a large number of files through Avamar Web Restore. Limit each
restore task to less than 200 files.
Data Domain system integration known problems and limitations

The following list describes known problems for this release of Avamar with Data Domain
system integration.
39003 — Browsing VMware backups stored on Data Domain systems may fail
When browsing VMware backups stored on Data Domain systems for FLR, after
browsing VMware backups on one Data Domain system, attempts to browse VMware
backups on another Data Domain system fail with the following error:
axionfs Error <10588>: Failed to get block data from DDR
stream, stream index:12, DDR stream: -1, DDR result code:
5008, desc: invalid argument
The interim solution to this problem is to log in to the proxy and restart the axionfs
service.
46433 — Original Bytes are displayed as twice the original size

The Original Bytes value appears as twice the original size when you execute the
Data Domain filesys show compression command is executed in the Avamar
namespace on the Data Domain system.
51085 — New Bytes % displays 0% until backup is complete
When performing file system backups to a Data Domain system, the New Bytes %
field displays 0% until the backup completes.
51684 — New Bytes % incorrect for replicated VMware image backups
When performing replication of VMware image backups that are stored on a Data
Domain system, the New Bytes % value is reported incorrectly.

Release Notes
53567 — hfscheck fails after clients are removed from the /REPLICATE domain and
then re-replicated
When you remove clients from the /REPLICATE domain and the client backups are
on a Data Domain system, the garbage collection process removes the replicated
backup files from the Data Domain system that is the replication destination. If the
client is then replicated to the Data Domain system again, subsequent hfschecks
fail with a MSG_ERR_DDR_ERROR error.
188526 — 100% CPU usage from avtar.bin on the Avamar server after restore fails
When you restore a backup from a Data Domain system with the Data Domain
encryption method set to High or Default, and the Avamar server connects to the
configured Data Domain system over a WAN, the Avamar server might experience
continuous 100% CPU usage from the avtar.bin process, even when no other
processes are running. This issue occurs because some WAN networks do not allow
pass-through of encrypted data.
To resolve this issue, log in to the Avamar server as root and type kill -9
avtar.bin to stop the avtar.bin process.
Known problems and limitations for all backup clients and plug-ins
The following list describes known problems for this release of all backup clients and
plug-ins.
1403 — Backups longer than seven days might fail due to session ticket expiration
Backups that take longer than seven days to complete might fail if they are forced to
re-establish a connection with the server and their session ticket has expired.
However, the data that was backed up is not lost. To complete the process, perform
another backup.
32873 — Special ACLs are not supported
The avtar process does not support backup or restore of special UNIX and Linux
ACLs such as setuid and setgid bits, or mandatory file lock bits in newer
versions of Linux.
52496 — Cluster Configuration Tool fails to activate virtual cluster clients in dual stack
environments
In a dual stack environment, when the Avamar server’s IPv6 address is used during
configuration with the Avamar Cluster Configuration Tool, the Cluster Configuration
Tool fails to properly activate virtual cluster clients.
The interim solution to this problem is to use the Cluster Configuration Tool to create
the cluster client, but clear the Bring the cluster client online and activate it with the
Avamar server checkbox. Then manually create the virtual cluster client and with
Avamar Administrator, and in Policy Management, edit the client and select the
Activated checkbox in the Edit Client dialog box.
56606 — Level 1 backup to Data Domain with over 16 critical disks may default to level 0
After a level 0 backup has been performed for a client with more than 16 critical
disks, cache file information for one or more of the disks may no longer be available,
and subsequent level 1 backups are performed as level 0.
AIX, FreeBSD, HP-UX, Linux, CentOS, and Solaris client known problems and
limitations
The following list describes known problems for this release of the Avamar clients for AIX,
FreeBSD, HP-UX, Linux, and Solaris.
Known problems and limitations for all backup clients and plug-ins 39
Release Notes
26077 — Push upgrade on Linux fails for non-default installation location

Using Avamar upgrade to push an Avamar client upgrade to a Red Hat Enterprise
Linux or SuSE Linux Enterprise Server client fails when the Avamar client software is
installed in a non-default location. The use of the rpm option --relocate to
install the Avamar client in a non-default location causes subsequent push upgrades
to fail.
IBM DB2 plug-in known problems and limitations

There are no significant known problems for this release of the Avamar Plug-in for DB2.
IBM Lotus Domino plug-in known problems and limitations

The following list describes known problems for this release of the Avamar Plug-in for
Lotus Domino.
206870 — Installation packages for RHEL7
The Avamar server Downloads page does not include specific Lotus Domino plug-in
installation packages for RHEL7. Download and use one of the following installation
packages for SLES 11 systems from the Linux for x86 (64bit) > Red Hat Enterprise
Linux 6 path on the Downloads page:
l AvamarLotus-dual-linux-sles11-x86-version.rpm
l AvamarLotus-linux-sles11-x86-version.rpm
l AvamarLotus-linux-sles11-x86_64-version.rpm
223120 — Cannot use the Cluster Configuration Tool to uninstall a cluster client
The Cluster Configuration Tool returns the following message when you uninstall a
cluster client:
There are one or more invalid fields on the page
This message appears on the Cluster Services page.
To work around this issue, perform the following steps:
1. Log in to the Windows computer as an administrator.
2. Delete the cluster group by using the Failover Cluster Manager.
3. Delete the Cluster services from all nodes by using the sc delete
service_name command.
4. Manually unregister the client from the Avamar server:
a. In Avamar Administrator, click the Policy launcher button.
The Policy window appears.
b. Click the Clients tab.
c. In the tree, select the client to unregister.
d. Click the Edit button.
The Edit Client window appears.
e. Clear the Activated checkbox.
f. Click OK.

Release Notes
Microsoft Exchange VSS plug-in known problems and limitations

Exchange VSS.
53773 — Cannot browse Exchange Information Store after upgrade to Exchange 2013
CU2
If a database in Active Directory Domain Services (ADDS) is corrupt, when you try to
browse that database in ADDS it will fail. When you browse the Exchange
Information Store it will time out and no databases will be displayed. As an interim
solution, if browsing the Exchange Information Store fails, determine which
database is corrupt using the Get-MailboxDatabase command from Exchange
Management Shell. This will return an error similar to:
The Exchange server for the database object "Database1"
wasn't found in Active Directory Domain Services. The
object may be corrupted.
Delete the corrupt database and browsing will be successful.
54465 — Restore of an incremental backup fails after restore a full backup

If you restore a full backup of an Exchange database and then you restore a
subsequent incremental backup of the database, the restore fails.
To work around this issue, rerun the restore and use the Move logs path plug-in
option to move the existing log files to a different directory.
61201 — GLR issues occur when you configure IPv6 after you create and register the
AvamarBackupUser account
Only one message restores during GLR, even if you select multiple messages, when
the following scenario occurs:
1. You install Avamar client software and configure the AvamarBackupUser account
on an Exchange server.
2. You install Avamar client software on other Exchange servers in the environment
that use the same domain controller, and you register with the
AvamarBackupUser account that you created on the first Exchange server.
3. You configure IPv6 on the first Exchange server and restart the server, but you do
not complete the IPv6 configuration by using the "re-enable IPv6" option from
http://support.microsoft.com/kb/929852.
4. You back up the Exchange database on one or more of the Exchange servers in
the environment.
5. You attempt to perform GLR of multiple email messages.
To resolve this issue, follow the steps in KB article 929852 on the Microsoft support
website at http://support.microsoft.com/kb/929852 to re-enable IPv6 on the first
Exchange server, and then perform the GLR again.
61256 — Restore of an Exchange 2007 backup completes with an error when the
database name contains special characters
You can use the Exchange VSS plug-in to back up an Exchange 2007 database when
the database name contains special characters, such as ! @ # $ % ^ &* ( ) { } [ ].
However, when you restore the database, the restore completes with an error that
the path to the database is not found.
To avoid this issue, do not use special characters in Exchange 2007 database
names.
Microsoft Exchange VSS plug-in known problems and limitations 41

Release Notes
Microsoft Hyper-V VSS plug-in known problems and limitations

Hyper-V VSS.
37177 — Conflict between Hyper-V host and guest backup application
If you install backup applications on a Hyper-V virtual machine and you perform
image-level backups with the Hyper-V VSS plug-in, then the two backups may
conflict.
To work around this issue, exclude virtual machines with backup applications from
image-level backups.
188679 — Restore takes a long time when restoring virtual machines on multiple CSVs in
an environment with multiple proxies
When you restore multiple virtual machines on multiple CSVs in an environment with
multiple proxies, the restore might take a long time.
To improve restore performance, ensure that the primary proxy node is the owner of
the CSV to which you restore the virtual machines.
189788 — Multi-stream backups by virtual machine from SMB to a Data Domain system
fail
If you enable multi-streaming by virtual machine to back up a virtual machine on an
SMB file share to a Data Domain system, the first backup completes successfully.
However, subsequent backups fail.
To work around this issue, disable multi-streaming for backups of virtual machines
on SMB file shares to a Data Domain system.
Microsoft SharePoint VSS plug-in known problems and limitations

SharePoint VSS.
190158 — GLR fails when the backup data is stored on a Data Domain system available
over a WAN
Granular level recovery (GLR) fails after a significant amount of processing time when
you store SharePoint backups on a Data Domain system over a WAN. An Error in
mounting disk message appears, and a virtual drive icon is visible in Windows
Explorer. However, you cannot browse the virtual drive for data to restore.
To work around this issue, restore the backup to a different location as files, and
then use a third-party recovery tool, such as Kroll Ontrack PowerControls, to restore
specific data from the backup.
191035 — Backup fails for a SharePoint 2007 database with Unicode characters in the
name
If a SharePoint 2007 database name contains Unicode characters, the SharePoint
VSS plug-in cannot back up the database. The backup of the farm completes with
exceptions and reports that the database could not be found.
This issue does not occur in SharePoint 2010 environments.

Release Notes
Microsoft SQL Server plug-in known problems and limitations

The following list describes known problems for this release of the Avamar Plug-in for SQL
Server.
19575 — Tail-log backup of a small amount of data may result in data not available
If the tail-log backup fails for any reason during a restore, then an error message
appears and the restore is aborted. However, if the amount of data added or
changed since the most recent backup is very small (less than about 25 MB) then
SQL Server may not be able to retain the information. The recovery exits with an
error, and the tail-log backup is not available.
49416 — Restore of differential backup after database is removed from availability group
may fail
After a database is removed from an availability group, restores from differential
backups of the database may fail.
52299 — Restore from a Data Domain system fails after upgrade
If you store backups on a Data Domain system, then you must perform a full backup
after you upgrade the SQL Server plug-in to a newer version. Otherwise, restore fails
when you restore from either a tail-log backup or an incremental backup that occurs
after the upgrade.
61026 — Restore of a differential backup fails when the transaction log is truncated from
a non-Avamar backup and you skip log gap detection for Avamar backups
Restore of a differential backup fails if you skip log gap detection when you back up
SQL Server data with the Avamar Plug-in for SQL Server, and you are also performing
transaction log backups with Microsoft SQL Server tools that truncate the transaction
log.
To work around this issue, restore the most recent Avamar full backup before the log
truncation and select the NORECOVERY recovery option; restore the database from
the differential backup to a file by using the Avamar Plug-in for SQL Server; and then
use SQL Server management tools to restore the database.
Microsoft Windows client known problems and limitations

The following list describes known problems for this release of the Avamar Client for
Windows.
26802 — Office XML files may need special flag to restore correctly
If you back up an Office XML file (.docx, .xlsx), then an error message similar to the
following may appear when you restore the file and open it:
Excel cannot open the file 'Spreadsheet.xlsx' because the file
format
or file extension is not valid...
or
The Office Open XML file filename.docx cannot be opened because
there are problems
with the contents, Word found unreadable content in document
file.docx.
Do you want to recover the contents of this document?
If you trust the source, click Yes.
If you open the file anyway, the file may be empty or unusable. When this occurs,
rerun the restore using the --deflateofficexml=false flag in the Restore
Command Line Options dialog box. After restore, when you open the file you may get
the same Office error message, but if you click OK to open the file anyway, the file
should open correctly.
Microsoft SQL Server plug-in known problems and limitations 43

Release Notes
58121 — Restore of a folder with 1,000,000 files fails on 32-bit operating system
If you restore a folder that contains a significant number of files, such as 1,000,000
files, on a 32-bit Windows operating system, then restore fails.
To work around this issue, restore the parent folder of the folder with the significant
number of files. For example, if F:\folder\large_folder contains 1,000,000
files, then restore F:\folder instead of F:\folder\large_folder.
186767 — Browsing for data to restore with the Cluster File Server plug-in returns no file
versions
If you are restoring data with the Windows Cluster File Server plug-in and you browse
for data on the By File/Folder tab on the Restore tab in the Backup, Restore and
Manage window, the system indicates that there is no version history for the
selected data.
To work around this issue, type a path to the data by using a share name, or select
the data to restore by using the By Date tab instead of the By File/Folder tab.
NDMP Accelerator known problems and limitations

The following list describes known problems for this release of the Avamar NDMP
Accelerator.
35153 — Redirected restore of multiple volumes does not work
Redirected restore of multiple volumes fails and results in the following error:
avndmp Error <11803>: [avndmp_assist] Unable to redirect
multiple volumes. Please restore them separately
To work around this issue, restore each volume separately.
60389 — Capacity issues occur when Isilon fails to delete snapshots for incremental
backups
When you enable snapshot-based incremental backups for one or more directories
on an Isilon system, OneFS does not delete the snapshots after incremental backups
occur. Snapshot-based incremental backups are also known as the Faster
Incrementals feature. The accumulation of snapshots can result in capacity issues
on the Isilon system. This is a known issue in OneFS that will be fixed in an
upcoming release.
To work around this issue, perform the steps in the EMC Isilon OneFS Backup and
Recovery Guide to view and delete snapshots for snapshot-based incremental
backups.
189337 — Redirected restore of the Windows summary file completes without errors, but
the file is not restored
If you restore the Windows summary file to a different location on an EMC Celerra
device, the restore completes without errors, but the file is not restored.
Novell NetWare client known problems and limitations

The following list describes known problems for the Avamar Client for NetWare.

Release Notes
30603 — Pre-6.1 client incompatibilities with 6.1 and later servers

Beginning with version 6.1, Avamar servers use a strengthened FIPS 140-2 compliant
SSL/TLS protocol that is incompatible with earlier versions of the Avamar Client for
NetWare. In most cases, if an earlier version client attempts to connect to an Avamar
6.1 or 7.0 server, then the connection is rejected by the server.
This situation can be remedied by any of the following actions:
l Upgrade the Avamar Client for NetWare software to release 6.1.
l Use unencrypted connections to communicate with the server.
l Use encrypted connections but disable FIPS mode on the server.
19822 — Stunnel limitation

There is a known issue with STunnel.NLM in which 656 bytes of memory is
allocated but not released. The NetWare operating system reclaims this memory
when STunnel unloads.
12641 — Maximum backup size and number of files
For optimal performance, limit backups with the Avamar Client for NetWare to a
maximum total size of 500 GB and less than 1 million files.
Furthermore, for best results, limit the maximum hash cache size to 10 MB. This
behavior is controlled by the Maximum client hash cache size (MBs) plug-in option.
Oracle database plug-in known problems and limitations

Oracle.
52700 — Point-in-time recovery of a pluggable database (PDB) fails
A point-in-time recovery of a PDB, which uses a manual channel, fails with the
following errors:
RMAN-00571:
================================================
RMAN-00569: ========== ERROR MESSAGE STACK FOLLOWS
===========
RMAN-00571:
================================================
RMAN-03002: failure of recover command at 07/05/2013
01:00:29
RMAN-03015: error occurred in stored script Memory Script
RMAN-06034: at least 1 channel must be allocated to execute
this command
This issue is a known bug in Oracle 12C: Bug 17080042 : RMAN-6034 POINT IN TIME
PDB OR TABLE RECOVERY ERRORS WITH RMAN MANUAL CHANNELS.
To work around this problem, use automatic channels for a point-in-time recovery of
a PDB.
Oracle database plug-in known problems and limitations 45

Release Notes
200018 — AvamarRMAN installation packages for SUSE Linux Enterprise Server (SLES) 10
The Avamar server Downloads page does not include specific AvamarRMAN
installation packages for SLES 10. Download and use the installation packages for
Red Hat Enterprise Linux 5 for SLES systems:
l For SLES 10 (64-bit), select Linux for x86 (64 bit) > Red Hat Enterprise Linux 5 >
Red Hat Enterprise Linux 5 > AvamarRMAN-linux-rhel4-x86_64-7.1.100-
build.rpm.
l For SLES 10 (32-bit), select Linux for x86 (32 bit) > Red Hat Enterprise Linux 5 >
Red Hat Enterprise Linux 5 > AvamarRMAN-linux-rhel4-x86-7.1.100-build.rpm.
Replication known problems and limitations

The following list describes known problems and limitations with replication for this
Avamar release.
61278 — Root-to-root replication overwrites Avamar server credentials
When you perform root-to-root replication from one Avamar server to another, the
replication process overwrites the server credentials on the target Avamar server
with the credentials from the source Avamar server.
To avoid this issue, use the same credentials on both the source and target Avamar
servers.
To resolve this issue if it occurs, reset the credentials to the original values on the
target Avamar server after replication.
192169 — Incorrect statistics appear for replication of Avamar backup data on a Data
Domain system
When you replicate Avamar backup data from one Data Domain system to another
Data Domain system, incorrect statistics appear for the file total in the avtar log file
and for progress bytes in the Activity Monitor in Avamar Administrator.
198140 — Replication fails when you specify an IPv6 address as the source server
hostname
Policy-based replication fails when you specify an IPv6 address as the hostname for
a source server either in Avamar Administrator or on the avrepl command line. The
failure occurs because the colons (:) in the IPv6 address are illegal characters for
Avamar domain names, which are created automatically on the destination Avamar
server during replication.
To work around this issue, specify the fully qualified domain name (FQDN) of the
source server instead of the IPv6 address. Alternatively, specify the --
[replscript]dpnname option with a value of the FQDN of the source server
either on the command line or in the Enter Attribute and Enter Attribute Value boxes
for the replication plug-in options.
207299 — Replicate button on the Policy Management tab of the Policy window is
dimmed for clients
The Replicate button on the Policy Management tab of the Policy window is dimmed
for clients.
To work around this issue and initiate an on-demand replication of a client in the
Policy window, right-click the client and select Replicate Client Now.
SAP with Oracle plug-in known problems and limitations

The following list describes known problems for this release of the Avamar Plug-in for SAP
with Oracle.

Release Notes
51870 — Oracle Optimized Deduplication option not supported with Data Domain
When backing up a SAP with Oracle database to a Data Domain system, the Oracle
Optimized Deduplication option is not supported.
Sybase ASE plug-in known problems and limitations

Sybase ASE.
26375 — Parallel restore might fail with Sybase ASE releases earlier than 15.0.2
With a Sybase ASE release earlier than 15.0.2, a Sybase plug-in restore with a
parallelism value greater than 1 might fail with the following error:
Error from server server_name: Msg 937, Level 14, State 1
Database 'database_name' is unavailable. It is undergoing
LOAD DATABASE.
This issue is due to a Sybase ASE defect (CR 467447) that is fixed in Sybase ASE
release 15.0.2 ESD 1 and later.
To work around this issue, perform one of the following tasks:
l Ensure that the parallelism value is set to 1 during a Sybase restore.
l Upgrade the Sybase ASE server to release 15.0.2 ESD 1 or later.
56299 — Sybase operations fail with Sybase ASE network password encryption
If Sybase ASE network password encryption is enabled, a Sybase plug-in backup or
restore fails with the following error:
avsybase Error <16177>: Adaptive Server requires encryption
of the login password on the network.
To work around this issue, disable the Sybase network password encryption by
running the following commands:
$
isql -X
1> sp_configure 'net password encryption reqd',0
2> go
Upgrade known problems and limitations

The following list describes known problems and limitations for upgrading to this release
of Avamar.
58586 — NDMP accelerator backup fails to complete if a push upgrade starts while the
backup is in progress
If an NDMP accelerator backup is in progress when a push upgrade starts, then the
upgrade may complete with errors but will be retried. However, the backup fails to
complete. If this issue occurs, retry the backup after the upgrade completes.
To work around this issue, perform a push upgrade to an NDMP accelerator only
when backups are not in progress.
Sybase ASE plug-in known problems and limitations 47

Release Notes
202146 — snmpwalk command for the Avamar SNMP sub-agent fails to display results
after upgrade
If you issue an snmpwalk command for the Avamar SNMP sub-agent (AVAMAR-
MCS-MIB) after you upgrade the Avamar server software, the command returns no
results.
To resolve this issue:
1. Rerun the avsetup_snmp command line utility to configure the Net-SNMP
agent to communicate with the Avamar server by using the Avamar SNMP sub-
agent. The EMC Avamar Administration Guide provides instructions.
2. Start the Avamar SNMP sub-agent by typing mcsnmp start.
VMware known problems and limitations

The following list describes known problems for this release of Avamar for VMware image
backup.
48465 — Restore to a new virtual machine operation fails if Storage vMotion occurs
during the restore
When restoring data to a new virtual machine, if storage migration is triggered during
the restore, the restore will fail with an error message, "vSphere Task failed:
'Detected an invalid snapshot configuration.'”

Release Notes
190128 — 7.0 proxy compatibility with upgraded 7.1 servers

Each 7.0 proxy hosts eight separate avagent plug-ins, each of which can process
one backup or restore job. Each 7.0 proxy can therefore process as many as eight
simultaneous backup or restore jobs.
Each 7.1 proxy hosts a single avagent plug-in, but that single avagent plug-in
can perform up to eight simultaneous backup or restore jobs. The maximum
simultaneous job limitation is still eight.
In order to precisely control the maximum number of simultaneous jobs allowed for
each proxy, Avamar 7.1 introduced a new setting in mcserver.xml:
max_jobs_per_proxy. The default setting is 8.
You cannot use both 7.0 and 7.1 proxies with the same Avamar server. This is
because the Avamar server max_jobs_per_proxy setting is global. It applies to
every proxy in the environment. Therefore, in a heterogeneous environment
comprising both 7.0 and 7.1 proxies, a max_jobs_per_proxy=8 setting would
work fine for 7.1 proxies, but might result in 7.0 proxies attempting to process as
many as 64 simultaneous backup or restore jobs (that is, eight jobs for each of the
eight avagent processes). This might cause degraded performance. Similarly, a
max_jobs_per_proxy=1 setting would work fine for 7.0 proxies, but would limit
7.1 proxies to performing only one backup or restore job at a time. This would
drastically underutilize each 7.1 proxy.
These proxy compatibility issues only affect customers who upgrade their Avamar
7.0 servers to 7.1. Customers deploying new 7.1 servers in their environments will
deploy new 7.1 proxies. Customers using existing 7.0 servers will already have 7.0
proxies in their environment, and can deploy additional 7.0 proxies to support that
server.
EMC suggests the following solutions for these proxy compatibility issues:
l If 7.1 proxies will be deployed, the preferred solution is to upgrade all existing
7.0 proxies to 7.1.
l If new 7.1 proxies will never be simultaneously deployed with the existing 7.0
proxies, change the mcserver.xml max_jobs_per_proxy setting to 1.
Supportability package known problems and limitations

The following list describes known problems for this release of Avamar supportability
packages.
33892 — Unnecessary Upgrade Client Downloads package option
The Upgrade Client Downloads package presents a Show advanced settings option
on the installation page called skip upgrading client download rpms.
If you select the Values checkbox and click Continue, then client downloads are not
upgraded on the system and the package no longer appears in Avamar Enterprise
Manager or Avamar Installation Manager.
If you clear the Values checkbox and click Continue, then the client downloads
upgrade works as designed.
To avoid the problem, do not select Show advanced settings on the installation
page.
Supportability package known problems and limitations 49

Release Notes
International language support

These sections provide important information about international language support in
Avamar 7.1.
International language support in Windows environments

Supported languages for Windows environments include:
l Arabic l Japanese
l Bulgarian l Korean
l Chinese (Simplified and Traditional) l Latvian
l Croatian l Lithuanian
l Czech l Norwegian
l Danish l Polish
l Dutch l Portuguese (Brazilian)
l Estonian l Romanian
l Finnish l Russian
l French l Slovak
l German l Slovenian
l Greek l Spanish (Iberian and Latin American)
l Hebrew l Swedish
l Hungarian l Turkish
l Italian
The following table describes additional international language support details in

Windows environments.
Table 7 Windows environment international language support
Windows data type International language support details

Windows files and You can back up and restore individual files and folders with file and
folders folder names in local languages.
File and folders names appear in the local language in Avamar
Administrator and Avamar Web Restore.
Microsoft Exchange You can back up and restore databases with the database name in
databases supported local languages.
Microsoft Exchange You can back up and restore individual folders and messages with the
folders and messages folder or message name in supported local languages.
Microsoft SQL Server You can back up and restore databases with the database name in
databases supported local languages.

Release Notes
International language support in UNIX/Linux environments

Supported languages for UNIX and Linux environments include:
l Arabic l Japanese
l Bulgarian l Korean
l Chinese (Simplified and Traditional) l Latvian
l Croatian l Lithuanian
l Czech l Norwegian
l Danish l Polish
l Dutch l Portuguese (Brazilian)
l Estonian l Romanian
l Finnish l Russian
l French l Slovak
l German l Slovenian
l Greek l Spanish (Iberian and Latin American)
l Hebrew l Swedish
l Hungarian l Turkish
l Italian
The following table describes additional international language support details in UNIX
and Linux environments.
Table 8 Windows environment international language support
Encoding International language support details

EUC-JP You can back up and recover EUC-JP encoded files and directories with names in the
Japanese language on Solaris.
Note
EUC-JP encoded file and directory names do not render correctly in either Avamar
Administrator or Avamar Web Restore. This issue does not apply to the client web UI
available through Avamar Desktop/Laptop.
UTF You can back up and restore individual UTF-encoded files and directories with file
and directory names in supported local languages.
File and directory names appear in the local language in Avamar Administrator and
Avamar Web Restore.
Known limitations of local language support

Keep in mind the following known limitations of local language support:
l Cross-platform redirected restore of files and directories with international character
set names is not supported.
International language support in UNIX/Linux environments 51

Release Notes
l Client machine hostnames must consist entirely of ASCII characters.

l The client software installation path must consist entirely of ASCII characters.
l Policy objects (such as, users, groups, datasets, schedules, retention policies,
notification profiles, and so forth) must consist entirely of ASCII characters.
l Log files do not correctly render non-ASCII characters.
l Error, warning, and informational messages incorrectly render non-ASCII characters,
both to the screen and to log files.
l Log files based on user-defined names (for example, database names) do not work
correctly.
l You cannot use non-ASCII characters in options and flags. If a flag or option takes a
file, folder, or identifier (for example, a database name) then that option is only
assured to work for ASCII names.
l Sorting is not localized. Sorting is strictly by byte-ordinal value.
l You cannot enter local language characters in the Avamar user interface using a
keyboard.
l The Avamar Management Console Command Line Interface (MCCLI) and avtar
support only ASCII arguments on the command line.
Restore of international characters with Avamar Web Restore

The Avamar Web Restore feature restores directories or multiple files in the form of a Zip
file. When you unzip the Zip file, file and directory names with international characters
might not restore properly due to inherent limitations in some Zip utilities.
To correctly restore files with international characters by using the Avamar Web Restore
feature, use a Zip utility that fully supports international characters. Examples of Zip
utilities that have been confirmed to work properly include:
l Winrar 3.80 or later
l Winzip 12.0 or later
l 7zip 4.65 or later
Also, do not use Microsoft Windows compressed folders with the Avamar Web Restore
feature, as it is known that these compressed folders do not reliably handle international
characters.
Support for non-UTF8 locales in the Management Console

Avamar includes support for browsing non-UTF8 file systems from the Management
Console. The following Java character sets are supported:
Big5 Big5-HKSCS COMPOUND_TEXT

EUC-JP EUC-KR GB18030
GB2312 GBK IBM-Thai
IBM00858 IBM01140 IBM01141
IBM01142 IBM01143 IBM01144
IBM01145 IBM01146 IBM01147
IBM01148 IBM01149 IBM037
IBM1026 IBM1047 IBM273

Release Notes

ISO-2022-CN ISO-2022-JP ISO-2022-JP-2
ISO-2022-KR ISO-8859-1 ISO-8859-13
ISO-8859-15 ISO-8859-2 ISO-8859-3
ISO-8859-4 ISO-8859-5 ISO-8859-6
ISO-8859-7 ISO-8859-8 ISO-8859-9
JIS_X0201 JIS_X0212-1990 KOI8-R
KOI8-U Shift_JIS TIS-620
US-ASCII UTF-16 UTF-16BE
UTF-16LE UTF-32 UTF-32BE
UTF-32LE UTF-8 windows-1250
windows-1251 windows-1252 windows-1253
windows-1254 windows-1255 windows-1256
windows-1257 windows-1258 windows-31j
x-Big5-Solaris x-euc-jp-linux x-EUC-TW
x-eucJP-Open x-IBM1006 x-IBM1025
x-IBM1046 x-IBM1097 x-IBM1098
x-IBM939 x-IBM942 x-IBM942C
x-IBM943 x-IBM943C x-IBM948
x-IBM949 x-IBM949C x-IBM950
x-IBM964 x-IBM970 x-ISCII91
x-ISO-2022-CN-CNS x-ISO-2022-CN-GB x-iso-8859-11
x-JIS0208 x-JISAutoDetect x-Johab
Support for non-UTF8 locales in the Management Console 53

Release Notes
x-MacArabic x-MacCentralEurope x-MacCroatian

x-MacCyrillic x-MacDingbat x-MacGreek
x-MacHebrew x-MacIceland x-MacRoman
x-MacRomania x-MacSymbol x-MacThai
x-MacTurkish x-MacUkraine x-MS932_0213
x-MS950-HKSCS x-mswin-936 x-PCK
x-SJIS_0213 x-UTF-16LE-BOM X-UTF-32BE-BOM
X-UTF-32LE-BOM x-windows-50220 x-windows-50221
x-windows-874 x-windows-949 x-windows-950
x-windows-iso2022jp
Technical notes
This section describes important notes and tips for using Avamar 7.1.
Avamar server technical notes

The following technical notes apply to the Avamar server.
Remove test data
Before starting the server or starting a new node for the first time, ensure that all test data
has been removed from /data*/partitions. In particular, if you ran disk tests before
startup, you might need to delete directories named QA.
Do not use the avmgr command

Improper use of the avmgr command line utility can destroy all access to data in the
Avamar system. Use this command only at the explicit direction of EMC Customer Service.
Vulnerability scanning
As part of every Avamar release, the product is scanned for vulnerabilities using at least
two common vulnerability assessments tools. This release was scanned with Foundstone
and Nessus. The Avamar solution has also been scanned by various customers by using
tools such as eEye Retina without issue. However, it is possible that the usage of other
port/vulnerability scanners might cause disruption to normal operation of the Avamar
server. Therefore, it might be necessary to disable scanning of the Avamar server if
problems occur.
Maximum number of concurrent connections for each storage node
The maximum number of concurrent connections for each storage node on the Avamar
server depends on the Avamar Data Store version. For Gen4 and Gen4s storage nodes,
the maximum is 72. For Gen3 storage nodes and Avamar Virtual Edition systems, the
maximum is 27.
VMware image proxies are not available for backups when they are in sleep mode and
you restart the MCS
If you stop the MCS and do not restart the MCS within five minutes, then VMware image
proxies go into a sleep mode for 40 minutes. When you restart the MCS, it might take
some time until all proxies reconnect to the MCS and are available for backups. This
issue can occur when performing backups after a rollback.

Release Notes
To ensure that all proxies are available, open the avagent.log file on each proxy, and
ensure that the following messages appear at the bottom of the log:
yyyy-mm-dd hh:mm:ss avagent Info <5964>: Requesting work from
10.2.345.678
yyyy-mm-dd hh:mm:ss avagent Info <5264>: Workorder received:
sleep
yyyy-mm-dd hh:mm:ss avagent Info <5996>: Sleeping 15 seconds
The messages indicate that the proxy can connect to the MCS. The avagent.log file is
available in the /usr/local/avamarclient/var directory.
AMS replication after an IP address change in a dual-stack network environment

If you change the IP address that you use for replication by switching from IPv4 to IPv6 or
from IPv6 to IPv4 in a dual-stack network environment with Avamar and one or more Data
Domain systems, then the first replication after the change uses Automated
Multistreaming (AMS) replication. AMS is also known as ninja chopping replication (NCR)
or ninja slicing replication. Subsequent replications use Virtual Synthetic Replication
(VSR).
Avamar Data Store Gen4x performance expectations

In certain circumstances, an Avamar multi-node server must rebuild the data on one or
more storage nodes (for instance, when increasing total server capacity or replacing a
defective node).
In those cases, the following information lists performance expectations:
l For servers running Avamar 7.0.x software, the rebuild will take a maximum of 28
hours at an average rate of 202 GB/hr (56 MB/s).
l For servers running Avamar 6.1.1 software, the rebuild will take a maximum of 52
hours at an average rate of 107 GB/hr (30 MB/s).
This performance data is based on a 1x10 Avamar Data Store Gen4x multi-node server
with 7.8TB or M2400 nodes filled to 50% capacity and a standard Allied Telesis switch
with the latest firmware and not configured as Round Robin. For Avamar servers with
3.6TB or M1200 nodes, the average rates would remain the same but the maximum
rebuild in hours would be halved.
Avamar Administrator technical notes

The following technical notes apply to Avamar Administrator.
Avamar Administrator directory browsing limitation
When browsing a client file system with Avamar Administrator, directories with very large
numbers of files can cause Avamar Administrator to run out of memory. For this reason,
Avamar Administrator is configured by default to only retrieve the first 50,000 files in
each directory. You can change this limitation by editing the max_browse_entries
settings in mcserver.xml and mcclient.xml. However, doing so could cause
unpredictable application behavior.
Jobs do not appear in the Activity Monitor after server restart
If you stop and then restart the administrator server, then jobs that started before the
administrator server stop do not appear in the Activity Monitor.
Schedule start times and end times
If you select a different start time in the schedule, you must reselect the desired end time.
Avamar Data Store Gen4x performance expectations 55

Release Notes
Client name change impacts license quota

If you rename a client, the old name of the client remains for activities reporting data for
the client. Avamar treats new activities for the same client as if they were for a new client,
leading to double counting the number of bytes protected for licensing purposes. If a
client name change is required, consult EMC Customer Service to ensure that the
database is correctly updated.
Additional “cold start” messages from netsnmp
To resolve an issue where SNMP stops responding, Avamar must frequently restart the
netsnmp agent. Because the netsnmp agent generates a “cold start” message on each
restart, additional “cold start” messages appear that are not related to actual restarts of
the Avamar system or incorrect operation of the system. Unfortunately, there is currently
no way to distinguish between a real “cold start” message that is triggered by an Avamar
system restart and a “cold start” message generated as the result of netsnmp agent
restarts.
Software conflicts with Black Ice and Timbuktu
The Avamar Administrator software is known to have conflicts with software packages
such as Black Ice and Timbuktu.
Avamar Enterprise Manager technical notes

The following technical notes apply to Avamar Enterprise Manager.
Incorrect Avamar Administrator version may launch after server upgrade
The wrong version of Avamar Administrator may appear the first time that you launch
Avamar Administrator using Avamar Enterprise Manager after a system upgrade. The first
launch might launch the pre-upgrade version of Avamar Administrator. The correct
upgraded version of Avamar Administrator appears in subsequent launches.
Errors when launching Avamar Administrator
Stale Java temporary Internet files can cause errors when you launch Avamar
Administrator from an Avamar Enterprise Manager session.
To resolve this issue on Windows computers:
1. From the Windows Control Panel, open the Java Control Panel.
2. In the Temporary Internet Files area, click Delete Files.
A confirmation dialog box appears.
3. Ensure that all temporary Internet file types are selected, and click OK.
Avamar Desktop/Laptop technical notes

The following technical notes apply to Avamar Desktop/Laptop.
Client-level Avamar accounts cannot log in to Avamar Desktop/Laptop
To provide the same level of security that exists in Avamar Administrator, Avamar
Desktop/Laptop blocks Avamar's default client-level accounts. This means that Avamar
Desktop/Laptop does not accept the credentials for the following default accounts:
l backuponly
l restoreonly
l backuprestore
l replonly

Release Notes
Avamar Web Restore technical notes

The following technical notes apply to Avamar Web Restore.
Enabling the full display on the Avamar login screen
Avamar Web Restore displays an empty Domain field and an empty Client field on the
Avamar login screen to prevent the display of domain information during a non-domain
login. When using Avamar Web Restore only in a secure domain, change this default
setting to enable the full display on this screen.
When the full display is enabled, a list of Avamar domains appears in the Domain field
and a list of clients appears in the Client field.
Note
This change does not affect the Avamar Web Restore LDAP login screen.
To enable the full display on the Avamar log in screen:

1. Open a command shell and log in:
l For a single-node server, log in to the server as root.
l For a multi-node server, log in to the utility node as root.
2. Switch user to root by typing the following command:
su -
3. Change the current working directory by typing the following command:

cd /usr/local/avamar/etc
4. Open the Avamar Desktop/Laptop properties file, dtlt.properties, in a plain

text editor.
5. Add the showWRClientList key with the value of true:
showWRClientList=true
If the key already exists, set the value to true.
6. Save and close the file.
Special characters in file name replaced during restore
Restoring a file with special characters in the file name results in replacement of the
characters in the restored file name. This occurs when the LANG variable on the Avamar
server is set to a locale that does not support the characters. To work around this issue,
either rename the file after it is restored or change the LANG variable on the Avamar
server to the correct locale.
Backup client technical notes

The following technical notes apply to backup clients.
Linux client installation binaries
Because various Linux operating systems are compatible, not all supported Linux
operating systems have natively built installation binaries. As a result, the names of
installation binaries do not always match the name of the operating system. For example,
client installation binaries for Red Hat Enterprise Linux 6 are built on SUSE Enterprise
Server 11 and therefore refer to SLES 11 in the name of the installation binaries.
Nonetheless these installation binaries are appropriate for installation on Red Hat
Enterprise Linux 6.
Avamar Web Restore technical notes 57

Release Notes
IPv6 not supported on HP-UX PA-RISC

Avamar support for IPv6 is not available for the HP-UX PA-RISC platform.
Log files are time/date stamped in UTC time
Some client log and other files created in the VARDIR are time/date stamped in Universal
Time Code (UTC) time (Greenwich Mean Time), and not the local time. This can cause
confusion when you look for a particular log file.
Firewall software must be configured to allow communication with the Avamar server
Firewall software inherently interferes with communication between the Avamar server
and Avamar clients by disabling inward connections to most data ports. Therefore, if you
use firewall software on a client computer (for example, ZoneAlarm, Norton, McAfee, and
so forth) or if you upgrade a Windows client to Windows XP Service Pack 2 (which
includes a new integrated firewall), then you must configure the firewall application to
allow bidirectional communication between the Avamar client and the Avamar server.
This is normally accomplished by adding the EMC Client Agent to an “allowed” or
“exceptions” list. The exact procedure for doing this depends on the firewall application.
The documentation for the firewall should provide additional information.
Avamar icon disappears from Mac system menu bar
On irregular and rare occasions, the Avamar icon disappears from the Mac system menu
bar. To restore the icon, restart the Avamar client using the Avamar Client application
launcher in the Applications folder.
Standby, sleep, and hibernate states interfere with backups
Issues may occur when computers go into standby/sleep (ACPI state G1-S3), hibernate
(ACPI state G1-S4), or hybrid sleep (Windows Vista) modes during a backup.
Upon returning to a working state (ACPI state G0-S0), the network connection between
the client and the Avamar server may be lost and yet appear, from the server side, to still
be established. Canceling the backup from the client side has no effect.
To drop the backup connection, cancel the backup from the server side. This occurs
automatically when the connection is inactive for more than one hour.
To help minimize this problem, be sure the BIOS and drivers on all supported computers
are up-to-date.
Browse of shared storage fails after failover in dual-stacked cluster environments
You cannot browse shared storage in a cluster by using the Avamar cluster client after a
failover in a dual-stacked cluster environment. To enable browsing, rerun the Cluster
Configuration Tool on the active node to remove and then reconfigure the Avamar cluster
client.
Backup cannot proceed when mandatory locks are encountered
Avamar client software honors all mandatory locks in the target file system on Solaris and
HP-UX operating systems. However, this can cause backup operations to hang
indefinitely if a mandatory lock is held by another application on files that Avamar is
backing up. To work around this issue, specifically exclude all files and directories with
mandatory locks from the backup dataset, and then perform another backup.
Solaris path length limitation
Solaris imposes a maximum path length limit of 1,023 characters. Therefore, you cannot
specify paths greater than 1,023 characters at any time.
Retention must expire before February 7, 2106 for 32-bit Windows and Linux clients
For backups of 32-bit Windows or 32-bit Linux client computers, do not assign a retention
period for a date after February 7, 2106. If you assign an extended retention period to a
32-bit Windows client, the backup completes with exceptions. For 32-bit Linux clients,
the backups complete but do not appear in Avamar Administrator.

Release Notes
Issues when running multiple CLI backup or restore operations at a time for a client
Stability issues occur when you run multiple command line interface (CLI) backup or
restore operations at a time for a client. To work around this issue, perform only one CLI
operation at a time for each client.
Password best practices

This following technical notes provide best practices for creating and protecting
passwords.
Best practices for creating passwords
The following table provides best practices for creating passwords.
Table 9 Best practices for creating passwords
Best practice Details

Do not use Personal Do not use PII in your password, such as:
Identifiable
l Your name
Information (PII).
l Your username
l Your birthday
l Names of pets
l Names of your children
l Name of your alma mater
l Keywords associated with your hobbies
Do not use words from Do not use any word that can be found in the dictionary as your full
the dictionary. password.
Use strong passwords. Always use strong passwords when creating passwords. Strong
passwords include:
l At least eight characters
l Special characters such as a percent sign (%) or ampersand (&)
l Non-alphabetic characters
l Both uppercase and lowercase characters
Use different Always use a different password for each user account.
passwords for user
accounts
Change your password l Change your most critical passwords on a regular basis.
regularly
l Change your passwords at least every 6 months.
l When you change your password, avoid using variations of a
previous password.
l Immediately change your password if you expect another person
has access to your account, or knows your password.
l Always change your password as soon as you receive an account.
Password best practices 59

Release Notes
Password protection best practices

You should always create a password that you can remember without needing to store it.
However, if the password must be stored, follow these recommendations:
l Use a password vault application to protect and help manage your passwords.
l If passwords must be written down on a piece of paper, store the paper in a secure
place and destroy it when it is no longer needed.
l Do not put your username and password on a post-it note under your keyboard.
l Do not write down your username and password in the same place.
l Use caution regarding where passwords are saved on computers. Some dialog boxes,
such as those for remote access and other telephone connections, present an option
to save or remember a password. Selecting this option poses a potential security
threat.
l Never share your passwords with anyone and do not give your password to anyone
over the phone.
Documentation
This section describes the documentation and information products that are available
with this release of Avamar.
Avamar product documentation

This section describes the product documentation that is available with Avamar 7.1.
EMC Avamar Administration Guide
This document describes how to configure, administer, monitor, and maintain the
Avamar system.
EMC Avamar Operational Best Practices
This document provides best practices for designing, configuring, managing, and tuning
the performance of the Avamar system.
EMC Avamar and EMC Data Domain System Integration Guide
This document provides best practices for designing, configuring, managing, and tuning
the performance of the Avamar system.
EMC Avamar Product Security Guide
This document discusses Avamar security considerations, including user authentication
and authorization, client/server access and authentication, data security and integrity,
system monitoring, server hardening, port usage, and firewall requirements.
EMC Avamar Reports Guide
This document describes how to create, manage, and interpret the information in Avamar
reports.
EMC Avamar Management Console Command Line Interface (MCCLI) Programmer Guide
This document describes how to install, configure, and use the Avamar Management
Console Command Line Interface (MCCLI), which is a Java software application that
provides command line access to Avamar Administrator features.
EMC Avamar Release Notes
This document contains information on new features and changes, fixed problems,
known limitations, and environment and system requirements for the latest Avamar
release.

Release Notes
EMC Avamar Backup Clients User Guide

This document describes how to install and activate Avamar backup clients on all
platforms. It also describes how to use the Avamar backup client to back up and restore
data.
EMC Avamar for VMware User Guide
This document describes how to install, configure, and use Avamar to back up and
restore virtual machines in a VMware environment.
EMC Avamar for Windows Server User Guide
This document describes how to install the Avamar client for Microsoft Windows, and
how to back up and restore data on a Windows server.
EMC Avamar for Hyper-V VSS Guide
This document describes how to install Avamar in a Microsoft Hyper-V environment, and
how to back up and restore virtual machines using Avamar with Microsoft Volume
Shadow Copy Service (VSS) technology.
EMC Avamar for Exchange VSS User Guide
This document describes how to install Avamar in a Microsoft Exchange Server
environment, and how to back up and restore data using Avamar with Microsoft Volume
Shadow Copy Service (VSS) technology.
EMC Avamar for SharePoint VSS User Guide
This document describes how to install Avamar in a SharePoint environment, and how to
back up and restore data using Avamar with Microsoft Volume Shadow Copy Service
(VSS) technology.
EMC Avamar for SQL Server User Guide
This document describes how to install Avamar in a Microsoft SQL Server environment,
and how to back up and restore SQL Server databases.
EMC Avamar for Lotus Domino User Guide
This document describes how to install Avamar in a Lotus Domino environment, and how
to back up and restore data.
EMC Avamar for Oracle User Guide
This document describes how to install Avamar in an Oracle database environment, and
how to back up and restore Oracle databases.
EMC Avamar NDMP Accelerator User Guide
This document describes how to install and configure the Avamar NDMP Accelerator, and
how to back up and restore data on supported EMC VNX and EMC storage systems and
NetApp filers.
EMC Avamar for SAP with Oracle User Guide
This document describes how to install Avamar in an SAP environment with Oracle, and
how to back up and restore SAP servers with Oracle databases.
EMC Avamar for Sybase ASE User Guide
This document describes how to install Avamar in a Sybase environment, and how to
back up and restore Sybase Adaptive Server Enterprise (ASE) databases.
EMC Avamar for IBM DB2 User Guide
This document describes how to install Avamar in an IBM DB2 environment and how to
back up and restore DB2 databases.
Avamar product documentation 61

Release Notes
EMC Avamar Plug-in for vCenter Administration Guide

This document describes how to install, configure, administer, and use the EMC Backup
and Recovery plug-in for vCenter to back up and restore VMware image backups on an
Avamar server.
Avamar related documentation

For more information about Avamar 7.1, refer to this related documentation:
EMC Avamar Compatibility and Interoperability Matrix
This document provides server, client, and platform compatibility and interoperability
information. The document is available on EMC Online Support at https://
support.EMC.com.
Technical notes and white papers
Avamar technical notes provide technical details on specific product features, including
step-by-step tasks, where necessary. White papers provide an in-depth technical
perspective of a product or products as applied to critical business issues or
requirements. Both technical notes and white papers are available on EMC Online
Support at https://support.EMC.com.
Documentation errata
This section provides corrections for Avamar 7.1 documentation errors that are
discovered after a publication is finalized.
EMC Avamar Product Security Guide
The Avamar Product Security Guide version released as part of the service pack 1 release of
Avamar 7.1 contains a table entitled "Required inbound ports on the utility node" and a
table entitled "Required outbound ports for utility node". Those tables should include the
following additional information for port 28001.
Table 10 Required inbound ports on the utility node (additional information)
Port Protocol Service name Source computer Additional information

28001 TCP l MCS l Replication source (Avamar server version 7.1.1 and newer) Bidirectional communication
between avagent and MCS on the replication source Avamar server
l Avagent l Replication target and the replication destination Avamar server to permit
authentication key exchange.
Table 11 Required outbound ports for the utility node (additional information)
Port Protocol Destination computer Additional information

28001 TCP Replication source system and Replication on Avamar server version 7.1.1 and newer systems requires bi-
replication target system directional access between the replication source Avamar server and the
replication destination Avamar server to permit authentication key exchange.
Avamar 7.1 contains a section entitled: “Unencrypted data-in-flight on new installs of
Avamar 7.1 and newer”. That section contains a task entitled: "Permitting unencrypted
data-in-flight on new installs of Avamar 7.1 and newer". The task neglects to mention as a
final step that the Avamar firewall must be restarted on all nodes. After completing the
steps contained in that task, complete the following additional step:
On a single node system, type: service avfirewall restart

Release Notes
On a multi-node system, type: mapall --noerror --all+ --user=root 'service

avfirewall restart'
Avamar 7.1 contains a section entitled: “Installing level-2 security hardening features”.
That section contains a task entitled: “Configuring the firewall to support Avamar Client
Manager”. The task should be limited to pre-7.1 Avamar systems. The task addresses an
issue that can occur when Avamar Client Manager running on Avamar server version 7.1
and later is used to manage Avamar systems running Avamar server versions earlier than
7.1.
The firewall on pre-7.1 version systems blocks port 5555. Avamar Client Manager
requires access to port 5555 on the Avamar systems that it manages. The firewall on
Avamar version 7.1 and later does not block this port.
Also, that section should include the instruction that the text that is inserted into /etc/
firewall.base must be inserted after the ########## BEGIN UTILITY NODE SPECIFIC
RULES ########## comment line and before the ########## END UTILITY NODE
SPECIFIC RULES ########## comment line.
EMC Avamar Administration guide
The Avamar Administration Guide version released as part of the service pack 1 release of
Avamar 7.1 contains a section entitled: "Adding a replication destination". The steps in
that section should be modified to the following:
1. In Avamar Administrator, click the Replication launcher button.
2. Select the Destinations tab.
3. Select Actions > New Destination.
The New Replication Destination dialog box appears.
4. In Name, type a reference name for the destination Avamar system.
5. In Destination server type, select Replicate.
6. In Encryption, select an encryption level.
The selected encryption level applies to replication data transfers with the
destination Avamar system.
7. In Target server address, type the DNS name or the IP address of the destination
Avamar system.
8. In Target server connection port, type the number of the outbound port on the source
Avamar system to use when communicating with the destination Avamar system.
The default port value is 27000.
Selecting High or Medium in Encryption results in an offset being applied to port to
allow connections through firewalls. The default offset is +2000. Edit the offset by
manually editing the secured_port_offset preference in mcserver.xml, and then
restarting the MCS.
9. In Target MCS connection port, type the number of the inbound port on the
destination Avamar server to use for data connections with MCS on the destination
system.
The default port value is 28001.
10. In User ID on target server, type a username for an account on the destination
Avamar system that has the backup privilege and the admin privilege.
Normally, type repluser or root.
11. In Password on target server, type the password that is associated with the
username.
Documentation errata 63
Release Notes
12. Click Verify Authentication.

The source Avamar system authenticates with the destination Avamar system by
using the specified settings.
In the Verifying Authentication dialog box, a results message appears.
13. In the Verifying Authentication dialog box, click Close.
14. In the New Replication Destination dialog box, click OK.
EMC Avamar Administration and Upgrade guides
EMC changed the package access functionality of the Avamar Downloader Service from
FTP-based to credentialed access on EMC Online Support. An upgrade notification
appears above the utility's task tray icon. Although some packages might appear in
Avamar Installation Manager or Enterprise Manager, they will be inaccessible for
download until you perform this upgrade.
The following information assumes that you already upgraded the Downloader Service
software.
The following changes are necessary to the Avamar 7.1 Administration and Avamar 7.1
Upgrade guides:
l Replace the "Defining an outbound rule for Microsoft Windows 7 hosts" section with
the following "Enabling HTTPS" section.
1. On the Windows computer on which Avamar Downloader Service runs, open
Control Panel > Windows Firewall.
2. Click Advanced Settings.
3. Right-click Outbound Rules and select New Rule.
4. In the New Outbound Rule Wizard, select Port and click Next.
5. Select Specific remote ports, enter 443 in the text box, and click Next.
6. Click Allow the connection and click Next.
7. Accept the default settings and click Next.
8. Provide a name for the outbound rule (for instance, “Avamar Downloader
Service”) and click Finish.
9. Right-click the outbound rule you created above from the Outbound Rules list
(should be at top of list) and select Properties.
10.Select the Programs and Services tab.
11.Click Settings.
12.Select Apply to this service.
13.From the list of services, select Avamar Downloader Service and click OK.
14.Click Apply and then OK.
15.Close the Windows Firewall with Advanced Security window.
l In the "Configuring the Avamar Downloader Service" section, modify the procedure as
follows.
1. Delete the Check For Network Connectivity step.
2. From the Welcome page, an EMC Credentials page appears before the Proxy
Configuration page.
On this page, specify the EMC Online Support Username and Password (plus
confirmation) provided with your EMC Avamar license at the time of product
purchase.

Release Notes
Note
To edit EMC credentials later, open the Show Advanced Settings window (task tray
icon > Show Advanced Settings). The Repository Credentials page no longer has
File Transfer Protocol and Host Address sections.
3. In addition to Proxy Host and Proxy Port options, the Proxy Configuration page
now displays a Use Authentication checkbox and EMC credentials fields
(Username, Password, and Confirm Password).
l In the "Avamar Downloader Service monitor status messages" table, the description
for the Network Error item should be: HTTPS browser settings prevent the Avamar
Downloader Service from requesting files from the Avamar Online Support site.
l In the "Troubleshooting Avamar Downloader Service issues" section, delete the "Not
receiving files from the Avamar FTP site" section.
EMC Avamar NDMP Accelerator for EMC NAS Systems User Guide
The Top-Level Directories (TLDs) for multi-streaming on Isilon systems is not available in
the Avamar 7.1 release. Ignore all content related to this feature, including the Enable
automated TLD generation for multistreaming plug-in option.
EMC Avamar NDMP Accelerator for NetApp Filers User Guide
The following additions and changes are necessary to support NetApp Cluster filers:
l To enable NDMP services on a NetApp Cluster:
1. Open a command shell, and then log in to the NetApp Cluster.
2. Type services ndmp on -vserver vservername, where vservername is the
hostname or IP address of the NetApp virtual storage system.
l The following text replaces the explanatory text before the procedure in the "Verifying
filer privileges" topic of the "Installation and Configuration" chapter:
Avamar supports node-scoped, Vserver-aware, and cluster-aware NDMP modes. In
node-scoped NDMP mode, the root user account always has sufficient privileges.
However, for security reasons you might want to use another user account. Backups
might fail to start or complete if the alternate user account has insufficient privileges.
In Vserver-aware and cluster-aware NDMP modes, user authentication is integrated
with the role-based access control mechanism. New user accounts must have
sufficient privileges to access the Vserver. In Vserver-aware NDMP mode, the NDMP
user must belong to either the vsadmin or vsadmin_backup role. In cluster-aware
NDMP mode, the NDMP user must belong to either the admin or backup role.
l When adding a NetApp Cluster to the accelerator, type the Vserver credentials when
prompted for the filer username and password by avsetupndmp.
l Redirected restore to a different volume is not supported in a cluster-aware filer
configuration.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Send your opinions of this document to
DPAD.Doc.Feedback@emc.com.
Please include the following information:
l Product name and version
l Document name, part number, and revision (for example, 01)
Your comments 65
Release Notes
l Page numbers
l Other details that will help us address the documentation issue
Installation
The following sections provide information about installation and upgrade in an Avamar
7.1 environment.
Avamar server installation and upgrade

An EMC technical representative must install the Avamar server.
Avamar server upgrades are scheduled and performed by the Avamar Support Upgrade
Team. To request an upgrade, go to EMC Online Support, https://support.EMC.com, and
open an upgrade Service Request. A technical representative then contacts you to gather
information about the Avamar environment and to schedule a resource for the upgrade.
Downgrading the Avamar server software to an earlier version is not supported under any
circumstances.
To upgrade client download installation packages on the Avamar server, follow the
instructions in the EMC Avamar Client-Only System Upgrades Technical Note available on
the EMC online support website.
Avamar client installation and upgrade

Client installation and upgrade procedures are provided in each client or plug-in user
guide, such as the EMC Avamar for Oracle User Guide, EMC Avamar for Windows Server User
Guide, or EMC Avamar for SQL Server User Guide. A full list of Avamar documentation is
available in Documentation on page 60.
Installation and upgrade of other Avamar components

The following table provides the location for installation and upgrade procedures for
additional Avamar components.
Table 12 Installation and upgrade of other Avamar components
Component Location for installation and upgrade procedures

Avamar Administrator EMC Avamar Administration Guide
Avamar Management Console EMC Avamar Management Console Command Line Interface
Command Line Interface (MCCLI) (MCCLI) Programmer Guide
Upgrade requirements for Avamar 7.1

Review the requirements in the following sections before you upgrade to Avamar 7.1.
Avamar release 5.x and earlier clients are no longer supported
If you are upgrading from Avamar 6.x to 7.1 and there are Avamar 5.x or lower clients
backing up to an existing Avamar server, you must upgrade the Avamar 5.x clients to
Avamar release 6.0.x or later to continue backups.

Release Notes
Avamar Data Store Gen1 and Gen2 hardware are no longer supported
Avamar software running on Avamar Data Store Gen1, Avamar Data Store Gen2, or any
customer provided Dell hardware is not supported with Avamar 7.1. The minimum
hardware requirement that support Avamar 7.1 is Avamar Data Store Gen3.
Upgrade requirements in a VMware environment
Ensure that the VMware environment meets the following requirements when you
upgrade to 7.1:
l You cannot upgrade proxies for the Avamar Plug-in for VMware. To use version 7.1 or
later functionality, deploy 7.1 proxies.
l You must reboot proxy virtual machines after you upgrade the Avamar server.
l The Avamar role requires additional privileges for release 6.1 Service Pack 1 or later
VMware image proxies. If you continue to use release 6.1 proxies, rather than 6.1
Service Pack 1 or later proxies, then the additional privileges are not required.
To set the additional privileges:
1. In the vSphere client, click Roles.
2. Right-click the Avamar role and select Edit Role.
3. Expand the Global privilege and select Disable method, Enable method, and
Licenses.
4. Expand the vApp privilege and select Export.
5. Click OK.
Upgrade requirements for a security-hardened Avamar server
If you are using a security-hardened Avamar server with release 6.1 or later, you must
upgrade the following plug-ins to 6.1 Service Pack 1 or later:
l Avamar Plug-in for Exchange VSS
l Avamar Plug-in for Hyper-V VSS
l Avamar Plug-in for SharePoint VSS
l Avamar Plug-in for SQL Server
l Avamar Plug-in for Windows VSS (System State)
Upgrade requirements for the SQL Server plug-in
When you upgrade the Avamar server to release 7.1, the Avamar Plug-in for SQL Server
must be release 6.1 or later. Do not use a SQL Server plug-in running release 6.0 or earlier
to back up to or restore from an Avamar server with release 7.1.
Upgrade requirements for Avamar Data Transport
To use Avamar Data Transport (ADT) with an Avamar 7.1 server, you must install ADT
release 1.0 Service Pack 3.
Upgrade requirements for Avamar Tape Out
To use Avamar Tape Out (ATO) with an Avamar 7.1 server, you must install ATO release
3.1.c.
Upgrade requirements for Avamar Extended Retention
If you are upgrading from Avamar release 6.1.x to Avamar release 7.1, you must upgrade
the Avamar Extended Retention software to 2.1.
Upgrade requirements for Avamar with a Data Domain system
You must use DD OS 5.4.1.1 or later on a Data Domain system with an Avamar 7.1 server.
Before you upgrade to Avamar 7.1, you must upgrade clients that back up to a Data
Domain system to Avamar 6.1.x or later.
Upgrade requirements for Avamar 7.1 67

Release Notes
The upgrade path for Avamar and Data Domain is very specific. Failure to upgrade
software in the proper order can cause Avamar maintenance functions to fail. If this
happens and the Avamar server fails, a rollback operation will fail. The EMC Avamar and
EMC Data Domain System Integration Guide provides details.
The following table lists the steps to upgrade Avamar with a Data Domain system.
Upgrade path Steps

Avamar 6.1 to Avamar 1. Ensure that all Avamar clients are running Avamar 6.1 client software.
7.1
2. Upgrade the Data Domain systems to DD OS 5.4.1.1.
3. Upgrade the Avamar server to release 7.1.
4. (Optional) Upgrade the Avamar clients to release 7.1.
Avamar 6.0 to Avamar 1. If you are using DD OS 4.9, upgrade to DD OS 5.4.1.1.

7.1
2. Ensure that all Avamar clients are running Avamar 6.1 client software.
4. Upgrade the Data Domain systems to DD OS 5.4.1.1.
6. (Optional) Upgrade the Avamar clients to release 7.1.
Note
If you fail to perform the upgrade steps or you perform the steps out of sequence, then
backup failures and data corruption on the backup device can occur.
Upgrade requirements for Microsoft Exchange 2003 and a Data Domain system
If you are backing up Microsoft Exchange 2003 to a Data Domain system, backups fail
after you upgrade to Avamar release 7.1. Support for Microsoft Exchange 2003 ended
with Avamar 6.0.x. To work around this issue:
l Upgrade Microsoft Exchange to a newer version.
l Store the backups on the Avamar servers instead of the Data Domain system by using
the Avamar 6.0 Plug-in for Exchange.
l Do not upgrade the Avamar server to release 7.1.
Upgrade requirements for Avamar with NetWorker
If you use Avamar with EMC NetWorker®, review the minimum NetWorker software
version requirements before you upgrade the Avamar server to release 7.1. The NetWorker
Software Compatibility Guide on EMC Online Support at https://support.EMC.com provides
information on the NetWorker version requirement for specific clients.
Upgrade requirements for environments with LDAP
If you upgrade to Avamar 7.1 from Avamar 6.0.x or earlier and you use LDAP to perform
external authentication for either Avamar Administrator or Avamar Desktop/Laptop, then
you must configure a new LDAP environment.
The way that Avamar communicates with the domain controller and the external
authentication server by using LDAP is different in version 6.1.x and later.
If there is an active older LDAP configuration, then the upgrade process disables the new
LDAP configuration method and maintains the older LDAP components without
transferring the old configuration values to the new method.

Release Notes
The EMC Avamar Administration Guide provides details on configuring the new LDAP
environment.
Microsoft update requirements for Avamar with Hyper-V on CSV
Backups fail in a Hyper-V environment with CSV unless you follow best practices and
apply Microsoft hotfixes in the correct order. The EMC Best Practices for Hyper-V over CSV
Cluster Data Protection Using EMC Avamar and EMC Networker Technical Note on EMC Online
Support provides details.
Troubleshooting and getting help

The Avamar support page provides access to licensing information, product
documentation, advisories, and downloads, as well as how-to and troubleshooting
information. This information may enable you to resolve a product issue before you
contact EMC Customer Support.
To access the Avamar support page:
1. Go to https://support.EMC.com/products.
2. Type a product name in the Find a Product box.
3. Select the product from the list that appears.
4. Click the arrow next to the Find a Product box.
5. (Optional) Add the product to the My Products list by clicking Add to my products in
the top right corner of the Support by Product page.
Knowledgebase
The EMC Knowledgebase contains applicable solutions that you can search for either by
solution number (for example, esgxxxxxx) or by keyword.
To search the EMC Knowledgebase:
1. Click the Search link at the top of the page.
2. Type either the solution number or keywords in the search box.
3. (Optional) Limit the search to specific products by typing a product name in the
Scope by product box and then selecting the product from the list that appears.
4. Select Knowledgebase from the Scope by resource list.
5. (Optional) Specify advanced options by clicking Advanced options and specifying
values in the available fields.
6. Click the search button.
Online communities
Visit EMC Community Network at http://community.EMC.com for peer contacts,
conversations, and content on product support and solutions. Interactively engage online
with customers, partners and certified professionals for all EMC products.
Live chat
To engage EMC Customer Support by using live interactive chat, click Join Live Chat on
the Service Center panel of the Avamar support page.
Service Requests
For in-depth help from EMC Customer Support, submit a service request by clicking
Create Service Requests on the Service Center panel of the Avamar support page.
Troubleshooting and getting help 69

Release Notes
Note
To open a service request, you must have a valid support agreement. Contact your EMC
sales representative for details about obtaining a valid support agreement or with
questions about your account.
To review an open service request, click the Service Center link on the Service Center
panel, and then click View and manage service requests.
Facilitating support
EMC recommends that you enable ConnectEMC and Email Home on all Avamar systems:
l ConnectEMC automatically generates service requests for high priority events.
l Email Home emails configuration, capacity, and general system information to EMC
Customer Support.

Release Notes
Copyright © 2002-2015 EMC Corporation. All rights reserved. Published in USA.
Published October, 2015
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.
EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
Troubleshooting and getting help 71

CU00610B Configurar Java en Windows Variables Entorno Java - Home y Path

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CU00610B Configurar Java en Windows Variables Entorno Java - Home y Path

Uploaded by

Copyright:

Available Formats

Release Notes

Table 1 Revision history

Revision Date Description

2 EMC Avamar 7.1 Release Notes

Table 1 Revision history (continued)

Revision Date Description

l Added Avamar Data Store Gen4x performance expectations on page 55.

01 June 18, 2014 Initial release of Avamar 7.1.

New features and changes

New features and changes for the Avamar 7.1 DA release

Avamar server features and changes

New location for client log files on the Avamar server

Avamar Extended Retention features and changes

Data Domain system support

Backup clients features and changes

IBM DB2 features and changes

IBM Lotus Domino features and changes

Microsoft Exchange VSS features and changes

Microsoft Hyper-V VSS features and changes

4 EMC Avamar 7.1 Release Notes

Microsoft SharePoint VSS features and changes

Microsoft SQL Server features and changes

Microsoft Windows features and enhancements

New features and changes for the Avamar 7.1 DA release 5

NDMP Accelerator features and changes

Oracle features and changes

SAP with Oracle features and changes

Sybase ASE features and changes

VMware features and changes

6 EMC Avamar 7.1 Release Notes

l Automated backup validation, which enables you to validate image backups on a

Discontinuation of Avamar Enterprise Manager

New features and changes for the Avamar 7.1 GA release

New features and changes for the Avamar 7.1 GA release 7

l Web servers on Avamar systems specify stronger default cipher suites

This will disable this feature.

8 EMC Avamar 7.1 Release Notes

Fixed problems for the Avamar 7.1 DA release

Table 2 Fixed problems for the Avamar 7.1 DA release

Issue Product feature Problem summary

59949 Administration guide Escalation 7251:Need clarification on Solaris restore documentation

60890 Administration guide Escalation 7235:Documentation: LDAP Maps over SSL

56747 Avamar Desktop/ Escalation 6798:Application-Level Security Vulnerabilities

Table 2 Fixed problems for the Avamar 7.1 DA release (continued)

Issue Product feature Problem summary

51426 Avamar server Escalation 6110:RCA REQUEST | gsan deadlock

52619 Avamar server Escalation 6294:checkpoint::validate file error

54467 Avamar server Escalation 6463:userdatastripe::cmdMovGetLink Namelistrec is already marked for

10 EMC Avamar 7.1 Release Notes

Table 2 Fixed problems for the Avamar 7.1 DA release (continued)

Issue Product feature Problem summary

57700 Avamar server Escalation 6923:RCA multiple nodes offline

Fixed problems for the Avamar 7.1 DA release 11

Table 2 Fixed problems for the Avamar 7.1 DA release (continued)

Issue Product feature Problem summary

55093 Client Escalation 6351:avtar: fails to restore large amount of data

12 EMC Avamar 7.1 Release Notes

Table 2 Fixed problems for the Avamar 7.1 DA release (continued)

Issue Product feature Problem summary

188312 DB2 plug-in Escalation 7513:DB2 restore failed : SQLO_PROG_ERR "Unknown"

Fixed problems for the Avamar 7.1 DA release 13

Table 2 Fixed problems for the Avamar 7.1 DA release (continued)

Issue Product feature Problem summary