Rev.

A00
May 2023

Dell Avamar 19.9 Release Notes

This document describes new and changed features, resolved issues, known issues, and supplemental information about the
Avamar 19.9 release.
Current Release Version: 19.9
Release Type: Major (MA)

Topics:
• Revision history
• Avamar overview
• New features and changes
• Changed features
• Resolved issues
• Known issues
• Environment and system requirements
• International language support
• Technical notes
• Documentation
• Installation and upgrade considerations
• Where to get help

Revision history
The following table presents the revision history of this document:

Table 1. Revision history

Revision Date Description
A00 May, 2023 First release of this document for Avamar 19.9.

Avamar overview
Avamar is backup and recovery software with integrated data deduplication technology. Avamar solves the challenges that
are associated with traditional data protection, enabling fast, reliable backup and recovery for remote offices, VMware
environments, Data Domain and Cloud Tier, and data center LANs.
Unlike traditional solutions, Avamar reduces the size of backup data at the source—before it transfers across the network
and stores to disk. As a result, Avamar delivers fast, efficient daily full backups despite slow or congested infrastructure, and
data encryption for added security. Avamar uses patented RAIN technology for high availability, and a scalable grid architecture
enables you to upgrade capacity and performance when necessary.
NOTE:
● Any references to the Data Domain systems and the Data Domain devices in the document indicate PowerProtect DD
appliances.
● This Dell product utilizes an embedded Linux distribution, which is licensed to Dell. This embedded Linux is authorized to
be used to operate only Dell products.

1
New features and changes
The following sections provide information about the new features and changes in Avamar 19.9:

Table 2. New features in Avamar 19.9

Functional area Feature description Summary of benefits
AVE Added support to use MFR as default replication method For Avamar 19.9 systems integrated with
to replicate data across Mtrees on the same host when DDOS 7.11 and later, MFR is used as a
the source system and the target system are on the same default replication method when the backup
DD with DDOS version 7.11 and later. resides in active tier. Whereas FastCopy is
used as replication method when the backup
resides in other tiers including cloud tier.
AVE Added support for period lock in immutable backups. When you enable period lock in immutable
backups, the backup residing in Data Domain
can be locked for several weeks ranging
from minimum 1 week to maximum 31 weeks.
The period lock duration must be less than
or equal to the retention period.
NOTE: Period lock feature is not
supported for clients who use vCD for
backup purpose.

Client Added support to perform backup and restore as a non- Non-root users can perform backup and
root user restore operations on Linux filesystems.
Data Domain Added support for DD Boost API of DD OS 7.11. NA
Data Domain Added support for Multifactor Authentication (MFA) Avamar 19.4 and later support MFA in Data
enabled Data Domain. Domain 7.10 and 7.11.
Data Domain Added support for MFA enabled Data Domain Avamar 19.4 and later support MFA in Data
Management Center. Domain Management Center 7.11.
Virtualization Added support to back up and restore VM tag information This feature provides a way to back up
as part of VM metadata. and restore the VM tags as part of VM
image level backup and restore. All tags
attached to the VM are backed up during
the VM image level backup process. During
the image level VM restore operation, tags
are retrieved from the VM backup and are
attached to the restored VM, if not already
attached. This feature is enabled by default
and can be managed by using two options,
backupvmtags and restorevmtags, in
the avvcbimageAll.cmd file on Avamar
proxy.
Virtualization Added support for truncated work order ID during backup This feature enables high-level entity (HLE)
of deeply recursive containers. clients, for example, container clients and
vApp clients to have shorter work order
ID. It allows you to create log filenames
on Avamar proxy for deep folder levels
without any issue. The new log filenames are
fewer than 255 characters. It also ensures
accessibility of these logs using the AUI.
Virtualization Added support for VM File Level Restore (FLR) on Red This feature embeds Avamar proxy with
Hat Enterprise Linux 9 in SLES 12. kernel builds of SLES 12 SP5 to ensure
support for FLR on Red Hat Enterprise Linux
9 VM with XFS on it.
MCS Upgraded support for BSafe in the MC component MC has upgraded the BSafe Crypto-J
from v6.2.5 to v6.2.5.0.2. To support
this upgrade, update the rsa_bsafe_version

2
Table 2. New features in Avamar 19.9 (continued)
Functional area Feature description Summary of benefits
in //AV/main/mc/lib/mcserver.xml
to 6.2.5.0.2

Changed features
The following table lists the changed features in this release:

Table 3. Changed features in Avamar 19.9

Functional area Feature description Summary of benefits
GUI The Windows and Mac Avamar client UI avscc, accessed NA
through system tray icon, displays the updated branding
of Dell Technologies as the company brand and Dell as the
product brand.
Virtualization FLR UI component is deprecated and is removed from FLR UI component is removed from Avamar
Avamar 19.9. 19.9. There is an alternative to perform FLR
by using AUI.
Virtualization Upgraded the VDDK library version for proxy plugins from NA
v7.0.3 to v8.0.0 in Avamar 19.9.
Microsoft Apps Added support for SQL Server 2022 This feature enables AV SQL plugin to
perform backup and restore operation on
SQL server 2022 in Windows Server 2022
and Windows Server 2019 operating system.

Operating system enhancements

Avamar 19.9 includes an upgrade for all supported platforms to the SUSE Linux Enterprise Server (SLES) 12 SP5 operating
system. This upgrade replaces the previous SLES 11 and SLES 12 operating systems.
NOTE: All routes to Avamar 19.4 and later require the deployment of, or upgrade to, SLES 12 SP5. The new operating
system is a required component of Avamar 19.4 and later.
The operating system upgrade does not affect the functionality or interfaces of the Avamar software. However, take note of
the following important points:
● The Avamar platform operating system security rollup supports Avamar servers that run SLES 12 SP5 starting with release
2020R1.
● The upgrade changes some underlying operating system commands, such as the move from systemv to systemd.
● The upgrade also updates some underlying libraries and dependencies.
● All new installations of Avamar 19.4 and later, and SLES 12 deploy with a 1 GB /boot partition to improve compatibility with
future kernel upgrades. Upgrades from SLES 11 preserve the existing 100 MB /boot partition.

Prerequisites
Review the following items when you create your deployment or upgrade plan:
● All nodes in the server must run one of the following operating systems:
○ SLES 12 SP5
○ SLES 12 SP4
○ SLES 11 SP4
○ SLES 11 SP3
○ SLES 11 SP1
● Avamar 7.5.1 or later is a prerequisite for the upgrade to Avamar 19.9.

3
 If the server or NDMP accelerator node runs an older release, upgrade to a supported version before you start the upgrade
to Avamar 19.4 and later.
● Supported hardware platforms:
○ Gen4T
○ Gen5A

New installations and deployments

New instances of AVE 19.4 and later for all supported virtual environments deploy with SLES 12 SP5. New VMware proxy
instance also deploys with SLES 12 SP5.
New installations of the Avamar Data Store (ADS) Gen4T and Gen5A platforms must have SLES 12 SP5 loaded before software
installation. The existing Avamar software installation procedures for the ADS do not change.
New installations of NDMP accelerator nodes, whether physical or virtual, must have SLES 12 SP5 loaded before software
installation. The existing NDMP accelerator software installation procedures do not change.

Upgrades from previous versions

NOTE: Consider the following:
● Customers running Avamar versions 7.5.1, 18.1.x, 18.2.x, 19.1.x, 19.2.x, 19.3.x, 19.4.x, 19.4.0.124, 19.7.x, and 19.8.x can
upgrade to 19.9.
● Before you upgrade, verify that the Avamar server or NDMP accelerator node meets the prerequisites.
● Upgrades from older releases of Avamar or the NDMP accelerator client software might require intermediate upgrades
to a supported Avamar release and operating system. Ensure that your upgrade plan includes any necessary incremental
steps, and that the server or NDMP accelerator node meets the prerequisites for any intermediate upgrades.
● You cannot upgrade an Avamar server to 19.9 if it uses Blowfish for its data-at-rest encryption. Instead, install a new
19.9 server and migrate the data from the old server.
The Avamar software upgrade workflow package integrates both the operating system upgrade to SLES 12 SP5 and the
software upgrade to Avamar 19.9. The upgrade workflow migrates the operating system and Avamar software configurations
and then replaces the existing system partitions.
Initial startup might take longer as the upgrade workflow installs necessary drivers and firmware, and configures new packages.
The upgrade workflow also takes checkpoints and performs health checks before and after the upgrade. The operating system
upgrade process is the same for AVE and for ADS single-node and multi-node servers.
For NDMP accelerator nodes, the process is similar. However, in this case, the Avamar accelerator upgrade workflow package
contains the new operating system and the new accelerator software.
You cannot upgrade VMware proxies from one operating system to another by using the ISO file. Instead, remove the existing
proxies and use the Proxy Deployment Manager (PDM) to deploy replacement Avamar 19.9 proxies. Remove any proxies that
you manually deployed. The Avamar for VMware User Guide provides more information.

FIPS mode
The Avamar software upgrade workflow disables Federal Information Processing Standard (FIPS) mode. If FIPS mode is enabled
before the upgrade, you must reenable FIPS mode after the upgrade completes.
NOTE: The upgrade workflow disables FIPS if the original version is 19.1. If the original version before upgrade is 19.3 and
later, upgrade workflow will not disable FIPS.
The Avamar Product Security Guide provides more information about FIPS mode.

Determine the installed Avamar version

Before you upgrade, determine the version of the installed Avamar so that you can plan the upgrade path.
You can also review the package installation history through the Avamar Installation Manager. The Avamar Administration Guide
provides more information.

4
1. Through the AUI:
For Avamar 18.1 and later, the AUI provides the preferred graphical method.
a. Log in to the AUI.
b. In the AUI header pane, click .
The About dialog box opens, and lists the installed Avamar version.
2. Through the command line:
Where the AUI is not available, verify the Avamar component versions with the following commands.
a. Log in to the server as admin.
b. Check the MCS version by typing the following command:
mcserver.sh --version
Information similar to the following is displayed in the command shell:

version: 19.1.0-38
c. Check the gsan version by typing the following command:
gsan --version
Information similar to the following is displayed in the command shell:

version: 19.1.0-38
build date: Apr 25 2019 19:23:45
d. Check the avtar version by typing the following command:
avtar --version
Information similar to the following is displayed in the command shell:

version: 19.1.0-38
build date: Apr 25 2019 19:32:16
Verify that the Avamar component versions match.

Compatibility updates
The updated software and database compatibility information is provided in the E-LAB Navigator at https://
elabnavigator.dell.com/eln/elnhome.

Resolved issues
There are no resolved issues in the Avamar 19.9 release.

Known issues
The following sections describe the known issues in Avamar. Temporary solutions are provided when they are available.

Avamar server known issues

The following table lists the Avamar server known issues in this release:

Table 4. Avamar server known issues

Issue ID Subject/Functional area Description Workaround/Resolution
161698 Replication fails with code The replication must fail with Hard quota NA
157: miscellaneous limit exceeded error, but instead it fails with
error code when hard code 157: miscellaneous error code.
quota limit exceeds.

5
Table 4. Avamar server known issues (continued)
Issue ID Subject/Functional area Description Workaround/Resolution
46224 Scheduled backups are Scheduled backups are missed during daylight During days when Daylight Saving
missed during daylight savings time transitions Time (DST) transitions occur,
savings time transitions if you have backups that are
scheduled to run during the
following times, the backups do
not occur:
● For the Spring DST transition,
daily backups that are
scheduled during the hour
from 2:00 a.m. through 2:59
a.m. do not occur.
● For the Autumn DST transition,
daily backups that are
scheduled during the hour
from 1:00 a.m. through 1:59
a.m. do not occur.
The interim solution to this
problem is to avoid scheduling
backups during these time ranges,
or to perform an ad-hoc backup
when the scheduled backup does
not occur.
299817 After root-to-root MC MC restore fails with clients violate foreign key The support team must update db
esc 29070 restore fails with "clients" constraint after root-to-root replication. schema with the provided script
violates foreign key manually.
constraint
309181 esc mcserver.sh --init fails If you run mcserver.sh with --init or -- NA
34646 to run mcrootca restore in the incorrect context, directories
successfully and also fails might be deleted. Note that the mcserver.sh
to decrypt passwords --init command is designed only for internal
for rmi_ssl_keystore_AP/ execution from the workflow framework during a
rootAP and viewuserAP new installation. An error occurs if you execute
the command manually.
309554 IPv4 traffic initiated by In a dual stack environment where both Avamar To avoid any IPv4 traffic, remove
Avamar in a dual stack and Data Protection Central (DPC) have IPv4 and Avamar from DPC, and then re-
environment IPv6 addresses configured, the communication add Avamar.
should occur using IPv6 since this is the preferred
network. However, IPv4 traffic is observed when
Avamar is connecting to the DPC for the first
time.
310471 MCS running MCS runs syncDisplayNameWithVmware if the NA
syncDisplayNameWithVm Rename VM event name contains ^vmfs/
ware when Rename VM volumes/*.vmx prefix. This issue typically
event name contains .vmx takes a day to correct itself automatically with
prefix the next vCenter synchronization.
311781 Jetty component on The Jetty component on the Avamar server and Upgrade the Jetty component to a
Avamar server and proxy proxy node is not at the minimum recommended minimum of version 9.4.16.
node requires upgrade version.
314532 Command output indicates The output of the systemctl status NA
that zzdpn.service failed zzdpn.service command indicates that the
zzdpn.service failed, even if all DPN services
such as GSAN, MCS, and avinstaller are running
normally. This error can be ignored, as there is no
negative impact to functionality of the currently
running server.
NOTE: Operating system-based shutdowns of
the Avamar server can result in data loss.

6
Table 4. Avamar server known issues (continued)
Issue ID Subject/Functional area Description Workaround/Resolution

The section "Powering off or restarting the

server" of the Avamar Administration Guide
provides more information about operating
system shutdown and reboot best practices.

317003 urgent restore fails with Urgent restore fails with an error when the SSD is If the SSD is empty, using avmaint
esc 36763 error Failed to empty. stripestate to bring the stripe
retrieve backup online sets it right and the stripe is
list from account rebuilt because it is missing from
xxx (error code 18 the disk.
MSG_ERR_NOT_PRESENT
)
317657 hwfaultd - add check for When the file system is full, an undefined behavior NA
file system free space is observed on ADS.
approaching 100% full
318619 Updating gen4t-sys zip to In gen4t-sys-2.3, which is the payload included NA
include latest ipmiutil-emc with Avamar 19.3.0-122 , it is still bundling
rpm the older ipmiutil-emc-2.7.9-8.x86_64.rpm.
The required fix must bundle ipmiutil-
emc-2.7.9-11.x86_64.rpm with a new gen4t-
sys-2.4.zip, and update the workflows to include
the gen4t-sys-2.4.zip payload.
319081 AWS m5: get kernel error Kernel error is observed during boot time of NA
EDAC skx: Can't get tolm/ an AWS m5 instance. It is an indicator that
tohm every boot time the VM Host implements the Skylake platform
incompletely; the tohm missing message is
printed when the operating system tries to
decode the EDAC information, and fails to access
the required I/O registers. The right way is
to implement those registers in the VM Host
emulation.
319461 esc WC - Win FS Restore - To turn the xflag into official flag, a new NA
37431 SR<16968788> - Not all procedure in flag handling that modifies many
permissions are restored APIs must be included.
when using --restore-acls-
only flag
320300 ADS4T-SLES11- After kickstart with SLES 12 SP5 v8 ISO, the Run ethtool -s to reset
SP4-64-0001.02.iso and eth0 interface runs at 100 Mbps on some gen4t the advertised link speed to
Gen4T, eth0 (shared nodes, which are not as expected. If same node 1000Mbps.
port) sometimes auto- is kickstarted with SLES 11 SP3 1.64, the eth0
negotiates to 100 Mbps interface runs at 1000 Mbps. These nodes only
run 1000 Mbps with SLES 11 SP3 and run 100
Mbps with SLES 11 SP4, SLES 12 SP4, or SLES 12
SP5.
320741 When VM backup jobs VM backup job work orders are not created Remove duplicated entries in
esc 37619 are configured to connect correctly if the backup is to a specific Data MCDB.
to Data Domain, the Domain in that dedicate customer environment.
proxyDirectives section of This is because of the incorrect database
the work order are not operations in that environment, which caused to
created have duplicated entries in MCDB.
321131 Avamar upgrade failed at The root cause of failure of the Avamar NA
Install Gen4T system tools Upgrade workflow is claimed to be an
(95 of 170) underlying system pathology that is particular
to a4t84d8.datadomain.com. In the case of
a4t84d8.datadomain.com, the get-platform-logs
command appeared to be unresponsive without
completing, which is a strong indication that

7
Table 4. Avamar server known issues (continued)
Issue ID Subject/Functional area Description Workaround/Resolution
the BMC on a4t84d8.datadomain.com is in a
bad state. If the BMC remains in a bad state,
then it might be necessary to do a power-drain
procedure, which involves shutting down the
node as gracefully as it will allow, and then pulling
utility power - either via remote power control or
by physically pulling the power cords - waiting a
minute or so, and then re-connecting power and
restarting the node.
321158 When FIPS is on, every This issue is being investigated by SUSE. The NA
time is boots, there fatal errors reported seem to be safe to ignore.
are dracut-pre-trigger
modprobe FATAL Model
not found messages on
console
321198 AdaptecEventMonitorServ On ADS Gen4T with SLES NA
ice.service incorrectly 12 SP5, systemctl status
reported as inactive AdaptecEventMonitorService.service
(seen as EventMonitor in 'ps' listings) incorrectly
shows the status as Inactive, even though the
service is up.
322055 Serviceability report is Serviceability report becomes unresponsive for NA
unresponsive for 1 hour on an hour because /usr/local/avamar/bin/
multi-node Avamar rptSiteInventory.pl is unresponsive. This
issue is observed when the SUDO is not working
on data node.
324711 Hyper-V-2012 kernel: Hyper-V-2012 kernel: hv_vmbus: probe failed for NA
hv_vmbus: probe device 2450ee40-33bf-4fbd-892e-9fb06e9214cf
failed for device (-19). It has dependency on SuSE.
2450ee40-33bf-4fbd-
892e-9fb06e9214cf
(-19)
325343 IDPA 2.6.0: MC is unable AV change password workflow causes the MC's Perform the following:
to log in to gsan after run gsan command to fail after rollback. 1. After AV change password,
password change. perform mc flush by using the
command mcserver.sh --
flush.
2. Create a gsan checkpoint by
using the command mccli
checkpoint create --
override_maintenance_s
cheduler.
325781 AWS: build 19.4.0.77 Kernel error is observed during boot time of an NA
kernel error: Cannot AWS instance: Cannot get hvm parameter
get hvm parameter CONSOLE_EVTCHN
CONSOLE_EVTCHN

8
Avamar Virtual Edition known issues
There are no known issues with Avamar Virtual Edition (AVE) in this release.

Avamar Web Client (AUI) known issues

The following table lists the AUI known issues in this release:

Table 5. Avamar Web Client(AUI) known issues

Issue ID Subject/Functional area Description Workaround/Resolution
326662 esc 38896 Redirected restore from Windows Redirected restore from Windows Perform the following steps:
server to Linux fails in 18.2 with server to Linux fails when accessed 1. Restore Windows backup
path not found in backup error. from AUI, with path not found in to Windows server.
backup error. 2. Restore all files (from
Windows backup to Linux
server) other than single
file.

Avamar Orchestra known issues

The following table lists the Avamar Orchestra known issues in this release:

Table 6. Avamar Orchestra known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
307990 Original task records removed Since there is currently no design for persistence of the NA
if Orchestra REST API service internal tasks in the Orchestra REST API, the original task
restarted records get removed upon restart of the REST API service.

Avamar Administrator known issues

The following table lists the Avamar Administrator known issues in this release:

Table 7. Avamar Administrator known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
52801 Progress Bytes column in the Activity The value that appears in the Progress Bytes NA
Monitor displays different values from column in the Activity Monitor for backups with
one Level 0 backup to the next the Windows File System plug-in is different from
one Level 0 backup to the next for an unchanged
backup set. The issue is a display issue only and
does not affect the validity of the backup itself.
263268 Storage utilization capacity of Avamar The storage utilization capacity of Avamar NA
server node reporting inaccurately server node that you displayed in the Avamar
Administrator is approximate and not an exact
value, and has no impact capacity for additional
backups.
324449 ESRS registration for AVE or AV grid ESRS gateway has issues supporting IPv6. Avamar NA
fails in IPv6 configured IDPA appliance. gets wrong response from ESRS Gateway REST
API, which causes Avamar to mark ESRS as
disconnected.
325077 IDPA 2.6.0: Avamar restarts agents Avamar restarts agents when the changing NA
when changing AV password. appliance password. Due to this, all active backup
jobs must be stopped to change password.

9
Table 7. Avamar Administrator known issues (continued)
Issue ID Subject/Functional area Description Workaround/
Resolution
326491 Capacity Report.xml incorrectly According to Avalanche data, the AVE flag in NA
reports if the system is an AVE. Capacity Report.xml is sometimes incorrect.
The ADS is wrongly marked to the AVE in the
Capacity Report.xml.
326661 Redirected restore from Windows server Redirected restore from Windows server to Linux NA
esc 38896 to Linux fails in 18.2 with path not found fails in Avamar Administrator.
in backup error.

Avamar Client Manager known issues

There are no known issues with Avamar Client Manager in this release.

Avamar Config Checker known issues

There are no known issues with Avamar Config Checker in this release.

Avamar Desktop/Laptop known issues

The following table lists the Avamar Desktop/Laptop known issues in this release:

Table 8. Avamar Desktop/Laptop known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
296558 esc Avamar does not support NIS This release of Avamar Desktop/Laptop no NA
31191 authentication with Avamar Desktop/ longer supports users with NIS login feature.
Laptop

File level restore client known problems and limitations

The following list describes file-level restore client known problems for this release of Avamar:

Table 9. File level restore client known problems and limitations

Bug number Problem statement Description Workaround
321697 esc FLR fails when esxi has configured FLR using esxi hostname failback method fails NA
37736 multiple network interfaces but the whole FLR process even if there is optimal
hostname connection unreachable. network route. This issue is observed when a proxy
connects to ESXi host and hostname connection
has an error. FLR fails because it does not support
selecting optimal network from route table.
280373 Issue when browsing a large number When browsing a folder with large number of files NA
of files with Internet Explorer (more than 40,000), Internet Explorer may take
more than 2 minutes to complete loading the page,
and is not responsive during the loading process.
The interim solution to this problem is to use
another browser, such as Chrome or FireFox.
304444 Files not cleaned up on target device When a workorder failure occurs during a file level NA
when workorder failure occurs during restore on Linux due to insufficient space on the
file level restore on Linux target device, the partially copied files do not get
cleaned up from the target device, which can result
in disk space issues. For example, if restoring 5 GB

10
Table 9. File level restore client known problems and limitations (continued)
Bug number Problem statement Description Workaround
of files and the target device has only 2 GB of free
space, the file level restore fails when the device
capacity is reached, but the 2 GB of already copied
files remain on the target device.

Restore operations fail when deselecting a few files from a folder containing 20,000
files
To workaround this issue, complete the following:
1. Use Apache Tomcat to enable Port 8543 which has an unlimited post size. Port 443 has a post size limit and causes restore
operations to fail from folders with 20,000 or more files.
2. Start the Data Protection Backup and Recovery File-Level Restore UI.
3. Browse to https://VMware_Backup_Appliance_Host:8543/flr.
4. Select the files that you are required to restore. Ensure that all the files in the folder are not selected.

Avamar Web Restore known issues

The following table lists the Avamar Web Restore known issues in this release:

Table 10. Avamar Web Restore known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
225311 Windows Explorer unzip does not After restoring multiple files with Web Restore in NA
display restored files Microsoft Windows, unzipping the compressed files with
Windows Explorer does not display the restored files.
Install and use the WinZip application to unzip and view
the files.
- Unable to log in using LDAP If "user-login-module=avamar" is set in the NA
in Web Restore with "user-login- ldap.properties file on the Avamar server, log in to
module=avamar" the Web Restore page using LDAP fails with the message,
Error initializing list of backups.

Data Domain system integration known issues

The following table lists the Data Domain system integration known issues in this release:

Table 11. Data Domain system integration known issues

Issue ID Subject/Functional area Description Workaround/Resolution
51085 New Bytes % displays 0% until When performing file system backups to a Data NA
backup is complete. Domain system, the New Bytes % field displays
0% until the backup completes.
53567 hfscheck fails after clients are When you remove clients from the /REPLICATE NA
removed from the /REPLICATE domain and the client backups are on a Data
domain and then re-replicated. Domain system, the garbage collection process
removes the replicated backup files from the
Data Domain system that is the replication
destination. If the client is then replicated to
the Data Domain system again, subsequent
hfschecks fail with a MSG_ERR_DDR_ERROR
error.

11
Table 11. Data Domain system integration known issues (continued)
Issue ID Subject/Functional area Description Workaround/Resolution
175640 Avamar cloud tiering does not Because of Data Domain issue 175640, the NA
support Data Domain Hardware HA Avamar cloud tiering solution does not support
in DDOS 6.0 Data Domain Hardware HA in DDOS 6.0. A patch
is available from Data Domain to resolve this
issue.
202755 Avamar backups exceeding 10 hours Any type of Avamar backup to Data Domain that NA
require minimum DDOS version exceeds 10 hours fails if the DDOS version is
6.1.1.5-581137 earlier than 6.1.1.5-581137. Ensure that all Data
Domain systems are updated to this version at a
minimum.
287264 Changing Data Domain system from When you configure a Data Domain system using NA
FQDN to IP results in error the FQDN of the Avamar server, and then update
the system to use the IP address instead, the
update fails with an error indicating "Failed to
connect to Data Domain system." Knowledgebase
article 503612 available on the Support page
provides more information.
288864 Avamar does not display the cloud If a backup is stored on the cloud tier, the NA
unit name for a backup that is Avamar UI displays Cloud as the storage location
stored on the cloud tier rather than the exact name of the cloud unit.
297904 Replication of Data Domain backups When you delete the Avamar client from NA
to target device does not occur the replication target device in the Avamar
immediately when Avamar client is Management Console UI, the replicated Data
deleted from the target device Domain backups on the device are set
to "expired." As a result, if you initiate
another replication before garbage collection has
completed on the target server, the Data Domain
backups will not be immediately replicated to the
target device.
If you want to replicate the backups immediately,
manually launch garbage collection on the target
server, and then restart the replication.

300657 Trigger group backup takes up to 3 With Data Domain Cloud Disaster Recovery (DD NA
minutes in CDR Advanced Mode Cloud DR) enabled and operating in Advanced
Mode, interactions between DD Cloud DR and
the Avamar server cause group backups to start
approximately 3 minutes after you trigger the
backup.
309261 Dual stack Data Domain system You cannot add a Data Domain system if an Remove the inaccessible
cannot be added when IPv4 address inaccessible IPv4 address point to the Data IPv4 address in the
is inaccessible Domain FQDN exists. DNS server, or modify
the IPv4 address to a
correct address so that
a successful connection
can be established.
309551 Unable to add Data Domain in a In a pure IPv6 environment, if dual stack (IPv4 Remove the IPv4 entry
pure IPv6 environment and IPv6) records exist on the Domain Name from the DNS.
Server (DNS), Avamar cannot add the Data
Domain system.

12
All backup clients and plug-ins known issues
The following table lists all backup clients and plug-ins known issues in this release:

Table 12. All backup clients and plug-ins known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
32873 Special ACLs are not supported The avtar process does not support backup or restore of NA
special UNIX and Linux ACLs such as setuid and setgid
bits, or mandatory file lock bits in newer versions of Linux.
52496 Cluster Configuration Tool fails to In a dual stack environment, when the Avamar server’s NA
activate virtual cluster clients in IPv6 address is used during configuration with the Avamar
dual stack environments Cluster Configuration Tool, the Cluster Configuration Tool
fails to correctly activate virtual cluster clients.
The interim solution to this problem is to use the Cluster
Configuration Tool to create the cluster client, but clear
the Bring the cluster client online and activate it with the
Avamar server checkbox. Then manually create the virtual
cluster client and with Avamar Administrator, and in Policy
Management, edit the client and select the Activated
checkbox in the Edit Client dialog box.

56606 Level 1 backup to Data Domain After a level 0 backup has been performed for a client NA
with over 16 critical disks may with more than 16 critical disks, cache file information for
default to level 0 one or more of the disks may no longer be available. The
subsequent level 1 backups are also performed as level 0.
297679 Manage Dataset for Source Data When creating a Dataset, under Source Data the File/ NA
option has discrepancies for MC Folder Path can only be added manually.
AUI
302911 Backup not supported for Avamar requires a Windows cluster to function as NA
SharePoint farms configured with designed. Configurations on clusterless architectures such
SQL clusterless AAG as SQL clusterless AAG are therefore not supported by
Avamar.

AIX, HP-UX, Linux, CentOS, and Solaris client known issues

The following table lists the AIX, HP-UX, Linux, CentOS, and Solaris client known issues in this release:

Table 13. AIX, HP-UX, Linux, CentOS, and Solaris client known issues
Issue ID Subject/Functional area Description Workaround/
Resolution
338194 Ownership of the files that were This action is as per the Linux Filesystem design. N/A
owned by root user would be
changed to the non-root user in
the new location, while restoring
to a different destination.
26077 Push upgrade on Linux fails for Using Avamar upgrade to push an Avamar client N/A
non-default installation location. 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.
249425 Unable to configure Linux Fast Linux Fast Incremental cannot be configured on N/A
Incremental at runlevel 5 in SUSE 12 file system that is protected at runlevel 5.
SUSE12. The interim solution to this problem is to configure
the file systems to be protected in run level 3.

13
Table 13. AIX, HP-UX, Linux, CentOS, and Solaris client known issues (continued)
Issue ID Subject/Functional area Description Workaround/
Resolution
307231 Limitations to avagent The following limitations apply to the avagent N/A
services on SLES 12 SP3 or service for Avamar on SuSE Enterprise Linux
later. (SLES) version 12 SP3 or later:
● You can only perform a manual stop and restart
the avagent service after running avregister.
● The avagent service does not start
automatically after a system restart. A manual
restart of avagent is required.
312367, 312368 SLES version 11 still appears in Several package names in Avamar 19.2, such N/A
some package names. as AvamarBundle and avinstaller-bootstrap, still
indicate SLES version 11 in the package name.
322219 Server is unable to detect plug- The following issues were observed with Oracle, Manually restart the
ins and backup, or restore jobs Sybase, DB2, SAP, and Lotus plug-ins for SLES12 avagent service.
are waiting for client. SP4 and SLES 15/15 SP1 platforms:
● Until you manually restart the avagent service,
the server is unable to detect the plug-ins.
● The backup/restore jobs are waiting for the
client until you manually restart the avagent
service.

Microsoft Exchange VSS plug-in known issues

The following table lists the Microsoft Exchange VSS plug-in known issues in this release:

Table 14. Microsoft Exchange VSS plug-in known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
Data Domain token Avamar release 7.5 introduced Data Domain token NA
authentication issue with clients authentication for the Microsoft application plug-
earlier than Avamar release 7.5 ins. Data Domain token-based authentication is not
supported for clients before release 7.5. The interim
solution to this problem is to upgrade the clients to
release 7.5, or to disable token-based authentication
on the Avamar server.
54465 Restore of an incremental backup If you restore a full backup of an Exchange database Rerun the restore and
fails after restoring a full backup and then you restore a subsequent incremental use the Move logs
backup of the database, the restore fails. path plug-in option
to move the existing
log files to a different
directory.

Microsoft Hyper-V VSS plug-in known issues

The following table lists the Microsoft Hyper-V VSS plug-in known issues in this release:

Table 15. Microsoft Hyper-V VSS plug-in known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
338344 Hyper-V Plug-in with Azure stack While performing restore operation on Hyper-V Plug- NA
HCI 21H2 may encounter issues in with Azure HCI stack 21H2, the Hyper-V GLR
during GLR restore operation. restore may face some issues.

14
Table 15. Microsoft Hyper-V VSS plug-in known issues (continued)
Issue ID Subject/Functional area Description Workaround/
Resolution
Data Domain token authentication Avamar release 7.5 introduced Data Domain token NA
issue with clients earlier than authentication for the Microsoft application plug-
Avamar release 7.5 ins. Data Domain token-based authentication is not
supported for clients before release 7.5. The interim
solution to this problem is to upgrade the clients to
release 7.5, or to disable token-based authentication
on the Avamar server.
274173 Command-line interface restores Restore operations from the command-line interface NA
from backups on Cloud fail for do not work for Microsoft application plug-ins (SQL,
Microsoft application plug-ins SharePoint, Exchange, Hyper-V) when the backup
resides in the Cloud.
For these restore operations, use the Avamar
Management Console's Avamar Administrator
window.

290914 Logfile option cannot be used When performing backups for Microsoft application NA
for Hyper-V, SharePoint, and plug-ins including Hyper-V, SharePoint, and
Exchange backups to specify Exchange, you cannot use the logfile option
an alternate path for log file to specify an alternate file path location for the
generation generated log files. Logs can only be generated in
the default path, C:\Program Files\avs\var\.
313896 [Windows 2019]For SMB VMs RCT Whenever we have VMs hosted on secondary nodes NA
Incremental backup fails for vms or remote nodes(passive nodes) other than the
hosted on remote nodes(passive primary node the incremental backups fail with
nodes) unable to get the RCT extents error.
322762 esc Avamar Config checker is unable Avamar Config Checker fails to get the version of NA
38247 to get the integration services Integration Services for VMs hosted on Hyper-V
version for Hyper-V VM in Hyper-V 2016/2019 nodes.
2016/2019 environment.
323821 [Windows 2019]AV-Hyper-V VSS VSS synthetic full original location restores and NA
Synthetic full restores fail with redirected-restores fail with error: Hyper-V VSS
an error: Hyper-V VSS Writer Writer failed in Post-Restore event
failed in Post-Restore on Windows 2019 S2D and on Windows
event on Windows 2019 S2D 2019. For Windows 2019, RCT workflow is
and on Windows 2019 recommended.
324145 [Windows 2019] AV-Hyper-V VSS VSS redirected restores fail with error: Hyper- NA
redirected restores fail with an V VSS Writer failed in Post-Restore
error: Hyper-V VSS Writer event on Windows 2019 S2D and on
failed in Post-Restore Windows 2019. For Windows 2019, RCT workflow
event on Windows 2019 S2D is recommended.
and on Windows 2019

Microsoft SharePoint VSS plug-in known issues

The following table lists the Microsoft SharePoint VSS plug-in known issues in this release:

Table 16. Microsoft SharePoint VSS plug-in known issues

Issue ID Subject/Functional area Description Workaround/Resolution
Data Domain token Avamar release 7.5 introduced Data Domain token NA
authentication issue with authentication for the Microsoft application plug-
clients earlier than Avamar ins. Data Domain token-based authentication is
release 7.5 not supported for clients before release 7.5. The
interim solution to this problem is to upgrade the

15
Table 16. Microsoft SharePoint VSS plug-in known issues (continued)
Issue ID Subject/Functional area Description Workaround/Resolution
clients to release 7.5, or to disable token-based
authentication on the Avamar server.
54465 Restore of an incremental If you restore a full backup of an Exchange Rerun the restore and
backup fails after restoring database and then you restore a subsequent use the Move logs path
a full backup incremental backup of the database, the restore plug-in option to move
fails. the existing log files to a
different directory.
246462 Granular Level Recovery SharePoint GLR may fail with the following error: Ensure that the latest
on SharePoint 2007 with Invalid mount letter, most likely updates for Windows
Windows 2008 R2 fails caused by AvFS mount failure. 2008 R2 have been
when most recent Windows installed.
update is not installed

Microsoft SQL Server plug-in known issues

The following table lists the Microsoft SQL Server plug-in known issues in this release:

Table 17. Microsoft SQL Server plug-in known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
337342 TLR Mount failure error When TLR is performed on Windows Server Add
2022, user might experience TLR Mount failure the --storage-
with 'mount_media throw ECBFS error' type=stDisk,--
largeprefetch=0
and --
smallprefetch=0
flags in
axionfs.cmd file
and save the file in
AV var folder to stop
the mount failure.
- Redirected restores fail when Redirected restore using the Restore to N/A
location is set in Restore different SQL server instance or location
Options dialog box. option fails when the location is set using the
Set Destination field in Restore Options dialog
box. To work around this issue, set path on the
Restore Command Line options page.
Data Domain token Avamar release 7.5 introduced Data Domain N/A
authentication issue with token authentication for the Microsoft
clients earlier than Avamar application plug-ins. Data Domain token-based
release 7.5 authentication is not supported for clients
before release 7.5. The interim solution to this
problem is to upgrade the clients to release 7.5,
or to disable token-based authentication on the
Avamar server.
49416 Restore of differential backup After a database is removed from an availability N/A
after database is removed from group, restores from differential backups of the
availability group may fail. database might fail.
54465 Restore of an incremental If you restore a full backup of a SQL database Rerun the restore
backup fails after restoring a and then you restore a subsequent incremental and use the Move
full backup. backup of the database, the restore fails. logs path plug-in
option to move the
existing log files to a
different directory.

16
SQL AAG configuration
In SQL AAG configuration, incremental backups on a secondary node may get promoted to full if SQL server takes time to
update LSN inside msdb during previous incremental backup on secondary.

Microsoft Windows client known issues

The following table lists the Microsoft Windows client known issues in this release:

Table 18. Microsoft Windows client known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
52801 File size discrepancy for NTFS For Windows NTFS file system backups, the displayed NA
backups file size of an L0 backup is different than the size
displayed for subsequent backups. This problem is a
statistical error that is displayed in both the Avamar
Administrator and log files, and does not reflect any
actual difference between the size of the files in the
backups.
273212 Cluster Shared Volume that is not a If a Cluster Shared Volume (CSV) is not part of NA
part of any role cannot be backed up any role, the Avamar system cannot back up the
volume. It is not available to be selected in the Avamar
Administrator under Windows Cluster File server nor
under Windows File System.
273991 Issue with restore of a Windows 2016 Because of an issue with Windows 2016, during restore NA
volume that does not support short of a Windows 2016 volume that does not support short
names (8.3) names, folders, and files are restored using the
short name and no warning is specified.

NDMP accelerator node known issues

The following table lists the NDMP accelerator node known issues in this release:

Table 19. NDMP accelerator node known issues

Issue ID Subject/Functional area Description Workaround/Resolution
- Push upgrade to Avamar Push upgrade of the NDMP accelerator node Perform a manual upgrade of
release 7.3 Service Pack 1 or from Avamar release 7.3 or earlier to Avamar the NDMP accelerator node.
newer is not supported release 7.3 Service Pack 1 or newer is not
supported.
60389 Capacity issues occur when When you enable snapshot-based incremental Upgrade OneFS to a release
Isilon fails to delete snapshots backups for one or more directories on an that contains the fix, or
for incremental backups Isilon system, OneFS does not delete the perform the steps in the
snapshots after incremental backups occur. Dell Isilon OneFS Backup
Snapshot-based incremental backups are also and Recovery Guide to view
known as the Faster Incrementals feature. The and delete snapshots for
accumulation of snapshots can result in capacity snapshot-based incremental
issues on the Isilon system. This issue is known backups.
in OneFS that is fixed in OneFS release 7.1.1.3 or
higher and 7.2.0.2 and higher.

17
Oracle database plug-in known issues
The following table lists the Oracle database plug-in known issues in this release:

Table 20. Oracle database plug-in known issues

Issue ID Subject/Functional area Description Workaround/Resolution
48182 RMAN CLI backups with RMAN CLI backups with Oracle RAC configuration do not NA
Oracle RAC configuration reflect the scan name in the Activity window. The interim
do not reflect the scan solution for this problem is to copy $ORACLE_RAC_VAR/
name in Activity window avoracle.cmd to $ORACLE_RAC_VAR/clientlogs/
avoracle.cmd.
273929 Best practices for Oracle When a cloud tiering policy is configured for Avamar plug- The best practice to
and Lotus plug-ins ins for Oracle and Lotus, an earlier Full/L0 backup that avoid this issue is to
to avoid issues with is performed through the plug-in may already have been select a Full/L0 backup
incremental backup when moved to the cloud tier. If this problem is the case, interval that is smaller
using a cloud tier subsequent incremental/L1 backups do not complete, than the age threshold
because no parent full/L0 backup is found on the active configured for moving
tier. backups to cloud tier.
This step guarantees that
For the Oracle plug-in, if this issue is encountered, the
the last Full/L0 backup
following error message is written to the plug-in log
is always available in the
and the incremental backup fails: An incremental
Active tier. For Oracle and
backup was requested but there is no
Lotus plugins, after the
previous full backup. Please perform a
incremental backup failure,
full backup before any subsequent full
you can either recall the
backups.
last Full/L0 backup from
For the Lotus plug-in, the following error message is the cloud tier, or perform a
written to the plug-in log and the incremental backup fails: new Full/L0 backup instead
No Full backup found, Incremental backups of the incremental. Then
cannot be taken without a full backup subsequent incremental
backups complete
successfully.
277013 Data Domain On Windows systems, when the Avamar Plug-in for NA
authentication problem Oracle does not have sufficient rights to the <install-
when Avamar Plug-in for dir>\avs\etc\.tmp directory, the Data Domain is
Oracle installation has unable to write its authentication certificate to the
insufficient rights directory, and backups fail. Interim solutions to this
problem are:
● To allow full file access to the oracle user, manually
change the privilege of the .tmp directory.
● Install the Avamar Plug-in for Oracle in a location that
the Oracle user has full file access.
● Disable user authentication on the Windows host.
281689 Known problem in Oracle, When a backup is initiated from the Avamar Administrator NA
DB2, and Sybase plug-in and fails in the late stages of the backup operation, it is
for snapview failures possible that the plug-in application considers the backup
to be successful. You cannot perform a restore operation
on this backup from Avamar Administrator. Restoring such
a backup might still be possible by using a command-line
restore. This step is documented as a supported operation
in the Oracle Plug-in user guide.
How to identify the issue:
1. The database reports the backup as successful,
although the Avamar Administrator reports it as failed.
2. Failed backup log messages include an error message
that is generated during the late stages of the backup.
For the Avamar Plug-in for Oracle, DB2, and Sybase
ASE, the failure is logged with the error message

18
Table 20. Oracle database plug-in known issues (continued)
Issue ID Subject/Functional area Description Workaround/Resolution
Failed to create the snapview. However,
the database data has been successfully
backed up and is marked as a hidden
backup. Restore is available through
CLI only. See the plug-in documentation
for information about restoring hidden
backups.

NOTE: Best practice is to monitor all backup failures

and ensure that such cases are followed with a
successful full backup. This step requires that you
create a successful full backup after any failed backup
event.

283392 Running two RMAN When two concurrent backup sessions are initiated on the NA
backups on same same database by using Oracle RMAN CLI by using a task
database results in file (for monitoring through the Avamar Administrator),
unexpected results one of the backups may fail. The following error message
displays on the CLI:

RMAN-03009: failure of backup command

on
c2 channel at 06/06/2017 11:32:25
ORA-19506: failed to create
sequential file,
name="ORCL_7us64227_1_1", parms=""
ORA-27028:
skgfqcre: sbtbackup returned error
ORA-19511: Error received from
media manager layer, error text:
(UTF-8) sbtbackup: aborted!!

Concurrent Oracle RMAN backups using a task file on the

same database are currently not supported. Instead, run
RMAN database backups using a task file, but archive logs
or any other backup for the same database without using
a task file.

293174 In Windows, backup Ensure that the Avamar Plug-in for Oracle software If the Avamar Plug-in
might fail if Oracle is is installed outside of the default path C:\Program for Oracle software
installed with the New Files\avs. was installed in the
Windows User and the default path, C:\Program
Avamar plug-in for Oracle Files\avs, perform
software that is installed either of the following
in the default path steps to prevent
authentication issues which
might cause backups to
fail:
● Manually change the
privilege of
C:\Program
Files\avs\etc\.tm
p to give the Oracle
user full control.
● Disable the
authentication.

19
IBM DB2 plug-in known issues
The following table lists the IBM DB2 plug-in known issues in this release:

Table 21. IBM DB2 plug-in known issues

Issue ID Subject/Functional area Description Workaround/Resolution
286466 Known problem in Oracle, When a backup is initiated from the Avamar NOTE: Best practice is to
DB2, and Sybase plug-in for Administrator and fails in the late stages monitor all backup failures
snapview failures of the backup operation, it is possible that and ensure that such
the plug-in application considers the backup cases are followed with
to be successful. You cannot perform a
a successful full backup.
restore operation on this backup from Avamar
Administrator. Restoring such a backup might still This step requires that
be possible by using a command line restore. This you create a successful
step is documented as a supported operation in full backup after any failed
the DB2 Plug-in user guide. backup event.
How to identify the issue:
1. The database reports the backup
as successful, although the Avamar
Administrator reports it as failed.
2. Failed backup log messages include an error
message that is generated during the late
stages of the backup.
For the Avamar Plug-in for Oracle, DB2,
and Sybase ASE, the failure is logged
with the error message Failed to
create the snapview. However,
the database data has been
successfully backed up and is
marked as a hidden backup.
Restore is available through
CLI only. See the plug-in
documentation for information
about restoring hidden backups.

289136 For consecutive Avamar DB2 When two consecutive Avamar DB2 (avdb2) As a best practice, do not
restores, the second restore restores are initiated and the second database start the second database
within the new connection restore starts before the previous restore is restore until the first restore
timeout period might fail complete, the second database restore within the has completed successfully.
new connection timeout period might fail, with Also, before issuing the
the following error displayed in the CLI and the second DB2 database restore
DB2 diagnostic log file db2diag: command, ensure that there
are no avdb2 processes
SQL2062N An error occurred while currently running on the
accessing media "VENDOR". system. If the previous
database restore operation is
taking longer than expected,
ensure that a sufficiently high
value has been set for the flag
--timeout-new-connection.

20
SAP with Oracle plug-in known issues
The following table lists the SAP with Oracle plug-in known issues in this release:

Table 22. SAP with Oracle plug-in known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
51870 Oracle Optimized Deduplication When backing up an SAP with Oracle database to NA
option is not supported with Data a Data Domain system, the Oracle Optimized
Domain Deduplication option is not supported.

Sybase ASE plug-in known issues

The following table lists the Sybase ASE plug-in known issues in this release:

Table 23. Sybase ASE plug-in known issues

Issue ID Subject/Functional Description Workaround/Resolution
area
286467 Known problem in When a backup is initiated from the Avamar NOTE: Best practice is to
Oracle, DB2, and Administrator and fails in the late stages of the monitor all backup failures
Sybase plug-in for backup operation, it is possible that the plug-in and ensure that such
snapview failures application considers the backup to be successful. cases are followed with
You cannot perform a restore operation on this
a successful full backup.
backup from Avamar Administrator. Restoring such
a backup, though not possible through the Avamar This step requires that
Administrator, may still be possible by using a you create a successful
command line restore. This step is documented as full backup after any failed
a supported operation in the Sybase Plug-in user backup event.
guides.
How to identify the issue:
1. The database reports the backup as successful,
although the Avamar Administrator reports it as
failed.
2. Failed backup log messages include an error
message that is generated during the late stages
of the backup.
● For the Avamar Plug-in for Oracle, DB2, and
Sybase ASE, the failure is logged with the
error message: Failed to create the
snapview. However, the database
data has been successfully backed
up and is marked as a hidden
backup. Restore is available
through CLI only. See the plug-
in documentation for information
about restoring hidden backups.
● In the case of an incremental backup,
the failure is logged with the error
message: If a transaction log
truncation was performed during
an incremental backup of a
Sybase database with the data
and log on separate devices,
the transaction log is now at
risk of being lost. Perform an
immediate full backup of the
impacted database to protect the

21
Table 23. Sybase ASE plug-in known issues
Issue ID Subject/Functional Description Workaround/Resolution
area
data. Consult the Avamar Plug-in
for Sybase documentation for more
information.

IBM Lotus Domino plug-in known issues

The following table lists the IBM Lotus Domino plug-in known issues in this release:

Table 24. IBM Lotus Domino plug-in known issues

Issue ID Subject/Functional area Description Workaround/Resolution
239003 Server field in Activity window The Server field in the Activity windows NA
is blank for the CLI restore is blank for restore operations that are
operation performed on the command line.
273929 Best practices for Oracle and When a cloud tiering policy is configured The best practice to avoid
Lotus plug-ins to avoid issues for Avamar plug-ins for Oracle and Lotus, this issue is to select a
with incremental backup when an earlier Full/L0 backup that is performed Full/L0 backup interval that is
using a cloud tier through the plug-in may already have been smaller than the age threshold
moved to the cloud tier. If this problem configured for moving backups
is the case, subsequent incremental/L1 to cloud tier. This step
backups do not complete, because no guarantees that the last
parent full/L0 backup is found on the Full/L0 backup is always
active tier. available in the Active tier. For
Oracle and Lotus plugins, after
For the Oracle plug-in, if this issue
the incremental backup failure,
is encountered, the following error
you can either recall the
message is written to the plug-in
last Full/L0 backup from the
log and the incremental backup fails:
cloud tier, or perform a new
An incremental backup was
Full/L0 backup instead of the
requested but there is no
incremental. Then subsequent
previous full backup. Please
incremental backups complete
perform a full backup before
successfully.
any subsequent full backups.
For the Lotus plug-in, the following error
message is written to the plug-in log
and the incremental backup fails: No
Full backup found, Incremental
backups cannot be taken without
a full backup

305687 Avlotus backups complete On the Lotus plug-in for some AIX systems, NA
successfully but report a backup is displayed as completed with
"[AvlotusMonitorCancel]INTERN errors, even when the backup is successful
ALERROR: <0001>assert error" and available for recovery, due to an
assertion failure that occurs while unlocking
a mutex at the end of the backup. This
error can be ignored.
314742 Domino plug-in cannot restore The Avamar Plug-in for Lotus Domino is Ensure that the DAOS folder
NLO file with overwrite option unable to restore an individual NLO file name in the NLO path is in ALL
selected when the overwrite option is selected due CAPS.
to case-sensitive path comparison for the
NLO path.

22
Replication known issues
The following table lists the replication known issues in this release:

Table 25. Replication known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
192169 Incorrect statistics appear When you replicate Avamar backup data from one Data NA
for replication of Avamar Domain system to another Data Domain system, incorrect
backup data on a Data statistics appear for:
Domain system ● The file total in the avtar log file.
● The progress bytes in the Activity Monitor in Avamar
Administrator.
262220 Invalid certificate after Reconfiguring the destination server for replication NA
upgrading and reconfiguring fails with the following an error message under the
a replication destination following conditions:Could not log in to remote
server destination. Check credentials and hostname
or IP. Authentication failed.
● After a replication is performed from a source Avamar
server to a destination Avamar server that uses
certification-based authentication.
● Upgrading the destination server to a new version of
Avamar.
● Deleting the replication configuration.
The interim solution for this problem is to issue the following
commands at the source server:

rm -rf /usr/local/avamar/etc/<destination
server IP>
rm -rf /usr/local/avamar/etc/client/
<destination server IP>

277208 Check for Remote backups During replication, when the Check for Remote backups NA
before deletion not working before deletion option is selected, the server deletes the
replication destination record even if remote backups exist on
the replication destination system.
309113 Replication job that is If a replication job is canceled after being partially created on NA
canceled after partial the destination system, or completes with an exception, the
creation or completes with status of the job displays as VALID in the Asset Management
an exception displays as window of the AUI, with no warning to indicate that any issue
VALID in the AUI occurred.
309388 Restore of replicated You cannot perform a restore of a replicated backup when the NA
backups fails when source system with the Avamar source backup and the destination
and destination Avamar system for the restore are attached to the same Data Domain.
system that is attached to
the same Data Domain
309501 Replication status was failed Due to a timeout that occurs when there are 5000 or more NA
at Avamar destination but clients in a domain, the destination system for a replication
replication was actually displays the replication job as "Failed" even though the job
successful was actually completed successfully, as indicated on the
source.
309624 Replication fails if both IPV4 Replication to the Avamar destination in a pure IPv6 Remove the IPv4
and IPv6 records exist in the environment (where both IPv4 and IPv6 records exist in entry from the
DNS server for the Avamar the DNS server but IPv4 is not configured) fails, with an DNS.
destination error message in the Activity logs of Avamar Administrator
indicating "Unable to connect to the IPv4 address of the
Destination Avamar."

23
Avamar Data Migration Enabler (ADMe) known issues
The following table lists the ADMe known issues in this release:

Table 26. Avamar Data Migration Enabler known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
253574 Staging and tape out Due to a known limitation with the ADMe software, staging NA
of Sybase backups not and tape out of backups that are created with the Sybase
supported plug-in is not supported in this release.

Upgrade known issues

The following table lists the upgrade known issues in this release:

Table 27. Upgrade known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
327044 The pre-installed and post-installed os- When upgrading from 19.4.0-68 to 19.4.0-114 on NA
rollup survey results.xml must Gen4T multiple node, rollup-2020-R3-v4 can be
be copied into data node. installed on both utility nodes and data nodes.
But only utility node has the pre-installed post-
installed os-rollup survey results.xml.
All data nodes have dont have os-rollup
survey results.xml.

VMware known issues

The following table lists the VMware known issues in this release:

Table 28. VMware known issues

Issue ID Subject/Functional area Description Workaround/
Resolution
337008 Proxy recommendation When you install OS rollup 2022-R3-v4 on a new ADS See the section "Obtain
fails to start and throws server, the permission of some of the web application proxy recommendation"
an internal error in the directories change, which results in the failure of in the Avamar
AUI. redeployment of these directories. As a result, the proxy Administration Guide
recommendation fails to start and throws an error in the for details on the
AUI. workaround.
esc 34477 Domain user not For non-Windows platforms, you cannot perform file-level NA
supported for file-level restore of a virtual machine backup as a Domain user. The
restore of virtual user can be part of the Standard or Administrators group.
machine backup
- Exclude the proxy from Including the Avamar proxy in a backup consumes a large NA
the virtual machine amount of space. When using other VMware software
backup if performing instead of the Avamar software to perform the virtual
the backup with other machine backup, it is recommended that you exclude the
VMware software proxy virtual machine from the backup.
- Adding vCenter as IPv6 When you register or add a VMware vCenter client to NA
address is not supported, Avamar, ensure that you specify the fully qualified domain
use FQDN instead name (FQDN) of the vCenter. Using the IPv6 address is
not supported
- HotAdd mode does not Due to a known limitation with VMware, documented in NA
work with a VSAN disk the VDDK 6.0.1 release notes regarding vSAN 6.1, ESXi
hosts do not allow HotAdd of a vSAN disk on a proxy

24
Table 28. VMware known issues (continued)
Issue ID Subject/Functional area Description Workaround/
Resolution
virtual machine with datastore types other than vSAN. As
a result, in a vSAN 6.1 environment, attempts to hotadd a
VMDK vSAN datastore by a proxy residing outside vSAN
fails. If hotadd mode is desired, host the proxy on the
vSAN datastore.
248502 Support for validation of When using the mccli backup validate, validation NA
VMware image backup in is scheduled but the activity is in waiting-client state. The
MCCLI is limited --dest-client-name and --dest-client-domain
options are not currently supported when validating a
non /REPLICATE client backup.
248775 Proxy running on non The virtual machine proxy can get abruptly powered off NA
PDL datastore is getting if the proxy is engaged in a hotadd backup of a VMCP-
powered off during a enabled virtual machine, in the event of a permanent
PDL of virtual machine device loss of the virtual machine datastore. This problem
datastore might occur due to HA attempting to restart the proxy
virtual machine, as it would have mounted the VMDK of
the virtual machine.
The interim solution to this problem is to ensure that the
next schedule starts correctly, which manually removes
all the hotadd disks from the Avamar proxy, and power
it back on. A snapshot consolidation may also be required
for the virtual machine.

263450 File-level restore not Avamar does not support the use of GPT/EFI drives on NA
supported for GPT/EFI Windows 2012 for file-level restore operations when the
drives on Windows 2012 drive has been edited by a disk tool from a third party
when drive has been software vendor. Before mounting the drive for file-level
edited by third party disk restore, verify that all the disks on the virtual machine
tool have valid/supported partitions.
278280 Instant Access that is Instant Access restores are not supported for data that is NA
not supported with cloud migrated to the cloud using the cloud tiering feature.
tiering
282640 Restoring a remote Restoring a remote backup fails when the restore is to NA
backup fails when the a specific ESXi that is different from the original ESXi
restore is to a specific server. The interim solutions to this problem are:
ESXi that is different ● If a local backup exists, restore the local backup to the
from the original ESXi specific ESXi.
server ● If a local backup does not exist, and the original ESXi
is running, restore the remote backup to original ESXi
and then restore the remote backup to the specific
ESXi.
Use the avrepl command to replicate the remote
backup to the source Avamar when the following occurs:
● A local backup does not exist.
● The original ESXi is not running.
Restore the local backup to the specific ESXi:

avrepl --[replscript]restore=true
--operation=replicate --
[replscript]dstaddr=SRC_ADDR
--[replscript]dstid=repluser
--dstpassword=Chang3M3Now.
--ap=Chang3M3Now. --
[replscript]dpnname=SRC_ADDR
--[replscript]dstencrypt=tls /
REPLICATE/CLIENTPATH

25
Table 28. VMware known issues (continued)
Issue ID Subject/Functional area Description Workaround/
Resolution

Where SRC_ADDR is the IP address of the source

Avamar server and CLIENTPATH is the client path. If
CLIENTPATH is a domain, instead of a path, it moves all
the clients' backups under the domain.

290464 esc BMR fails When performing bare metal recovery (BMR) to a virtual The following
29814 machine with VMware hardware version 11, the following workarounds apply:
problems might occur: ● Restore the system
● WinPE cannot find a virtual disk. backup to a
● The restored virtual machine will not boot. virtual machine with
VMware hardware
version 8 or 9.
● Ensure the hardware
configuration of
the target host
is the same
as the hardware
configuration of the
source host.
291803 When logged in as Local Due to the introduction of User Account Control (UAC) On the guest operating
user with administrator in Microsoft Windows 7 and later versions, when logged system, turn off Admin
role, Advanced Policy in as a Local user with the administrator role, the Approval Mode in the
Builder fails to install/ Advanced Policy Builder fails to install/upgrade/register UAC settings for the
upgrade/register client client agents on SQL virtual machines. admin group.
agents on SQL Virtual
machines
292446 During a restore, If a virtual machine with the Active Directory role is Perform the following
the virtual machine restored by using the Avamar backup data loss might workaround:
Generation ID might not occur as a result of a USN rollback. In this scenario, 1. Restore the virtual
increment which might the restored virtual machine retains the same virtual machine from the
cause data loss GenerationID as the source virtual machine. backup.
2. Do not start the
virtual machine.
3. Take a snapshot of
the virtual machine
by using VMware.
4. Revert the virtual
machine to the
snapshot.
5. Start the virtual
machine.
293950 Virtual machine client After a vCenter high availability fail-over, virtual machine If this issue occurs,
jobs in waiting, failed or client jobs that were in a waiting, failed or canceled state restart the Avamar
canceled state might not before the fail-over might not be restarted by the Avamar Management Console
get restarted after fail- Management Console. services.
over
300223 If a rule is not created to PDM registration fails and the following error message When using rule-based
exclude proxy VMs when appears if a rule is not created to exclude proxy protection, create a rule
rule-based protection is VMs when rule-based protection is used: Could not to exclude proxy VMs.
used, PDM registration register proxy: invalid domain
fails
307561 Image-level virtual Performance issues are observed when performing NA
machine restore for 1400 or more image-level virtual machine restores
a very large (1400+) simultaneously.
number of virtual

26
Table 28. VMware known issues (continued)
Issue ID Subject/Functional area Description Workaround/
Resolution
machines simultaneously
is not supported
309541 Limitations to vCenter Note the following limitations that are related to support Perform the following
High Availability for vCenter High Availability (VCHA): workaround
● If the proxy is not available after the VCHA event, a 1. Bring the proxy
restart order gets issues for all failed/restarted jobs, back online, and
which will not complete because the proxy is not then perform an
available. on-demand backup
● If Hot Add transport mode is used for the virtual disks with the same
and the proxy fails, all the associated clients with Hot proxy. Disks are
Add disks in the proxy fail, and a new backup cannot consolidated and the
be performed. backups proceed.
2. Manually remove all
Hot Add disks from
the proxy.
309934 Jetty service continues When you run the service jetty stop command to Stop the back-end jetty
to run in proxy virtual stop the jetty service in the proxy virtual machine, the process manually.
machine after stop back-end process continues to run.
command
319308 Backup failed in Avamar In Avamar release 19.3, Virtual Machine backup is not NA
19.3 with VMC 1.10 supported with VMware VMC 1.10 release.
319375 Backup failed in Avamar In Avamar release 19.3, Virtual Machine backup is not NA
19.3 with VMC 1.9 supported with VMware VMC 1.9 release.
319482 Virtual Machine image Virtual Machine image restore to a different existing VM is NA
restore to a different not supported.
existing VM is not
supported.
320131 vddk errors are seen vddk error during VM Image backup and restore NA
for successful VM Image "Error while loading feature config file: /etc/vmware/
backup and restores vsphereFeatures/vsphereFeatures.cfg, using
default feature state values". This is treated as warning
message from proxy perspective and safe to ignore.

Supportability package known issues

The following table lists the Avamar supportability package known issues in this release:

Table 29. Supportability package known issues

Issue ID Subject/Functional area Description Workaround/Resolution
33892 Unnecessary Upgrade Client The Upgrade Client Downloads package presents a Do not select Show
Downloads package option Show advanced settings option on the installation advanced settings on the
page called skip upgrading client download rpms. installation page.
If you select the Values check box and click
Continue, client downloads are not upgraded on
the system and the package no longer appears in
Avamar Installation Manager.
If you clear the Values check box and click
Continue, the client downloads upgrade works as
designed.

27
Avamar plug-in for vSphere Web Client configuration application
known issues
There are no known issues with Avamar plug-in for vSphere Web Client configuration application in this release:

Environment and system requirements

The following sections describe specific environment and system requirements that are associated with this release of Avamar.

Client, server, and platform compatibility

Updated and detailed client, sever, and platform compatibility information is available in E-LAB Navigator at https://
elabnavigator.dell.com/eln/elnhome.

Client hardware requirements

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

Avamar Downloader Service operating system requirements

Beginning with release 7.3, the Avamar Downloader Service is now available on the Avamar utility node or single-server node.
The Windows-based legacy Avamar Downloader Service is also supported and is available on the following Windows platforms:
● Windows Server 2019
● Windows Server 2016
● Windows 10
● Windows Server 2012 (64-bit only)
● Windows Server 2008 R2
● Windows 8
● Windows 7 SP1
The Avamar Administration Guide provides a list of supported operating systems for the Avamar Downloader Service.

Data Domain system requirements

Updated, detailed, supported DD OS and DD Boost version information is available in the E-LAB Navigator at https://
elabnavigator.dell.com/eln/elnhome.

International language support

The following sections provide important information about international language support in Avamar:

International language support in Windows environments

Supported languages for Windows environments include:

● Arabic ● Japanese
● Bulgarian ● Korean
● Chinese (Simplified and Traditional) ● Latvian

28
● Croatian ● Lithuanian
● Czech ● Norwegian
● Danish ● Polish
● Dutch ● Portuguese (Brazilian)
● Estonian ● Romanian
● Finnish ● Russian
● French ● Slovak
● German ● Slovenian
● Greek ● Spanish (Iberian and Latin American)
● Hebrew ● Swedish
● Hungarian ● Turkish
● Italian

Table 30. Windows environment international language support

Windows data type International language support details

Windows files and folders You can back up and restore individual files and folders with file and folder names
in local languages.
File and folders names appear in the local language in Avamar Administrator and
Avamar Web Restore.

Microsoft Exchange databases You can back up and restore databases with the database name in supported local
languages.

Microsoft Exchange folders and messages You can back up and restore individual folders and messages with the folder or
message name in supported local languages.

Microsoft SQL Server databases You can back up and restore databases with the database name in supported local
languages.

International language support in UNIX/Linux environments

Supported languages for UNIX and Linux environments include:

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

Table 31. Windows environment international language support

Encoding International language support details

EUC-JP You can back up and recover EUC-JP encoded files and directories with names in the Japanese
language on Solaris.

29
Table 31. Windows environment international language support (continued)
Encoding International language support details

NOTE: EUC-JP encoded file and directory names do not render correctly in either Avamar
Administrator or Avamar Web Restore. This issue does not apply to the client web UI available
through Avamar Desktop/Laptop.

UTF You can back up and restore individual UTF-encoded files and directories with file and directory names
in supported local languages.
File and directory names appear in the local language in Avamar Administrator and Avamar Web
Restore.

Known limitations of local language support

Consider the following known limitations of local language support:
● Cross-platform redirected restore of files and directories with international character set names is not supported.
● 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) must consist entirely of
ASCII characters.
● Log files do not correctly render non-ASCII characters.
● Error, warning, and informational messages incorrectly render non-ASCII characters, both to the screen and to log files.
● Log files which are based on user-defined names (for example, database names) do not work correctly.
● You cannot use non-ASCII characters in options and flags. If a flag or option takes a file, folder, or identifier (for example, a
database name), then that option is only assured to work for ASCII names.
● Sorting is not localized. Sorting is strictly by byte-ordinal value.
● You cannot type local language characters in the Avamar user interface using a keyboard.
● The Avamar Management Console Command Line Interface (MCCLI) and avtar support only ASCII arguments on the
command line.

Restore international characters with Avamar Web Restore

The Avamar Web Restore feature restores directories or multiple files in the form of a Zip file. When you unzip the Zip file, file
and directory names with international characters might not restore correctly due to inherent limitations in some Zip utilities.
To correctly restore files with international characters by using the Avamar Web Restore feature, use a Zip utility that supports
international characters. Examples are:
● Winrar 3.80 or later
● Winzip 12.0 or later
● 7zip 4.65 or later
Do not use Microsoft Windows compressed folders with the Avamar Web Restore feature. These compressed folders do not
reliably handle international characters.

Support for non-UTF8 locales in the Management Console

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

Big5 Big5-HKSCS COMPOUND_TEXT

EUC-JP EUC-KR GB18030
GB2312 GBK IBM-Thai
IBM00858 IBM01140 IBM01141
IBM01142 IBM01143 IBM01144

30
IBM01145 IBM01146 IBM01147
IBM01148 IBM01149 IBM037
IBM1026 IBM1047 IBM273
IBM277 IBM278 IBM280
IBM284 IBM285 IBM297
IBM420 IBM424 IBM437
IBM500 IBM775 IBM850
IBM852 IBM855 IBM857
IBM860 IBM861 IBM862
IBM863 IBM864 IBM865
IBM866 IBM868 IBM869
IBM870 IBM871 IBM918
ISO-2022-CN ISO-2022-JP ISO-2022-JP-2
ISO-2022-KR ISO-8859-1 ISO-8859-13
ISO-8859-15 ISO-8859-2 ISO-8859-3
ISO-8859-4 ISO-8859-5 ISO-8859-6
ISO-8859-7 ISO-8859-8 ISO-8859-9
JIS_X0201 JIS_X0212-1990 KOI8-R
KOI8-U Shift_JIS TIS-620
US-ASCII UTF-16 UTF-16BE
UTF-16LE UTF-32 UTF-32BE
UTF-32LE UTF-8 windows-1250
windows-1251 windows-1252 windows-1253
windows-1254 windows-1255 windows-1256
windows-1257 windows-1258 windows-31j
x-Big5-Solaris x-euc-jp-linux x-EUC-TW
x-eucJP-Open x-IBM1006 x-IBM1025
x-IBM1046 x-IBM1097 x-IBM1098
x-IBM1112 x-IBM1122 x-IBM1123
x-IBM1124 x-IBM1381 x-IBM1383
x-IBM33722 x-IBM737 x-IBM834
x-IBM856 x-IBM874 x-IBM875
x-IBM921 x-IBM922 x-IBM930
x-IBM933 x-IBM935 x-IBM937
x-IBM939 x-IBM942 x-IBM942C
x-IBM943 x-IBM943C x-IBM948
x-IBM949 x-IBM949C x-IBM950
x-IBM964 x-IBM970 x-ISCII91
x-ISO-2022-CN-CNS x-ISO-2022-CN-GB x-iso-8859-11
x-JIS0208 x-JISAutoDetect x-Johab
x-MacArabic x-MacCentralEurope x-MacCroatian

31
x-MacCyrillic x-MacDingbat x-MacGreek
x-MacHebrew x-MacIceland x-MacRoman
x-MacRomania x-MacSymbol x-MacThai
x-MacTurkish x-MacUkraine x-MS932_0213
x-MS950-HKSCS x-mswin-936 x-PCK
x-SJIS_0213 x-UTF-16LE-BOM X-UTF-32BE-BOM
X-UTF-32LE-BOM x-windows-50220 x-windows-50221
x-windows-874 x-windows-949 x-windows-950
x-windows-iso2022jp

Technical notes
This section describes important notes and tips for using Avamar.

Avamar server technical notes

The following technical notes apply to the Avamar server.

Common Vulnerabilities and Exposures (CVE) list

Avamar engineering addresses Common Vulnerabilities and Exposures (CVE) in operating system patch releases (also known as
OS Rollup releases). A list of all CVEs addressed is provided in the Security Advisory for each OS Rollup release.

Remove test data

Before starting the server or starting a new node for the first time, ensure that all test data is removed from /data*/
partitions. In particular, if you ran disk tests before startup, you might need to delete directories that are named QA.

