- Notes, cautions, and warnings
- Preface
- Getting Started
- Preparing for a Deployment
- Licensing PowerProtect Data Manager
- PowerProtect Data Manager interoperability introduction
- Microsoft application agent, Oracle RMAN agent, and PowerProtect Data Manager interoperability
- File System agent interoperability and supported operating systems
- Memory optimization
- Scalability limits for vCenter server, VM Direct Engine, and DD systems
- PowerProtect Data Manager resource requirements in a VMware environment
- Requirements for an external VM Direct Engine
- Requirements for the PowerProtect Search Engine
- Network requirements
- Deployment
- Configuration
- Management
- Performing Updates
- Managing update packages
- Updating the version of PowerProtect Data Manager
- Updating from a released version of PowerProtect Data Manager that has been updated
- Update PowerProtect Data Manager from versions 19.10 through 19.13 to version 19.14
- Licensing
- Deployment Best Practices and Troubleshooting
- Glossary
PowerProtect Data Manager 19.14 Deployment Guide
Log bundle creation to troubleshoot configuration failures
If errors appear in the PowerProtect Data Manager console after appliance configuration, and the configuration did not complete successfully, you can create a log bundle to determine the cause of the error and troubleshoot the issue.
To create a log bundle:
- Log in to the VM console through the vCenter server with the username root and the password changeme.
- Run the following:
logs tar -cvf vmd_logs.tar * cd /logs/vmdirect/ tar -cvf ecdm_messages messages*
Example command usage
The following screen shows an example command that is run on the VM console to create the log bundle.
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: <>()\