Last post 04-02-2020, 1:53 PM by ApK1. 7 replies.
Sort Posts: Previous Next
  • MongoDB
    Posted: 04-01-2020, 4:23 PM

    Hi all.


    The MongoDB agent, is that only working with intellisnap or can you disable intellisnap?


    We are running 3 servers with MongoDB in a cluster on Vmware, so are not able to use Intellisnap.


    Any one knows the answer?




  • Re: MongoDB
    Posted: 04-02-2020, 1:47 AM


    Intellisnap is mandatory for backing up mongodb cluster using MongoDB ida. If the db path is on a lvm(linux) or on local volume(windows) we would be able to use native snap engine. Can you provide more details about the configuration.

  • Re: MongoDB
    Posted: 04-02-2020, 3:16 AM

    We have 3 windows servers running in vmware with disks (C:\OS D:\MongoDB) on datastores. You write "or on local volume(windows)"so the native snapshots will not work when the disks are on vmware datastores?

  • Re: MongoDB
    Posted: 04-02-2020, 3:45 AM

    This is expected to work. Native snap engine will be supported on the disks from vmware datastore. 

  • Re: MongoDB
    Posted: 04-02-2020, 4:19 AM

    Thats great news.


    Any now, when trying to run the backup I get this error:


    0x80070490:{MongoDbIDA::MongoDbBackupCoordinator::populateNodeAndTaskList(493)} + {MongoDbIDA::MongoDbBackupCoordinator::GetSecondaryDataPath(332)/W32.1168.(Element not found.)-Could not figure out the client node name to use for the secondary MongoDB Hostname [].}



    In the instance properties (details) field I can see the client names and the hostnames for all 3 servers. Eventhough the hostnames are populated with IP adresses, is this normal and have you seen the above error message before?

  • Re: MongoDB
    Posted: 04-02-2020, 4:33 AM

    Can you pleaes escalate this with logs and staged db. It would help in analyzing and providing a solution.

  • Re: MongoDB
    Posted: 04-02-2020, 5:36 AM



    I have now created a ticket.

  • Re: MongoDB
    Posted: 04-02-2020, 1:53 PM

    Hostnames must be same in the CommCell Console as configured in the Database, this solved the problem.

    Mine was different from what was configured in the DB and comcell, as the hostnames in the DB was set with IP adresses and in comcell with FQDN.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy