Resource

Backing Up and Maintaining Your AI PHP Apps Product

Learn how to safely back up and maintain your AI PHP Apps installation, including application files, MySQL databases, updates, backup schedules, and recovery planning.

Why Backups Matter

Your AI PHP Apps product contains more than application files. Depending on the product, your database may contain settings, customer information, generated content, application history, and other important business data.

A reliable backup gives you a recovery point if something goes wrong.

Backups are especially important before installing updates, changing server settings, modifying application files, or moving your installation to another hosting provider.

What Should You Back Up?

A complete application backup normally includes two major components:

  • Your application files
  • Your MySQL database

You need both if you want to be able to fully restore the application.

1. Back Up Your Application Files

Your application files include the PHP source files, assets, configuration files, uploaded documents, and other files used by the application.

Most hosting providers allow you to create a compressed ZIP archive through their file manager.

You can also download the application files using FTP or another file transfer tool.

Important: Make sure your backup includes any private configuration files and user-uploaded files that are part of your installation.

2. Back Up Your MySQL Database

Your database contains information that cannot be recovered simply by restoring the PHP files.

Most shared hosting environments provide phpMyAdmin, which can be used to export your database.

Using phpMyAdmin

  1. Open phpMyAdmin from your hosting control panel.
  2. Select the database used by your AI PHP Apps product.
  3. Choose Export.
  4. Select the SQL format.
  5. Download the exported database file.

The resulting SQL file can be used to restore the database if necessary.

3. Back Up Before Every Application Update

Create a fresh backup before installing an application update.

Your pre-update backup should include both the application files and database.

This gives you a recovery option if an update is interrupted or your particular hosting environment encounters an unexpected compatibility issue.

4. Use a Regular Backup Schedule

The right backup schedule depends on how frequently your application data changes.

A small business application that changes occasionally may only require periodic backups, while an application receiving new data every day should be backed up more frequently.

Example Backup Schedule

  • Before every update: Full files and database backup
  • Weekly: Database backup
  • Monthly: Full application backup
  • After major configuration changes: Full backup

This is only a general example. Adjust the schedule based on how important your data is and how often it changes.

5. Do Not Store Every Backup on the Same Server

A backup stored only on the same hosting account may be lost if the entire account becomes unavailable or compromised.

Keep at least one recent backup in another secure location.

Possible locations include:

  • Your local computer
  • An external drive
  • A trusted cloud storage provider
  • Your hosting provider's separate backup system

6. Keep Multiple Recovery Points

Do not automatically replace your only good backup every time you create a new one.

Keeping several recent backups can be valuable because problems are not always discovered immediately.

For example, if corrupted data went unnoticed for several days, your newest backup might already contain the same problem.

7. Test Your Backups

A backup is most valuable when you know it can actually be restored.

Periodically verify that your backup archives open correctly and that your SQL database exports contain the expected tables and data.

Businesses with more advanced hosting environments may also choose to test restoration using a separate staging installation.

8. Keep Track of Application Changes

If you manually customize application files, keep a record of those changes.

Custom modifications may need to be reviewed when installing future software updates.

A simple change log can save considerable time when maintaining your application later.

9. Review Available Updates

Periodically check for new application releases and review what has changed before updating.

Updates may include:

  • Bug fixes
  • Security improvements
  • Compatibility updates
  • Performance improvements
  • New features

Do not make major application or server changes without having a current backup available.

10. Monitor Your Hosting Environment

Occasionally review your hosting environment to make sure it continues to meet the application requirements.

Things worth checking include:

  • Available disk space
  • PHP version
  • Database availability
  • SSL certificate status
  • Email functionality
  • Scheduled tasks or cron jobs, when used

Restoring From a Backup

The exact restoration process depends on your hosting provider, but a typical recovery involves restoring the application files and importing the corresponding MySQL database backup.

Whenever possible, restore files and database backups from the same recovery point so the application remains synchronized.

Maintenance Checklist

  • Back up application files
  • Back up the MySQL database
  • Create a backup before every update
  • Keep an off-server backup copy
  • Maintain multiple recent recovery points
  • Verify backups periodically
  • Document custom modifications
  • Review application updates
  • Monitor server requirements

A Few Minutes of Maintenance Can Save Hours Later

Self-hosted applications give you ownership and control, and a simple backup routine helps protect that investment.

You do not need an elaborate maintenance system. Consistent backups, sensible updates, and occasional server checks are enough to provide a dependable foundation for most small-business installations.

Need more help?

If you have questions about setting up an AI PHP Apps product, contact support and we’ll help point you in the right direction.

Contact Support