When you migrate from one Microsoft SQL Server to another, the new Microsoft SQL Server must run the same or later version of Microsoft SQL Server, and the Microsoft SQL Server edition (Enterprise or Standard) must also be the same or higher
than that of the old Microsoft SQL Server.
In other words, do not migrate vault databases from Microsoft SQL Server to an older
version or lower edition of Microsoft SQL Server.
See also Important tasks after installation, vault creation, or vault migration for
a checklist of tasks that we recommend to be done with vault creation.
To migrate a vault database from one Microsoft SQL Server to another:
-
Open M-Files Admin.
-
In the left-side tree view, expand a connection to M-Files server.
-
Open the context menu of a vault and select .
-
Open Microsoft SQL Server
Management Studio and take a full backup of the vault
database.
-
Restore the database to the new Microsoft SQL Server as a new database.
-
In M-Files Admin, open the context menu of the document vault and select
Properties.
Result:The Document Vault Properties dialog opens.
-
Open the Advanced tab.
-
Under the Use Microsoft SQL Server option, select
Define....
Result:The Document Vault - Microsoft SQL Server dialog opens.
-
In the Server name field, specify the name of the new Microsoft SQL Server.
-
In the Database name field, specify the name of the new database.
-
In the Administrator credentials and Basic user
credentials sections, specify the new authentication settings.
-
Select OK to close the Document Vault - Microsoft SQL Server dialog and then select OK
to close the Document Vault Properties dialog.
-
In the left-side tree view, open the context menu of the vault and select .
From this point forward, the M-Files server will
access the vault database from the new Microsoft SQL Server.
After you migrate the vault database to the new Microsoft SQL Server, you must create a backup job for the new database in Microsoft SQL Server
Management Studio on the new Microsoft SQL Server.
For more details and recommendations, see M-Files Backup Policy.