Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restoration seems too old. #297

Open
mookman288 opened this issue Oct 12, 2023 · 1 comment
Open

Restoration seems too old. #297

mookman288 opened this issue Oct 12, 2023 · 1 comment

Comments

@mookman288
Copy link

Hi,

I'm using fastback-0.11.2+1.20.0.jar on Windows and I have the software making incremental quarter-day backups. Approximately every 6 hours it takes a snapshot. It's been running for just over a week, and the backup size is ~1.5gb.

Initially I had some issues with git, but a stash seemed to correct those issues.

We had an issue on our server which prompted me the opportunity to test the backup system. The restoration was flawless to the temp directory. I brought the server down. Backed up the current world directory, and replaced it with the new world directory.

To look at the restored snapshot, quit the current world and open the restored snapshot world. (In server mode, you’ll have to manually copy the restored files from the location displayed at the end of the command).

Following the above directions, I replaced all of the files, and did not overwrite files.

When I loaded the server, playerdata seemed to be in the correct approximate location, and inventories appeared correct, but the world was days old, possibly older.

I'm going to assume right now that the backup system isn't working as expected, and try to do manual snapshots of the world folder daily (or schedule the task in Windows for a robocopy.)

I think this might be related to #215 but I'm not sure. Let me know if you need any other information.

Thank you!

@mookman288
Copy link
Author

I've noticed this might be related to Fabric, and not necessarily Fastback. Maybe it's an implementation? I've found that Pl3xMap doesn't update consistently unless the server is restarted. If #215 is related, then that would mean something in Fabric (?) is preventing map state from updating regularly unless the server is restarted. That would explain why Fastback doesn't update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant