Data, backups, imports, and exports

Open Data before a migration, major cleanup, or reset. Everything on this page is scoped to the currently selected instance unless the page explicitly says Global Kompendium data and you are a global administrator.

Database backups

Kompendium creates automatic daily backups and keeps them for the displayed retention period. It also keeps one monthly copy. Manual backups stay until you choose to remove them.

Press Back up this instance before an import, reset, or large configuration change. The backup is created for the selected instance only. Wait for its status to become completed, then press Download to keep a copy somewhere you control.

The backup table has five columns:

• Created is when the backup job began.
• Kind tells you whether it is daily, monthly, or manual.
• Status tells you whether it is pending, running, completed, or failed. A failed row may show a short error message.
• Size is the generated file size.
• Download appears only after a completed backup.

The Delete button is available only for manual backups. It removes that manual recovery copy, so download it first if you may need it later. Automatic daily and monthly retention is managed by Kompendium.

Global administrators may also see Back up global data and a separate global table. That backup contains account, billing, instance, and other main-system data. It is not a replacement for an instance backup when you are protecting a bot’s collectibles and player records.

Create a data job

The form creates an import or export job. It does not run an import the instant you choose a file; you create the job, then use the Recent jobs section to run it and read its log.

Use the switch at the top to choose Import or Export.

Import

For a normal Ballsdex migration, leave the form on Import, choose Ballsdex as Source, Kompendium as Destination, and SQL as Data Type. Press Choose File, select your SQL dump, then press Create import job.

For a Kompendium configuration backup, use Kompendium as both source and destination and select JSON config. For image and asset archives, select Media.zip. The file picker accepts .sql, .json, and .zip; selecting a matching file updates the data type for you.

The dashboard locks invalid combinations. For example, a JSON configuration import is Kompendium-to-Kompendium, and the common SQL migration path targets Kompendium. This prevents a job whose source and destination do not make sense.

Export

Turn the switch to Export. Kompendium becomes the source and no upload file is needed. Choose the destination and available data type, then press Create export job. JSON configuration is import-only in this form, so the dropdown hides it for exports.

Recent jobs and logs

Each job row shows its ID, creation date, operation, source and destination, type, status, and actions.

New or failed jobs show Run. Press it to start the job or retry it after fixing the file or configuration. Press Log at any time to open the job log. The log window shows the current status, progress bar, detailed lines, and a problem card if the job fails. Keep it open while an import is running; it refreshes as the job progresses.

Do not create several imports of the same dump while one is still running. If a job fails, read the log first, fix the underlying file or configuration, and then press Run to retry that job. Taking a manual backup before an import gives you a clean rollback point if the imported data is not what you expected.

Before a reset or migration

1. Create a manual instance backup and download it.
2. Confirm the instance in the sidebar is the correct one.
3. Verify the source file type and that it is complete, not a partial browser download.
4. Create one job and inspect its log.
5. Test the imported bot before inviting players or deleting old data.

Use the dedicated migration guide for the full Ballsdex preparation checklist.