Do not use the avmgr command

Improper use of the avmgr command line utility can destroy all access to data in the Avamar system. Use this command only at
the explicit direction of Customer Service.

Vulnerability scanning
As part of every Avamar release, the product is scanned for vulnerabilities using at least two common vulnerability assessments
tools. This release was scanned with Foundstone and Nessus. Various customers scan the Avamar solution by using tools such
as eEye Retina without issue. However, it is possible that the usage of other port/vulnerability scanners might cause disruption
to normal operation of the Avamar server. Therefore, it might be necessary to disable scanning of the Avamar server when
problems occur.

Avamar 7.2 and later scalability limits for virtualization support

The scalability limits of each Avamar 7.2 and greater with Data Domain integrated solution are approximately:
● 5000 virtual machine clients
● 180TB provisioned virtual machine storage
● 72 concurrent backup proxy client stream instances (not proxy virtual machines)
These limits are applicable only when the backup data is sent to the Data Domain system and assume that the Data Domain
is correctly specified to support the backup, restore, and, if applicable, replication activities. These limits may be impacted if

32
additional client types are backed up to the Avamar/Data Domain solution. These limits may be further limited by the overall
performance of the VMware environment, including the performance of the Avamar Virtual Edition server, if applicable.
Customers who plan to operate near these limits should validate their deployments with their account representative.

