- Notes, cautions, and warnings
- Avamar Release Notes
- Revision history
- Avamar overview
- New features and changes
- Changed features
- Resolved issues
- Known issues
- Avamar server known issues
- Avamar Virtual Edition known issues
- Avamar Web Client (AUI) known issues
- Avamar Orchestra known issues
- Avamar Administrator known issues
- Avamar Client Manager known issues
- Avamar Config Checker known issues
- Avamar Desktop/Laptop known issues
- File level restore client known issues
- Avamar Web Restore known issues
- Data Domain system integration known issues
- All backup clients and plug-ins known issues
- AIX, HP-UX, Linux, CentOS, and Solaris client known issues
- Microsoft Exchange VSS plug-in known issues
- Microsoft Hyper-V VSS plug-in known issues
- Microsoft SharePoint VSS plug-in known issues
- Microsoft SQL Server plug-in known issues
- Microsoft Windows client known issues
- NDMP accelerator node known issues
- Oracle database plug-in known issues
- IBM DB2 plug-in known issues
- SAP with Oracle plug-in known issues
- Sybase ASE plug-in known issues
- IBM Lotus Domino plug-in known issues
- Replication known issues
- Avamar Data Migration Enabler (ADMe) known issues
- Upgrade known issues
- VMware known issues
- Supportability package known issues
- Avamar plug-in for vSphere Web Client configuration application known issues
- Environment and system requirements
- International language support
- Technical notes
- Documentation
- Installation and upgrade considerations
- Where to get help
Dell EMC Avamar 19.7 Release Notes
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.
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 EMC 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.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\