Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC Avamar 19.7 Release Notes

Backup client technical notes

The following technical notes apply to backup clients.

Linux client installation binaries

Because of many compatible Linux operating systems, not all supported Linux operating systems have natively built installation binaries. The names of installation binaries do not always match the name of the operating system. For example, client installation binaries for Red Hat Enterprise Linux 6 are built on SUSE Enterprise Server 11. Refer to SLES 11 in the name of the installation binaries. However, these installation binaries are appropriate for installation on Red Hat Enterprise Linux 6.

IPv6 not supported on HP-UX PA-RISC

Avamar support for IPv6 is not available for the HP-UX PA-RISC platform.

Log files are time/date stamped in UTC time

Some client log and other files that are created in the VARDIR are time/date stamped in Universal Time Code (UTC) time (Greenwich Mean Time) and not the local time. This step can cause confusion when looking for a particular log file.

Firewall software must be configured to allow communication with the Avamar server

Firewall software inherently interferes with communication between the Avamar server and Avamar clients by disabling inward connections to most data ports. Configure the firewall application to allow bi-directional communication between the Avamar client and the Avamar server when the following occurs:

  • If firewall software is used on a client computer (for example, ZoneAlarm, Norton, McAfee).
  • If the integrated firewall is used with Windows clients.

This step is accomplished by adding the EMC Client Agent to an “allowed” or “exceptions” list, which also depends on the firewall application. The documentation for the firewall should provide additional information.

Avamar icon disappears from Mac system menu bar

On rare occasions, the Avamar icon disappears from the Mac system menu bar. To restore the icon, restart the Avamar client using the Avamar Client application launcher in the Applications folder.

Standby, sleep, and hibernate states interfere with backups

Issues may occur when computers go into standby/sleep (ACPI state G1-S3), hibernate (ACPI state G1-S4), or hybrid sleep (Windows Vista) modes during a backup.

On 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. Canceling the backup from the client side has no effect.

To drop the backup connection, cancel the backup from the server side. This step occurs automatically when the connection is inactive for more than 1 hour.

To help minimize this problem, ensure that the BIOS and drivers on all supported computers are up-to-date.

Browse of shared storage fails after failover in dual-stacked cluster environments

Shared storage cannot be browsed in a cluster by using the Avamar cluster client after a failover in a dual-stacked cluster environment. To enable browsing, rerun the Cluster Configuration Tool on the active node to remove and then reconfigure the Avamar cluster client.

Backup cannot proceed when mandatory locks are encountered

Avamar client software honors all mandatory locks in the target file system on Solaris and HP-UX operating systems. However, this can cause backup operations to hang indefinitely when a mandatory lock is held by another application on files that Avamar is backing up.

To work around this issue, exclude all specified files and directories with mandatory locks from the backup dataset, and perform another backup.

Solaris path length limitation

Solaris imposes a maximum path length limit of 1,023 characters. Therefore, paths cannot be specified for greater than 1,023 characters.

Retention must expire before February 7, 2106 for 32-bit Windows and Linux clients

For backups of 32-bit Windows or 32-bit Linux client computers, do not assign a retention period for a date after February 7, 2106. If an extended retention period is assigned to a 32-bit Windows client, the backup completes with exceptions. For 32-bit Linux clients, the backups complete but do not appear in Avamar Administrator.

Issues when running multiple CLI backup or restore operations at a time for a client

Stability issues occur when multiple command line interface (CLI) backup or restore operations are run at a time for a client. To work around this issue, perform only one CLI operation at a time for each client.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\