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
Additional steps required after a MongoDB snapshot restore
The following steps are required after you restore a MongoDB snapshot. Even though the restore operation itself is successful, these steps are required for the application database to be available for normal use again.
Note:
These manual steps are not required in case of a disk-level restore to the same location.
Perform the following steps
- Ensure that the snapshot restore operation has completed successfully and a new disk is created and attached to the application host (in case of a disk-level restore) or the application host is up and running (in case of a host-level restore).
- Connect to the application host.
- Mount the attached disk on the application host using the following command:
# sudo mount /dev/<diskname> /<mountdir>
Here, <diskname> is the name of the new disk that was created after restore, and <mountdir> is the path where you want to mount the disk.
- Edit the MongoDB config file
/etc/mongod.conf
and set the dbPath parameter value to the<mountdir>
path that you specified in the earlier step. - Start the MongoDB service on the application host and verify that the service is running.
Use the following commands:
# sudo systemctl start mongod.service
# sudo systemctl status mongod.service
Note:
In case of a disk-level restore to a new host, ensure that
mongo
is installed on that host. - Log on to the MongoDB server using the MongoDB client and verify that the database is running.