rpie-preservatives - Save file remote backup & synchronization tool

[LiquidDivide]

rpie-preservatives on github

I've been using/developing this personally, as time allows, for about a year now, and I think it's finally ready to show to the public and get some feedback from other users. This is a pair of runcommand scripts to sync battery save files on a cloud storage platform. This can be used as a simple script to backup up saves, but the true intent is to allow you to synchronize save files across multiple retropie machines.

This does perform sync operations, so there is a potential for lost data if things are not setup correctly. Follow all instructions carefully and please, please, PLEASE backup your files before using. Any feedback is welcome.

[zerojay]

Your timing couldn't be better as I was just looking to try to find an older solution I used to run ages ago. I'll give this a shot tonight.

[LiquidDivide]

@zerojay Awesome. Glad I could help. Hope it works out for you.

[SuperPitendo]

Hi,

I´ve been using @jandalf81 's setup script for syncing saves with a cloud service --> https://retropie.org.uk/forum/topic/18712/script-setup-script-to-sync-saves-to-cloud-services

in combination with his save state selector --> https://retropie.org.uk/forum/topic/18978/script-setup-for-an-automatic-savestate-selector

@LiquidDivide Give it a shot to get some inspiration for your own script.

@zerojay maybe is the "older solution" you've been looking for.

[LiquidDivide]

@SuperPitendo I was looking for something like this about 2 years ago. Must have been just before
@jandalf81's script was published, and I somehow missed it. So I wrote my own. Pretty cool that we both went with rclone. His solution is definitely more mature than mine and has a much cleaner setup process. I planned to do something similar, but was just trying to get something that worked before making it nice to use. I'm not sure if I like him moving the save files. May complicate things on other machines, so I'll have to look into that, but overall it appears to do essentially the same thing mine does. I'll have to look at his more closely and see if it's even worth continuing mine.

Thanks for pointing this out to me.

[LiquidDivide]

@SuperPitendo I've looked into it some more, and I think I do like mine better. I'll improve the install process eventually, but my script supports more complex systems (PSP, Gamecube, and Wii for example) and doesn't move your files around. I also use mine to sync from non-retropie devices that are running retroarch, and my script seems to handle this better too. It's also concerning that he hasn't touched the thing in 2 years and there are some pull requests that have been open for a long time that address some of these issues.

Still, a lot of work and thought went into it, and I have gotten some ideas and inspiration from @jandalf81's script. Thanks again for sharing.

[SuperPitendo]

@LiquidDivide I am glad that I could help. Thanks for pointing out the differences, especially the point with the non-retropie devices and that nothing has been done on the other script for 2 years. This should make your script much more interesting. Do you plan to include a save state selector as well?

[LiquidDivide]

@SuperPitendo I wasn't planning too originally. Mostly because the save state files are quite a bit larger and it takes more than just a few seconds to upload them most of the time. I wanted it to be as seamless as possible. Battery saves are usually done in < 2 seconds or so. But, I definitely could add that option. Right now, I'm trying to streamline the install process.

[zerojay]

@SuperPitendo said in rpie-preservatives - Save file remote backup & synchronization tool:

@LiquidDivide I am glad that I could help. Thanks for pointing out the differences, especially the point with the non-retropie devices and that nothing has been done on the other script for 2 years. This should make your script much more interesting. Do you plan to include a save state selector as well?

Yes and no. If something works well, there's not really a need to keep changing and updating it. The other script does still work well and I had minimal issues with getting it working again, though I added a few changes from one of the other forks as well. I'm happy with it for now, but if this script gets more features, more robust, I'll happily switch.

[langest]

@LiquidDivide thanks for the awesome scripts!

I made some local changes and hacks to get it working on my own system, not pretty enough to contribute. I hope I get some time to clean it up and contribute it back.