VMware image proxies are not available for backups when they are in sleep mode
and you restart the MCS
If you stop the MCS and do not restart the MCS within 5 minutes, then VMware image proxies go into a sleep mode for
40 minutes. When you restart the MCS, it might take some time until all proxies reconnect to the MCS and are available for
backups. This issue can occur when performing backups after a rollback.
To ensure that all proxies are available, open the avagent.log file on each proxy, and ensure that the following messages
appear at the bottom of the log:
yyyy-mm-dd hh:mm:ss avagent Info <5964>: Requesting work from 10.2.345.678
yyyy-mm-dd hh:mm:ss avagent Info <5264>: Workorder received: sleep
yyyy-mm-dd hh:mm:ss avagent Info <5996>: Sleeping 15 seconds

The messages indicate that the proxy can connect to the MCS. The avagent.log file is available in the /usr/local/
avamarclient/var directory.

AMS replication after an IP address change

If you change the IP address that you use for replication with Avamar and one or more Data Domain systems, then the first
replication after the change uses Automated Multistreaming (AMS) replication. Subsequent replications use Virtual Synthetic
Replication (VSR).

Original Bytes are displayed as twice the original size

The Original Bytes value appears as twice the original size when you run the Data Domain filesys show compression
command in the Avamar namespace on the Data Domain system.

