- Notes, cautions, and warnings
- Preface
- Introduction
- Configuration and Setup
- Best practices
- (Optional) Configuring support for multiple vCenters
- Installing Avamar Administrator software
- Configure vCenter-to-Avamar authentication
- Creating a dedicated vCenter user account
- Add a vCenter as an Avamar client in the AUI
- Register or add a proxy client
- Edit vCenter
- Auto-discovery of virtual machines
- Deploying proxies using Proxy Deployment Manager from AUI
- Upgrading proxies
- Maintaining proxies
- Monitor proxy status
- Import custom certificate in Avamar VMware Image Backup Proxy
- Security patch updates for proxies
- Additional Avamar server configuration
- Administration
- Clients and containers
- Add a VMware client
- Delete a VMware client
- Enable changed block tracking
- Viewing protected virtual machines in Avamar Administrator
- Viewing a replicated virtual machine name in Avamar Administrator
- Monitoring the vCenter connection in Avamar Administrator
- Manually synchronize the AUI with vCenter and VM clients
- Rename a vCenter client
- VMware Image Dataset
- Adding guest backup throttling parameters to a dataset in Avamar Administrator
- Groups
- Changing proxy datastore and group assignments in Avamar Administrator
- Backup
- Limitations
- Perform an on-demand backup of a virtual machine by using AUI
- Set advanced plug-in options in the AUI
- Schedule backups using the AUI Policy wizard
- Log truncation backups
- Monitor backups
- Cancel backups
- Support for vCenter HA failover for inflight backups
- Configure a backup to support VMware encryption
- Configure a backup to support vSAN encryption
- Enforcement of backups to Data Domain
- Restore
- Image and file-level restore guidelines
- Image backup overview
- File Level Restore
- Performance improvements for File Level Restore
- File-level restore supported configurations
- RSA SecurID authentication in the AUI
- File Level Restore troubleshooting and limitations
- File Level Restore (FLR) in the AUI
- Restore ACL for non-root user configuration
- Perform a File Level Restore (FLR) operation by using the Data Protection Backup and Recovery File Level Restore (FLR) UI
- Backup Validation
- Protecting the vCenter Management Infrastructure
- vCenter deployments overview
- Best practices for backup and restore
- Protecting an embedded PSC
- Protecting external deployment models
- vCenter server appliance(s) with one external PSC where PSC fails
- vCenter server appliance is lost but the PSC remains
- vCenter server appliance with multiple PSCs where one PSC is lost, one remains
- vCenter server appliance remains but all PSCs fail
- vCenter server appliance remains but multiple PSCs fail
- vCenter server appliance fails
- vCenter server restore workflow
- Platform Services Controller restore workfow
- Command reference
- Support for vCenter HA failover for inflight backups
- Additional considerations
- Protecting ESX Hosts
- Avamar Image Backup and Recovery for VMware Cloud on Amazon Web Services (AWS)
- Avamar image backup and recovery for VMware Cloud on AWS
- Configure the VMware Cloud on AWS web portal console
- Amazon AWS web portal requirements
- vCenter server inventory requirements
- Deploy the vProxy OVA on a vCenter server in VMware Cloud on AWS
- Configure vCenter-to-Avamar authentication for VMware Cloud on AWS
- Avamar image backup and restore for VMware Cloud on AWS best practices
- Unsupported Avamar operations
- Backing up VMware Cloud Foundation (VCF) Components on VxRail
- Manually deploying proxies
- Overview
- Downloading the proxy appliance template file
- Deploying the proxy appliance in vCenter
- Deploying a proxy appliance in vCenter using the vSphere Web Client
- Registering and activating the proxy with the Avamar server
- Configuring proxy settings in Avamar Administrator
- Performing optional proxy performance optimization
- vSphere Data Ports
- Using VMware vRealize Log Insight
- Plug-in Options
- Troubleshooting
- Installation and configuration problems and solutions
- Backup problems and solutions
- Backup does not start
- Exclude the proxy from the virtual machine backup if performing the backup with other VMware software
- Backups fail with No Proxy errors
- Changed block tracking does not take effect
- Proxies are not assigned to backup jobs
- VM snapshot fails backups due to incorrect pre-evaluation of available space
- Backup and restore of vFlash Read Cache enabled VMs will use NBD transport mode
- Exchange log truncation unsupported when VMDK is encrypted via vSphere
- Indexing VMware image backups requires HotAdd transport mode
- Proxy status alert
- Restore problems and solutions
- Glossary
Dell EMC Avamar for VMware 19.7 User Guide
Configuring the MCS to support both guest and image backup
In order to support using both image and guest backup to protect the same virtual machine, you must configure the Avamar MCS to allow duplicate client names.
Steps
-
Open a command shell and log in by using one of the following methods:
- For a single-node server, log in to the server as admin.
- For a multi-node server, log in to the utility node as admin.
-
Stop the MCS by typing the following command:
dpnctl stop mcs
- Open /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml in a UNIX text editor.
- Find the allow_duplicate_client_names entry key.
-
Change the
allow_duplicate_client_names setting to
true.
<entry key="allow_duplicate_client_names" value="true" />
- Close mcserver.xml and save your changes.
-
Start the MCS and the scheduler by typing the following command:
dpnctl start mcs
dpnctl start sched
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: <>()\