Skip to main content
Revo Backup provides multiple ways to create and manage backups - through the in-game UI, commands, and txAdmin console.

​
Accessing the Backup System

​
In-Game Methods

UI Interface

Command: /backup
Key: F6
Description: Opens the full backup management interface

​
Server Console (txAdmin)

For server administrators, Revo Backup provides powerful console commands for backup management:

Create Backup with Label

makebackup "Daily Backup"
makebackup "Before Update"
makebackup "Emergency Backup"
Purpose: Creates a manual backup with a custom label Format: makebackup "[label]" Note: Labels help identify the purpose of each backup

Delete Backup by ID

deletebackup 1
deletebackup 5
deletebackup 12
Purpose: Removes a specific backup by its ID Format: deletebackup [id] Note: Use the backup list to find the correct ID

​
Backup File Storage

All backup files are stored in the script’s root folder for easy access and management.

​
File Location

/resources/revo_backup/
├── backup_2024-01-15_12-00-00.sql
├── backup_2024-01-16_12-00-00.sql
├── backup_2024-01-17_12-00-00.sql
└── backup_2024-01-18_12-00-00.sql
├── config.lua
├── fxmanifest.lua
└── ...

​
What’s Included in Backups

  • All Tables: Every table in your database
  • Table Structure: Column definitions, data types, constraints
  • Indexes: All database indexes for optimal performance
  • Triggers: Database triggers and stored procedures
  • Player Data: All player information and progress
  • Server Data: Items, vehicles, properties, etc.
  • Transaction History: All financial and gameplay records
  • Configuration Data: Server settings and customizations
  • Foreign Keys: All relationships between tables preserved
  • Referential Integrity: Data consistency maintained
  • Cascading Rules: Update and delete rules preserved
  • Constraints: All database constraints intact

​
Database Restoration

​
Step-by-Step Restoration Guide

1

Access phpMyAdmin

  1. Open your web browser and navigate to phpMyAdmin
  2. Log in with your database credentials
  3. Select your database from the left sidebar
2

Clear Existing Data (Optional)

If you want to restore over existing data:
  1. Click on your database name
  2. Select all tables (Ctrl+A or Cmd+A)
  3. Choose “Drop” to remove existing tables
This will permanently delete all current data. Make sure you have a backup!
3

Import Backup File

  1. Click the “Import” tab at the top
  2. Click “Choose File” or “Browse”
  3. Navigate to your backup file location: 
    /resources/revo_backup/
  4. Select your desired backup file (e.g., backup_2024-01-15_12-00-00.sql)
4

Configure Import Settings

  1. Format: Leave as “SQL” (default)
  2. Character Set: Usually “utf8mb4” or “utf8”
  3. Partial Import: Leave unchecked for complete restoration
  4. SQL Compatibility Mode: Leave as “NONE” unless needed
5

Execute Import

  1. Click “Go” or “Import” button
  2. Wait for the import process to complete
  3. Check for any error messages
  4. Verify your tables and data are restored

​
Alternative Restoration Methods

  • MySQL Command Line
  • MySQL Workbench
  • HeidiSQL
mysql -u username -p database_name < backup_file.sql
Usage:
  1. Open terminal/command prompt
  2. Navigate to backup file location
  3. Run the command above
  4. Enter your MySQL password when prompted

​
Backup Management Best Practices

Regular Backups

  • Set up automatic daily backups
  • Create manual backups before major updates
  • Test restoration process periodically

Storage Management

  • Monitor backup folder size
  • Use automatic cleanup settings
  • Keep backups in multiple locations

Labeling System

  • Use descriptive labels for backups
  • Include dates in manual backup labels
  • Document backup purposes

Testing

  • Regularly test backup restoration
  • Verify data integrity after restore
  • Keep restoration documentation updated

​
Troubleshooting Restoration

Common Issues:
  • File size too large (increase PHP limits)
  • Character set mismatches
  • Insufficient database permissions
Solutions:
  • Use command line import for large files
  • Check character set settings
  • Verify database user permissions
Symptoms:
  • Some tables missing
  • Data inconsistencies
  • Foreign key errors
Solutions:
  • Check for SQL errors during import
  • Verify backup file integrity
  • Import in smaller chunks if needed
Large Database Restoration:
  • Use command line tools for better performance
  • Increase MySQL timeout settings
  • Consider restoring during low-traffic periods
Always test your restoration process with a copy of your database before performing a real restoration. This ensures you’re familiar with the process and can identify any potential issues.
⌘I