FiveM Backups, Restarts, and the Ops That Save a City

Players forgive a restart they knew about. They do not forgive a restart that ate the cars. The unglamorous work, backups and a schedule, is the difference between a bad patch and a dead server.

Back up the database on a timer

Inventory, vehicles, properties, and characters live in the database. The server files are not a backup of any of that. Dump the database at least daily, keep seven days, and keep one copy somewhere that is not the game box. Test a restore once, on a spare database, before you need it. A backup you have never restored is a rumor.

Take an extra dump before any framework update, any inventory migration, and any night where you plan to change more than one resource. Name the file with the date and the reason.

A restart schedule people can remember

Pick a quiet hour and use it most days. Post it in the announcements channel and on the connect screen. Warn in-game ten minutes ahead, then five. A restart with no warning during a planned scene is how you lose the groups who make the city feel occupied.

Daily restarts also clear leaked entities and scripts that bloat until the tick rate sags. They are not a substitute for fixing the leak. If you need three restarts a day to stay playable, read the performance guide and find the resource.

Update one resource, then boot clean

Download escrowed updates from the Cfx.re Portal, replace the resource folder, and restart. Read the changelog on the product page first. Kyros packs and scripts ship notes for a reason: a new item name or a config key is better discovered in the note than in a ticket.

Do not update the framework, the inventory, and three weapon packs in the same restart. If the console throws, you want one suspect. Keep the previous folder for a day so you can put it back without re-downloading under pressure.

When a patch goes wrong

Stop the server. Restore the resource folder you kept. If the database changed shape, restore the dump you took before the update. Boot, confirm a test character still has a car and a weapon, then tell players what happened in two sentences. Silence makes it sound like the wipe was the plan.

If the damage is item metadata from a bad merge, a full restore is cleaner than hand-editing rows you half understand. Write down what broke so the next update does not repeat it.

A one-page runbook

Leave this where staff can find it:

• Where backups live and who can reach them
• The restart hour
• Who is allowed to ensure resources on production
• The Cfx.re account that owns the grants

Ops is how a soft launch becomes a server that is still here in month six. The city can be loud. The process should be dull.