Can the SystemLink Mongo Database Store Data on a Different Drive?

Updated Dec 12, 2025

Reported In

Software

  • SystemLink Base
  • SystemLink Server

Issue Details

Is it possible for SystemLink Base / SystemLink Server to use the local Mongo database engine that it installs on the C: but have it configured to send its database disk footprint to a location that is NOT on the C: drive?  If so, how do I check if its Mongo is configured to send its database files to the non-default location, both now and in the past?

Solution

  • The easiest way to check the current disk footprint of the Mongo database is to launch the SystemLink Server Configuration dialog and look in the NoSqlDatabase section in the Database path field:
     
         
  • You can check 2 different ways for past configurations of the Mongo database disk footprint path.
    • If you have backed up the mongodb.conf file in the past, you can find the disk footprint path in the dbPath field
      • systemLog:
          traceAllExceptions: true
          verbosity: 0
        storage:
          dbPath: D:\NoSqlDatabase\db
          wiredTiger:
            engineConfig:
              cacheSizeGB: 1
        net:
          bindIp: localhost
          port: 27018
          ipv6: false
        security:
          authorization: enabled
    • If you have exported a Troubleshooting Report, you can check the in all the  ...\logs\MongoDB\log*.txt files for entries of these types:
      • 2025-11-14T03:02:06.116-0500 I  CONTROL  [initandlisten] MongoDB starting : pid=17120 port=27018 dbpath=D:\NoSqlDatabase\db 64-bit host=ito125236
      • 2025-11-14T03:02:06.116-0500 I  CONTROL  [initandlisten] options: { config: "C:\ProgramData\National Instruments\Skyline\NoSqlDatabase\mongodb.conf", net: { bindIp: "localhost", ipv6: false, port: 27018 }, security: { authorization: "enabled" }, storage: { dbPath: "D:\NoSqlDatabase\db",...

Additional Information

It is of course also possible to configure SystemLink Base / SystemLink Server to use a remote Mongo database instance or service, where both the Mongo database engine and the disk footprint are located on a different server from the one SystemLink Base / SystemLink Server is installed on.