Frequently Asked Questions
Frequently Asked Questions: M-Files
Migrating Server Instructions Without Upgrading
Posted by Ramez Mohsene (M-Files) on 22 June 2018 09:15 PM

Here's an outline for a procedure to move the whole M-Files installation to a new server:

 

1. Take backups of the master database and document vaults.

 

2. Shut down the M-Files Server services on the current server computer to prevent users from accessing the vaults during the server migration.

 

3. Install M-Files Server and Server Tools on the new server computer.

 

4. Restore the master backup taken from the original server to the new server and install the license key. If you have customized notification templates or additional M-Files tools, copy them to the new server manually.

 

5. Install SQL Server on the new server computer and restore/copy the original vault databases to the new server. Copy the file data to a new location separately, if it is stored outside the SQL database.

**NOTE: This is only needed if you are using an SQL server for the database. If you are using Firebird, skip this step.**

 

6. Attach the vaults from the new SQL Server instance to the new M-Files server using their original identities.

**NOTE: This is only needed if you are using an SQL server for the database. If you are using Firebird, simply restore the vault database..**

 

7. Make whatever changes are required in your firewalls/routers to allow traffic to the new server's IP address, if the new server does not use the same IP as the old server.

 

8. Update your DNS to point to the new server, in case you want to use the same DNS name for the new server. If you don't use the same DNS name for the server, then you probably need to update vault connection settings on all client workstations.

(1 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case