-
-
Notifications
You must be signed in to change notification settings - Fork 0
Restore Backup
TeknoParrot Manager backs up your entire UserProfiles folder automatically at the start of every run, backs up LaunchBox's own library files before every direct write (since v0.98), and backs up your Postgres databases before every Postgres Setup run (since v0.99). Mode 9 lets you restore any of these from inside the script -- no File Explorer needed.
When you choose mode 9, you're first asked which backup to restore:
- TeknoParrot UserProfiles backup
- LaunchBox library backup -- only relevant if you've used the direct LaunchBox integration
- Postgres database backup -- only relevant if you've used Postgres Setup
<TeknoParrotRoot>\UserProfiles\FullBackup\<date_time>\
If backup folder creation fails (disk full, permissions), the script exits rather than proceeding without a restore point.
- Close TeknoParrot completely (the script checks and will stop if it detects TeknoParrot is still running).
- Run the script, choose mode 9 -- Restore backup, then 1) TeknoParrot UserProfiles backup.
- The script lists all available backups, most recent first, with file counts.
- Pick one by number.
- Type
YESto confirm. - The restore runs. Re-open TeknoParrot to use the restored profiles.
If you need to restore outside the script:
- Close TeknoParrot completely.
- Copy the
.xmlfiles from any backup subfolder back into<TeknoParrotRoot>\UserProfiles\, overwriting the current files. - Reopen TeknoParrot.
Scripts\LaunchBoxBackups\<date_time>\
Only the specific files the direct LaunchBox integration was about to change are backed up (Emulators.xml, Platforms.xml, and the target platform file(s)) -- never LaunchBox's entire Data\ folder, since some platform files run 20+ MB. If the backup fails, nothing is written to LaunchBox in the first place.
- Close LaunchBox and BigBox completely (the script checks and will stop if either is still running).
- Run the script, choose mode 9 -- Restore backup, then 2) LaunchBox library backup.
- The script lists all available backups, most recent first, with file counts.
- Pick one by number.
- Type
YESto confirm. - The restore runs, copying each backed-up file back to its original relative location under your LaunchBox root.
If you need to restore outside the script:
- Close LaunchBox completely.
- Copy the files from
Scripts\LaunchBoxBackups\<date_time>\back into LaunchBox'sData\folder at the matching relative path, overwriting the current files. - Reopen LaunchBox.
Scripts\PostgresBackups\<date_time>\<dbname>.backup
Every existing Postgres database belonging to a registered, Postgres-needing game is backed up (via pg_dump, custom format) every time Postgres Setup runs, before anything else happens. Skipped silently if PostgreSQL isn't installed yet, or no databases exist -- nothing to back up on a first run.
- Run the script, choose mode 9 -- Restore backup, then 3) Postgres database backup.
- The script lists all available backups, most recent first, with the database names in each.
- Pick one by number.
- Type
YESto confirm -- this replaces the current content of each database being restored. - The script drops and recreates each database from its backup (your existing PostgreSQL install is not touched, just the database content).
If you need to restore outside the script, use pg_restore directly against the .backup file with PostgreSQL's own tools (pg_restore.exe in C:\Program Files (x86)\PostgreSQL\8.3\bin\).
- Restore mode cannot run with
-Unattended-- it requires you to pick a backup interactively. - UserProfile XMLs, LaunchBox's own library files, and Postgres databases are each backed up and restored independently; game files on your staging drive are never touched.
Getting started
Modes
- AutoSync (1)
- Register (2)
- Crosshairs (3)
- ReShade (4)
- dgVoodoo2 (5)
- GPU Fix (6)
- FFB Setup (7)
- BepInEx (8)
- Restore Backup (9)
- Postgres Setup (11)
Reference