Upgrading

Plan an MRBS upgrade as an application and database change.

Before the upgrade

1. Read the release notes for every version being crossed.
2. Back up the database and verify that it can be restored.
3. Back up config.inc.php, custom themes, site FAQ files, and other local changes.
4. Record the current PHP, database, authentication, and mail configuration.
5. Schedule a maintenance window for production systems.

Warning

Do not overwrite the installation and assume local changes will survive. Compare your configuration with the new sample and reapply intentional overrides.

Replace application files

Install a clean copy of the new release. Carry forward site-specific files, not old application files.

In particular:

• start from the new config.inc.php-sample;
• transfer required values from the old config.inc.php;
• reapply custom themes and FAQ content deliberately; and
• do not replace new defaults files with old copies.

Database upgrade

MRBS upgrades supported historical schemas automatically when the application first runs. It may request database credentials with rights to alter tables.

Use a dedicated upgrade account if the normal runtime account cannot change the schema.

Verification

After upgrading, test:

• login and logout;
• administrator access;
• day, week, and month views;
• create, edit, and delete;
• recurring bookings;
• approval and registration where enabled;
• search, reports, and export;
• email delivery; and
• background or integration paths such as LDAP, SAML, or CMS login.

Check the administrator Help page for the expected MRBS and schema versions.

Rollback

A rollback requires both the previous application files and a compatible database backup. Restoring only the files may leave the old application connected to a newer schema.