docu53934_Avamar-7.1-Release-Notes (7.1.0-302 ).pdf

8/10/2019 docu53934_Avamar-7.1-Release-Notes (7.1.0-302 ).pdf

1/55

Release Notes

EMCAvamar

Release number 7.1

Release Notes302-000-836

03

September, 2014

These release notes contain supplemental information about EMC Avamar release 7.1.Topics include:

l Revision history......................................................................................................... 2l Product description....................................................................................................2l New features and changes......................................................................................... 2l Security updates........................................................................................................7l Fixed problems.......................................................................................................... 7l Environment and system requirements.................................................................... 21l Known problems and limitations..............................................................................22l International language support................................................................................37l Technical notes........................................................................................................41l Documentation........................................................................................................ 47l Installation.............................................................................................................. 50l Troubleshooting and getting help.............................................................................53


2/55


3/55


4/55

IBM DB2 features and changes

Release 7.1 of the Avamar Plug-in for DB2 supports restore and recover operations fromthe 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 fromeither an Avamar server or a Data Domain system by using Avamar Administrator or theCLI.

Microsoft Exchange VSS features and changes

The Avamar Plug-in for Exchange VSS supports multi-stream restore from a Data Domainsystem 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 VSSin release 7.1.

Microsoft SharePoint VSS features and changes

The Avamar Plug-in for SharePoint VSS includes the following new features and changesfor 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 theBackup, Restore and Managewindow in Avamar Administrator.

l Support for backup and restore of SharePoint databases on the primary replica inSQL Server AlwaysOn availability groups.

Microsoft SQL Server features and changes

The Avamar Plug-in for SQL Server includes the following new features and changes forrelease 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 2012R2 active/passive cluster on shared disks, clustered shared volumes (CSVs), andshared virtual hard disk (VHDX) files. Shared VHDX files must be located on either aCSV 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 20to 30 seconds to complete for each database. Transaction log backups may take anexcessive amount of time to complete in environments with a significant number ofdatabases.

If the performance issues outweigh the risk of possible log gaps, then you candisable log gap detection by selecting the Skip log gap detectionoption in thebackup plug-in options to improve performance. You can also use the --skip-log-

gap-detectionoption in the avsqlcommand line interface (CLI).

Microsoft Windows features and enhancements

The Avamar Client for Windows includes the following new features and changes for

release 7.1:

Release Notes

4 EMC Avamar7.1 Release Notes


5/55

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 thefollowing 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 operatingsystems, use Avamar 6.x clients and application plug-ins.

The Windows VSS plug-in for System State backups includes the following new featuresand 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 release7.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 forrelease 7.1:

l On-demand and scheduled backups of an entire Isiloncluster to a Data Domainsystem.

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 backupfeature 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 featuresand changes:

l Support for Oracle operating system authentication for the database connectionduring backup browse operations in Avamar Administrator.

l Support for BR*Tools secure storage password and role-based secure storage inAvamar 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

Release Notes

New features and changes for the Avamar 7.1 DA release 5


6/55

Sybase plug-in now recognizes when an incremental backup of a Sybase database iscancelled before its completion. The next incremental backup from a GUI or CLI of thesame 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 andchanges for release 7.1:

l Improved multitenancy support for service providers.

l File-level restore now supports extended LVM partitions.

l Automated backup validation, which enables you to validate image backups on aregular basis by using validation groups and schedules.

l Intelligent automated proxy selection for backup and restore operations, with theability 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 virtualmachines to support third party tools such as Kroll OnTrack PowerControls to performdata 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 protectionto clouds built using vCloud Director. The plug-in allows vCloud Director systemadministrators to manage backup, restore, and replication operations for cloudorganizations, Org VDCs, and vApps. It is targeted primarily at Service Providers, and canalso be used by enterprises using vCloud Director. Avamar 7.1 has embedded backupservices 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 extendedthe 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 in2015. EMC introduced a comparable but more robust tool that replaces EM called EMCBackup and Recovery Manager (BRM). BRM provides centralized enterprise monitoringcapabilities 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 forAndroid and iOS tablets, job restart capabilities, and search and filtering capabilities. Allcustomers 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 includingAvamar 7.1. Existing EM customers will continue to receive the same customer supportthat 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 ofAvamar 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.

Release Notes



7/55

l Support for NetApp cluster mode.

Security updatesThe 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 andfirewall packages that improve security capabilities on the Avamar server. Installation ofthese packages does not restrict supported server functionality, and the packages cannotbe uninstalled. In some cases, such as future upgrades, EMC Customer Supportpersonnel 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

SFTP for the Avamar Downloader Service

The Avamar Downloader Service now uses Secure File Transfer Protocol (SFTP) to

communicate with the EMC repository for server updates, hotfixes, and workflowpackages. In most cases, this change has no impact on Avamar installers and users.However, due to additional communication activity in SFTP mode, EMC recommends thatyou initiate no more than two package downloads at the same time.

In addition, if security rules for the Avamar Downloader Service host computer block port22, you must define a custom outbound rule in the Windows Firewall with AdvancedSecurity console to unblock the port. If you cannot unblock port 22 on the AvamarDownloader Service host, then unblock port 21 and configure the Avamar DownloaderService to use the FTP protocol, which uses port 21.To use the FTP protocol, right-click theAvamar Downloader Service task tray icon and select Show Advanced Settings. Select theFTPcheckbox on the Repository Credentialspage, and then clickApply. Note that use ofSFTP and port 22 will be required in a future release.

Fixed problemsThis 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.

Release Notes

Security updates 7


8/55

Table 2 Fixed problems for the Avamar 7.1 DA release

Issuenumber

Product feature Problem summary

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/

Laptop

CLONE: bug 50766-Escalation 5931:DTLT browse shows no backups although there are

backups.


Laptop

CLONE: bug 50317-Escalation 6018:Avamar 7.0 Beta >> German Help Menu in English &

German


Laptop

CLONE: bug 51998-Escalation 5883:Popup message has returned post Hotfix 41951 but

only on one of three Avamar Servers


Laptop

CLONE: bug 54237-Escalation 6519:CVE-2013-2251 -Apache Struts 2.0.0 through 2.3.15

allows remote attackers to execute arbitrary OGNL expressions


Laptop

Escalation 6798:Application-Level Security Vulnerabilities


Laptop

CLONE: bug 58469-Escalation 7029:Browse for redirecting a restore in DTLT shows SQL

instance as destination


Laptop

Escalation 7266:Web restore interface 'indexing' functionality - popup message does not

match the button selections offered to the user


Laptop

CLONE: bug 60920-Escalation 7381:DTLT Write in protect directory

50065 Avamar Downloader

Service

Escalation 5978:ER: File adsinfo.txt does not contain enough information from the

Downloader Service

59041 Avamar Enterprise

Manager

Escalation 6918:EM is not updating server status for days. Similar to Esc 6753

59241 Avamar Enterprise

Manager

Escalation 7159:Missing required Permissions manifest attribute in main jar

186201 Avamar Installation

Manager

Password security setting in Avamar Installation Manager fails to enforce password

requirements during Avamar server installation

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]

Release Notes



9/55

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

Issuenumber


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: 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

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

Release Notes

Fixed problems for the Avamar 7.1 DA release 9


10/55


Issuenumber


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'

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

Release Notes



11/55


Issuenumber


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 : Internal Warning: Very large amount of pending data in filepipe59437 Client Escalation 7167: Multi-stream backups to DD does not throttle the max number of

streams

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

Release Notes



12/55


13/55


Issuenumber


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 : 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

guide

Escalation 6457: Exchange2010:Incremental federated backup promoted to full if "list"

changes

56922 Exchange VSS user

guide

DOCS: Document "--use-ps-displayname", "--remote-ps-server" flags to be used in

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

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

Release Notes



14/55


15/55


Issuenumber


190411 Management Console Escalation 7678:exported Activity Report file is 0 bytes

50754 Management Console

Server

CLONE: bug 50592-Escalation 6050:Avamar 7.0 Beta - Passwords for plug-in based

replication destinations are stored in plain text


Server

Escalation 6091:Avamar 7.0 Beta - Vcenter Delete issue - Unable to delete directory

