Please enter search query.
Search <book_title>...
Veritas CloudPoint Administrator's Guide
Last Published:
2020-06-04
Product(s):
CloudPoint (2.2.2)
Platform: Linux
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Docker may fail to start due to a lack of space
During CloudPoint deployment, the Docker image may fail to start if there is not enough space for the MongoDB database. The failure occurs after you enter the docker run command.
Workaround:
The following procedure shows the steps to take if the image fails to start.
- Check the log file
/mount-point-from-host/logs/init.log
.Note that MongoDB starts, then immediately stops. (See the information messages in bold.)
# sudo cat /mount-point-from-host/logs/init.log Oct 03 11:24:45 init:INFO - Veritas CloudPoint init process starting up. Oct 03 11:24:45 init:INFO - Veritas CloudPoint init process starting up. Oct 03 11:24:45 init:INFO - Started mongodb[9] Oct 03 11:24:45 init:INFO - Started mongodb[9] Oct 03 11:24:45 init:INFO - mongodb already stopped, 100 Oct 03 11:24:45 init:INFO - mongodb already stopped, 100
- Verify the amount of available space on the host boot disk. MongoDB needs about 4 GB of space.
In the following example, only 1.6 GB is available.
# sudo df -kh / Filesystem Size Used Avail Use% Mounted on /dev/xvda1 7.7G 6.2G 1.6G 80% /
- Free up space on the book disk.
- After the boot disk has more than 4.0 GB of available space, restart the container.
# sudo docker restart container-id