MongoDB restore operation completes successfully from the Commvault side. The restore job finishes with a successful status, and the database files are restored correctly.

Issue Summary:

The MongoDB restore operation completes successfully from the Commvault side. The restore job finishes with a successful status, and the database files are restored correctly.

Observed behavior:

• The mongod process starts automatically after the restore.

• MongoDB is accessible using mongosh.

• Authentication works successfully.

• The database is operational.

• However, the MongoDB service is shown as:

  systemctl status mongod
  Active: inactive (dead)
  

• The mongod process is running independently:

  ps -ef | grep mongod
  

• The process is not associated with the mongod.service.

Additional observations:

• The restore logs indicate that CVMongoDBUtil launches the recovery process.

• The MongoDB process starts successfully but is not managed by systemd.

• Starting the service manually using:

  systemctl start mongod
  

  changes the service state to:

  Active: active (running)
  

Temporary workaround implemented:

• A post-recovery script was configured:

  #!/bin/bash
  sleep 30
  
  if pgrep mongod >/dev/null; then
      pkill mongod
      sleep 5
  fi
  
  systemctl start mongod
  

• Post Recovery Command:

  /bin/bash /opt/mongo_restart.sh
  

Request:
Please confirm whether this behavior is expected during MongoDB restores or whether the recovery workflow should start MongoDB using the systemd service (systemctl start mongod) instead of launching the mongod process directly.