because it contains groups


Server

CLONE: bug 50975-Escalation 5982:Insecure permission errors when logrotate runs


Server

CLONE: bug 51508-esc 5891:Communications module scanner encountered an error


Server

CLONE: bug 51861-Escalation 6199:6.1.1.-87 Upgrade workflow fails updating MCS -

Update Failed: Error processing preferences file merge


Server

CLONE: bug 27819-Escalation 2982:Backup browsing performance related to bug 17637


Server

Escalation 6398:Randomly and Intermittently, physical clients failing backup with


Server

CLONE: bug 54513-"No Vm" workorder is not generated. Escalation 6526:Avamar 7

Scheduled backups not running


Server

CLONE: bug 54451-Escalation 6539:7.0 Plug-in based replication jobs were stuck in


Server

CLONE: bug 54420-CANCEL jobs at group level no longer works (from Escalation 6526)


Server

Escalation 6596:Domain and clients are not visible in MC GUI


Server

CLONE: bug 55109-Escalation 6610:cannot edit vm client's policy settings when the vm

is inside a static container


Server

Escalation 6597:Avamar 7.0 DA - Replication reports inconsistent number of clients

succeeded in source vs target MCGUI Dashboard


Server

CLONE: bug 55829-Encounter javax.xml.rpc.JAXRPCException while cloning connection.

Escalation 6526:Avamar 7 Scheduled backups not running

56161 Management ConsoleServer Escalation 6332:Scheduled backups fail seemingly at random with "TCP timeout onreceive ack (seconds 300)" followed by "avagent Warning : Null message received

from MCS"


Server

Escalation 6767:Different rollbacktime across nodes will cause MCS restore to fail


Server

Escalation 6905:Adding vCenter fails with error message pop-up: "Unexpected exception

occurred"


Server

Escalation 6917:Cannot restore VM after upgrade to 7.0 -- restore is reject because ESX is

not in vCenter


Server

Escalation 6827:BRSIL: Avamar 7 VMware backups hanging

Release Notes



16/55


Issuenumber



Server

Escalation 6958:Backups for VMs protected with dynamic inclusion are incorrectly tagged

with yearly retention


Server

Escalation 7014:new vms discovered in dynamic containers have CBT disabled


Server

Escalation 6996:Running 2 scheduled backups of the same client at the same time failed

one of them with the lock error rather than waiting for the first one to complete


Server

"Ghost" VMs emerge after VMs are relocated. Escalation 6774:Avamar Schedule image

backup is running but does not backup all VMs in policy>


Server

CLONE: bug 58456-Escalation 7044:WC | Restore | SQL | RESDTCvAP59 - SQL browse

restore takes long

58797 Management ConsoleServer

Escalation 7114:Vmimage Restore sits in waiting queued state for 7 SP1


Server

Escalation 7095:failed avtar backup shows 30000 success in Activity Report


Server

Escalation 7112:Vm's disabled in a dynamic container still show failed in activity window


Server

Escalation 7130:The user has insufficient privileges to access the system resource


Server

Escalation 7206:The backup completion email is not sent for the container clients

60527 Management ConsoleServer

Escalation 7351:Java process using 12,000+ threads


Server

Escalation 7416:When replicating internal Avamar system accounts AVI_BACKUPS,

EM_BACKUPS and MC_BACKUPS fail after 15 minutes.


Server

Escalation 7540:Activity Monitor/Summary don't show any activities after installing MCS

hotfix# 60601


Server

Escalation 7594:MCS crashed due to lack of jdbc connections

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.059475 MCCLI Escalation 7176:Datasets with Type Unknown after being imported from Avamar 6.1

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

Release Notes



17/55


Issuenumber


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

guide

Escalation 6938:restoring NDMP backup to a CIFS share is corrupted if compression is

enabled

59053 NDMP Accelerator user

guide

CLONE: bug 58417-Escalation 7031:Modify "EMC Avamar 7.0 NDMP Accelerator user

guide" manual to reflect modify introduced to avndmp script to resolve BUG 30164

48451,

48452

