Backup & Restore Guide - QBCore Guide for FiveM

Introduction

This tutorial turns Backup & Restore Guide into a clean, developer-friendly guide for QBCore/FiveM. You will follow a step-by-step flow, copy the relevant code patterns, and learn the “why” behind the setup.

Requirements

• QBCore installed and running on a dev server
• Basic Lua knowledge and comfort reading FiveM patterns
• A test workflow for iterating safely (dev server, not production)
• Optional: a code editor with Lua/FiveM helpers (VS Code recommended)

Step-by-Step Guide

Step 1: Overview

In this step, you will apply the overview concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 2: Quick Backup Commands

In this step, you will apply the quick backup commands concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 3: Essential Backup Commands

In this step, you will apply the essential backup commands concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 4: Quick Restore Commands

In this step, you will apply the quick restore commands concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 5: Comprehensive Backup Strategy

In this step, you will apply the comprehensive backup strategy concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 6: 1. Automated Backup System

In this step, you will apply the 1. automated backup system concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 7: 2. Incremental Backup System

In this step, you will apply the 2. incremental backup system concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 8: 3. Database-Specific Backup

In this step, you will apply the 3. database-specific backup concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Code Example

# Complete server backup (recommended before any changes)
./scripts/backup-complete.sh
 
# Database-only backup  
mysqldump -u username -p database_name > backup-$(date +%Y%m%d-%H%M%S).sql
 
# Resources-only backup
tar -czf resources-backup-$(date +%Y%m%d).tar.gz resources/
 
# Configuration backup
tar -czf config-backup-$(date +%Y%m%d).tar.gz server.cfg txAdmin/config/

Tips & Best Practices

• Keep authority on the server: validate inputs before money/database operations.
• Start with one resource/module at a time, then refactor after you verify it works.
• Use callbacks for request/response flows and events for push/UX updates.
• When you run loops, avoid freezes: always yield with Wait() (client/server) and cache hot values.