- 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
- Edit the retention period for backup copies
- Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier)
- 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
- vSphere Installation Bundle 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
- Perform a manual PowerProtect-policy backup in the vSphere Client
- Perform an image-level restore of a PowerProtect backup in the vSphere Client
- File-level restores 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
- Uninstalling the VM Direct agent
- Updating the Microsoft Application Agent and VM Direct agent software
- Supported file-level restore platforms and OS versions
- File-level restore and SQL restore requirements 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
- Support for backup and restore of encrypted virtual machines
- 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 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 Direct 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
- Troubleshooting vSphere Plugin deployments
- VMware knowledge base articles and product documentation
- Glossary
- AAG: Always On availability group
- ACL: access control list
- AD: Active Directory
- AKS: Azure Kubernetes Service
- ARM: Azure Resource Manager
- API: application programming interface
- AVS: Azure VMware Solution
- AWS: Amazon Web Services
- AZ: availability zone
- BBB: block-based backup
- CA: certificate authority
- CBT: Changed Block Tracking
- CDC: change data capture
- CIFS: Common Internet File System
- CLI: command-line interface
- CLR: Common Language Runtime
- CN: common name
- CPU: central processing unit
- CR: custom resource
- CRD: custom resource definition
- CSI: container storage interface
- CSV: Cluster Shared Volume
- DAG: database availability group
- DA: database administrator
- DBID: database identifier
- DDMC: DD Management Center
- DDOS: DD Operating System
- DDVE: DD Virtual Edition
- DFC: DD Boost over Fibre Channel
- DNS: Domain Name System
- DPC: Data Protection Central
- DRS: Distributed Resource Scheduler
- DR: disaster recovery
- DSA: Dell security advisory
- EBS: Elastic Block Store
- EC2: Elastic Compute Cloud
- eCDM: Enterprise Copy Data Management
- ECS: Elastic Cloud Storage
- EKS: Elastic Kubernetes Service
- ENI: Elastic Network Interface
- EFI: Extensible Firmware Interface
- EULA: end-user license agreement
- FC: Fibre Channel
- FCD: first class disk
- FCI: failover cluster instance
- FETB: front-end protected capacity by terabyte
- FLR: file-level restore
- FQDN: fully qualified domain name
- FTP: File Transfer Protocol
- GB: gigabyte
- Gb/s: gigabits per second
- GCP: Google Cloud Platform
- GCVE: Google Cloud Virtual Edition
- GID: group identifier
- GLR: granular-level restore
- GUI: graphical user interface
- GUID: globally unique identifier
- HA: High Availability
- HANA: high-performance analytic appliance
- HTML: Hypertext Markup Language
- HTTP: Hypertext Transfer Protocol
- HTTPS: Hypertext Transfer Protocol Secure
- IAM: identity and access management
- IDE: Integrated Device Electronics
- IP: Internet Protocol
- IPv4: Internet Protocol version 4
- IPv6: Internet Protocol version 6
- KB: kilobyte
- LAC: License Authorization Code
- LAN: local area network
- MB: megabyte
- ms: millisecond
- MTU: maximum transmission unit
- NAS: network-attached storage
- NBD: network block device
- NBDSSL: network block device over SSL
- NDMP: Network Data Management Protocol
- NFC: Network File Copy
- NFS: Network File System
- NIC: network interface card
- NTFS: New Technology File System
- NTP: Network Time Protocol
- OS: operating system
- OSS: open-source software
- OVA: Open Virtualization Appliance
- PCS: Protection Copy Set
- PDF: Portable Document Format
- PEM: Privacy-enhanced Electronic Mail
- PIN: personal identification number
- PIT: point in time
- PKCS: Public Key Cryptography Standards
- PSC: Platform Service Controller
- PVC (cloud computing): private virtual cloud
- PVC (Kubernetes): Persistent Volume Claim
- RAC: Real Application Clusters
- RAM: random-access memory
- RBAC: role-based access control
- ReFS: Resilient File System
- REST API: representational-state transfer API
- RHEL: RedHat Enterprise Linux
- RMAN: Recovery Manager
- RPO: recovery-point objective
- RSA: Rivest-Shamir-Adleman
- S3: Simple Storage Services
- SaaS: software as a service
- SAP: System Analysis Program Development
- SCSI: Small Computer System Interface
- SDDC: software-defined data center
- SELinux: Security-Enhanced Linux
- SFTP: Secure File Transfer Protocol
- SLA: service-level agreement
- SLES: SuSE Linux Enterprise Server
- SLO: service-level objective
- SPBM: Storage Policy Based Management
- SQL: Structured Query Language
- SRS: Secure Remote Services
- SSD: solid-state drive
- SSH: Secure Shell
- SSL: Secure Sockets Layer
- SSMS: SQL Server Management Studio
- SSVs: System Stable Values
- TB: terabyte
- TCP: Transmission Control Protocol
- TDE: Transparent Data Encryption
- TLS: Transport Layer Security
- TPM: Trusted Platform Module
- TSDM: Transparent Snapshot Data Mover
- T-SQL: Transact-SQL
- UAC: user account control
- UDP: User Datagram Protocol
- UI: user interface
- UID: user identifier
- UTC: Coordinated Universal Time
- VADP: VMware vStorage APIs for Storage Awareness
- VBS: virtualization-based security
- VCF: VMware Cloud Foundation
- vCLS: vSphere Cluster Service
- VCSA: vCenter Server Appliance
- vCSA: vCenter Server Appliance
- VDI: Virtual Device Interface
- vDisk: virtual disk
- vDS: virtual distributed switch
- vFRC: Virtual Flash Read Cache
- VGT: Virtual Guest Tagging
- VIB: vSphere Installation Bundle
- VLAN: virtual LAN
- VM: virtual machine
- VMC: VMware Cloud
- VMDK: virtual machine disk
- VNet: virtual network
- VPC: virtual private cloud
- vRSLCM: vRealize Suite Lifecycle Manager
- VST: Virtual Switch Tagging
- vTPM: Virtual Trusted Platform Module
- VVD: VMware Validated Design
- vVol: virtual volume
- WAN: wide area network
PowerProtect Data Manager 19.12 Virtual Machine User Guide
Troubleshooting an issue with trailing spaces in Microsoft SQL Server database names
Due to a VSS limitation, you cannot use trailing spaces within the names of Microsoft SQL Server databases protected by an application-consistent data protection policy.
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: <>()\