Backing Up Microsoft SQL Server Databases

The administrator is responsible for making backup copies and timing the backup copies of the vault database. Backup copying is done with SQL Server's own management tools and backup copying solutions offered by third parties. When restoring a backup copy, the administrator first returns the vault database to the SQL Server, and then reattaches the vault to M-Files with the Attach Document Vault function.

If your file data is stored on the file system separately from the database, you must back up both the Microsoft SQL database and the files on the file system separately.

For more instructions, see the M-Files knowledge base article M-Files Backup Policy.

Important information

  • Always back up the SQL database (metadata) first and then the file system data (object files) to avoid references to non-existing object files. Do not run M-Files Server optimization after you have backed up the SQL database. Otherwise, the files that have been marked for destruction are removed.
  • Do not back up an active M-Files system with a snapshot of the file system where its data is stored. This can create a damaged or unusable backup because write operations to files (most importantly, the database engine files) can be ongoing and, thus, incomplete. If you use full virtual machine (VM) snapshots for backups, make sure that the VM software fully supports creation of snapshots of an active system. This means that the software can restore the system to exactly the same state, including the memory and CPU states.