Sie sind auf Seite 1von 63

EMC AVAMAR

VERSION 5.0 RELEASE NOTES

RELEASE NOTES
P/N 300-008-811 REV A14 JANUARY 28, 2011

These release notes contain information about the following releases of Avamar 5.0: EMC Avamar 5.0 (builds 5.0.0-407, 5.0.0-409, and 5.0.0-410) EMC Avamar 5.0 client releases 5.0.100-414 and 5.0.105-169 EMC Avamar 5.0 Service Pack 1 (server build 5.0.1-32) EMC Avamar 5.0 Service Pack 2 (server build 5.0.2-41) EMC Avamar 5.0 Service Pack 3 (server build 5.0.3-29 and client build 5.0.106-28) EMC Avamar 5.0 Service Pack 4 (server build 5.0.4-30) Topics include: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 How to Obtain Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 New Features, Improvements and Enhancements . . . . . . . . . . . . . . . . . 4 Server Dependencies for Features in This Release . . . . . . . . . . . . . . . . . 9 International Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 End of Life Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Known Issues and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Documentation Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Issues Resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Introduction

Introduction
EMC Avamar is backup and recovery software with integrated data de-duplication technology. EMC Avamar solutions solve 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 is transferred across the network and stored to disk. As a result, Avamar delivers fast, efficient daily full backups despite slow or congested infrastructure and data can be encrypted for added security. Avamar utilizes patented RAIN technology for high availability and a scalable grid architecture makes it easy to upgrade capacity and performance when needed.

How to Obtain Technical Support


Should you require assistance with your Avamar product, EMC Technical Support offers the following ways to obtain additional information and technical support: EMC Powerlink Avamar Support Page (page 2) EMC Avamar Support Forum (page 3) EMC Support Live Chat (page 3) EMC eServices (page 3) EMC Telephone Support (page 3) EMC Powerlink Avamar Support Page. Powerlink is accessed by logging on to: The Avamar Support page on EMC

https://support.emc.com/products/Avamar It provides direct links to various customer-facing resources, including: Product manuals and guides White papers Technical advisories You can subscribe to EMC Technical Advisories by clicking the Alert Me icon (shown left) next to product documents. By default, the Powerlink home page will show recently updated documents to which you are subscribed each time you log on to Powerlink. However, you can choose to be notified by email as new alerts become available. Knowledge base solutions - a compilation of issues and resolutions searchable by keyword End of Support/End of Service Life dates for all Avamar products and versions EMC Avamar Support forum EMC Support live chat

AVAMAR 5.0 RELEASE NOTES

Your Comments EMC Avamar Support Forum. The EMC Avamar Support forum is an online message board in which Avamar users can post questions and share product related information. The EMC Avamar Support forum is accessed by a link from the EMC Powerlink Avamar Support page or by logging on to: https://community.emc.com/community/support?view=all&community=2433 EMC Support Live Chat. You can also chat with an EMC Technical Support representative live in real time (24x7) by logging on to http://emc.powerlink.com, then selecting Support > Request Support > Live Chat. EMC eServices. You can initiate a technical support service request online by logging on to http://emc.powerlink.com, then selecting Support > Request Support > Create Service Request. EMC Telephone Support. You can also contact EMC Technical Support by telephone using the following North America and Worldwide telephone numbers:
United States Canada Worldwide

1-800-782-4362 1-800-543-4782 ++1-508-497-7901 NOTE: Also view http://powerlink.emc.com/km/live1/en_US/ Corporate_Information/About_EMC_Resources/H4165-cscphonelist-ho.pdf for additional worldwide telephone numbers.

In addition to some native language support (French, Italian, Spanish, Japanese, Chinese and Korean) available during local business hours for that geography, EMC Technical Support has translation services available should they be necessary.

Your Comments
Your suggestions will help us continue to improve the accuracy, organization and overall quality of our publications. You may email your comments to: BSGDocumentation@emc.com Please include the following information: Product name and version Publication name, part number and revision (for example, A01) Page numbers Other details that will help us address the documentation issue

AVAMAR 5.0 RELEASE NOTES

New Features, Improvements and Enhancements

New Features, Improvements and Enhancements


This topic introduces new features, improvements and enhancements that have been added since the Avamar 4.1.2 release.
New for Support for VMware 4.1. Release 5.0.3-29 includes code changes to support 5.0.3-29 interoperability with VMware vCenter 4.1 (ESX/ESXi 4.1).

Larger Capacity ADS Storage Nodes. Avamar GEN3 storage nodes with Avamar 5.0 software installed offer 3.3 TB of licensable storage capacity per node, compared to 2 TB licensable storage capacity per node available in previous versions. Larger capacity storage nodes mean that fewer nodes are required to protect the same amount of data, which results in reduced Total Cost of Ownership (TCO). Improved Server Maintenance Scheduling. Server maintenance activity scheduling has been greatly enhanced by dividing each calendar day into three user-defined operational windows:
Backup Window Blackout Window

That portion of each day reserved for performing backups. The server is fully functional and accessible during this time. That portion of each day reserved for performing server maintenance activities (primarily checkpoint and garbage collection) that require unrestricted access to the server. The server is read-only for at least part of that time. If these activities complete before the allotted time, the server begins performing Maintenance Window tasks. That portion of each day reserved for performing routine server maintenance activities (primarily checkpoint validation). The server is generally accessible during this time for backup and restore activities, but these activities should be minimized if possible in order to optimize these maintenance tasks.

Maintenance Window

More Efficient Checkpoint Validation. The checkpoint validation mechanism (also known as HFS check) has been updated to optimize checkpoint validation tasks by performing complete HFS checks on only new and modified stripes by default. This change significantly reduces the amount of time necessary to validate checkpoints and ensures that the data most likely to be at risk of corruption (new stripes and modified stripes) is checked completely. NAT Support for Multi-Node Avamar Servers. The Avamar 5.0 server can be configured to support external IPs that are different from internal IPs to support interoperability with NAT firewalls and routers. Elimination of ADS Switch or NIC as Single Point of Failure. An Avamar Data Store system can optionally be configured with two switches, each connected to a different NIC on each Avamar Data Store node, to support high availability in the event that a NIC or a switch fails. Server Recovery Option for Windows Server 2003. Avamar 5.0 provides the ability to perform server-level backup and hardware independent recovery of Windows Server 2003 32-bit and 64-bit systems. AVAMAR 5.0 RELEASE NOTES 4

New Features, Improvements and Enhancements ConnectEMC Support. Avamar 5.0 provides full integration with ConnectEMC.

Secure Deletion of Backups. Avamar 5.0 supports the ability to securely delete or shred data in accordance with the U.S. Department of Defense 5220.22-M (ECE) standard. JRE 1.6 Support for Avamar Administrator. With Avamar 5.0, you can install Java Runtime Environment (JRE) 1.6 on client machines to launch the Avamar Administrator either when it is installed on the client or when you use Enterprise Manager with the Java Webstart technology. Note that the JRE cannot be greater than JRE 1.6_18. New Clients. The following client platforms and applications are now supported:

Operating systems: Cent OS (v4,v5) Debian (v4,v5) HP/UX on PA-RISC (11iv1-3) MacOS 10.6 Oracle Unbreakable Linux (v4,v5) RHEL 5 on zLinux (IBM System z) Solaris 10 x64 with VCS 5.0 SLES 11 x64 SLES 10SP3 on zLinux (IBM System z) Solaris 10 x86 Solaris 8 SPARC with VCS 5.0 Windows Server 2008 R2 Windows 7 NDMP NetApp OnTap 7.3.x Applications: DB2 9.7 (AIX 6.1, RHEL 5.x) Exchange Server 2010 (Windows 2008/Windows 2008 R2) Lotus 8.5.x (Windows 2008, Windows 2008 R2) Oracle 11Gr2 on RHEL 5 & SLES 10 Oracle 10 on Solaris 10 x64 with VCS 5.0 Oracle 9.2 on Solaris 8 SPARC w/VCS 5.0 SharePoint Server 2007 (Windows 2008 R2) SQL Server 2008 (Windows 2008 R2) SQL Server 2005 (Windows 2008, Windows 2008 R2) Passive node backup for Exchange 2010 and 2007 Veritas Cluster Server (VCS) support: VCS 4.1 on Solaris 8 SPARC and Solaris 10 x86 file systems VCS 5.0 on Solaris 10 SPARC VxFS file systems Extended client support on Microsoft Windows Windows Server 2008 R2 x64 bit. Windows Server 2008 R2 x64 bit Cluster (A/A and A/P). AVAMAR 5.0 RELEASE NOTES 5

New Features, Improvements and Enhancements Windows Server Core Windows 7 Extended Capabilities for Windows and Mac Desktops/Laptops. This release delivers new features that build on the extended capabilities available for desktop and laptop computers running Avamar client for Windows or Avamar client for Mac. These new features are specifically intended for desktop and laptop users on those computing platforms: User interface improvements to enhance speed, usability, and appearance, including: Faster server processing and page generation Easy access to high-use menu items available from system tray or Dock On Windows, double-click the system tray icon to open the Restore UI Pause/resume or stop tasks through the clients Progress Window Minimize/restore and close/open actions for Progress Window Plain language notifications and enhanced balloon messages Global Entries per Page setting Notifications on by default Time displayed using the clients local timezone For each user/client, a two-week historical view of all activity, including: Status of each backup The folders and files included in each successful backup Status of each restore Canceled tasks When enabled by the administrator, users can change the earliest start time of their automatic backups through the web browser interface New directory service configuration utility Microsoft Internet Explorer 6 support Memory management improvements Avamar Activation Manager New Features. This release provides additional Avamar Activation Manager tools designed primarily for administrators working with large numbers of desktop and laptop clients: Create new groups as needed from within Avamar Activation Manager Move clients to new Avamar server from within Avamar Activation Manager Track the status of client moves through Process Viewer and the log Enhanced logging, and plain language log entries Activation request queuing and retry logic Improved status and error messages Log export, print, and clear New directory service configuration utility

AVAMAR 5.0 RELEASE NOTES

New Features, Improvements and Enhancements Enhanced Capabilities for Protecting VMware Environments. In addition to the capabilities offered in previous releases (guest-level backup and restore, VCB 3.0 and ESX Server backup and restore), Avamar 5.0 provides a tight integration with vSphere 4.0 environments, including: Image-level backup and restore Block-based incremental backups File-level recovery from image backups Ability to schedule and manage backups using the policy-based features of the Avamar Administrator graphical management console Other Client Improvements and Enhancements. In addition to the previously mentioned new features, Avamar 5.0 also offers the following client improvements and enhancements: Improved backup performance for Oracle databases Ability to utilize change logs for faster backups of Oracle databases Re-architected NDMP support for NetApp filers for improved performance and scale Optional multi-threading capabilities for file system backups that leverage multi-core servers Windows 2003 Server system state backup and recovery Enhanced file-level recovery options for Celerra by way of the NDMP protocol that supports multi-file restore in a single recovery operation New system backup/recovery process for Windows Server 2008 New Windows cluster configuration wizard
New for 5.0.105-169

Ability to roll forward (recover) DB2 database restores to a specific point in time, to the end of the archive logs, or to the end of the backup Support for Oracle RMAN retention periods Support for point-in-time recovery and multi-channel backup with the Oracle plug-in Support for point-in-time recovery (date/time or SQL log mark) and automated log tail backups for Microsoft SQL File level recovery for NetApp devices Windows Disaster Recovery (DR) for Windows Server 2008, Windows Server 2008 R2 and Windows 7 Support for Windows 2008 R2 VSS express writers Support for Exchange Server 2007 CCR Passive Node backups Support for Lotus Domino Attachment and Object Services (DAOS) Improved documentation guidelines to improve Lotus plug-in performance

AVAMAR 5.0 RELEASE NOTES

New Features, Improvements and Enhancements


New for New Guides Included with version 5.0.105-169. 5.0.105-169 provides several new guides:

Version 5.0.105-169

The new Avamar VMware Guide addresses various customer concerns and request for enhancements. The information in this publication replaces information previously found in the Avamar System Administration Guide and Avamar Backup Clients User Guide. The new Avamar for Windows Servers User Guide describes how to install, configure, administer, and use the Avamar Windows Client and Avamar Windows Cluster Client, as an Avamar Administrator. The information in this publication replaces information previously found in the Avamar System Administration Guide and Avamar Backup Clients User Guide. The new Avamar for Exchange VSS Client User Guide describes how to install, configure, administer and use the Avamar Exchange Client for VSS writer backup and recovery on Microsoft Exchange Server 2010 and 2007 platforms.
New for Guides Integrated with version 5.0.105-169. Version 5.0.105-169 removes 5.0.105-169 two guides from the Avamar documentation set by fully integrating the

information into the Avamar System Administration Guide: Avamar Activation Manager Administration Guide Avamar Desktop/Laptop Guide

New for 5.0.106-28 Additional Features for Windows and Mac Desktops/Laptops. Client and 5.0.3-29 version 5.0.106-28 and server version 5.0.3-29 add new features to the extended

capabilities available for desktop and laptop computers running Avamar client for Windows or Avamar client for Mac: User interface and online help localized in 10 languages International Language Support (page 10) describes this feature. Transparent login option This option eliminates the web UI login screen for Windows clients by using a secure channel to transfer authentication information. The login screen still appears for Mac clients. To enable this feature: 1. Log in to the Avamar utility node as root. 2. Change the working directory to: /usr/local/avamar/etc 3. Open ldap.properties in a plain text editor. 4. Add the key user-login-required and set its value to false: user-login-required = false 5. Modify the value of user-login-module to either kerberos or ldap: user-login-module = kerberos 6. Save and close ldap.properties. 7. Restart the Avamar Desktop/Laptop server: dpnctl stop dtlt dpnctl start dtlt

AVAMAR 5.0 RELEASE NOTES