Token based authentication notes

Data Domain version 5.7.1.x or later supports token based authentication. Previous versions fall back to traditional connection.
Clients must use a resolvable Fully Qualified Domain Name to use token based authentication.

Avamar Administrator technical notes

The following technical notes apply to Avamar Administrator.

Avamar Administrator directory browsing limitation

When browsing a client file system with Avamar Administrator, large numbers of files in the directories can cause Avamar
Administrator to run out of memory. Avamar Administrator is configured by default to only retrieve the first 50,000 files in
each directory. Change this limitation by editing the max_browse_entries settings in mcserver.xml and mcclient.xml.
However, this step could cause unpredictable application behavior.

Jobs do not appear in the Activity Monitor after server restart

If the administrator server is stopped and restarted, the jobs that started before the administrator server stop do not appear in
the Activity Monitor.

33
Schedule start times and end times
If a different start time is selected in the schedule, reselect the desired end time.

Client name change impacts license quota

If a client is renamed, the old name of the client remains for activities reporting data for the client. Avamar treats new activities
for the same client as if they were for a new client, leading to double counting the number of bytes protected for licensing
purposes. If a client name change is required, consult Dell Customer Service to ensure that the database is correctly updated.

Additional “cold start” messages from netsnmp

To resolve an issue where SNMP stops responding, Avamar must frequently restart the netsnmp agent. The netsnmp agent
generates a “cold start” message on each restart, in which additional “cold start” messages that are unrelated to actual restart
of the Avamar system or incorrect operation of the system appear. However, there are some difficulties to distinguish between
a real “cold start” message from the restart of Avamar system and a “cold start” message that is generated as the result of
netsnmp agent restarts.

