- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Storage Direct Agent Overview
- Enabling the Storage Direct Agent for VMAX Systems
- Managing Storage, Assets, and Protection
- About asset sources, assets, and storage
- Add protection storage
- Manage the Storage Direct agent
- Enable an asset source
- Add and discover the SMIS server for the Storage Direct agent
- Add a self-service protection policy for Storage Direct
- Add a centralized protection policy for Storage Direct
- Add a service-level agreement
- Add assets to an existing storage group protection policy
- Remove assets from an existing storage group protection policy
- Edit the retention period for backup copies
- Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier)
- Delete backup copies
- Restoring a Storage Direct VMAX storage group
- Restore backup copies from replication DD when source Storage Direct agent host, PowerProtect Data Manager server, and VMAX are unavailable
- Manage the PowerProtect agent service
- About the PowerProtect agent service
- Start, stop, or obtain the status of the PowerProtect agent service
- Troubleshooting PowerProtect agent service installations
- Troubleshooting PowerProtect agent service operations
- Register the PowerProtect agent service to a different server address on Windows
- Recovering the PowerProtect agent service from a disaster
- Storage Direct Best Practices and Troubleshooting
- Storage Direct agent limitations
- Troubleshooting agent registration
- Troubleshooting PowerProtect agent service installations
- Troubleshooting PowerProtect agent service operations
- Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname
- Troubleshooting when protection policies cannot be created from an imported configuration file that uses VMAX
- Troubleshooting initiation of SMIS server discovery job
- Troubleshooting SDFSA install/update failure when using absolute path
- Troubleshooting when encapsulation fails during policy creation
- Troubleshooting when restart of encapsulation fails
- Troubleshooting when encapsulation fails with error "SYMAPI_C_NET_HANDSHAKE_FAILED"
- Troubleshooting failure of configuration file validation
- Troubleshooting failure of MTree replication
- Troubleshooting replication for assets already configured for a stand-alone agent
- Troubleshooting creation of new snapshot after restart of failed backup
- Troubleshooting a configuration file that is generated by PowerProtect Data Manager and imported during an agent update
- Troubleshooting storage policy backup failure and PowerProtect config validation error
- Troubleshooting method to retrieve a backup catalog deleted using the force option with retention lock enabled
- – Glossary of Acronyms –
- 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 Storage Direct User Guide
Troubleshooting failure of configuration file validation
Configuration file validation fails when multiple storage group assets are selected for policy inclusion if the configuration file is not formatted correctly.
When you select multiple storage group assets as part of a VMAX Storage Group protection policy in PowerProtect Data Manager, validation fails if the configuration file is not formatted correctly. For example, a configuration file with the following format might be pushed to the host:
DDBOOST_USER = 148_78-xxxxx-932c9 DEVICE_HOST = IP address DEVICE_PATH = /148_78-xxxxx-932c9-SU DDVDISK_USER = 148_78-xxxxx-932c9 #RESTORE_DEVICE_POOL = 148_78-xxxxx-932c9 #RESTORE_DEVICE_GROUP = R-sdm_xxxxx_SG7-0638 #RESTORE_DEVICE_GROUP = R-sdm_xxxxx_SG8-0638 # DD_BOOST_FC = # DD_PORT = VMAX_FASTX_RESTORE_SG = R-sdm_xxxxx_SG7-0638 #VMAX_FASTX_RESTORE_SG = R-sdm_xxxxx_SG8-0638
To work around this issue, enclose VMAX_FASTX_RESTORE_SG in a comment and remove RESTORE_DEVICE_POOL and one of the entries for RESTORE_DEVICE_GROUP from the comment.
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: <>()\