You can upgrade an MDriven application safely by creating recoverable backups before you update MDriven Server, MDriven Turnkey, or upload an updated model; this guide is for administrators responsible for a running application.

Upgrade workflow

An upgrade can change the server and Turnkey application, the model running on MDriven Server, or both. Create a restore point before making any of these changes so that you can recover if an update causes data loss or does not behave as expected.

For example, if you plan to upload a revised model to a production MDriven Server, first save the current model, the Admin database snapshot, and the model data XML file. Do not rely on the new model as the recovery copy.

1. Back up the application and its data by following MDriven Backup & Restore Guide. Back up all of the following:
   • The Admin database snapshot. The Admin database contains application data, including the model and its metadata, user accounts, roles, and access rights.
   • A copy of the model currently running on MDriven Server. If you do not have that copy, download the model through the MDriven Designer Cloud Connection dialog.
   • The model data as an XML file from the MDriven Designer Migrate window.
2. Deploy the updated MDriven Server and Turnkey application using the guide for your hosting environment. For deployment options, see Deployment.
3. Upload the updated model to MDriven Server when your upgrade includes a model change.
4. Check that MDriven Server is running before continuing. When creating an Admin database snapshot, a 502 Bad Gateway expected due to server forced restart message is normal; check the server status afterward and restart MDriven Server if it does not start after some seconds.
5. Validate the upgraded application with the application data in place. Keep the backup files available until you have confirmed the result.

Recover from an unsuccessful upgrade

You can return to the saved application state by restoring the backed-up model and model data.

1. Upload the previously backed-up model.
2. In MDriven Designer, open the System Prototype and select the MDriven Server tab.
3. Select Start System. When the connection succeeds, the Migrate button is enabled.
4. Select Migrate, then use the button that reads the XML data file.
5. Select Chunk Save to upload the model data to MDriven Server.
6. Save in the System Prototyper window to persist the loaded data permanently in the database.

Follow the complete restore procedure in MDriven Backup & Restore Guide.

Moving from .NET Framework to .NET Core

Use Migrating From MDriven .NET Framework to .NET Core when the upgrade also moves a Visual Studio project from .NET Framework to .NET Core.

For Visual Studio projects that target .NET Framework, change the project target framework to .NET Core and confirm that the project compiles without errors. Use the latest MDriven Designer for model projects and the latest MDriven Visual Studio extension for Visual Studio model projects from the MDriven Downloads page.

If Turnkey is blocked from connecting after this migration, use PwdReset to set a new password for user a.

See also

• MDriven Backup & Restore Guide
• Migrating From MDriven .NET Framework to .NET Core
• Deployment