Software conflicts with Black Ice and Timbuktu

The Avamar Administrator software is known to have conflicts with software packages such as Black Ice and Timbuktu.

Avamar Desktop/Laptop technical notes

The following technical notes apply to Avamar Desktop/Laptop.

Client-level Avamar accounts cannot log in to Avamar Desktop/Laptop

To provide the same level of security that exists in Avamar Administrator, Avamar Desktop/Laptop blocks Avamar's default
client-level accounts. The issue shows that Avamar Desktop/Laptop does not accept the credentials for the following default
accounts:
● backuponly
● restoreonly
● backuprestore
● replonly

Back up System State option not recommended

For datasets with the Windows file system plug-in, do not enable the Back up System State option when using Avamar
Desktop/Laptop.

Entourage support requires default installation location

The Avamar Client for Mac OS X supports Microsoft Entourage by using scripts that shut down the Microsoft Database daemon
before starting a backup. Restart the database after the backup completes. These scripts do not work when the Avamar Client
for Mac OS X is installed in a non-default location. To support clients for Entourage, use the default location when installing the
Avamar Client for Mac OS X.

Viewing logs from the Mac console requires default installation

When the 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, open the text editor from the clientlogs folder.

34
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 the limit of 96 MB that Dell recommends. Any
value below 96 MB affects the backup and restore performance.
During installation of the Avamar for Mac OS X Client, the installer looks at the value of this setting. If the value is less than 96
MB, the installer should change to 96 MB. The new value takes effect after the computer restarts.
The installer then launches a restart reminder. To ensure optimal performance, restart the computer as soon as possible after
completing the installation.

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 the drive may work, depending on permissions and domain settings, it is not supported.