Server Dependencies for Features in This Release Option to use LDAP authentication without Kerberos encryption This option removes Kerberos encryption from all data transmissions used for LDAP authentication. When this option is enabled, LDAP authentication data transmissions are sent as cleartext. To enable LDAP authentication without Kerberos encryption: 1. Log in to the Avamar utility node as root. 2. Change the working directory to: /usr/local/avamar/etc 3. Open ldap.properties in a plain text editor. 4. Modify the value of user-login-module to ldap: user-login-module = ldap 5. Save and close ldap.properties. 6. Restart the Avamar Desktop/Laptop server: dpnctl stop dtlt dpnctl start dtlt

Server Dependencies for Features in This Release


The following lists the minimum server level for specific features in this release: VMware vSphere support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) NAT support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) Windows and Mac Desktop and Laptop support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) Desktop and Laptop features in this release require 5.0 Service Pack 2 server (build 5.0.2-41 or greater) except where client version 5.0.106-28 and server version 5.0.3-29 are specified in the feature description. The following SQL features requires Avamar 5.0 Service Pack 1 server (build 5.0.1-32 or greater): Automated log tail backups Point in time restore Force incremental backups

AVAMAR 5.0 RELEASE NOTES

International Language Support

International Language Support


Windows Environments
Supported languages for Windows environments include: Arabic Bulgarian Chinese (Simplified and Traditional) Croatian Czech Danish Dutch Estonian Finnish French German Greek Hebrew Hungarian Italian Japanese Korean Latvian Lithuanian Norwegian Polish Portuguese (Brazilian) Romanian Russian Slovak Slovenian Spanish (Iberian and Latin American) Swedish Turkish

Files and Folders


Ability to backup/restore files and folders (directories) with names in local languages at the granularity of individual files/folders. File and folder names appear in the local language in the Avamar restore user interfaces (both Avamar Administrator Java client and web-based Avamar web restore user interface).

Microsoft Exchange
Ability to backup/restore databases with the database name in local languages as specified above. Ability to backup/restore individual folder and messages with the name in local languages as specified above.

Microsoft SQL Server


Ability to backup/restore databases with the database name in local languages as specified above.

AVAMAR 5.0 RELEASE NOTES

10

International Language Support


New for 5.0.106-28 and 5.0.3-29

Extended Desktop/Laptop Functionality


Client version 5.0.106-28 and server version 5.0.3-29 add additional international language support to the extended capabilities available for desktop and laptop computers running Avamar client for Windows or Avamar client for Mac. This release provides localized versions of the client UI, the web browser UI, and the online help for the following languages. LANGUAGE Chinese (Simplified) English French German Italian Japanese Korean Portuguese Russian Spanish COUNTRY China United States France Germany Italy Japan South Korea Brazil Russia Latin America

Client UI. The client UI uses the locale of the operating system. If that locale is not supported, it uses: (Windows) United States English. (Mac) The next available supported locale on the operating system's Languages & Text control. If none of the locales on Languages & Text is supported, it uses United States English. To change the Windows client UI to another supported locale: 1. Right-click the system tray icon. 2. From the context menu, select the submenu Languages and select a language. 3. Right-click the system tray icon again and select Exit. 4. On the Stop Client Warning, click Yes. 5. In Windows, click Start > Programs > EMC Avamar > Client. To change the Mac client UI to another supported locale, select that locale in the operating systems Languages & Text control. Web Browser UI. By default, the web browser UI is displayed in the locale used by the web browser if that locale is supported. If the locale used by the web browser is not supported, the client UI appears in English. To change from the displayed locale to any of the supported locales, select one from the language list on the configuration menu. The locale changes immediately and a cookie is set to store the choice over multiple sessions. AVAMAR 5.0 RELEASE NOTES 11

International Language Support

Unix/Linux Files and Directories


Ability to backup/restore UTF encoded files and directories with names in local languages at the granularity of individual files/directories. File and folder names appear in the local language in the Avamar restore user interfaces (both Avamar Administrator Java client and web-based Avamar web restore user interface). Supported languages include: Arabic Bulgarian Chinese (Simplified and Traditional) Croatian Czech Danish Dutch Estonian Finnish French German Greek Hebrew Hungarian Italian Japanese Korean Latvian Lithuanian Norwegian Polish Portuguese (Brazilian) Romanian Russian Slovak Slovenian Spanish (Iberian and Latin American) Swedish Turkish

EUC-JP Support
Ability to backup and recover EUC-JP encoded files and directories with names in the Japanese language on Solaris. NOTE: EUC-JP encoded file and directory names will not be correctly rendered in either Avamar Administrator Java client or the web-based Avamar web restore user interface.

AVAMAR 5.0 RELEASE NOTES

12

International Language Support

Known Limitations of Local Language Support


Cross-platform redirected restore of files and directories with international character set names is not supported. With the Avamar web restore user interface, certain international characters might not render properly due to inherent limitations in zip tools that might not fully support international characters. Client machine hostnames must consist entirely of ASCII characters. The client software installation path must consist entirely of ASCII characters. Policy objects (such as, users, groups, datasets, schedules, retention policies, notification profiles, and so forth) must consist entirely of ASCII characters. Log files will not correctly render non-ASCII characters. Error, warning and informational messages will render non-ASCII characters incorrectly, both to the user's screen and to log files. Log files based on user-defined names (for example, database names) will not work correctly. Non-ASCII characters cannot be 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. Sorting is not localized. Sorting is strictly by byte-ordinal value. The product does not support the ability to enter local language characters using a keyboard into the Avamar user interfaces. The Avamar Management Console Command Line Interface (MCCLI) and avtar support only ASCII arguments on the command line. Restoring International Characters With Avamar Web Restore. When performing restores using the Avamar Web Restore feature, restores containing directories or multiple files are delivered in the form of a zip file. When unzipping the zip file, file and directory names containing international characters might not restore properly due to inherent limitations in some zip utilities. Therefore, in order to correctly restore files containing international characters using the Avamar Web Restore feature, you must use a zip utility that fully supports international characters. Examples of zip utilities that have been confirmed to work properly include: Winrar 3.80 or later Winzip 12.0 or later 7zip 4.65 or later Also be advised that Microsoft Windows compressed folders are specifically known to not reliably handle international characters and should not be used with the Avamar Web Restore feature.

AVAMAR 5.0 RELEASE NOTES

13

End of Life Notification

End of Life Notification


Beginning with this release, formal support for the following legacy client platforms and applications is officially discontinued: DB2 8.2 HP-UX 11.0 (PA-RISC) Microsoft Exchange 2000 Microsoft SQL Server 2000 Microsoft Windows 2000 Microsoft Windows 2000 Server NetApp Data ONTAP 6.3, 6.4, 6.5, 7.0.4, 7.0.5 and 7.0.6

AVAMAR 5.0 RELEASE NOTES

14

Known Issues and Limitations

Known Issues and Limitations


The following topics discuss known issues and limitations in this release of Avamar and include temporary solutions if available.

General
Non-Supported Third-party Software Cannot be Installed on an Avamar system. Except for software that is installed initially with the Avamar system as part of the kickstart image, or as specified by EMC Support, it is not supported to install or run any third-party products on any nodes of an Avamar system.

Server
Version Downgrades Not Supported. Downgrading the Avamar server software to an earlier version is not supported under any circumstances. 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 the /data*/partitions. In particular, if disk tests were run prior to startup, there might be directories called QA that must be deleted. Do Not Use the avmgr Command. Improper use of the avmgr command line utility can destroy all access to data in the Avamar system. It should only be used at the explicit direction of EMC Technical Support. Vulnerability Scanning. As part of every Avamar release, the product is scanned for vulnerabilities using at least two commonly-used vulnerability assessments tools. The 5.0 release was scanned with Foundstone and Nessus. The Avamar solution has also been scanned by various customers 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. Configuring ConnectEMC After Initial Installation or Upgrade. To configure ConnectEMC after initial installation or upgrade, perform the following: 1. Open a command shell.
User=admin

2. Do one of the following: IF Administering a single-node server. Administering a multi-node server. DO THIS Log into the server as user admin. Log into the utility node as user admin.

3. When prompted for a password, type the admin password and press ENTER. AVAMAR 5.0 RELEASE NOTES 15

Known Issues and Limitations


Stop MCS

4. Type: dpnctl stop mcs 5. Switch user to root by typing: su 6. When prompted for a password, type the root password and press ENTER. 7. Change directory to /usr/local/avamar/var by typing: cd /usr/local/avamar/var 8. Do one of the following: IF Reconfiguring ConnectEMC after initial installation. Reconfiguring ConnectEMC after a server upgrade. DO THIS Type the following on a single command line: /usr/local/avamar/lib/dpnutils/ initialize_connectemc --config=install.conf Type the following on a single command line: /usr/local/avamar/lib/dpnutils/ initialize_connectemc --config=upgrade.conf

User=root

user=admin

9. Switch to user admin by typing: exit 10. Restart the MCS by typing: dpnctl start mcs ConnectEMC Requires DialHome. If you are running Avamar server version 5.0.0-410 or later and have ConnectEMC enabled, you must have DialHome contacts defined to facilitate auto-generation of future service requests. To define DialHome contacts, send the following email message: To: Support@emc.com CC: Avamar_DialHome_Contacts@emc.com Subject: Request Avamar DialHome Contact Update Please provide the following information in the body of the email message: Site ID: Customer Name: Customer Location: (street, city, state, postal code, country) Primary DialHome Contact Name: Primary DialHome Contact Email: Primary DialHome Contact Phone: Alternate DialHome Contact Name: Alternate DialHome Contact Email: Alternate DialHome Contact Phone:

Restart MCS

AVAMAR 5.0 RELEASE NOTES

16

Known Issues and Limitations Testing ConnectEMC Configuration. To test if ConnectEMC is properly configured, use the following mccli command: mccli event publish --code=22915 Restart the mcsnmp Program after Upgrade. If the Avamar software is configured to use SNMP, you should stop the mcsnmp service prior to upgrading to the latest release of Avamar, and restart it after the upgrade is complete (20650). To stop the mcsnmp service prior to upgrading: 1. Log in to the Avamar utility node as root. 2. Type the following: /usr/local/avamar/bin/mcsnmp stop To restart the mcsnmp program after upgrading: 1. Log in to the Avamar utility node as root. 2. Type the following: /usr/local/avamar/bin/mcsnmp start

Avamar Enterprise Manager


Incorrect Avamar Administrator Version Launched Following Server Upgrades. Following a system upgrade, the first time Avamar Administrator is launched using Avamar Enterprise Manager it might be the wrong version. The first launch might launch the pre-upgrade version of Avamar Administrator. Subsequent launches will launch the correct (upgraded) version of Avamar Administrator (6621). Replication Schedule. The replication feature provides support for a dedicated replication schedule that is separate from other scheduled maintenance activities. While it is possible to use multiple schedules to control replication, each additional schedule must be created and managed at the command line using scripts. Avamar Enterprise Manager Can Only Manage Like Version Avamar Servers. Due to known limitations with Java web services, Avamar Enterprise Manager can only connect to, and manage Avamar Administrator servers running the same version Avamar software. Effectively, this means that Avamar Enterprise Manager can only manage Avamar servers running the same version Avamar software (10587).

Avamar Administrator
1.5.0_16 Online Help Issues. If you download Avamar Administrator using the Webstart feature and your computer is running JRE 1.5.0_16, online help will not be available. There are two interim solutions: either upgrade your JRE to version 1.6 or download the Avamar Administrator install file directly from the Avamar server Documents and Downloads web page (23033). Schedule Start Times and End Times. If you select a different start time in the schedule, you must reselect the desired end time. AVAMAR 5.0 RELEASE NOTES 17

Known Issues and Limitations Multi-Display Configurations. When running the Avamar Administrator on multiple displays, you might encounter a Java exception if Avamar Administrator is not running on the main display. This is a Java bug that has been fixed in JRE version 1.6. Users running multiple displays should use JRE 1.6 or later. Bytes Protected is Updated Twice Daily. By default, the Avamar server detail Bytes protected value is updated twice daily according to the new Statistics Schedule. If you want this statistic to be updated more frequently, change the Statistics Schedule settings accordingly. Stale Java Temporary Internet Files. Under certain circumstances, stale Java temporary internet files can cause errors when attempting to launch Avamar Administrator directly from an Avamar Enterprise Manager session. If this occurs on Windows computers, select Start > Control Panel > Java. The Java Control Panel Appears. In the Temporary Internet Files area, click Delete Files... A confirmation dialog box appears. Ensure that all temporary internet file types are selected and click OK. Activity Monitor Limitations. The jobs that were started before the administrator server was stopped are not displayed in the Activity Monitor when the administrator server is restarted (1078). Software Conflicts. The Avamar Administrator software is known to have conflicts with software packages such as Black Ice and Timbuktu (1657). Client Name Change Impacts License Quota. Activities reporting data for a client will still have its old name when the name of client is changed. This causes new activities for the same client to be treated 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, EMC Technical Support should be consulted so that we can update the database correctly (6781). Email Home Messages Must Be Sent Using a Valid Email Account. The EMC Technical Support email system is unable to receive messages that do not originate from valid email accounts. Therefore, messages generated by the Email Home feature must be sent using a valid email account or they will never arrive. Furthermore, EMC Technical Support will be completely unaware that these programmatically-generated messages were rejected, and because no valid sending email account is specified, warnings to the sender that these messages could not be sent will never be viewed by anyone who can correct the problem (9261). Capacity Information Following a Rollback. When an Avamar system rollback occurs, the historical capacity graph and report will not have any data from the date of the rollback to the checkpoint date. As a result, the graph will show a flat line and the capacity forecasting information and graph will be skewed. In some cases, there will be insufficient data to provide any information or graph at all. Forecasting information and graph will be come more accurate 30 days after the date of rollback (12920). netsnmp "Cold Start" Messages. In order to implement an interim solution for bug 11872, Avamar must restart the netsnmp agent frequently. Because the netsnmp agent will generate a "cold start" message on each restart, customers will see additional "cold start" messages that are not related to actual restarts of

AVAMAR 5.0 RELEASE NOTES

18

Known Issues and Limitations 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 actual Avamar system restart and a "cold start" message generated as the result of netsnmp agent restarts (13019). MCCLI Group Export Command Only Supports Regular Groups. The mccli group export command only supports exporting of REGULAR groups. It does not supports exporting of VCENTER groups (that is, Proxy or Virtual Machine groups) (16942). Each VMware Proxy Client Must Have Unique IP Address. Be advised that currently the only way Avamar Administrator can differentiate between VMware Proxy clients is by IP address. Therefore, you must ensure that each proxy client within the same vCenter has a unique IP address (16357). VMware File Level Restores Do Not Report Progress Bytes. Currently, VMware file level restore jobs do not report progress byte updates (16727). VMware Image Dataset Change Block Tracking Disabled By Default. By default, the VMware Image Dataset disables change block tracking. Because the change block tracking feature can drastically reduce backup times and improve performance, EMC anticipates that most customers will want to enable this feature. The interim solution is the open the VMware Image Dataset and select Enable change block tracking option (16956). VMware File Level Restore Browse Limitations. When performing VMware file level restores, browsing a directory (folder) containing a large number of files and subfolders can take up to two minutes to complete. Furthermore, browsing a directory (folder) containing more than 5000 files and subfolders will result in a silent timeout in which Avamar Administrator will display nothing for the browsed folder contents. This behavior applies to both browsing the VMware Image Backup stored on the Avamar server, as well as browsing virtual machine filesystems during redirected restores. The interim solution for browsing a VMware Image Backup stored on the Avamar server is to avoid browsing into a folder with large numbers of files and subfolders. Instead, select the entire directory (folder) to be restored. The interim solution browsing virtual machine filesystems during redirected restores is to browse another directory (16096). Backup of .vmx and nvram Files Might Fail Because the ESX Server Has an Exclusive Lock on the Files. Because of a known limitation in the vCenter software, backing up .vmx and nvram files might fail because the ESX server maintains an exclusive lock on these files. If the vCenter attempts to use an ESX server other than the one that has the exclusive lock on the file to back up the files, the server without the lock will be unable to read the .vmx and nvram files to back them up. The interim solution for this issue is to add the --x22=8192 option to the dataset for scheduled group backups, or to the Backup Options dialog box for on-demand backups. This allows the backup to complete even if the .vmx file is not backed up. Because the .vmx file contains the VM configuration information, when restoring the backup, you can select Restore to original virtual machine or Restore to existing virtual machine, but you cannot select Restore to a new virtual machine. To restore to a new virtual machine, you must manually create AVAMAR 5.0 RELEASE NOTES 19

Known Issues and Limitations a VM with the same configuration as the original VM, then use the Restore to existing virtual machine option to restore the backup to the newly created VM. Restoring to a manually-created VM will issue new virtual NIC MAC addresses and new virtual disk serial numbers which may cause license activation issues with VMs running Windows. Special Characters Not Allowed in Datastore, Folder or Datacenter Names. Because of a known limitation in the VCenter software, when special characters are used in the datastore, folder or datacenter names, the.vmx file will not be included in the backup. The following is a list of the special characters (in the format of character/escape sequence format) that will cause the .vmx file to fail to be backed up: & %26 + %2B / %2F = %3D ? %3F % %25 \ %5C ~ %7E ] %5D As a long-term solution for this issue, you should upgrade the VMware software to a version where this issue is resolved. However, until a fix is provided by VMware, the interim solution for this issue is to rename the datastore, folder, and/or datacenter names without using these special characters. Backups Scheduled for 12:00 AM in Singapore Time Zone Function Incorrectly. For backups scheduled for the Nth day of every month at 12:00 AM in the Singapore timezone, the backup will actually occur on the N+1 day. This is only applicable in the Singapore timezone, and only applicable for backups scheduled at 12:00 AM. As an interim solution, set the backup for another time other than 12:00 AM. (24285) Restore to Existing VM with Existing Snapshots Fails. If an existing virtual machine has existing snapshots, restore to the VM will fail. The workaround for this issue is delete existing snapshots before performing a restore. (24318)

All Backup Clients


Can Perform Only One Operation Per Client. As currently configured, Avamar client agents can only execute one operation at a time. Therefore, it is not possible to perform multiple simultaneous backups or restores on the same client. Limited Client-Based Restores. For Avamar clients that are not using the extended capabilities available for desktop and laptop computers, client restores are performed using a web browser and should be limited to only a few files. If many files need to be restored, this should be done by an administrator using Avamar Administrator. AVAMAR 5.0 RELEASE NOTES 20

Known Issues and Limitations 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), not the local time. This can cause confusion if users are looking for a particular log file. Wildcard Characters Not Implemented During Restore. Wildcard pattern matching characters such as * and ? are not implemented when restores are performed. Only partial paths are permitted to filter portions of a backup to be restored (878). Backups Over Seven Days Long 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. Simply take another backup to complete the process (1403).

Windows Backup Clients


Firewall Software Must Be Configured to Allow Communication with Avamar Server. Firewall software inherently interferes with the Avamar servers ability to communicate with Avamar clients by disabling inward connections to most data ports. Therefore, be advised that if you are running 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), you must configure the firewall application to allow bidirectional communication between the Avamar Windows 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 is dependent on which firewall application you are running. Refer to your firewall documentation for additional information. Potential Conflicts With Anti-Virus Software. Initial backup activity might cause anti-virus applications such as McAfee VirusScan Enterprise to consume large amounts of CPU capacity (as high as 100% of CPU capacity). This can occur when anti-virus software is running and the Avamar client examines large numbers of files for any reason. Windows User Account Control (UAC) Install Issues. If installing any Avamar client on Windows Vista, Windows Server 2008 or later operating system, Windows User Account Control (UAC) is known to interact unfavorably with the installation process. This is as-designed Microsoft Windows behavior that is completely out of Avamars control. The interim solution is to temporarily disable UAC prior to installing the Avamar client software. This is accomplished by opening a command prompt as Administrator (that is, right-click Command Prompt shortcut and select Run as administrator). From the Command Prompt window opens, use the cd command to navigate to the directory where the installation package has been saved, then type the following command: msiexec /package AVAMAR-INSTALLATION-PACKAGE.msi, where AVAMARINSTALLATION-PACKAGE is the specific type and version Avamar client software you are installing.

AVAMAR 5.0 RELEASE NOTES

21

Known Issues and Limitations Avamar Simple Client Console May Not Start after Upgrade on Microsoft Windows 7. After upgrading an existing Avamar client on Microsoft Windows 7 to the 5.0.106-28 build, the Avamar Simple Client Console (AVSCC) may not start automatically with User Account Control (UAC) enabled. The interim solution for this issue is to either install the client in a different location (for example, c:\program files\avs1), or rename the avscc.exe program after installation and change the startup shortcut to point to the renamed executable. Cannot Specify Exclude/Include Lists within Windows System Tray Applet. It is not possible to specify exclude or include lists or optional avtar options when using the Windows system tray applet Back Up Now command. If you need to apply special rules to a Windows client backup, initiate the backup using Avamar Administrator. Interaction with Samba Mounts. Restores of network mounted drives across Samba to Unix might not result in the proper file user and group permissions. Incompatibility with Venturi Wireless Client. Backups of Windows clients with the SSL encryption option enabled will sporadically fail with older versions of the Venturi Wireless client. Upgrading the Venturi Wireless client to version 3.1.4 appears to resolve the incompatibility. Windows File Attributes Are Converted to Unix Style Attributes. Windows style file attributes (Read-Only, System, Hidden and Archive) are converted to Unix style file attributes (rwxrwxrwx) when displayed in Avamar Administrator. The Windows file attributes (except for Archive) are set correctly when files are restored on Windows clients (2485). You Cannot Combine UNC and non-UNC Paths in a Single Backup. Currently, datasets and on-demand backups cannot use both UNC and non-UNC paths; each dataset and on-demand backup must contain only one type of path syntax. For example, if UNC style syntax is used (for example, \\SERVER\DIR), then it cannot be combined with other path syntax. Specifying a UNC path with other non-UNC paths will cause the UNC path to be silently ignored (7127). Windows Server 2008 System State Restore Fails When Top-Level Node Is Selected. When using the Avamar Windows VSS plug-in to restore System State, do not select the top-level node in the VSS System State backup. Otherwise restore will fail with an error message Computer must be restarted in Directory Services Restore Mode in order to restore Active Directory. Only the Active Directory writer can be restored online. Online restore of other BootableSystemState writers is not supported. See the EMC Avamar for Windows Servers Users Guide for more information. Certain Avamar Warnings That Appear In Windows Server 2008 System Restore Can Be Ignored. When performing a Windows client System State Restore in Windows Server 2008 using Avamar, warnings like the following can be ignored:
2009-08-27 21:24:48 avtar Warning <7834>: Access denied due to security constraints, path:"C:\ProgramData\Application Data". 2009-08-27 21:24:48 avtar Warning <7870>: Pre-existing directory cannot be restored, path:"C:\ProgramData\Application Data". 2009-08-27 21:24:48 avtar Warning <7834>: Access denied due to security

AVAMAR 5.0 RELEASE NOTES

22

Known Issues and Limitations


constraints, path:"C:\ProgramData\Desktop". 2009-08-27 21:24:48 avtar Warning <7870>: Pre-existing directory cannot be restored, path:"C:\ProgramData\Desktop".

Backing Up NetApp Shares From Windows Clients is Not Supported. Backing up NetApp shares from Windows Vista, Windows 7, Windows 2008 Server or Windows Server 2008 R2 using Avamar Windows Client software. Instead, you must back up NetApp shares using the Avamar NDMP Accelerator. Integrated System Recovery Limited to Windows Server 2003. Avamar integration with EMC Homebase does not support backup of Windows 2008 and Windows 2008 R2 at this time. Incompatibility of Integrated System Recovery backups from previous version of Avamar. Avamar client 5.0.105-169 includes EMC Homebase version 6.4. Because backups created using Homebase version 6.3.x are not compatible with backups created using Homebase version 6.4, upgrading to Avamar client 5.0.105-169 will cause Integrated System Recovery backups created with previous versions of Avamar to be unrecoverable. To recover from Integrated System Recovery backups created with previous versions of Avamar, you must downgrade to a version of Avamar prior to client 5.0.105-169. Windows Server Update Services Role May Not Be Recovered Correctly. When performing a disaster recovery of a Windows Server 2008 R2 with the Windows Server Update Services (WSUS) role, the WSUS role may not be recovered correctly and the following errors might be displayed:
The The The The The The Reporting Web Service is not working API Remoting Web Service is not working Server Synchronization Web Service is not working Client Web Service is not working SimpleAuth Web Service is not working DSS Authentication Web Service is not working

The interim solution to this problem is to reconfigure the WSUS role after recovery. Temporary directory ignored for VSS Plug-in. In the Backup Command Line Options dialog box for the VSS plug-in, the Temporary directory for the plug-in option is ignored. (18601) Windows Server Role with Database Using Microsoft SQL Server. If the Windows server role has been configured to use an Microsoft SQL database rather than the Windows Internal Database, then in addition to backing up the system state using the Avamar Windows VSS plug-in, you should also use the Avamar SQL plug-in to back up the databases of the server role. To restore the server role in this case, you should restore both the system state and perform an SQL server disaster recovery. Then use the Avamar SQL client to restore the system databases and the databases used by the server role. For information about how to install Windows SQL client and back up and restore SQL server databases, refer to Avamar SQL Server Client User Guide. For information regarding to perform SQL Server disaster recovery, refer to http:/ /msdn.microsoft.com/en-us/library/ms189302.aspx. (19219)

AVAMAR 5.0 RELEASE NOTES

23

Known Issues and Limitations Disaster Recovery Wizard Fails to Restore Files. When performing disaster recovery of the system state on a system where a dynamic disk is a critical volume, recovery may fail it attempts to restore and reformat the volumes. To restore files in this case, use the Avamar system recovery disk image from the 5.0.105-169 release and perform the restore using this version. Extended Firmware Interface not supported. The use of Extended Firmware Interface (EFI) is not supported when performing Windows VSS System State backups.

Extended Desktop/Laptop Functionality


Entourage Support Requires Default Installation Location. Avamar Client for Mac OS X supports Microsoft Entourage using scripts that shutdown the Microsoft Database daemon prior to starting a backup and restart it after the backup is finished. These scripts do not work when Avamar Client for Mac OS X is installed in a non-default location. On clients that need support for Entourage, use the default location when installing Avamar Client for Mac OS X. Mac Install Volume Cannot Have Space Character in Name. Installation of Avamar Client for Mac OS X on a non-default volume that has a space character in its name causes several important Avamar client scripts to fail. To avoid problems caused by the failure of these scripts, install Avamar Client for Mac OS X on the Mac default volume or on a volume that does not have a space character in its name. Viewing Logs from Mac Console Requires Default Installation. When Avamar Client for Mac OS X is installed in a non-default location, work order logs cannot be viewed from the Avamar client console. To view a work order log in this situation, use a text editor to open it from the clientlogs folder. Standby, Sleep, and Hibernate States Interfere with Backups. Computers that go into standby/sleep (ACPI state G1-S3), hibernate (ACPI state G1-S4), or hybrid sleep (Windows Vista) modes during a backup may encounter problems with the 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 will have no affect. To drop the backup connection, the backup must be cancelled from the serverside. 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. Firewalls Must Allow Communication between Windows Client and Server. Firewall software may interfere with the Avamar servers ability to communicate with Avamar clients by blocking inward connections to required data ports.

AVAMAR 5.0 RELEASE NOTES

24

Known Issues and Limitations If firewall software is running on a client computer configure the firewall application to allow bidirectional communication between the Avamar Windows Client and the Avamar server. Normally this is accomplished by adding the Avamar client agent to an allowed or exceptions list. The exact procedure for doing this is dependent on which firewall application you are running. Refer to your firewall documentation for additional information. Potential Conflicts With Windows Anti-Virus Software. Initial backup activity might cause anti-virus applications to use large amounts of CPU capacity (as high as 100% of CPU capacity). This can occur when anti-virus software is running and the Avamar client examines large numbers of files for any reason. Windows Bare Metal Restores Require Additional Software. Not all information necessary to fully restore a hard drive is recorded during a backup. Therefore it is not possible to perform bare metal recovery of a lost hard drive without the use of additional third-party software. However, Avamar is compatible with most bare metal recovery software. Windows File Attributes Are Converted to Unix Style Attributes. Windows style file attributes (Read-Only, System, Hidden and Archive) are converted to Unix style file attributes (rwxrwxrwx) when displayed in Avamar Administrator. The Windows file attributes (except for Archive) are set correctly when files are restored on Windows clients (2485). Default Limit for Process Data Segments Is Too Low. On Mac OS X, the default limit for process data segments (6 MB) is lower than EMCs recommended limit of 96 MB. Any value below 96 MB has an impact on backup and restore performance. In this release, during installation of Avamar Mac OS X Client, the installer looks at the value of this setting. If it is less than 96 MB, the installer changes it to 96 MB. The new value takes effect after the computer is restarted. At the conclusion of the installation, the installer launches a restart reminder. To ensure optimal performance, restart the computer as soon as possible after completing the installation. Loading Message Persists for Restore Location Feature on Mac. To restore data to a new location you click Browse in the Restore To field to open a Browse dialog box. While the browse applet is loading, a Loading message appears. In a specific situation the Loading message will persist over the Browse dialog box after it is populated with available drives. The situation that causes this error is on Mac, running Safari web browser and completing the following steps: 1. In Restore To, click Browse. 2. After the Browse dialog box appears, close the Safari window without selecting a location or canceling the selection, and without closing the Safari application. 3. Start a restore from the Dock icon. 4. In Restore To, click Browse. The Loading message appears and persists. AVAMAR 5.0 RELEASE NOTES 25

Known Issues and Limitations The interim solution for this issue is to click Cancel on the Browse dialog box and restart the task by clicking Browse. Column Adjustment Causes Error in Internet Explorer. Adjusting the size of a column on the Restore by Search page, Restore by Browse page, or the Activity History page can cause a JavaScript error in Internet Explorer. The interim solution for this issue is to refresh the page. This clears the error and returns the column to its default size. Extended Drives Are Visible on Some Operating Systems. On some operating systems, extended or mapped network drives can be seen in the Restore Location dialog box. While a restore to such a drive may work, depending on permissions and domain settings, it is not a supported feature.

Mac OS X Clients
SCC Menu Items May Not Be Available after Avamar Mac OS X Client Installation. Immediately after installing the Avamar Mac OS X Client software, some items in the Avamar Simple Client Console (AVSCC) menu might be unavailable. For example, when you right-click the Avamar icon on the Dock, the Back Up Now and Restore menu items are dimmed. Wait 45-60 seconds. These menu items will then become available (19060).

AIX, FreeBSD, HP-UX, Linux and Solaris Backup Clients


NFS Mounts Are Ignored By Default. When backing up a computer, any Network Filesystem (NFS) mounts are ignored unless you specify to back up the directory of the NFS mount. Backup Always Modifies the atime Value. On Unix and Unix variants, avtar will always modify the atime (access time) value for files that are opened and read during the backup. This occurs during an initial backup, if the file has been modified since the last backup or if the client's file cache has been deleted (696). Solaris Path Length Limitation. Solaris imposes a maximum path length limit of 1023 characters. Therefore, you cannot specify paths greater than 1023 characters at any time (10460). Avamar Directory Protection Issues. In response to requests for enhanced security, by default Avamar now protects the VARDIR (/var/avamar or /usr/local/avamar/var depending on your installation) so that only the root user can create files. However, certain applications (for example, Oracle) are known to require access to the Avamar VARDIR by other user accounts. If this is the case at your site, modify the ownership of /var/avamar or /usr/local/avamar/var to allow read/write access by the necessary user accounts. (10392). Delays Encountered When Mandatory Locks Found. Avamar client software will honor all mandatory locks in the target file system. Unfortunately, this can cause backup operations to hang indefinitely if a mandatory lock is held by another application on files that Avamar is backing up. The interim solution is the specifically exclude all files and directories with mandatory locks from the backup dataset and perform another backup (10531). AVAMAR 5.0 RELEASE NOTES 26

Known Issues and Limitations FreeBSD Full System Backup Issue. When performing a full system backup on FreeBSD, you might occasionally encounter an avagent FATAL <5889>: Fatal signal 11 error if the file system has at least one directory that contains a large number of files (>100,000). The interim solution is to exclude these large directories from the full system backup, then back up each of these large directories separately in subsequent back up jobs (17095). System Recovery Not Supported for Sun Solaris ZFS Filesysetm. System recovery of a Sun Solaris host to its original system state is supported with UFS filesystems only. This operation is not supported with ZFS filesystems.

Novell NetWare Clients


Refer to your Avamar Backup Clients User Guide for a complete discussion of Avamar NetWare Client capabilities and limitations. In addition to general capabilities and limitations, the following known issues exist with this Avamar NetWare Client release: Maximum Backup Size and Number of Files. EMC recommends that backups taken with the Avamar NetWare Client be limited to a maximum total size of 500GB and that these backup comprise no more than 1 million files. Furthermore, for best results, maximum hash cache size should be limited to 10 MB. This behavior is controlled by the following plug-in option: OPTION Maximum client hash cache size (MBs) VALUE 10

If performing an on-demand backup, use this setting in the Backup Options dialog box. If scheduling a backup, use this setting in the Edit Dataset dialog box Options tab (12641). Encryption Is Not Supported. The Avamar NetWare Client does not support encryption for backup or restore operations. If an encryption method other than None is specified for a backup or restore, Avamar automatically changes the encryption method to None. UTF-8 Characters in File and Folder Names. File and folder names that contain UTF-8 characters will not display correctly in Avamar Administrator. This does not affect actual backup or restore behavior, or data integrity (12804). NSS Compression Should Be Suspended During Backups. NSS volumes with compression enabled can cause memory contention issues during backups. Therefore, EMC strongly recommends that compression be suspended during backup operations. If performing on-demand or scheduled backups with Avamar Administrator, selecting the Suspend NSS Compression backup option will suspend NSS compression during backups and automatically resume NSS compression afterward.

Microsoft Exchange Clients

AVAMAR 5.0 RELEASE NOTES

27

Known Issues and Limitations Refer to your Avamar Exchange Client User Guide or Avamar Exchange VSS Client User Guide for a complete discussion of Avamar Exchange Client capabilities and limitations. In addition to general capabilities and limitations, the following known issues exist with this Avamar Exchange Client release: Exchange 2000 Not Supported. Avamar 5.0 software does not support Exchange 2000. Instead, use version 4.0.x of the Avamar Exchange Client software to backup Exchange 2000 servers (12748). Cancelled Database Backups Might Show as Completed. Occasionally, cancelling a database backup from Avamar Administrator using the Exchange plug-in will cause that activity to show a Completed status in the Activity Monitor even though no backup took place (12891). Exchange Public Folders and Items Permissions Changed Following Recovery. Avamar can recover folders and items within Exchange Server Public Folders. However, when using the Exchange plug-in, the recovered items might take ownership and permissions from the recovery process, instead of recovering those attributes as they originally existed in the Exchange Server. The interim solution is, after recovering the Public Folder folders and items, log in under the username that performed the recovery (typically, AvamarBackupUser) and reset permissions as needed (14998). Public Folders Permissions Requirements. In order for Public Folders to be backed up by the Exchange plug-in, the Public Folders Exchange Permission Level for the account that is performing the backup must be set to a minimum of Reviewer (i.e., the Read permission must be set to Full Details and the Other permissions must be set to Folder Visible). This is done on the Permissions tab of the Mailbox Properties dialog box. In order for Public Folders to be restored, the account that is performing the restore must have sufficient permissions to write to the folders and their parent folders (i.e., the Write permission must have Create Items and Create Subfolders selected, and the Other permissions must be set to Folder Visible). If the account that is performing the restore does not have write permissions, the recover operation will be reported as successful but no data will be restored. NOTE: Permissions to Public Folders can be set such that the Public Folders are hidden by deselecting the Folder Visible option in the Other permissions on the Permissions tab of the Mailbox Properties dialog box. If a folder is set such that it is hidden from the account that is performing the backup, then the folder will be hidden from the backup process. The hidden folder will not be saved, and no errors or warnings will be provided.

Change In Chunking Algorithm Requires New Level-0 Backup of Exchange Server Clients. The chunking algorithm used for Exchange plug-in database backups has changed in version 5.0. This change improves deduplication for Exchange database backups. However, because the version 5.0 chunks are not identical to previous implementations, upgrading to version 5.0 will create a onetime increase in backup time and network utilization. It is recommended that users with multiple Exchange servers stagger their upgrades to version 5.0 to AVAMAR 5.0 RELEASE NOTES 28

Known Issues and Limitations spread the impact of this change over time. Users with network bandwidth, Avamar Server capacity, or replication network bandwidth constraints, should plan their upgrade to version 5.0 carefully to assure the one-time increase in backup time, network bandwidth and replication bandwidth can be accommodated. In very constrained cases where this one-time increase cannot be accommodated, customers may elect to forego upgrading their Exchange plug-ins. Backups Taken with Exchange VSS Plug-in Show Incorrect Size in Contents Pane. When restoring from backups originally taken with the VSS plugin, the size will be reported as 0 bytes in Backup and Restore Window Restore tab contents pane. However, the correct size is shown in the backup selection pane (17380).

Microsoft SharePoint Clients


Refer to your Avamar SharePoint Client User Guide for a complete discussion of Avamar SharePoint Client capabilities and limitations. In addition to general capabilities and limitations, the following known issues exist with this Avamar SharePoint Client release: Full Backup Required after Upgrade from 4.1. If you upgrade from Avamar 4.1 to Avamar 5.0, you should perform a full backup. Avamar 5.0 cannot recover differential backups performed with the 4.1 client. You only can recover full backups performed with the 4.1 client (16529). Issues Following Upgrade to Windows SharePoint Services 3.0 SP2. When upgrading from Windows SharePoint Services 3.0 or Windows SharePoint Services 3.0 SP1 to Windows SharePoint Services 3.0 SP2 on a system already running Avamar SharePoint Client software, the SharePoint topology will not display correctly in Avamar Administrator. This can affect the ability to backup a SharePoint farm. This issue is discussed in detail in Microsoft knowledge base article 913384 http://support.microsoft.com/kb/913384). This knowledge base article provides detailed instructions for resolving these issues, which might include removing .NET frameworks later than 2.0 and applying the patch discussed in the article before reapplying updated framework software.

Microsoft SQL Server Clients


Refer to your Avamar SQL Server Client User Guide for a complete discussion of Avamar SQL Server Client capabilities and limitations. In addition to general capabilities and limitations, the following known issues exist with this Avamar SQL Server Client release: Log Tail Backup Feature Requires Avamar 5.0 Service Pack 1 or Later Server. In order to perform restores in which database log tails will be backed up following the restore, the backup from which you are restoring must reside on an Avamar 5.0 Service Pack 1 or later server (17552). Filegroup Restore Issues. If an SQL Server database has been instanced as a filegroup, redirected restores or restores in which the SQL Server database is renamed will fail (17647). AVAMAR 5.0 RELEASE NOTES 29

Known Issues and Limitations Redirected Restores to Default Path Fail If Path Does Not Exist. When performing a redirected restore of an SQL Server database, if the file path of the target database is not specified, the restore will default to using the data path of the SQL instance that is being restored. However, if this path does not exist on the target, the restore will fail. If you specify the file path of the target database, the restore will be successful. (17648). Log Tail Backup of Small Amount of Data May Result in Data Not Available. When an SQL recovery operation is invoked with log tail backup enabled, the Avamar software attempts to save the log tail information in the SQL log files since the most recent backup. If the backup of the log tail fails for any reason, an error message will be produced, and the recovery will be aborted. However, if the amount of data added or changed since the most recent backup is very small (less than about 25 MB) then the SQL Server may not be able to retain the information. The recovery will exit with an error, and the log tail data will not be available. (19444)

Oracle Database Clients


Refer to your Avamar Oracle Client User Guide for a complete discussion of Avamar Oracle Client capabilities and limitations. In addition to general capabilities and limitations, the following known issues exist with this Avamar Oracle Client release: Avamar Administrator Reports Incorrect Database Sizes. When viewing or browsing Oracle databases in Avamar Administrator, the database size will always be reported as 44,040,192 bytes. This is only a reporting error; actual data is unaffected (10281). Avamar Administrator Reports Incorrect Progress Bytes. When viewing the status information from the Activity Monitor tab in Avamar Administrator, the progress bytes for a clients backup may differ from the progress bytes from the same clients restore. The backup and restore in this instance completed successfully. The discrepancy in the size of the progress bytes occurs if the number of RMAN channels specified for the backup differs from the number of RMAN channels specified for the restore. This is only a reporting error (17974). Difference in Backup and Restore Size. The size of an Oracle client backup differs from the size of the restore if the restore does not require all of the files (especially archive logs) to be restored (17974).

NDMP Accelerator (EMC Celerra IP Storage Systems and NetApp Filers)


Refer to your Avamar NDMP Accelerator User Guide for a complete discussion of Avamar NDMP Accelerator capabilities and limitations. In addition to general capabilities and limitations, the following known issues exist with this Avamar NDMP Accelerator release: Backward Compatibility with Pre-5.0 Avamar Servers. For best results, you should use a version 5.0 accelerator with a version 5.0 Avamar server.

AVAMAR 5.0 RELEASE NOTES

30

Known Issues and Limitations However, if you must use a version 5.0 accelerator with an earlier version Avamar server, the following limitations apply:
EMC Celerra IP Storage Systems

EMC Celerra backups stored on an Avamar 4.1 or earlier server cannot be used to restore more than one individual file in the same restore operation. Multiple restore operations must be used to restore several individual files. NetApp backups taken with a version 5.0 accelerator are not compatible with older Avamar backups. Therefore, the first time a filer is backed with a version 5.0 accelerator, a full backup is automatically taken (forced). Version 5.0 accelerators are able to restore from pre-5.0 backups with no limitations. Furthermore, in order to perform backups and restores with an Avamar 4.1 server, version 5.0 dpnavclient RPM must be installed on the serer utility node. NetApp backups taken with a version 5.0 accelerator cannot currently be store on pre-4.1 Avamar servers.

NetApp Filers

Passwords Cannot Contain Single-Quotes. During installation and configuration of the Avamar NDMP Accelerator for use for use with one or more supported storage devices, the avsetupndmp script asks for an NDMP user account password. This password cannot contain single-quotes (9302). Hardlinks on Celerra. Hardlinks to device files (block or char) might fail to backup. Errors might occur during backup if attempt is made to backup a hardlink to a device file on Celerra. You can safely ignore these errors during backup, and manually recreate these hardlinks following a restore (9692). Additionally, restores of hardlinks that contain characters other than A-Z, a-z, 0-9, dash (-) and underscore (_) might complete with exceptions. If this occurs, the hardlinks will be restored as separate duplicate files, causing potential wasted hard drive space (12826). Restore of an Incremental Celerra Backup with No Changes Fails in ASCII Mode. On Celerra, if an incremental backup contains no changes (that is, it is identical to the previous backup), then attempting to restore that backup will fail if the Celerra is operating in ASCII mode. The interim solution is to avoid restoring these empty backups. Instead, restore the previous (identical) backup (12830). NetApp LUN Restore Issue. When restoring a LUN, the Avamar Administrator Restore to original location setting does not correctly restore the data as a LUN. The interim solution is to manually specify a NetApp Qtree root directory as a restore location for the LUN. Doing this will cause the NetApp filer to create the proper LUN container (18377). Browsing Backups on NetApp Are Not Sorted Alphabetically. When browsing a NetApp backup for restore the contents are not sorted alphabetically. (18216) NDMP Backup Performance for Large NetApp Volumes. Performance of NDMP NetApp backups of volumes with more than approximately 10 million files

AVAMAR 5.0 RELEASE NOTES

31

Known Issues and Limitations may degrade over time. This is typically seen in backups that exceed 24 hours. Both initial backups and incremental backups are impacted.

AVAMAR 5.0 RELEASE NOTES

32

Documentation Errata

Documentation Errata
The following topics discuss minor documentation defects that were not able to be fixed prior to the Avamar 5.0 release. Correct information is provided. Each of these defects will be fixed and revised publications included with the next appropriate product release.

EMC Data Store Gen 3 System Installation (REV A03)


Alternate Configurations:Delivered with dual network switches (page 18)
The Data Store dual switch alternative configuration can lose network connectivity with network devices internal and external to Data Store, resulting in lost packets and incomplete transactions. There is no risk to customer data that is stored in Data Store, but backups and restores (and other network operations, including implementation) can be impacted. Customers who wish to implement the dual switch alternative configuration should see the Configuration of High-Availability ADS Network Technical Note (PN/300-011-174) REV A03.

Avamar SQL Server Client User Guide


Capabilities and Limitations (page 9)
In the section Restore Limitations, the current text states that the following is not supported: Redirected restore to another SQL Server instance or restore with a new name of databases that contain multiple log files This is inaccurate. It should say: Redirected restore of databases with multiple file groups and/or log files to another SQL Server instance or to a new database name. In the same section, a note about restore limitations incorrectly states that a valid tail-log backup is initiated even though the restore process fails when you attempt to perform a redirected restore of multiple filegroup databases. The tail-log backup does not take place.

AVAMAR 5.0 RELEASE NOTES

33

Documentation Errata

On-Demand Backup (page 26)


The following note is incorrect: IMPORTANT: This setting breaks the chain of log backups and should not be used unless the backup type is set to full. It should read: IMPORTANT: This setting breaks the chain of log backups and should not be used unless the backup type is set to incremental.

Windows SQL Server Plug-in Options (page 63)


NOTE: This erratum also occurs on page 554 of the Avamar Administration Guide. The Description column in the Force Incremental backup row of the Backup Options table should read as follows: If a full backup exists and then another full backup occurs, this option creates an incremental backup that contains transactions that occur from the end of the first full backup or the most recent incremental backup, whichever is later, until the time that the forced incremental backup occurs (after the first backup of the new backup cycle). This ensures that a point-in-time recovery to a point in time between the two full backups can occur, if necessary. Two backup sessions are created when a forced incremental backup occurs. The first session contains transactions that occur from the end of the first full backup until the start time of the second full backup. The second session contains transactions that occur from the end of the second full backup until the time that the forced incremental backup occurs. To restore and recover the database to a point after the forced incremental backup, select the last backup from the last backup session that has the most recent full backup, during the restore process.

Avamar Event Codes Listing


Event 4014 Code Omitted.
4014 INFORMATION skipping scheduled hfscheck due to %s

AVAMAR 5.0 RELEASE NOTES

34

Documentation Errata

Avamar Release Notes Addendum


Event 4014 Code Omitted.
4014 INFORMATION skipping scheduled hfscheck due to %s

Avamar Technical Addendum


avlockboxcfg (page 52)
--avamaruser and --avamarpassword options do not provide full valid syntax.
Is Should Be

--avamaruser and --avamarpassword. --avamaruser=USERNAME and --avamarpassword=PASSWORD.

Avamar Product Security Guide


Default User Accounts (page 15)
The Avamar VMware image backup proxy and repluser accounts were omitted from the Default User Accounts section. The following should be added to the table in this section: USER ACCOUNT AVAMAR ADMINISTRATOR repluser DEFAULT PASSWORD 9RttoTriz DESCRIPTION/REMARKS Account for internal use by Avamar Administrator server for replication.

AVAMAR 5.0 RELEASE NOTES

VMWARE IMAGE BACKUP PROXY

root

avam@r

Default root account on an Avamar VMware image backup proxy

35

Documentation Errata

Avamar for VMware Guide


The following information should be added as a new appendix to the Avamar for VMware Guide:

Minimum Required vCenter User Account Permissions


In high-security environments, you can restrict the vCenter user account permissions required to configure and administer the Avamar VMware image backup and restore feature to all of the following: Datastore > Allocate Space Browse datastore Low level file operations Move datastore Remove datastore Remove file Rename datastore Folder > Create Folder Global > Cancel task Log event Settings Network > Assign network Configure Resource > Assign virtual machine to resource pool Sessions > Validate session Tasks > Create task Update task

AVAMAR 5.0 RELEASE NOTES

36

Documentation Errata Virtual machine > Configuration > Add existing disk Add new disk Add or Remove device Advanced Change CPU count Change resource Disk change tracking Disk Lease Host USB device Memory Modify device setting Raw device Reload from path Remove disk Rename Reset guest information Settings Swapfile placement Upgrade virtual hardware Extend Virtual disk Virtual machine > Interaction > Power Off Power On Reset Virtual machine > Inventory > Create new Register Remove Unregister Virtual machine > Provisioning > Allow read-only disk access Allow virtual machine download Mark as Template Virtual machine > State Create snapshot Remove snapshot Revert to snapshot

AVAMAR 5.0 RELEASE NOTES

37

Issues Resolved

Issues Resolved
The following topics list issues (bugs) that have been resolved in various releases.

Version 5.0 (5.0.0-407)


The following issues (bugs) have been resolved in version 5.0 (5.0.0-407): BUG# 10577 ISSUE/RESOLUTION Corrected an issue in which the sbtinfo2 routine was not retrieving the specified backup files correctly. The problem was isolated to libobk_avamar library. It did not implement the sbtinfo2 and sbtremove routines. These routines crosscheck and delete backups, respectively. The sbtinfo2 and sbtremove calls have been implemented in the libobk_avamar library. Implemented a customer enhancement request to support online backups of DB2 databases from Microsoft Windows 64-bit platforms. Corrected an issue in which the standard OpenLDAP library included with Red Hat Linux 4 caused authentication failures. The Red Hat Linux 4 update 8 kickstart image now includes new versions of OpenLDAP rpms, which fix the authentication failures. Implemented a customer enhancement request to support Network Address Translation (NAT). Avamar clients can now access the server by NAT IP addresses as well as real IP addresses. Corrected an issue in which Avamar Enterprise Manager could not display plug-in options. The problem was isolated to the plug-in catalog. The plug-in catalog is now fixed so that Avamar Enterprise Manager now displays plug-in options correctly. Corrected an issue in which backing up a Celerra IP storage system by using the Avamar NDMP Acceleratorr client failed. The avndmp.log file contained Media errors. The use of NDMP version 4 with Avamar 5.0 resolves this issue. Corrected an issue in which backups of a significant number of files, such as 22 million, failed. Backups of as many as 100 million files now can complete successfully. Corrected an issue in which backup performance in version 4.x was considerably slower than in version 3.7.x. The problem was isolated to a change in the way hashing threads were processing data on multiprocessor Windows platforms. An unequal distribution of data to hashing threads caused inefficient CPU usage, which in turn caused longer backup times. The problem has been fixed so that backups on multiprocessor Windows platforms now distributes data equally to hashing threads.

11015 11501

11596

11985

12254

12497

12852

AVAMAR 5.0 RELEASE NOTES

38

Issues Resolved BUG# 12963 ISSUE/RESOLUTION Corrected an issue in which MCS failed if an event contained an invalid character. The problem was isolated to an attempt to insert an event that contained an invalid character into the MCS database. MCS now handles events with invalid characters correctly. Implemented an enhancement request to allow the attachment of reports to domain profiles as long as the reports are in the same domain. Implemented a documentation enhancement request to update the Technical Addendum with more details about the cplist command. The cplist command in Technical Addendum now includes details about its output. Corrected an issue in which the avmaint rmcp command could be used to delete all checkpoints, leaving the Avamar server without a checkpoint to which to roll back. Corrected an issue in which the Avamar server would unexpectedly become unresponsive. The problem was isolated to a storage node whose critical thread had terminated, which caused the critical threads for other storage nodes in the configuration to terminate as well. Avamar now include procedures to handle circumstances that might terminate critical threads. Corrected an issue in which replication failed with the error: INTERNAL CYCLE ERROR: bad response in repldata SRC_GET_DATA: GET_HASH_DATA The problem was isolated to the use of both include and exclude lists for backups. The exclude list specified a directory that contained more files than the default amount specified by the --bigdirgroup option. The combination using the include and exclude lists caused corruption to backed up data. The corrupt backup, consequently, caused the replication process to fail. The problem has been corrected. 13218 Corrected an issue in which the restore of an Exchange store failed with the error: Database not found. This problem was isolated to multiple Recovery Storage Groups that contained servers with the same name, but with different globally unique identifiers (GUIDs). To resolve this issue, the GUIDs are now verified with the Active Directory before a restore process starts. Corrected an issue in which the restore would fail if you attempted to restore a backup of a UNC path to its original location. Corrected an issue in which data for v_audits, v_ev_catalog and other views were missing from MCS database views after a trial license for Avamar was extended. The problem was isolated to the method used to read character arrays into the MCS database. The method of reading character arrays in the MCS database has been revised so that missing view are no longer an issue.

12971

12984

12994

13140

13154

13225 13231

AVAMAR 5.0 RELEASE NOTES

39

Issues Resolved BUG# 13233 ISSUE/RESOLUTION Corrected an issue in which nodes were failing benchmark tests. The problem was isolated to the firmware version of two drives: Seagate HS09 and Hitachi A4C2. After upgrading the firmware for the Seagate HS09 and Hitachi A4C2 drives, the nodes passed the benchmark tests. Corrected an issue in which the content for an email notification was delivered as an attachment instead of inline text even though the inline attachments option was selected in the Edit Profile dialog box. Selecting the inline attachments option in the Edit Profile dialog box now correctly sends content as inline text for email notifications. Corrected an issue in which a laptop used in more than one domain was not recognized as a client by the Avamar server. The Avamar server would return the following message: A client with this name already exists and duplicate names are prohibited. The problem was isolated to the use of fully qualified domain names (FQDN) in a clients name. Avamar resolved this issue by adding a preference to the mcserver.xml file, which enables you to use duplicate client names. 13393 Corrected an issue in which the Start Date/Time Range and End Date/ Time Range checkboxes in the Node Utilization Report Graph Options dialog box were not associated to any functionality. The Start Date/ Time Range and End Date/Time Range checkboxes have been removed. Corrected an issue with the Avamar Administrator Online Help in which the Session Monitor Tab topic incorrectly described the User - Domain value as the client domain. The User - Domain value is the domain in which the user is defined. Corrected an issue in which the system access mode was being erroneously reset by a garbage collection task. The garbage collection task no longer changes the system access mode. Corrected an issue in which the Activity Sessions dialog box contained a button labeled Cancel. The use of the Cancel button was unclear as to whether it would cancel the backup or just close the dialog box. The button label has been changed to Close. Corrected an issue in which the message log from an Avamar backup of a SQL server database included the following warning message: WARNING: java.lang.NullPointerException This problem was isolated to missing session elements in the messages log. To address this problem, a SQL server backup now generates an informational message about the missing session element.

13338

13356

13396

13401

13453

13467

AVAMAR 5.0 RELEASE NOTES

40

Issues Resolved BUG# 13473 ISSUE/RESOLUTION Corrected an issue in which large values (greater than 107) in the Activity Report are displayed by using scientific notation. The problem was isolated to values displayed in the bytes_scanned, bytes_new, bytes_excluded, bytes_skipped and bytes_overhead columns. Large values that represent bytes are now displayed in standard decimal notation. Corrected an issue in which after upgrading Avamar, the Enterprise Manager Dashboard always reported Not available for the Capacity Forecast. The problem was isolated to the way Enterprise Manager reported capacity utilization when the days left value was negative. The status message has been changed, and now reports Not enough data in the Dashboard and Not enough data to forecast on the Status page. Corrected an issue in which an installation of Avamar on Solaris consistently failed with the error message: Error! Specified vardir (var directory) "/var/avamar" does not exist. The problem was isolated to a logic problem in the request script that is included with the client installation package. The script has been corrected and now the installation package runs as intended. 13587 Corrected an issue in which a restore of a SQL Server database failed because the state of the database was locked. The problem was isolated to attempting to restore a database that had active user sessions. Users who were still connected to the database caused the locked status, which prevented the restore from running. Corrected an issue in which using the restart.dpn program with the --nodes=NODE-LIST and --offlineok options failed. The problem was isolated to restart.dpn selecting an offline node as the main host. The restart.dpn program now selects a node that is online. Corrected an issue in which checkpoints created after a node had gone offline were deleted. The problem was isolated to a policy to delete checkpoints while the system is running in a reduced state (one node is offline). Checkpoints created when a node is offline are now retained instead of deleted. Corrected an issue in which a server was suspended or maintenance activities, such as GC, could not start after the server restarted. The issue occurred because there was insufficient disk space to create additional necessary stripes for future backups. Corrected an issue in which running the emserver.sh --restore script prompted you for information specific to restoring MCS. The emserver.sh script has been corrected and now works as intended. Corrected an issue in which the avmaint rebuildstripe command failed to check for multiple simultaneous rebuilds on stripes in the same parity group. The server now allows only one stripe rebuild at a time by way of avmaint rebuildstripe, regardless of parity groups for the stripes. 41

13511

13543

13607

13609

13613

13630

13700

AVAMAR 5.0 RELEASE NOTES

Issues Resolved BUG# 13711 ISSUE/RESOLUTION Corrected an issue in which backing up Oracle databases by using Avamar Oracle Client failed with an I/O error from RMAN: ORA-19511: Error received from media manager layer, error text: sbtwrite2: I/O error writing to file qok9i6t9_1_2, errno = 11 The problem was isolated to a resource deficiency. Oracle backups now complete successfully. 13714 Corrected an issue in which an Oracle database backup stops responding. The problem was isolated to running an Oracle backup and Avamar maintenance activities at the same time. The avtar log file contained an error about failing to establish a session with the Avamar server. RMAN never terminated. This backup issue has been fixed. Corrected an issue in which an NDMP backup stopped responding after two hours. The problem was isolated to how other backup-related processes responded to the stalled NDMP backup. The avtar process stopped responding, but the NDMP processes continued to run. When a backup stops responding and is eventually terminated, Avamar now cleans up all other backup-related processes. Corrected an issue in which MCS terminated with the following error message: WARNING: Attempted to store duplicate node capacity information. Aborting The problem was isolated to a time change made on the Avamar server at the same time morning_cron job was scheduled to run. 13750 Corrected an issue in which HFS check failed during an index-stripe split operation. The problem was isolated to an index-stripe split operation running while excessive swapping was taking place on the Avamar server. The amount of time to complete the index-stripe split operation was inadequate. The index-stripe split operation has been modified to allow it to work correctly. Corrected an issue in which backups that completed with errors were used as base candidates for successive incremental backups. Corrected an issue in which connection error messages were written to the avsql log file despite the backup completing. The problem was isolated to the following error messages: SQLDMO connect Connect failed with 'code 0x80040000: Invalid OLEVERB structure' SQLDMO connect Microsoft SQL-DMO (ODBC SQLState: 08S01) returned error 0: [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken. The severity of the messages have been downgraded from errors to debug messages.

13744

13747

13792 13816

AVAMAR 5.0 RELEASE NOTES

42

Issues Resolved BUG# 13828 ISSUE/RESOLUTION Corrected an issue in which restarting MCS while a node was offline failed with the error: WARNING: com.avamar.asn.StartupException: ERROR: Node 0.N has state "OFFLINE". MCS now ignores offline nodes and starts successfully. 13843 Corrected an issue in which a client used in a NetWorker environment sent duplicate END messages to Avamar. This resulted in the following error message from MCS: Event Code = 22602 Event Date/Time = 04/23-17:04:24.00950 Event Type = ERROR Event Severity = PROCESS Event Summary = The database encountered an error. Software Source = MCS:DPN_Proxy This problem was isolated to the session ID. 13868 Corrected an issue in which a client registration failed because the client hostname contained a / (forward slash). Added hostname validation for client initialization messages. Implemented a customer enhancement request for the replication process to create a partial backup on the destination server when it receives a MSG_ERR_CANCEL response. In addition, it does not provide INTERNAL CYCLE ERROR messages in the replication log file. Previously, the replication process immediately aborted when a MSG_ERR_CANCEL response occurred. Corrected an issue in which restore operations using the Avamar Web Services feature corrupted filenames and folder names that were composed of Japanese characters. The problem was isolated to the zip utility being used. It did not support unicode filenames. Revised the Avamar Backup Clients User Guide to include a topic about zip utilities that are supported by the Avamar Web Services feature. Corrected an issue in which duplicate items were created when performing a message-level restore of Microsoft Exchange files. The restore process now checks for items that have already been restored. Corrected an issue in which the default version of the zip utility from Red Hat Enterprise Linux did not support unicode characters. This caused the corruption to filenames and file folders during a restore operation using Avamar Web Services feature. Corrected an issue in which the memory consumed by avtar during a restore of large files and directories could exceed 2 GB and prevent the restore from completing successfully. Added new throttling logic to limit the number of simultaneously open directories.

13869

13871

13872 13896

13902

13907

AVAMAR 5.0 RELEASE NOTES

43

Issues Resolved BUG# 13965 ISSUE/RESOLUTION Corrected an issue in which installing Avamar Windows Client version 4.1 failed with an Application Error: Faulting application avscc.exe, version 4.1.100.1470, faulting module avscc.exe, version 4.1.100.1470, fault address 0x00268829. The client system also had APC Powerchute software installed. The problem was isolated to an incompatibility with Avamar Windows Client version 4.1 and APC Powerchute software. 13967 Corrected an issue in which client backups failed with 10003 errors because avtar was unresponsive after NTBackup could not return from the system state backup process. The avtar process now includes a timeout for NTBackup for the system state backup process. When the timeout expires, avtar ends the NTBackup process so that it can proceed with backups. Corrected an issue in which only the user who installed the Avamar Windows Cluster Client software could see the software in the Add/ Remove programs list to uninstall the software. Corrected an issue in which HFS checks failed due to license expiration errors, even though a valid license had been updated properly through avmaint license. The proper licensing information had not been updated on the secondary server listener thread. Corrected an issue in which Garbage Collection (GC) was failing because of a MSG_ERR_DISKFULL message. The message occurred because of a lack of balance of free disk space among partitions, which caused the data server (formerly known as GSAN) to continue to allocate new stripes from the partition with the most free disk space. This lead to a disk full condition on the partition. Corrected an issue in which avw_axion_install would unpack and install a client tarball if one was located in the /usr/local/avamar/src/ directory. Corrected an issue in which corrupted Microsoft Word 2007 files could be backed up but not restored. Corrected an issue in which the data server allowed the initiation of multiple simultaneous avmaint testintegrity commands. The multiple ongoing processes could cause disk corruption. Corrected an issue in which the avamaint removebadhashes command removed the wrong data during a hash removal. Data is now checked to ensure that the hash of the data matches the index stripe hash entry before the data is removed. Corrected an issue in which the HFS check directory was deleted even though there were errors during the check. The directory now remains if errors occur, and is deleted only if the HFS check completes successfully.

14015

14028

14066

14081

14089 14094

14126

14139

AVAMAR 5.0 RELEASE NOTES

44

Issues Resolved BUG# 14148 ISSUE/RESOLUTION Corrected an issue in which corruption occurred while GC was in progress. The corruption occurred because GC failed to time out properly on the node because the system clock on the node was out of sync with the system clock on the node that ran the GC controller. Corrected an issue with the Avamar Backup Clients User Guide in which the command to uninstall the AIX client was incorrect. The correct command, geninstall -u AvamarClient-aix5-ppc and its resulting output have been updated in the guide. This problem was also corrected in the Avamar Oracle Client User Guide. 14174 Implemented a customer enhancement request to allow exclusion of unwanted backups from the replication process based on the plug-in ID. Corrected an issue in which Avamar could not import clients definition files in XML format if the files contained the byte order marker (BOM) for UTF-8 encoding. Corrected an issue in which users with special characters in their passwords could not log in when the user accounts were part of an Active Directory domain (in other words, external authentication was used) and when the user accounts were added in a batch through the command line interface. You do not need to specify the password for external authentication user accounts when you add the accounts to Avamar. Corrected an issue in which GC ignored errors that occurred when traversing a stripe that had a mismatching chunk, and then additional errors occurred. When GC encounters an error with a chunk, a MSG_ERR_CORRUPT_DATA error now occurs and GC stops. Corrected an issue in which the MCS ran out of memory when you tried to acknowledge a significant number of events. Corrected an issue in which a backup of a SCO UNIX client would fail to respond due to an issue with SCO UNIX when throttling was used. A workaround was implemented in the Avamar software to resolve the problem. Corrected an issue in which an upgrade could continue even if the data server does not shut down properly. The upgrade would then encounter problems. Corrected an issue in which message-level backups on Microsoft Exchange servers were slow when the subject lines of the messages were greater than 100 characters and contained multibyte characters. Corrected an issue in which fatal errors occurred because parity stripes attempted to load data from their write logs even when the write logs were known to be corrupt.

14158

14185

14203

14226

14244 14267

14291

14335

14343

AVAMAR 5.0 RELEASE NOTES

45

Issues Resolved BUG# 14470 ISSUE/RESOLUTION Corrected an issue in which a particular node times out during a balance operation and then put a stripe into an inconsistent state compared to the rest of the system. Specifically, the stripe was marked OFFLINE on the node that was receiving the new stripe, whereas the rest of the data nodes have the stripe marked as ONLINE. Corrected an issue in which Oracle client backups would fail when the dataset, group, or schedule name was greater than 40 characters. Corrected an issue with the Avamar SQL Server Client User Guide in which the document lacked sufficient details for incremental backups and restores of SQL Server databases. Additional details on the incremental backup and restore process have been added. Corrected an issue in which the HFS check checkpoint information was not included correctly in Email Home notifications. Corrected an issue in which it was impossible to delete a dataset that was assigned to a retired client. Corrected an issue with the Avamar Exchange Client User Guide in which the document did not include information on log truncation for cluster continuous replication (CCR). Corrected an issue in which the avtar program did not exit properly on a SCO Unixware 7.1.3 client. As a result, additional backups and restores could not proceed. Corrected an issue in which the expiration date would change to No expiration for backups that belong to a client when you retired the client by using the Management Console Command Line Interface (MCCLI). Corrected an issue in which the upgrade process would abort when there was a significant amount of output from the mcupgrade4.0.0.3.pl upgrade script. The output from the script is now directed to a separate log file: /usr/local/avamar/var/mc/server_log/mcupgrade4.0.0.3.log 14616 Corrected an issue in which the avagent.bin program experienced a fatal error when starting on a Red Hat Linux 8.0 server where the Linux username was longer than eight characters. Corrected an issue in which a a checkpoint-complete file was corrupted and prevented the Avamar server from starting properly after a rollback to the checkpoint. In addition, you could not delete the checkpoint with the corrupted checkpoint-complete file. Revised the content of a message that appeared when a MAPI session failed to start on an Avamar Exchange Client. The message returned by the failure was: avtar Error <5838>: MAPISESSION::init GetServerDN failed 40380 The error message now includes an explanation of the failure and the action to take to correct the problem. AVAMAR 5.0 RELEASE NOTES 46

14476 14484

14492 14520 14554

14561

14589

14603

14662

14733

Issues Resolved BUG# 14842 ISSUE/RESOLUTION Corrected an issue in which on-demand restores stopped responding. The current processes running on the system at the time included two avagent processes. The problem was isolated to avagent forking a sub-process, which was unsuccessful in running avtar (by using the exec command). Corrected an issue in which a Windows client backup failed with the following message: [avtar] context::sendstats kind: INTERRUPTED mess1: <INTERRUPTED>terminated</INTERRUPTED> The backup log also contained Connection killed messages. 14937 Corrected an issue in which two process threads accessed the statedoc-stripeman.xml file at the same time. One process thread attempted to save the statedoc-stripeman.xml file while another process thread attempted to copy the statedoc-stripeman.xml file to a checkpoint. Consequently, the checkpoint operation failed, which caused the Avamar data server to crash with the following error: Fatal gsan error - Unix exception No such file or directory 14953 Corrected an issue in which the admin_can_direct_restores and restore_admin_can_direct_restores preferences in mcserver.xml did not retain their values after an Avamar server upgrade. The problem was isolated to merge=newvalue in the mcserver.xml template, which set the values for the admin_can_direct_restores and restore_admin_can_direct_restores preferences to false. Revised the description of the client load-bulk command in the Avamar Management Console Command Line Interface (MCCLI) Programmer Guide. Corrected an issue in which using avmgr resf failed to resolve the clients path name. The problem was isolated to blocks in the accounting management system that split due to an unusually high number of clients within a domain. Corrected an issue in which the avtar --restoresystem command ignored pipe files and special files during a restore operation and completed with a success exit code. Revised the Avamar SharePoint Client User Guide. It lacked sufficient details about how to use the Avamar SQL Server Client to back up and restore SQL server databases used by SharePoint. Corrected an issue in which memory leak messages appeared on the NetWare console approximately every six minutes. The problem was isolated to a failure to clean up an unreleased resource of the Avamar Avtar module. Corrected an issue in which an event notification for the following error is sent by the Email Home feature: ERROR: duplicate key violates unique constraint The problem was isolated to event notifications.

14912

15063

15066

15086

15112

15114

15254

AVAMAR 5.0 RELEASE NOTES

47

Issues Resolved BUG# 15273 ISSUE/RESOLUTION Corrected an issue in which event traps did not match the Management Information Base (MIB). The problem was isolated to Net-SNMP sending an incorrect OID. The OID has been corrected and now event traps match the MIB. Corrected an issue in which a backup completes with a success exit code despite failing to back up the System State. In this instance, the log file contains a message similar to the following: avtar Error <7831>: Problem processing System State "C:\Program Files\avs\var\SystemState.bkf" This problem was isolated to the avtar program failing to process the SystemState.bkf file if its size is very small (2 KB, for example). The avtar program now checks the size of the SystemState.bkf file. If the files size is not greater than 2 KB, avtar generates a backup error code. 15585 15586 Enhanced Login Manager debug capabilities. Corrected an issue in which exception handling for the Login Manager was insufficient and was therefore causing the program to exit unexpectedly. Corrected an issue during restores in which a parent folder checkbox was automatically and unexpectedly selected if all sub-folder checkboxes had been selected. Corrected an issue in which the avtar program would not appropriately freeze file systems below the drive volume level for a snapshot backup with Microsoft Volume Shadow Copy Service (VSS). Corrected an issue in which the VSS system-state plug-in did not invoke the avtar program with the --restoreshortnames flag, which recreates 8.3 filenames if possible when paths are re-created. Corrected an issue in which duplicate entries appeared in the Activity Report. Revised the Avamar System Administration Guide to clarify that when you schedule replication activities, the start time is displayed in your local timezone and not in the timezone of the source or target server. Corrected an issue in high volume environments in which replicated EM_BACKUPS and MC_BACKUPS accounts did not have the same CID on the target as on the source. Corrected an issue in which it took a significant amount of time to retire a client. Corrected an issue in which the dpnnetutil network configuration tool quits with an error when dpnnetutil is used to configure more nodes than can be accommodated in the available display area.

15392

15736

15883

15887

16078 16355

16488

16655 17165

AVAMAR 5.0 RELEASE NOTES

48

Issues Resolved BUG# 17202 ISSUE/RESOLUTION Corrected a Windows file system plug-in issue in which if a dataset explicitly lists volumes or directories to be backed up, then the FilesNotToBackup registry entries beginning with slash (\) will not be excluded. These registry entries include for example, \Pagefile.sys or \hiberfil.sys. This could cause significantly more data to be sent to the Avamar server during the daily backups. Corrected a Mac OS X file system plug-in issue in which backing up multiple targets on a non-root volume fails to back up any files, but backing up a single target (such as the whole non-root volume) will successfully back up all files. Also, backing up all local file systems only backs up files in the root volume. Corrected an issue with VMware image backup and restore in which datastores associated with datacenters in folders and subfolders are not listed in vSphere datastores to protect section when configuring VMware Image Proxy clients. Corrected an issue in which Avamar Windows Client software fails to install on clients running French, Spanish, German and other language-based Windows systems. The MSI installer explicitly requires the presence of the Users group, but the Users group is replaced with differently named ones on French, Spanish, German and other language-based Windows systems. Corrected an issue with the NetApp NDMP client plug-in in which the avndmp process occasionally fails to retrieve the list of volumes on a NetApp filer, which, in turn, will cause the backup to fail. Corrected a Celerra NDMP client plug-in issue in which backing up a file system with alternate data streams on some files or directories can cause avtar to consume all available memory, which causes all backups being performed on the Avamar NDMP Accelerator node to immediately fail. Corrected an issue in which the Celerra NDMP client plug-in fails to authenticate with the Celerra data mover if the Celerra data mover is set up to use text authentication (instead of MD5sum authentication) of the NDMP password. Corrected an issue in which the gsan process fragments memory over time and might not be able to allocate a 4MB block of memory when loading the index cache into memory. This caused the GSAN process on a data node to terminate with a FATAL ERROR: <0001> Fatal signal 11 message.

17203

17230

17236

17258

17306

17319

17330

AVAMAR 5.0 RELEASE NOTES

49

Issues Resolved

Version 5.0.0-409
The following issues (bugs) have been resolved in version 5.0.0-409: BUG# 17205 ISSUE/RESOLUTION Corrected an issue on multi-node servers in which if the data server (also known as GSAN) processes are already running on the data nodes, then restarting the ASCD process on the utility node will cause ASCD to fail to redirect clients to the data nodes. Typing ascd restart on the utility node as user admin will cause this issue to occur. Also, if you issue dpnctl start after the GSAN is already up (for example, to restart the MCS, EMS or the scheduler), then dpnctl start will issue the ascd restart command, and this will cause this issue to occur. Corrected an issue in which the data server (also known as GSAN) fails to cancel backups at the beginning of the blackout window starting with the second day's blackout window. The GSAN process is designed to cancel all backups at the beginning of the blackout window. Canceling the backups gives the clients an opportunity to wrap-up the session and create a partial backup. If the backup sessions continue running, they will be killed later in the blackout window when the garbage collect process starts. Updated Avamar clients to correct an issue in which, if 5.0.100-407 clients are backing up to a pre-v5.0 server, the data server (also known as GSAN) might create multiple entries for the same hash in the indexstripe.

17250

17312

Version 5.0.0-410
The following issues (bugs) have been resolved in version 5.0.0-410: BUG# 17520 ISSUE/RESOLUTION Corrected an issue in which, following an upgrade to version 5.0 (5.0.0-407), all event profiles would be set to enable ConnectEMC reporting. It was determined that this was not desired behavior. The problem was addressed by creating an upgrade script that disables ConnectEMC reporting on event profiles other than the ConnectEMC Event Notification Profile and ConnectEMC Reports Profile.

AVAMAR 5.0 RELEASE NOTES

50

Issues Resolved

Client Version 5.0.100-414


The following issues (bugs) have been resolved in client version 5.0.100-414: BUG# 17216 ISSUE/RESOLUTION Corrected an issue in which selecting About from the Avamar Windows Client tray applet would not show all client information if the client machine was running a non-English version of Windows. Corrected an issue in which initiating a restore from the Avamar Windows Client tray applet would not properly display the select for restore web page, thereby preventing successful completion of the restore activity. Corrected an issue with the optional desktop/laptop feature in which selecting Backup Up Now or Restore did not launch Internet Explorer 7, which is required to complete the operation. Corrected an issue with Mac OS X restores in which some directories were incorrectly restored as files, causing any files within those directories to not be restored. The problem was isolated to the way in which certain kinds of symbolic links are handled during the restore process. The issue has been corrected and Mac OSX restores now correctly restore all directories, files and symbolic links. Corrected several issues that caused Exchange Message backups to be unacceptably slow. Corrected an issue in which Avamar Administrator showed incorrect progress bytes for replication activities. Corrected various localization issues with Japanese and Portuguese languages. Corrected an issue with AIX, HP-UX, Linux and Solaris restores in which files larger than 2GB are always overwritten regardless of the selected restore mode. Corrected an issue in which invoking avagent --debug on Linux machines would cause a fatal signal 11 (segfault) error. Corrected an issue in which the avsetupndmp program running on the Avamar NDMP Accelerator failed to update the /usr/local/avamar/var/.../ndmp-emc.pin file, which caused subsequent backups to fail. Corrected an issue in which a backup operation from a 5.0 client to a 4.x server terminates unexpectedly if a checkpoint is initiated on the server. Additionally, if you are performing replication operations from a 5.0 server to a 4.x server, contact EMC Technical Support to install a patch for your server.

17225

17300

17339

17411 17672 17533 17664 17674

17679 17704

17780

AVAMAR 5.0 RELEASE NOTES

51

Issues Resolved

Version 5.0 Service Pack 1 (5.0.1-32)


The following issues (bugs) have been resolved in version 5.0 Service Pack 1 (5.0.1-32): BUG# 15858 16571 ISSUE/RESOLUTION Implemented an enhancement to the rollback.dpn command so that logs are retrieved and saved prior to the rollback. Corrected an issue in which health_check.log displays contained a sh: status.dpn: command not found error. The problem was isolated to the manner in which the MCS programmatically issues the status.dpn command (manual invocation of status.dpn was not affected and has been corrected. Corrected an issue with the mechanism for retiring clients in which a retired client checking in with MCS would generate event code 22280. The problem was isolated to a hostname mismatch (the MCS internally renames retired clients to <hostname>.<timestamp> when they are retired). Additional workorder handling logic has been implemented to address this situation. Corrected an issue in which the data server (also known as GSAN) would occasionally fail if an HFS check operation was stopped before it fully completed. Corrected an issue with the Web Restore feature in which attempting to restore Office 2007 filenames that contained spaces would fail with an Internal Server Error. Corrected an issue in which Avamar Administrator and the avmaint nodelist command would return correct disk usage statistics. The problem was isolated to differences in the way RHEL 3 and RHEL 4 server operating systems report disk usage. Implemented a customer-requested enhancement to support snmpwalk. Corrected an issue with the Avamar Administrator Manage All Schedules window Maintenance Window tab in which it would fail to set the window if the computer running the Avamar Administrator software was not configured for a POSIX timezone. Provided UI and online help content for the Desktop/Laptop feature in the following localized versions: Chinese (zh_CN), English (en_US), French (fr_FR), German (de_DE), Italian (it_IT), Japanese (ja_JP), Korean (ko_KR), Portuguese (pt_BR), Russian (ru_RU), and Spanish (es_LE). Corrected a potential cross-site scripting vulnerability in the online help. 17441 Corrected an issue in which a checkpoint initiated by the system near the end of the maintenance window did not occur. The problem was isolated to control logic which ensures there was sufficient time to complete the checkpoint.

16759

17042

17059

17172

17192 17347

17401

AVAMAR 5.0 RELEASE NOTES

52

Issues Resolved BUG# 17451 ISSUE/RESOLUTION Corrected an issue where MCS may shut down unexpectedly when Avamar is used in conjunction with Networker and Networker starts multiple backup jobs for different clients within the same second. Corrected an issue in which the MCS would occasionally shut down unexpectedly if it received client messages with extended characters. Corrected an issue in which the Avamar VMware image backup and restore feature did not work reliably with the Japanese version of vSphere. Corrected an issue with replication in which attempting to replicate a client with the string avmgr in the client name was unsuccessful because avmgr is a known Avamar command line utility. If backups were configured to use the Always allow overtime setting, garbage collection did not honor this setting and backups were terminated when garbage collection started. This issue was corrected, so that now, if the capacity utilization of the data server (GSAN) doesn't exceed the diskwarning limit, or if garbage collection is suspended, no backups are cancelled. If the data servers capacity utilization DOES exceed the diskwarning limit: Backups are not cancelled for clients with Always allow overtime set. Backups are cancelled for clients that do not have Always allow overtime set. 17708 Corrected an issue in which Exchange database restores fail if the Exchange server is associated with an Active Directory child domain (for example, child-domain.example.com). Corrected an issue in which VMware image level backups would fail if the datacenter was not at the root level of vCenter node. Corrected an issue Avamar Administrator Manage All Schedules window in which setting some day of the week checkboxes would cause others to behave unpredictably. Added documentation errata entry to these release notes explaining that incremental backups are not supported on Oracle AIX systems. The Avamar Oracle Client User Guide will be revised accordingly in a future release. Corrected an issue in which VM image restores would fail if the image backup contained certain localized number strings. Corrected an issue in which the avsetup_mccli script did not properly configure systems if an existing mcclimcs.xml preferences file was present. Corrected an issue in which the mcupgrade4.1.0.8.pl server upgrade script did not correctly handle a utility node hostname change.

17532 17591

17646

17701

17841 18118

18157

18245 18250

18436

AVAMAR 5.0 RELEASE NOTES

53

Issues Resolved BUG# 18458 18478 ISSUE/RESOLUTION Corrected an issue in which the bytes-recovered information logged to dumpmaintlogs --types=gc did not match avmaint gcstatus. Corrected an issue in which backup clients had difficulties connecting to the Avamar server in a NATd environment.

Client Version 5.0.105-169


The following issues (bugs) have been resolved in client version 5.0.105-169: BUG# 10317 ISSUE/RESOLUTION Corrected an issue in which Exchange message backups of messages or folders containing Japanese extended characters did not successfully complete. Corrected an issue in Avamar Exchange plug-in (AvExchange) logs were not automatically pruned from the /var/avamar directory. Corrected an issue in which scripted Oracle 9i RMAN backups occasionally did not successfully complete. Enhanced Avamar Oracle Client User Guide to better explain Windows Oracle 9i and 10g redirected restores. Modified the .alg log file to remove inaccurate error counts listed in the file. Corrected an issue in which Avamar Windows Client software would not install correctly on a localized version of Windows. Corrected an issue in which incremental Celerra backups occasionally failed to complete. Corrected an issue in which client data would not be replicated if the client name contained the string avmgr. Corrected an issue in which avtar would fail when attempting to freeze Windows 2000 volumes. Corrected an issue in which certain Oracle RMAN restores would output erroneous error messages. Enhanced Avamar Backup Clients User Guide to better explain web restore limitations, particularly the inability to restore NetWare data with the web restore feature. Corrected an issue with the Avamar Administrator Activity Monitor in which replication status and statistics did not include source server activity. Corrected an issue with the backup and restore of Windows hardlinks for Windows 2008 and above.

12157 13165 14703 16884 17217 17240 17338 17442 17464 17499 17840 17546

17610

AVAMAR 5.0 RELEASE NOTES

54

Issues Resolved BUG# 17645 17850 17931 ISSUE/RESOLUTION Corrected an issue in which NetApp Data ONTAP 7.3 backups occasionally failed with ACL or inode errors. Created new Avamar VMware Guide publication to address various customer concerns and request for enhancements. Corrected an issue in which the first Celerra backup taken after upgrading NDMP accelerators from 4.1 to 5.0 is incorrectly forced to be a level 0 backup. Corrected an issue in which incremental backups of certain large Celerra datasets exhibited poor data deduplication. Corrected an issue in which some Desktop/Laptop users encountered session has expired errors. Corrected an issue in which avtar running on 32-bit Red Hat Enterprise Linux 5 client would occasionally fail with a Fatal signal 11 error. Implemented a customer-requested enhancement to add browser requirements to client compatibility matrix. Implemented a customer-requested enhancement to not make marking Exchanges databases for overwrite the default selection. Corrected an issue in which Celerra backups would occasionally experience errors when backup up directories containing multiple hard links. Corrected an issue where, after a Recovery Storage Group was created, it could not be bound in Active Directory and recovery into the Recovery Storage Group was not possible. Corrected an issue in which some NetAPP backups would fail with code 1: Operation not permitted. Corrected an issue in which Avamar image proxy clients would occasionally shut down unexpectedly when a VMware image backup was canceled. Corrected an issue in which some Microsoft Office 2007 files would not back up properly. Corrected an issue in which some Celerra NDMP back ups would fail if they contained a hardlink to a file that had been migrated to secondary storage. Corrected an issue in which specifying a Windows drive letter inside a dataset without including a backslash character would cause subsequent backups of that drive to fail. Corrected an issue in which certain NetApp Data ONTAP 7.3 back ups did not correctly report back up progress bytes.

18063 18327 18486

18489 18555 18583

18700

18995 19014

19031 19037

19040

19076

AVAMAR 5.0 RELEASE NOTES

55

Issues Resolved BUG# 19187 ISSUE/RESOLUTION Corrected an issue in with Exchange Message back up in which messages in Public Folders occasionally did not back up or restore properly. Corrected an issue in which the disaster recovery wizard did not correctly validate user credentials when an external authentication system was used. Corrected an issue in which Solaris 9 and 10 clients would occasionally fail to boot following a restore of the /platform directory. Corrected an issue where a failed or cancelled WMware backup left undeletable snapshots behind. This issue was due to the fact that VDDK 1.1.0 marked the snapshot as undeletable when performing a hot add. Avamar 5.0.105-169 uses VDDK 1.1.1, which does not mark the snapshots as undeletable. Corrected an issue in which cancelling an NDMP activity would cause Avamar Administrator to quit unexpectedly.

19188

19232 19261

19440

Version 5.0 Service Pack 2 (5.0.2-41)


The following issues (bugs) have been resolved in version 5.0 Service Pack 2 (5.0.2-41): BUG# 14798 18375 18709 18726 ISSUE/RESOLUTION Corrected an issue where the Avamar Administrator fails to re-connect to the vCenter after the vCenter was down/rebooted. Corrected an issue where an inadequate vCenter connection pool size setting may cause backup jobs to fail. Corrected an issue where the checkpoint process hung waiting for index stripe to complete. Corrected issues with use of the fully qualified domain name of the Avamar server or utility node to connect to the Management Console Server. Corrected an issue where two VM backup work orders were sent to proxy client at the same time, causing the proxy client to crash. Corrected several issues and added enhancements to the expiresnapups command. Corrected an issue in which server checkpoint operations would occasionally time out. Corrected an issue in which server checkpoint operations would occasionally cause node failures. Corrected an issue where VMware restores were failing with a message invalid datastore for disk xx.

18801 18874 18849 18855 19176

AVAMAR 5.0 RELEASE NOTES

56

Issues Resolved BUG# 19265 19673 19811 ISSUE/RESOLUTION Corrected an issue in which redirected virtual machine image restores would fail if the target virtual machine contained snapshots. Corrected an issue in which change logs for index stripes may get out of sync when the data server does not shutdown cleanly. Corrected an issue where a new installation or an upgrade to Avamar 5.0 SP2 failed when the IPMI Event ID 1012 is not filtered from the / var/log/messages file.

Version 5.0 Service Pack 3 (5.0.3-29)


The following issues (bugs) have been resolved in version 5.0 Service Pack 3 (5.0.3-29): BUG# 17215 ISSUE/RESOLUTION Corrected an issue in which rebuilding a node and balancing may cause the server to go into read-only mode because there were a large number of empty parity stripes, making the system appear to be unbalanced. Corrected an issue on Microsoft Windows systems where the Management Console did not correctly display upper and lowercase client and domain names. Corrected issues with index caching that resulted in a segmentation fault. Corrected an issue where folders with the same name across different vCenter virtual machine and template views did not restore correctly. Corrected a problem where the Management Console did not correctly identify the plug-in for replicated virtual machine client restores, causing the restores to fail. Also corrected an issue where restores to an existing VM that is also an Avamar client were failing. Corrected a race condition during checkpoint and poolcheck operations that caused the server to crash. Corrected an issue where duplicate key violation errors are printed to the mcserver.log file during successful WMware backups. A new event code, number 30945, has been added with the description "A duplicated snapshot was detected. This is not an expected condition but it is not harmful to the backup created." Corrected an issue where garbage collection was not able to kill backups that were running when garbage collection started. Corrected an issue where vmdk base file and datastore names were incorrect when a virtual machine has disks spanning multiple datastores.

18302

19458 19700 19753

20016 20096

20257 20408

AVAMAR 5.0 RELEASE NOTES

57

Issues Resolved BUG# 20459 20498 ISSUE/RESOLUTION Corrected an issue where node balancing would suspend indefinitely for a system that has a node decommissioned. Corrected an issue where secure delete failed with the following error: "0 ERROR! Exit code 0: Request failed" as well as "hash referenced but not defined" errors in log files. Corrected an issue where hfscheck failed with multiple errors after a node crashed and was restarted. Improved the performance of the Management Console interface when editing a virtual proxy client, which could take several minutes because of the time it took to browse datastores. Corrected an error with log file truncation which, in specific cases, could cause the server to inadvertently truncate the log file's header block or end of file marker. This caused the server to crash.

20531 20586

20665

Client Version 5.0.106-28


The following issues (bugs) have been resolved in client version 5.0.106-28: BUG# 19556 ISSUE/RESOLUTION Corrected an issue with NetApp OnTap 7.3 where incremental backups failed when the filer has recycled an inode from being a file or directory to being an ACL. Corrected issues related to the Avamar softwares integration with Homebase. Avamar Integrated System Recovery did not correctly handle NICs that had an empty list of DNS servers. Also, Integrated System Recovery used the first agent.dll found in the search path, which may not be the correct agent.dll required to perform backups. Corrected a problem on Solaris 10 with resetting ACLs on symlinks during restore if the linked target file was not yet restored. Corrected a problem where filenames that are longer than 254 bytes lose their extension when the filename is truncated during backup. The filename is still truncated, but the file's extension is now preserved. On a Windows Desktop/Laptop client, selecting Restore or Back Up Now from the system tray icon caused the error: "GetUserName failed 1332". Corrected an issue with the Avamar Oracle plug-in when there are multiple locations for Oracle archive logs and the plug-in option Delete archive logs after backup is selected; the archive logs were deleted from only one of the destinations.

19643

19655 19737

19913

19815

AVAMAR 5.0 RELEASE NOTES

58

Issues Resolved BUG# 19846 ISSUE/RESOLUTION Corrected an incorrect symlink created after upgrading accelerator nodes, in which /usr/local/avamar/var/ was a symlink to /var/avamar/ instead of /data01/avamar/var/. Corrected an issue with the Avamar for Lotus Notes client, which was not rolling back to the proper time on different locales, and the client was not properly handling the cancellation of recovery operations. Corrected an issue where restores of the Microsoft Exchange database did not work if the Exchange server version was not determined correctly during backup. Corrected a problem with Desktop/Laptop restores on all Windows platforms other than Vista where the local admin user was unable to restore all files in a backup. Corrected an issue where the Avamar Oracle plug-in would core dump due to improper memory allocation during restores involving a large number of files. Corrected a problem where System State backup did not detect an ASR writer error when a dynamic disk was offline. Added support for multiple Network Interface Cards (NICs) with Windows 2008 SP2 System State WinPE restore. Corrected performance problems with incremental backups on Windows by preventing hard links from being included in the file cache. This applies to all Windows backups except System State backups, which will continue to have hard link processing enabled. To enable hard link processing for all other backups, you will need to include the --x18=1048576 flag with avtar.exe. Corrected an issue where backups performed with the Windows Exchange VSS plug-in failed when there are too many transaction logs in the backup. Corrected an issue with the Avamar Oracle plug-in on Windows where the plug-in was timing out while waiting for the Avamar server to complete a history command. The timeout limit was removed. Corrected an issue where restores of SCO Unixware clients fail if the client has more than 256 backups. Corrected an issue with Avamar Exchange plug-in where user names in Active Directory are not detected correctly for the Exchange Backup User Configuration tool. The Exchange Backup User Configuration tool displayed the error "CERR: Check user member of group failed 'Username' is not member of Domain Admin." Corrected an issue with the Avamar Windows VSS plug-in where noncritical disks were formatted when offline restore was performed on different hardware.

19894

19938

19996

20006

20008 20025 20055

20110

20154

20247 20272

20285

AVAMAR 5.0 RELEASE NOTES

59

Issues Resolved BUG# 20376 ISSUE/RESOLUTION Corrected a problem with the Avamar Windows VSS plug-in where System State backups would hang if there were a large numbers of files for the VSS writer to exclude. Corrected several issues related to the use of the Windows Exchange plug-in with recovery of items in Exchange Public Folders. Corrected an issue where restore of a Microsoft Exchange database will fail if the client is version 4.1.x and the server is version 5.0.2. The problem was duplicate entries of the same name in the plug-in catalog. Corrected an issue where Celerra backups failed with the following error message: avtar Error <7779>: Unable to find a matching entry in prevlist for historytable ('<table>' -> '') 20479 Corrected an issue where Windows VSS backups would fail when the Avamar server received certain transient errors from the VSS snapshot process. The server will now retry the snapshot when these errors are encountered. Corrected an issue where the Avamar Simple Client Console (AVSCC) did not start automatically on Microsoft Windows 7 with User Account Control enabled. However, if the Avamar client was previously installed on the system and the system was upgraded to client version 5.0.10628, the problem may persist.

20390 20453

20469

20564

Version 5.0 Service Pack 4 (5.0.4-30)


The following issues (bugs) have been resolved in version 5.0 Service Pack 4 (5.0.4-30): BUG# 20210 21376 21442 21698 ISSUE/RESOLUTION Corrected an issue where the Management Console did not correctly connect to the Avamar server by IP address. Corrected an issue where Avamar SNMP traps were not following the proper naming convention for trap variables. Corrected an issue where the v_gcstatus table contained extraneous records. Corrected an issue with VMware image file backup, where a very large image file backup could cause clients to time out waiting for the server to respond. Corrected an issue in which avmaint testintegrity rebuilds stripes even when --repair is not supplied. Furthermore, the statuses of a safe stripe and its parity stripe show rebuilding and corrupt, respectively, instead of rebuilding and good.

21917

AVAMAR 5.0 RELEASE NOTES

60

Issues Resolved BUG# 22022 ISSUE/RESOLUTION Corrected an issue in which logging out of Avamar Activation Manager, while client invitation processes were running, left process threads in memory indefinitely, potentially leading to performance problems. Corrected an issue where the shutdown.dpn process failed to properly shut down the data server (formerly known as the GSAN) on all nodes. Corrected an issue with the ascd server process in which, after receiving certain data messages, ascd does not shutdown and must be manually terminated. Corrected an issue in which ConnectEMC messages were too large to send. Incorporated latest version connectEMC binary in order to enhance stability and robustness. Corrected an issue with the system upgrade process in which upgrading the server from version 4.1 to version 5.0 caused historical information in the activities database to be deleted. Corrected an issue in which on-demand HFS checks initiated using Avamar Administrator would occasionally fail. Corrected an issue in which the server could become unresponsive if accounting updates were being applied while node balancing was occurring. Corrected an issue in which the server reported numerous tfilepool::freefilelist::allocate no more files on nodes with much less than 97% of the filesystem space used. Corrected an issue in which a very large number of small chunks that are stored sequentially can cause an error. Corrected an issue in which canceling VMware image backups was not always successful. Corrected an issue with the Avamar Administrator Backup Management window in which browsing client filesystems located in the REPLICATE domain and subdomains was very slow. Corrected an issue in which garbage collection occasionally failed with an integer overflow error. Corrected an issue where an upgrade could leave an older version of the data server (formerly known as the GSAN) installed. In Avamar Activation Manager, client move tasks failed when the repluser account had a non-default password. This has been fixed to work with any repluser password. Corrected an issue in which Avamar Activation Manager failed to display a server that was properly registered in Avamar Enterprise Manager when the MCUser password for the server was changed from the default.

22097 22107

22172 22175 22301

22371 22585

22667

22676 22721 22732

22740 22894 23120

23121

AVAMAR 5.0 RELEASE NOTES

61

Issues Resolved BUG# 23217 ISSUE/RESOLUTION Corrected an issue in which the avldap tools LDAP trace functionality (avldap --test) was not logged or displayed when the authentication type was set to non-Kerberos. Corrected an issue in which the server maintenance activities failed to start due to the changeover to Daylight Savings Time (DST). Implemented a customer enhancement request to enable logging into Avamar Administrator by supplying the server IP address rather than the DNS name. Implemented a customer enhancement request to improve HFS check performance. Corrected an issue where using avldap to configure Avamar Client Manager for LDAP without Kerberos encryption, and then selecting Directory Service as the data source in the Avamar Client Manager UI caused a failure during Active Directory login. Corrected an issue in which terminating a replication activity from within Avamar Administrator would occasionally cause Avamar Administrator to become unresponsive. Corrected an issue where the Avamar server failed to backup a VMDK disk after the size of the disk was modified. Corrected issues that resulted in incorrect backup schedules when the backup is scheduled to run at 12:00 AM. Corrected an issue where modifying a schedule with a computer in a different timezone resulted in a change to the timezone for the schedule. As part of this fix, a new drop down was added to select the timezone. Corrected an issue where the server would be in a deadlock state when stripe flushing occurred while the same stripe was being crunched.

23270 23322

23350 23371

23537

23595 23696 24782

24817

AVAMAR 5.0 RELEASE NOTES

62

Copyright 2011 EMC Corporation. All rights reserved. EMC Corporation 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 Corporation software described in this publication requires an applicable software license. For the most up-to-date listing of EMC Corporation product names, see EMC Corporation Trademarks

AVAMAR 5.0 RELEASE NOTES

63