Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ CloudPoint Install and Upgrade Guide
  3. Section I. CloudPoint installation and configuration
  4. CloudPoint application agents and plug-ins
  5. Additional steps required after a MongoDB snapshot restore
Veritas NetBackup™ CloudPoint Install and Upgrade Guide

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

  1. 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).
  2. Connect to the application host.
  3. 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.

  4. 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.
  5. 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.

  6. Log on to the MongoDB server using the MongoDB client and verify that the database is running.

Feedback

Was this page helpful?
Previous

Disk-level snapshot restore fails if the original disk is detached from the instance

Next

Additional steps required after an Oracle snapshot restore

Feedback

Was this page helpful?