Brazil's biggest MU Online portal — since 2003
Tutorial Intermediate Server

How to back up your MU server database

Protect your players' work: learn to set up automatic SQL Server backups for your MU Online server.

VI ViciadosMU Team · Updated on 30 jun 2026 · ⏱ 6 min read

A server without backups is an accident waiting to happen. Disk failure, intrusion or human error can wipe out months of player progress. Here's how to protect yourself.

Atenção: Backup is not optional. The question is never "if" something will go wrong, but "when". Those with a recent backup recover in minutes; those without lose everything.

What needs to be saved

The essential is the database (MuOnline and ranking/event databases). It holds accounts, characters, items and guilds.

How to back up SQL Server

  1. In SSMS, right-click the database → Tasks → Back Up;
  2. Choose the Full type and the destination for the .bak file;
  3. To automate, create a Job in SQL Server Agent that runs the backup at a set time.
BACKUP DATABASE MuOnline
TO DISK = 'D:\backups\MuOnline.bak'
WITH FORMAT, INIT;

Automate and take it off-site

  • Schedule the backup daily at a low-traffic time;
  • Copy the file elsewhere (another disk or the cloud);
  • Keep a few versions (e.g., the last 7 days).
Dica: Test the restore from time to time. A backup that's never been tested may be corrupted — and you only find out at the worst moment.

Quick recovery plan

  1. Identify the problem (failure, intrusion, error);
  2. Stop the MuServer services;
  3. Restore the most recent, intact backup;
  4. Start the server and validate.

Perguntas frequentes

How often should I back up?

For active servers, daily (or more frequent) is ideal. The more activity, the more you lose if something goes wrong without a recent backup.

Where should I store backups?

Never only on the same server. Keep copies elsewhere (another disk, the cloud) — if the machine fails, a local backup is gone with it.

VI

ViciadosMU Team

Equipe editorial do ViciadosMU — portal de MU Online no ar desde 2003.

Keep reading

Related articles