Oracle plug-in Escalation 5707: The avoracle SQL files creating in vardir should not have file names

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 snapshotconfiguration 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 toreplicated backups

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)

Release Notes



18/55


Issuenumber


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 SQLAlias 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.

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 :

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

Release Notes



19/55


20/55


21/55

Table 3 Fixed problems for the Avamar 7.1 GA release

Issue number Product feature Problem summary

195384 Backup and Recovery

Manager

esc 7890:PGP Signature for BRM fails on RHEL

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


Server

CLONE: bug 193392-Escalation 7822:Similar errors as mentioned in Esc7810,

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

Environment and system requirementsThis 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 AvamarCompatibility and Interoperability Matrixon 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

Release Notes

Environment and system requirements 21
https://support.emc.com/https://support.emc.com/


22/55

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 Avamarfor Oracle User Guide, EMC Avamar for Windows Server User Guide, or EMC Avamar for SQLServer User Guide. A full list of Avamar documentation is available in Documentation onpage 47.

Avamar Downloader Service operating system requirements

The Avamar Downloader Service is supported on Windows operating systems, includingWindows Server 2012 (64-bit), Windows Server 2008, Windows 8, Windows 7, andWindows Vista.

Starting with release 7.1, the Avamar Downloader Service is no longer supported onWindows XP or Windows Server 2003.

The EMC Avamar Administration Guideprovides a list of supported operating systems forthe Avamar Downloader Service.

Server dependencies for client features

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

l Granular Level Recovery (GLR) with the Exchange VSS plug-in requires build 6.0.0-580or 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 Matrixprovides details on supported DDOS and DD Boost versions.

Avamar supports the Data Domain with Extended Retention feature on DD OS version5.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 limitationsThe 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.

Release Notes



23/55


24/55

Avamar Config Checker known problems and limitations

The following list describes known problems and limitations with the Avamar ConfigChecker.

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 GLRservice is running on the server as the AvamarBackupUser account, then theconfiguration check fails.

To work around this issue, temporarily assign a different service account to theExchange GLR service while you run the Config Checker, and then reset the serviceaccount 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 notinstalled, then the Avamar Config Checker exits unexpectedly.

To avoid this issue, run a SharePoint configuration check only on servers whereSharePoint 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 rerunningdpnnetutilon ADS Gen4 systems.

If you rerun dpnnetutil, the following prompt appears: Use existing

dpnnetutil configuration file?If you clickYes(the proper response),

then management and replication prompts are excluded in successive screens.

To work around this issue, delete the probe.xmlfile in the /usr/local/

avamar/vardirectory before you rerun dpnnetutil.

Changing subnets is not allowed on single-node servers

You cannot use dpnnetutilto change subnets in a postinstallation single-node

server environment. The dpnnetutilutility initially allows you to change the

subnet IP address, but an error message appears later that directs you to return theconfiguration to its original state. To work around this issue:

l Run a nodedb update ifcommand 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.

Release Notes



25/55

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 haveadministrative privileges on that computer.

l The user logs in to the Avamar Desktop/Laptop web UI using Avamarauthentication.

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 InstallationManager.

200207 "Configuring Website if required Failed" error appears occasionally during

installation

When you are performing a new installation of the Avamar server software, a failureerror sometimes occurs during the Configuring Website if requiredtask in AvamarInstallation Manager.

To work around this issue, click Retry Current Taskto retry the installation. The taskcompletes successfully upon the retry.

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 thevSphere 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 LANGvariable is not set on an Avamar server, using Avamar Web Restore torestore a file with special characters in the file name fails. To fix this issue, set theLANGvariable 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 JavaScriptcommands in the Avamar Web Restore pages. To workaround this issue add theAvamar 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 eachrestore task to less than 200 files.

Release Notes

Avamar Installation Manager known problems and limitations 25


26/55


27/55

Known problems and limitations for all backup clients and plug-ins

The following list describes known problems for this release of all backup clients andplug-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 tore-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, performanother backup.

32873 Special ACLs are not supported

The avtarprocess does not support backup or restore of special UNIX and Linux

ACLs such as setuidand setgidbits, 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 servers IPv6 address is used during