Avamar Web Restore technical notes

The following technical notes apply to Avamar Web Restore.

Enabling the full display on the Avamar login screen

Avamar Web Restore displays an empty Domain field and an empty Client field on the Avamar login screen. This step prevents
the display of domain information during a non-domain login. When using Avamar Web Restore only in a secure domain, change
the default setting to enable the full display on the screen.
When the full display is enabled, a list of Avamar domains appears in the Domain field and a list of clients appears in the Client
field.

NOTE: This change does not affect the Avamar Web Restore LDAP login screen.

To enable the full display on the Avamar log in screen:

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

3. Change the current working directory by typing the following command:

cd /usr/local/avamar/etc

4. Open the Avamar Desktop/Laptop properties file, dtlt.properties, in a plain text editor.
5. Add the showWRClientList key with the value of true:
showWRClientList=true
If the key exists, set the value to true.

6. Save and close the file.

Special characters in file name replaced during restore

Restoring a file with special characters in the file name results in replacement of the characters in the restored file name. This
step occurs when the LANG variable on the Avamar server is set to a locale that does not support the characters. To work
around this issue, either rename the file after being restored or change the LANG variable on the Avamar server to the correct
locale.

35
Restore of files with special characters in file name when Avamar server LANG
variable is not set
When the LANG variable is not set on an Avamar server, using Avamar Web Restore to restore a file with special characters in
the file name fails. To fix this issue, set the LANG variable in /etc/locale.conf and reboot the Avamar server.

Proper UI rendering on Internet Explorer 11 browser

High Security setting in Internet Explorer 11 prevents rendering of JavaScript commands in the Avamar Web Restore pages. To
work around this issue, add the Avamar Web Restore server to the trusted sites list in Internet Explorer.

Restore of large number of files

Users cannot restore a large number of files through Avamar Web Restore. Limit each restore task to fewer than 200 files.

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

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

Password best practices

The following technical notes provide best practices for creating and protecting passwords.

Best practices for creating passwords

The following table provides best practices for creating passwords:

Table 32. Best practices for creating passwords

Best practice Details

Do not use Personal Identifiable Do not use PII in the password, such as:
Information (PII).

37
Table 32. Best practices for creating passwords (continued)
Best practice Details
● Your name
● Your username
● Your birthday
● Names of pets
● Names of your children
● Name of your alma mater
● Keywords that are associated with your hobbies

Do not use words from the Do not use any word that can be found in the dictionary as your full password.
dictionary.

Use strong passwords. Always use strong passwords when creating passwords. Strong passwords include:
● At least eight characters
● Special characters such as a percent sign (%) or ampersand (&)
● Non-alphabetic characters
● Both uppercase and lowercase characters

Use different passwords for Always use a different password for each user account.
user accounts

Change your password regularly ● Change your most critical passwords regularly.
● Change your passwords at least every 6 months.
● When you change your password, avoid using variations of a previous password.
● Immediately change your password if you expect another person has access to your
account, or knows your password.
● Always change your password as soon as you receive an account.

Password protection best practices

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

38
Documentation
The following sections describe the documentation and information products that are available with this release of Avamar:

Avamar product documentation

The Avamar documentation set includes the following:

Table 33. Avamar documentation set

Document Description
Avamar Administration Guide This document describes how to configure, administer, monitor, and maintain the
Avamar system.
Avamar Backup Clients User Guide This document describes how to install and activate Avamar backup clients on all
platforms. It also describes how to use the Avamar backup client to back up and
restore data.
Avamar Fitness Analyzer User Guide This document describes how to use the reporting and analysis software for Avamar
servers .
Avamar Management Console This document describes how to install, configure, and use the Avamar Management
Command Line Interface (MCCLI) Console Command Line Interface (MCCLI), which is a Java software application that
Programmer Guide provides command-line access to Avamar Administrator features.
Avamar NDMP Accelerator for NAS This document describes how to install and configure the Avamar NDMP Accelerator,
Systems User Guide and how to back up and restore data on supported Dell storage systems
(Unity,VNX,Isilon), NetApp filers, and Oracle ZFS.
Avamar Operational Best Practices This document provides best practices for designing, configuring, managing, and
tuning the performance of the Avamar system.
Avamar Orchestra Getting Started This document provides an introduction to the Avamar Orchestra REST API
Guide for multisystems management, including the Orchestra web UI and the Swagger
interface.
Avamar Plug-in for vCenter This document describes how to install, configure, administer, and use the Dell
Administration Guide Backup and Recovery plug-in for vCenter to back up and restore VMware image
backups on an Avamar server.
Avamar Product Security Guide This document discusses Avamar security considerations, including user
authentication and authorization, client/server access and authentication, data
security and integrity, system monitoring, server hardening, port usage, and firewall
requirements.
Avamar Release Notes This document describes new and changed features, resolved issues, known issues,
and supplemental information about the latest Avamar release.
Avamar Reports Guide This document describes how to create, manage, and interpret the information in
Avamar reports.
Avamar Virtual Edition Installation and This document describes how to install the Avamar Virtual Edition solution, a
Upgrade Guide single-node, non-RAIN Avamar server that runs as a virtual machine in various
environments.
Avamar and Data Domain System This document provides best practices for designing, configuring, and managing Data
Integration Guide Domain integration with the Avamar system.
Avamar for Exchange VSS User Guide This document describes how to install Avamar in a Microsoft Exchange Server
environment, and how to back up and restore data using Avamar with Microsoft
Volume Shadow Copy Service (VSS) technology.
Avamar for Hyper-V VSS Guide This document describes how to install Avamar in a Microsoft Hyper-V environment,
and how to back up and restore virtual machines using Avamar with Microsoft
Volume Shadow Copy Service (VSS) technology.
Avamar for IBM DB2 User Guide This document describes how to install Avamar in an IBM DB2 environment and how
to back up and restore DB2 databases.

39
Table 33. Avamar documentation set (continued)
Document Description
Avamar for Lotus Domino User Guide This document describes how to install Avamar in a Lotus Domino environment, and
how to back up and restore data.
Avamar for Oracle User Guide This document describes how to install Avamar in an Oracle database environment,
and how to back up and restore Oracle databases.
Avamar for SAP with Oracle User Guide This document describes how to install Avamar in an SAP environment with Oracle,
and how to back up and restore SAP servers with Oracle databases.
Avamar for SQL Server User Guide This document describes how to install Avamar in a Microsoft SQL Server
environment, and how to back up and restore SQL Server databases.
Avamar for SharePoint VSS User Guide This document describes how to install Avamar in a SharePoint environment, and
how to back up and restore data using Avamar with Microsoft Volume Shadow Copy
Service (VSS) technology.
Avamar for Sybase ASE User Guide This document describes how to install Avamar in a Sybase environment, and how to
back up and restore Sybase Adaptive Server Enterprise (ASE) databases.
Avamar for VMware User Guide This document describes how to install, configure, and use Avamar to back up and
restore virtual machines in a VMware environment.
Avamar for Windows Server User Guide This document describes how to install the Avamar client for Microsoft Windows, and
how to back up and restore data on a Windows server.

Avamar related documentation

In addition to the product documentation, the following related links and documentation provide more information about Avamar:

E-lab Navigator
E-LAB Navigator
Provides server, client, and platform compatibility and interoperability information. The E-LAB Navigator at https://
elabnavigator.dell.com/eln/elnhome.

Technical notes and white papers

Avamar technical notes provide technical details on specific product features, including step-by-step tasks, where necessary.
White papers provide an in-depth technical perspective of a product or products as applied to critical business issues or
requirements. Both technical notes and white papers are available on Online Support at https://www.dell.com/support.

Installation and upgrade considerations

The following sections provide information about installation and supported upgrades in an Avamar environment:

Avamar server and Avamar Virtual Edition installation and upgrade

For a physical Avamar server, a technical representative must perform the installation or upgrade. Downgrading the Avamar
server software to an earlier version is not supported under any circumstances.
Support to upgrade Avamar from 7.5.1 with SLES version 11 SP1, SLES version 11 SP3, SLES version 11 SP4, SLES version 12
SP4, SLES version 12 SP5 to Avamar 19.9. This upgrade will also upgrade SLES to SLES 12 SP5, which is the required version
for 19.4 and later release.
The client downloads, which provide the ability to download the current client versions from the server’s Documents and
Downloads web interface, are installed along with the server upgrade. The upgrade is provided by the Avamar Server Upgrade
team unless a request is made that the team refrains from installing. However, the upgrade team does not install the Avamar
Upgrade installers, which provide the client kits for the Avamar Client Manager's automated update feature. This option is a

40
customer-upgradeable kit which can be obtained from the upgrade information. For instructions on application of the client
installers, see the Avamar Client-Only System Upgrades Technical Note available on the online support website at https://
dell.com/support/.
AVE can be deployed using M5 instance in AWS. It can work normally after being deployed using M5 instance. The M5 instance
is a Nitro-based instance. M5 instances are built on the AWS Nitro System and Elastic Block Storage (EBS) volumes are
exposed as NVMe block devices on Nitro-based instance. The Nitro system is a collection of AWS- built hardware and software
components which enable high performance, high availability, and high security. For more information, see the Amazon EC2 M5
Instances.
To install a 16 TB AVE on Azure, customers must use the D14_v2 instance type instead of A9 since A9 will no longer be
supported by Azure.
To install a 0.5 TB or 2 TB AVE, support new instance type A2m_v2.

Avamar client installation and upgrade

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

Installation and upgrade of other Avamar components

The following table provides the location for installation and upgrade procedures for additional Avamar components:

Table 34. Installation and upgrade of other Avamar components

Component Location for installation and upgrade procedures
Avamar Management Web user interface (AUI) Avamar Administration Guide
Avamar Administrator Avamar Administration Guide
Avamar Management Console Command Line Interface Avamar Management Console Command Line Interface
(MCCLI) (MCCLI) Programmer Guide

Upgrade requirements for Avamar

Review the requirements in the following sections before you upgrade to Avamar 19.9:

Upgrade requirements in a VMware environment

Ensure that the VMware environment meets the following requirements when you upgrade to Avamar 19.9:
● Reboot proxy virtual machines after you upgrade the Avamar server.
● Ensure that the Avamar server time is synchronized with ESXi host before upgrade. If the Avamar server is a configured
NTP server, also ensure that the ESXi host time is synchronized with the same NTP server.

Upgrade requirements for Avamar with a Data Domain system

Use DD OS version 7.11 on a Data Domain system with an Avamar 19.9 server. Before you upgrade to Avamar 19.9, you must
upgrade any clients that back up to a Data Domain system to Avamar 7.5 or later.
The upgrade path for Avamar and Data Domain is specific. Failure to upgrade software in the proper order can cause Avamar
maintenance functions and/or backups to fail. If this happens and the Avamar server fails, a rollback operation fails. The Avamar
and Data Domain System Integration Guide provides details.
NOTE: Support to upgrade Avamar from 7.5.1 with SLES version 11 SP1, SLES version 11 SP3, SLES version 11 SP4, SLES
version 12 SP4, or SLES version 12 SP5 to Avamar 19.4 and later. This upgrade will also upgrade SLES to SLES 12 SP5,
which is the required version for 19.4 and later releases.

41
Table 35. Upgrade Avamar with a Data Domain system
Upgrade path Steps
Avamar 19.8 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 19.8 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 19.7 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 19.7 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 19.4 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 19.4 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 19.3 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 19.3 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 19.2 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 19.2 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 19.1 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 19.1 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 18.2 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 18.2 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 18.1 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 18.1 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.
Avamar 7.5.1 to Avamar 19.9 1. Ensure that all Avamar clients are running Avamar 7.5.1 client software.
2. Upgrade the Data Domain systems to DD OS 6.2 or later.
3. Upgrade the Avamar server to release 19.9.
4. (Optional) Upgrade the Avamar clients to release 19.9.

NOTE: If you fail to perform the upgrade steps or you perform the steps out of sequence, backup failures and data
corruption on the backup device can occur. All Avamar and Data Domain upgrades should be planned ahead of time with
the assistance of the Remote Proactive Avamar Upgrade team. Do not attempt to proceed without their assistance and
planning.

Upgrade requirements for Avamar with NetWorker

If you use Avamar with NetWorker, review the minimum NetWorker software version requirements before you upgrade the
Avamar server to release 19.4 and later. The NetWorker Software Compatibility Guide at https://elabnavigator.dell.com/eln/
elnhome provides information about the NetWorker version requirement for specific clients.

42
Microsoft update requirements for Avamar with Hyper-V on CSV
Backups fail in a Hyper-V environment with CSV unless you follow best practices and apply Microsoft hotfixes in the correct
order. The Best Practices for Hyper-V over CSV Cluster Data Protection Using Avamar and Networker Technical Note on
Online Support provides details.

Where to get help

The Dell Technologies Support site (https://www.dell.com/support) contains important information about products and
services including drivers, installation packages, product documentation, knowledge base articles, and advisories.
A valid support contract and account might be required to access all the available information about a specific Dell Technologies
product or service.

Troubleshooting and getting help

The Avamar support page provides access to licensing information, product documentation, advisories, and downloads, as well
as how-to and troubleshooting information. This information may resolve a product issue before contacting Customer Support.
To access the Avamar support page:
1. Go to https://www.dell.com/support.
2. Type a product name in the Enter a Service Tag, Serial Number, Service Request, Model, or Keyword search box.
3. Select the product from the list that appears. When you select a product, the Product Support page loads automatically.
4. (Optional) Add the product to the My Products list by clicking Add to My Saved Products in the upper right corner of the
Product Support page.

Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx)
or by keyword.
To search the Knowledgebase:
1. Go to https://www.dell.com/support.
2. Under the Support tab, click Knowledge Base.
3. Type either the solution number or keywords in the search box. Optionally, you can limit the search to specific products by
typing a product name in the search box and then selecting the product from the list that appears.

Online communities
Go to Community Network at https://www.dell.com/community for peer contacts, conversations, and content on product
support and solutions. Interactively engage online with customers, partners, and certified professionals for all products.

Live chat
To engage Customer Support by using live interactive chat, click Join Live Chat on the Service Center panel of the Avamar
support page.

Service requests
For in-depth help from Customer Support, submit a service request by clicking Create Service Requests on the Service Center
panel of the Avamar support page.
NOTE: To open a service request, you must have a valid support agreement. Contact a sales representative for details
about obtaining a valid support agreement or with questions about an account.

43
To review an open service request, click the Service Center link on the Service Center panel, and then click View and manage
service requests.

Enhancing support
It is recommended to enable ConnectEMC and Email Home on all Avamar systems:
● ConnectEMC automatically generates service requests for high priority events.
● Email Home sends configuration, capacity, and general system information to Customer Support.

Comments and suggestions

Feedback helps to improve the accuracy, organization, and overall quality of publications. Perform one of the following steps to
provide feedback:
● Go to https://contentfeedback.dell.com/s, and submit a ticket.
● Send feedback to [email protected].

44
Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2001 - 2023 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners.