Backup
Intro
I guess you want to use or are already using OpenPLi great, but there are a few things you should do if you want a hassle free usage. At the time of this writing OpenPLi has nightly builds, so there are no alfa’s, beta’s or stable versions and are distinguished by creation date. Nightly builds means that every night a (new) version of OpenPLi gets build, whether there have been made changes or not. When changes have been made it is always meant to make things better, but there are no guarantees. Keep in mind that the developers have day time jobs and all this is done in their spare time.
Updating isn’t necessary, when things work there is no good reason why you should update. Remember, If it ain’t broke than don’t try to fix it! It is always sane to check the commit logs or read the forum if there is good cause to update or not.
When you choose to update OpenPLi, you willingly take the risk that it can be for better or worse.
So, when things don’t turn out for the better, having a backup is essential. If you don’t like the changes that the update has made and want to revert to before these changes were made.
Here I will deal with two types of backup that are a must have. These two can make you always go back to the state of OpenPLi when they were created, in say less than 5-10 minutes or so. There are much more details about the two types of backup I mention here, but I want to keep it simple.
First things first, Autobackup which is native to OpenPLi and second BackupSuite maintained by Pedro_Newbie. There are differences between these two that (can) make them complementary.
Complementary
So using these two backups, Autobackup and BackupSuite, you are fairly safe, well as safe and stable as at the time you created them. These two methods are complementary. Autobackup when you’ll need to flash and don’t want to set all the settings manually and BackupSuite when you want to restore to your last stable version of OpenPLi.