configuration with the Avamar Cluster Configuration Tool, the Cluster ConfigurationTool fails to properly activate virtual cluster clients.

The interim solution to this problem is to use the Cluster Configuration Tool to createthe cluster client, but clear the Bring the cluster client online and activate it with theAvamar servercheckbox. Then manually create the virtual cluster client and withAvamar Administrator, and in Policy Management, edit the client and select theActivatedcheckbox in the Edit Clientdialog 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 criticaldisks, 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 andlimitations

The following list describes known problems for this release of the Avamar clients for AIX,FreeBSD, HP-UX, Linux, and Solaris.

26077 Push upgrade on Linux fails for non-default installation location

Using Avamar upgrade to push an Avamar client upgrade to a Red Hat EnterpriseLinux or SuSE Linux Enterprise Server client fails when the Avamar client software isinstalled in a non-default location. The use of the rpmoption --relocateto

install the Avamar client in a non-default location causes subsequent push upgrades

to fail.

IBM DB2 plug-in known problems and limitations

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

Release Notes

Known problems and limitations for all backup clients and plug-ins 27


28/55

200019 Backup to a Data Domain system fails with errors 15101 and 19168

A backup of considerable size that you save to a Data Domain system can fail withthe following errors:

2014-08-28 16:01:48 avtar Error : Backup completionfailed due to DDR 'Not Ready' state.

2014-08-28 15:57:30 avdb2 Error : Timeout on waitfor sub-process.

To work around this issue, specify the --

[avdb2]subprocesstimeoutsecs=350 option as text in Avamar

Administrator. You set this option in the Backup Command Line Optionsdialog box.The EMC Avamar for IBM DB2 User Guideprovides instructions in the Troubleshootingappendix.

IBM Lotus Domino plug-in known problems and limitations

There are no significant known problems for this release of the Avamar Plug-in for Lotus

Domino.

Microsoft Exchange VSS plug-in known problems and limitations

The following list describes known problems for this release of the Avamar Plug-in forExchange 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 tobrowse that database in ADDS it will fail. When you browse the ExchangeInformation Store it will time out and no databases will be displayed. As an interimsolution, if browsing the Exchange Information Store fails, determine which

database is corrupt using the Get-MailboxDatabasecommand from ExchangeManagement Shell. This will return an error similar to:

The Exchange server for the database object "Database1"wasn't found in Active Directory Domain Services. Theobject 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 asubsequent incremental backup of the database, the restore fails.

To work around this issue, rerun the restore and use the Move logs pathplug-in

option to move the existing log files to a different directory.

Release Notes



29/55

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, whenthe 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 theAvamarBackupUser account that you created on the first Exchange server.

3. You configure IPv6 on the first Exchange server and restart the server, but you donot complete the IPv6 configuration by using the "re-enable IPv6" option fromhttp://support.microsoft.com/kb/929852.

4. You back up the Exchange database on one or more of the Exchange servers inthe 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/929852to re-enable IPv6 on the firstExchange 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 whenthe database name contains special characters, such as ! @ # $ % ^ &* ( ) { } [ ].However, when you restore the database, the restore completes with an error thatthe path to the database is not found.

To avoid this issue, do not use special characters in Exchange 2007 databasenames.

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

The following list describes known problems for this release of the Avamar Plug-in forHyper-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 performimage-level backups with the Hyper-V VSS plug-in, then the two backups mayconflict.

To work around this issue, exclude virtual machines with backup applications fromimage-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 withmultiple proxies, the restore might take a long time.

To improve restore performance, ensure that the primary proxy node is the owner ofthe CSV to which you restore the virtual machines.

Release Notes

Microsoft Hyper-V VSS plug-in known problems and limitations 29
http://support.microsoft.com/kb/929852http://support.microsoft.com/kb/929852http://support.microsoft.com/kb/929852http://support.microsoft.com/kb/929852


30/55


31/55

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 upSQL Server data with the Avamar Plug-in for SQL Server, and you are also performingtransaction log backups with Microsoft SQL Server tools that truncate the transactionlog.

To work around this issue, restore the most recent Avamar full backup before the logtruncation and select the NORECOVERYrecovery option; restore the database from

