Hi Microvellum Support,

I have a few questions regarding the export/backup functionality within Database Management.

Is there a maximum size limitation for a database exported through Database Management? If so, is there any way to increase this maximum export size?

We are trying to archive a relatively large amount of historical project data. For example, if the selected projects contain approximately 20 GB of data, is there a way for Database Management to automatically split the export into multiple archive databases rather than attempting to create one large database and eventually returning a size-limit error?

Ideally, we are looking for functionality similar to:

• Archive 01 – first group of projects

• Archive 02 – second group of projects

• Archive 03 – third group of projects

• Archive 04 – fourth group of projects

• Archive 05 – fifth group of projects

Each archive could remain below the maximum supported database size.

My understanding is that Database Management currently does not show the database size associated with each individual project. If that is correct, it also makes it difficult to manually determine how many projects can safely be included in each archive before reaching the export size limit.

Could you please confirm:

1. What is the maximum supported size for a database exported through Database Management?

2. Can this maximum size be increased?

3. Can Database Management automatically split a large export into multiple archive databases?

4. Is there a way to determine the approximate database size of individual projects before exporting them?

5. If automatic splitting is not available, what is Microvellum's recommended method for archiving a large number of historical projects while keeping each archive within the supported size limit?

Our goal is to archive older project data in manageable groups so that we can reduce the size of the active Microvellum database without risking incomplete or failed exports.

Thank you.