Considerations and Limitations

This section lists considerations and known limitations of Veeam Explorer for MongoDB.

General

When Veeam Explorer for MongoDB is installed on a server on which both Veeam Backup & Replication and Veeam Backup for Microsoft 365 are installed, the notification settings will be inherited from the Veeam Backup & Replication Global Notification settings.

Restore

Consider the following when planning to restore MongoDB data:

Veeam Explorer for MongoDB does not support restore using PowerShell Direct, VIX API or vSphere Automation API.
Before you use TLS authentication, make sure that the Certificate Authority file of the target replica set is added to the Trusted Root Certification Authorities certificate store of the mount server associated with the backup repository.
Before you restore MongoDB data to another server, make sure MongoDB is installed on the target server. For more information on supported MongoDB versions, see System Requirements.

Before you restore MongoDB data, make sure that the target system has the same MongoDB version as the one installed on the backed-up system.

Restore to MongoDB sharded clusters is not supported.
Restore to machines running MongoDB Community Edition is not supported.
Point-in-time restore of MongoDB data is not supported. You can only restore your data to the latest state in your backup file.
Restoring an entire MongoDB instance does not preserve replica set infrastructure. For more information on how to redeploy the replica set, see the MongoDB Manual.

When restoring collections, you can only restore to the primary node of the target MongoDB replica set.
You cannot restore MongoDB data from multiple backups in parallel to the same target machine.
You cannot restore MongoDB data encrypted with native MongoDB encryption.