the differential backup to a file by using the Avamar Plug-in for SQL Server; and thenuse SQL Server management tools to restore the database.

189394 Restore fails when an availability group database name includes an

apostrophe

When the name of a database in an AlwaysOn availability group includes anapostrophe ( ' ), backups complete successfully, but restore fails.

189507 Restore fails when an availability group database name includes Unicode

characters

When the name of a database in an AlwaysOn availability group includes one ormore Unicode characters, backups complete successfully, but restore fails.

197437 Restore fails when the transaction log on the secondary replica is not

synchronized during the backup

When you restore from an incremental backup of a database on a secondary replicain an AlwaysOn availability group environment, and you select the option to performa tail-log backup, the restore sometimes fails with an error that a log gap occurred,even though a log gap does not exist.

The issue occurs when the transaction log on the secondary replica is notsynchronized with the transaction log on other availability replicas when theincremental backup occurs.

To work around this issue, restore the backup to a file, and then use SQL Server toolsto restore the data to SQL Server.

Microsoft Windows client known problems and limitations

The following list describes known problems for this release of the Avamar Client forWindows.

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,000files, 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,000files, then restore F:\folderinstead 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 browsefor data on the By File/Foldertab on the Restoretab in the Backup, Restore andManagewindow, the system indicates that there is no version history for theselected data.

To work around this issue, type a path to the data by using a share name, or selectthe data to restore by using the By Datetab instead of the By File/Foldertab.

Release Notes

Microsoft Windows client known problems and limitations 31


32/55

NDMP Accelerator known problems and limitations

The following list describes known problems for this release of the Avamar NDMPAccelerator.

35153 Redirected restore of multiple volumes does not work

Redirected restore of multiple volumes fails and results in the following error:

avndmp Error : [avndmp_assist] Unable to redirectmultiple 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 directorieson an Isilon system, OneFS does not delete the snapshots after incremental backupsoccur. Snapshot-based incremental backups are also known as the FasterIncrementals 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 anupcoming release.

To work around this issue, perform the steps in the EMC Isilon OneFS Backup andRecovery Guideto view and delete snapshots for snapshot-based incrementalbackups.

61269 UTF-8 character sets do not appear correctly in Avamar Administrator for

restores on EMC VNXe NAS devices

When you restore data on a VNXe NAS device, UTF-8 character sets do not appearcorrectly in the Backup, Restore and Managewindow in Avamar Administrator. Thisis a known issue with the VNXe device and will be fixed in a future release.

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 Celerradevice, 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.

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 compliantSSL/TLS protocol that is incompatible with earlier versions of the Avamar Client forNetWare. 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.NLMin which 656 bytes of memory is

allocated but not released. The NetWare operating system reclaims this memorywhen STunnel unloads.

Release Notes



33/55

12641 Maximum backup size and number of files

For optimal performance, limit backups with the Avamar Client for NetWare to amaximum total size of 500 GB and less than 1 million files.

Furthermore, for best results, limit the maximum hash cache size to 10 MB. Thisbehavior is controlled by the Maximum client hash cache size (MBs)plug-in option.

Oracle database plug-in known problems and limitations

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

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 thefollowing errors:

RMAN-00571:================================================RMAN-00569: ========== ERROR MESSAGE STACK FOLLOWS

===========RMAN-00571:================================================RMAN-03002: failure of recover command at 07/05/201301:00:29RMAN-03015: error occurred in stored script Memory ScriptRMAN-06034: at least 1 channel must be allocated to executethis command

This issue is a known bug in Oracle 12C: Bug 17080042 : RMAN-6034 POINT IN TIMEPDB 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.

200018 AvamarRMAN installation packages for SUSE Linux Enterprise Server (SLES) 10

The Avamar server Downloadspage does not include specific AvamarRMANinstallation packages for SLES 10. Download and use the installation packages forRed 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 thisAvamar release.

Release Notes

Oracle database plug-in known problems and limitations 33


34/55

61278 Root-to-root replication overwrites Avamar server credentials

When you perform root-to-root replication from one Avamar server to another, thereplication process overwrites the server credentials on the target Avamar serverwith the credentials from the source Avamar server.

To avoid this issue, use the same credentials on both the source and target Avamarservers.

To resolve this issue if it occurs, reset the credentials to the original values on thetarget 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 anotherData Domain system, incorrect statistics appear for the file total in the avtarlog 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 avreplcommand line. Thefailure occurs because the colons (:) in the IPv6 address are illegal characters forAvamar domain names, which are created automatically on the destination Avamarserver during replication.

To work around this issue, specify the fully qualified domain name (FQDN) of thesource 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 Attributeand Enter Attribute Valueboxesfor the replication plug-in options.

SAP with Oracle plug-in known problems and limitationsThe following list describes known problems for this release of the Avamar Plug-in for SAPwith Oracle.

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 Deduplicationoption is not supported.

Sybase ASE plug-in known problems and limitations

The following list describes known problems for this release of the Avamar Plug-in forSybase ASE.

Release Notes



35/55

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 aparallelism value greater than 1 might fail with the following error:

Error from server server_name: Msg 937, Level 14, State 1Database '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 ASErelease 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 orrestore fails with the following error:

avsybase Error : Adaptive Server requires encryptionof the login password on the network.

To work around this issue, disable the Sybase network password encryption byrunning the following commands:

$isql -X

1> sp_configure 'net password encryption reqd',0

2> go

Upgrade known problems and limitationsThe following list describes known problems and limitations for upgrading to this releaseof 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 theupgrade may complete with errors but will be retried. However, the backup fails tocomplete. If this issue occurs, retry the backup after the upgrade completes.

To work around this issue, perform a push upgrade to an NDMP accelerator onlywhen backups are not in progress.

190984 Error code appears during push upgrade of NDMP accelerator, but upgrade

succeeds

When you perform a push upgrade of NDMP accelerator software, the followingerrors appear:

l Failure error code 50002, Avamar was unable to retrieve the log

or the log does not exist, appears in Avamar Client Manager.

l Dot or dot dot cannot be used anywhere in a directory

path...and Errors occurred preparing for backupappear in the

push upgrade log in the vardirectory on the NDMP accelerator.

However, the upgrade completes successfully despite the error messages.

Release Notes

Upgrade known problems and limitations 35


36/55

VMware known problems and limitations

The following list describes known problems for this release of Avamar for VMware imagebackup.

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 duringthe restore, the restore will fail with an error message, "vSphere Task failed:

'Detected an invalid snapshot configuration.'

190128 7.0 proxy compatibility with upgraded 7.1 servers

Each 7.0 proxy hosts eight separate avagentplug-ins, each of which can process

one backup or restore job. Each 7.0 proxy can therefore process as many as eightsimultaneous backup or restore jobs.

Each 7.1 proxy hosts a single avagentplug-in, but that single avagentplug-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 foreach 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 isbecause the Avamar server max_jobs_per_proxy setting is global. It applies to

every proxy in the environment. Therefore, in a heterogeneous environmentcomprising 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 asmany as 64 simultaneous backup or restore jobs (that is, eight jobs for each of theeight avagentprocesses). This might cause degraded performance. Similarly, a

max_jobs_per_proxy=1 setting would work fine for 7.0 proxies, but would limit7.1 proxies to performing only one backup or restore job at a time. This woulddrastically underutilize each 7.1 proxy.

These proxy compatibility issues only affect customers who upgrade their Avamar7.0 servers to 7.1. Customers deploying new 7.1 servers in their environments willdeploy new 7.1 proxies. Customers using existing 7.0 servers will already have 7.0proxies in their environment, and can deploy additional 7.0 proxies to support thatserver.

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 existing7.0 proxies to 7.1.

l If new 7.1 proxies will never be simultaneously deployed with the existing 7.0proxies, change the mcserver.xmlmax_jobs_per_proxy setting to 1.

Supportability package known problems and limitations

The following list describes known problems for this release of Avamar supportabilitypackages.

Release Notes



37/55

33892 Unnecessary Upgrade Client Downloads package option

The Upgrade Client Downloads package presents a Show advanced settingsoptionon the installation page called skip upgrading client download rpms.

If you select theValuescheckbox and click Continue, then client downloads are notupgraded on the system and the package no longer appears in Avamar EnterpriseManager or Avamar Installation Manager.

If you clear theValuescheckbox and click Continue, then the client downloadsupgrade works as designed.

To avoid the problem, do not select Show advanced settingson the installationpage.

International language supportThese sections provide important information about international language support inAvamar 7.1.

International language support in Windows environments

Supported languages for Windows environments include:

l Arabic

l Bulgarian

l Chinese (Simplified and Traditional)

l Croatian

l Czech

l Danish

l Dutch

l Estonian

l Finnish

l French

l German

l Greek

l Hebrew

l Hungarian

l

Italian

l Japanese

l Korean

l Latvian

l Lithuanian

l Norwegian

l Polish

l Portuguese (Brazilian)

l Romanian

l Russian

l Slovak

l Slovenian

l Spanish (Iberian and Latin American)

l Swedish

l Turkish

The following table describes additional international language support details inWindows environments.

Table 4 Windows environment international language support

Windows data type International language support details

Windows files and

folders

You can back up and restore individual files and folders with file and

folder names in local languages.

Release Notes

International language support 37


38/55

Table 4 Windows environment international language support (continued)

Windows data type International language support details

File and folders names appear in the local language in Avamar

Administrator and Avamar Web Restore.

Microsoft Exchange

databases

You can back up and restore databases with the database name in

supported local languages.

Microsoft Exchange

folders and messages

You can back up and restore individual folders and messages with the

folder or message name in supported local languages.

Microsoft SQL Server

databases

You can back up and restore databases with the database name in

supported local languages.

International language support in UNIX/Linux environments

Supported languages for UNIX and Linux environments include:

l Arabic

l Bulgarian

l Chinese (Simplified and Traditional)

l Croatian

l Czech

l Danish

l Dutch

l Estonian

l Finnish

l French

l German

l Greek

l Hebrew

l Hungarian

l Italian

l Japanese

l Korean

l Latvian

l Lithuanian

l Norwegian

l Polish

l Portuguese (Brazilian)

l Romanian

l Russian

l Slovak

l Slovenian

l Spanish (Iberian and Latin American)

l Swedish

l Turkish

The following table describes additional international language support details in UNIXand Linux environments.

Table 5 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.

Release Notes



39/55

Table 5 Windows environment international language support (continued)

Encoding International language support details

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 characterset names is not supported.

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 afile, folder, or identifier (for example, a database name) then that option is onlyassured 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 akeyboard.

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 Zipfile. When you unzip the Zip file, file and directory names with international charactersmight not restore properly due to inherent limitations in some Zip utilities.

To correctly restore files with international characters by using the Avamar Web Restorefeature, use a Zip utility that fully supports international characters. Examples of Ziputilities that have been confirmed to work properly include:

l Winrar 3.80 or later

Release Notes

Known limitations of local language support 39


40/55

l Winzip 12.0 or later

l 7zip 4.65 or later

Also, do not use Microsoft Windows compressed folders with the Avamar Web Restorefeature, as it is known that these compressed folders do not reliably handle internationalcharacters.

Support for non-UTF8 locales in the Management Console

Avamar includes support for browsing non-UTF8 file systems from the ManagementConsole. 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










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

Release Notes



41/55

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

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_0213x-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 notesThis 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 datahas been removed from /data*/partitions. In particular, if you ran disk tests before

startup, you might need to delete directories named QA.

Release Notes

Technical notes 41


42/55

Do not use the avmgr command

Improper use of the avmgrcommand 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 Foundstoneand Nessus. The Avamar solution has also been scanned by various customers by usingtools such as eEye Retina without issue. However, it is possible that the usage of otherport/vulnerability scanners might cause disruption to normal operation of the Avamarserver. Therefore, it might be necessary to disable scanning of the Avamar server ifproblems occur.

Maximum number of concurrent connections for each storage node

The maximum number of concurrent connections for eac

Documents

docu53934_Avamar-7.1-Release-Notes (7.1.0-302 ).pdf