What does "Switching/migrating to external database is recommended" mean?

[Axel.]

I got this message and wondering if migration to an external database is really needed.

What are the limitations of the internal database?

Our environment: vSphere Cluster with 7 hosts, about 130 VMs in the backup and a repository size of 120 TB (8 TB deduplicated/compressed).

Everything is running well, the backup each night will be done within 2-3 hours. The performance is good enough for us.

Do we have to many VMs? Is the repository too big? What is the problem with the internal database.
I want to avoid switching to another database because that would add a lot of complexity and additional maintenance efford. But I want to understand the limitations.

Thanks for an answer.

[The Official Moderator]

On 9/22/2025 at 9:27 PM, Axel. said:

I got this message and wondering if migration to an external database is really needed.

What are the limitations of the internal database?

Our environment: vSphere Cluster with 7 hosts, about 130 VMs in the backup and a repository size of 120 TB (8 TB deduplicated/compressed).

Everything is running well, the backup each night will be done within 2-3 hours. The performance is good enough for us.

Do we have to many VMs? Is the repository too big? What is the problem with the internal database.
I want to avoid switching to another database because that would add a lot of complexity and additional maintenance efford. But I want to understand the limitations.

Thanks for an answer.

This message brings a new feature of an external database to customer's attention.
If there are no issues and the customer is satisfied with NAKIVO performance, there is no need to switch.

If there are some issues, it;s better to contact NAKIVO support to resolve them.

The message on the UI about switching to an external database may be ignored.

[Axel.]

Thank you for the answer. So we will ignore it.
The warning is a little bit misleading and it got me a bit confused.