The existing documentation considers that the repository can easily re-created:

“Backing up a repository

A repository database is a normal DBMS database that can be backed up with other data managed by the DBMS. However, since the repository is synchronized from data stored in Meridian Enterprise, the repository database is not at a high risk of loss. It can be easily re-created by resynchronizing it from its source vault either manually or by the next run of the synchronization job scheduled task. However, because full synchronization can take a considerable length of time depending on the size of the source vault, you might want to back up the repository database anyway so that it can be restored more quickly.”

But it is not the case if you also need to migrate all the comments, redlines and potential attachments added by explorer users. The tables related to the comments are linked to the user’s tables managed in the configuration database.

In this case, the only way to migrate Meridian on new servers is to also migrate the configuration and repositories databases.

I think that the Enterprise server administration guide should be completed with a detailed chapter related to backup and restore procedures.

The only available information about this procedure can be found in a KB article called: "HOW TO COPY AN ENTERPRISE SERVER ENVIRONMENT FOR TESTING OR DEVELOPMENT". This article should be developed and take place in the  Enterprise Server administration guide.

Thanks,

Pierre