- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Virtual Machines Overview
- Enabling Virtual Machine Protection
- Managing Virtual Machine Assets and Protection
- Protection policies
- Additional protection policy options
- Before you create a protection policy
- Supported enhanced VMware topologies for virtual-machine protection
- Add a protection policy for virtual-machine protection
- Managing virtual-machine backups
- Add a service-level agreement
- Add or remove assets in a protection policy
- Extended retention
- Edit the retention period for backup copies
- Protection rules
- Restoring Virtual Machine Data and Assets
- Prerequisites to restore a virtual machine
- Self-service restores
- View backup copies available for restore
- Restoring a virtual machine or VMDK
- Restoring a virtual machine backup with the storage policy association
- Image-level restores
- Instant Access virtual-machine restore
- File-level restores
- Restore an application-aware virtual machine backup
- Protecting Virtual Machines Using the Transparent Snapshot Data Mover
- Overview of transparent snapshots for virtual machine protection
- VIB installation monitoring and management
- Transparent snapshot data mover system requirements
- Prerequisites to virtual machine protection with the Transparent Snapshot Data Mover
- Virtual machine transparent snapshot unsupported features and limitations
- Transparent Snapshot Performance and Scalability
- PowerProtect Functionality Within the vSphere Client
- PowerProtect functionality within the vSphere Client
- Overview of the PowerProtect plug-in for the vSphere Client
- Prerequisites for enabling the vSphere Client PowerProtect plug-in
- Monitor PowerProtect Data Manager virtual machine protection copies
- Manual PowerProtect policy backup in the vSphere Client
- Image-level restore of a PowerProtect backup in the vSphere Client
- File-level restore of a PowerProtect backup in the vSphere Client
- Overview of VASA and VMware Storage Policy Based Management
- VMware Cloud (VMC) on Amazon Web Services (AWS)
- PowerProtect Data Manager image backup and recovery
- Supported PowerProtect Data Manager and DDVE deployment configurations
- Deployment and configuration best practices and requirements
- Configuring the VMC-on-AWS portal
- Interoperability with PowerProtect Data Manager features
- vCenter server inventory requirements
- Creating a dedicated cloud-based vCenter user account
- Add a VM Direct Engine
- Unsupported operations
- Azure VMware Solution (AVS) on Microsoft Azure
- PowerProtect Data Manager image backup and recovery
- Supported PowerProtect Data Manager and DDVE deployment configurations
- Deployment and configuration best practices and requirements
- Configuring the AVS-on-Azure portal
- vCenter server inventory requirements
- Creating a dedicated cloud-based vCenter user account
- Add a VM Direct Engine
- Unsupported operations
- Google Cloud VMware Engine (GCVE) on Google Cloud Platform (GCP)
- PowerProtect Data Manager image backup and recovery
- Supported PowerProtect Data Manager and DDVE deployment configurations
- Deployment and configuration best practices and requirements
- Configuring the GCVE-on-GCP portal
- vCenter server inventory requirements
- Creating a dedicated cloud-based vCenter user account
- Add a VM Direct Engine
- Unsupported operations
- Backing Up and Recovering a vCenter Server
- Backing up and recovering a vCenter server
- vCenter deployments overview
- Protecting an embedded PSC
- Protecting external deployment models
- vCenter server appliance 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 but 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
- Additional considerations
- Command reference
- Backing Up VMware Cloud Foundation (VCF) on VxRail
- Backing up VCF on VxRail
- VCF and VxRail overview
- VCF components and backup methods
- Check VMware certification
- Backup prerequisites
- The backup script
- Quick protection
- Selective protection: SDDC and NSX-T Managers
- Selective protection: vCenter servers
- Selective protection: vRSLCM, VxRail Manager, Workspace ONE Access, and vRealize Suite virtual machines
- SFTP password change: SDDC and NSX-T Managers
- SFTP password change: vCenter servers
- Backup-script troubleshooting
- Virtual Machine Best Practices and Troubleshooting
- Software and hardware requirements
- Scalability limits for vCenter server, VM Direct Engine, and DD systems
- PowerProtect Data Manager resource requirements in a VMware environment
- Best practices and additional considerations for the VM Direct Engine
- VM Direct Engine performance and scalability
- Transport mode considerations
- Change the limit of instant access sessions
- Configuring a backup to support vSAN datastores
- Configuration checklist for common issues
- Disable vCenter SSL certificate validation
- vProxy Agent for virtual-machine file-level restore
- FLR-supported platform and OS versions for virtual machine restores
- File-level restore and SQL restore troubleshooting and limitations
- Virtual disk types supported
- Virtual machine data change rate
- VM Direct Engine data ingestion rate
- VM Direct Engine limitations and unsupported features
- VM Direct Engine selection with virtual networks (VLANs)
- Deploying VM Direct appliance to datastore cluster unsupported
- Best practices for vCenter server backup and restore
- Changing the vCenter server FQDN
- Replacing security certificates
- Troubleshooting network setup issues
- Troubleshooting virtual machine backup issues
- Backup completes with a non-quiesced snapshot warning
- Backup fails when names include special characters
- Deleting vCenter asset sources or moving ESXi to another vCenter server
- Failed to lock virtual machine for backup: Another EMC vProxy operation 'Backup' is active on VM
- Lock placed on virtual machine during backup and recovery operations continues for 24 hours if VM Direct appliance fails
- Managing command execution for VM Proxy Agent operations on Linux
- PowerProtect plug-in and portlet for vSphere display errors after replacing security certificates
- SQL Server application-consistent backups fail with error "Unable to find VSS metadata files in directory"
- Troubleshooting virtual machine restore issues
- Troubleshoot virtual machine SQL application consistent policy issues
- Support for backup and restore of encrypted virtual machines
- Troubleshooting vSphere Plugin deployments
- VMware knowledge base articles and product documentation
PowerProtect Data Manager 19.11 Virtual Machine User Guide
Delete vProxy or Search nodes when a vCenter server asset source is no longer required
Perform the following procedure when you delete a vCenter server as an asset source in PowerProtect Data Manager and you will not be re-adding the vCenter server:
About this task
NOTE Manual cleanup of the virtual machine for the vProxy or Search node has to be performed from the vCenter server.
Steps
-
Run the following command to source the environment file.
source /opt/emc/vmdirect/unit/vmdirect.env
-
For vProxy removal:
- Obtain the list of vProxies that require removal by running /opt/emc/vmdirect/bin/vproxymgmt get
- Make note of the ID of any vProxy that needs to be deleted.
- Use the vproxymgmt tool to delete vProxies by running /opt/emc/vmdirect/bin/vproxymgmt delete -vproxy_id ProxyID
-
For Search Node removal:
- Obtain the list of Search nodes that require removal by running /opt/emc/vmdirect/bin/infranodemgmt get
- Make note of the ID of any Search node that needs to be deleted.
- Use the infranodemgmt tool to delete Search nodes by running /opt/emc/vmdirect/bin/infranodemgmt delete -node_id NodeID
- In the PowerProtect Data Manager user interface, ensure that any sessions have been removed for both the vProxy or Search nodes.
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: <>()\