User guide

44 EMC Avamar 7.0 Release Notes
Known problems and limitations
AIX, FreeBSD, HP-UX, Linux, CentOS, and Solaris clients
The following table lists known problems for this release of the Avamar clients for AIX,
FreeBSD, HP-UX, Linux, and Solaris.
Table 15 AIX, FreeBSD, HP-UX, Linux, CentOS, and Solaris client known problems
ID Description
10392 Avamar directory protection issues
Only the root user can create files in the VARDIR (/var/avamar or
/usr/local/avamar/var, depending on the installation). However, certain
applications, such as Oracle, are known to require access to the Avamar VARDIR by
other user accounts. If this is the case, modify the ownership of /var/avamar or
/usr/local/avamar/var to allow read/write access by the necessary user
accounts.
10460 Solaris path length limitation
Solaris imposes a maximum path length limit of 1,023 characters. Therefore, you
cannot specify paths greater than 1,023 characters at any time.
10531 Backup cannot proceed when mandatory locks are encountered
Avamar client software honors all mandatory locks in the target file system. However,
this can cause backup operations to hang indefinitely if a mandatory lock is held by
another application on files that Avamar is backing up. To work around this issue,
specifically exclude all files and directories with mandatory locks from the backup
dataset, and then perform another backup.
26077 Push upgrade on Linux fails for non-default installation location
Using Avamar upgrade to push an Avamar client upgrade to a Red Hat Enterprise Linux
or SuSE Linux Enterprise Server client fails when the Avamar client software is installed
in a non-default location. The use of the rpm option --relocate to install the
Avamar client in a non-default location causes subsequent push upgrades to fail.
45520 Push upgrade for 32 bit CentOS 5 upgrades to the wrong version of the RHEL binary
The Avamar push upgrade for Avamar 7.0 does not push the correct client package for
the 32-bit CentOS 5 client.
The interim solution to this problem is to install the RHEL 4.0 binary on the client
before the push upgrade or to perform the upgrade manually.
N/A 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.