Haha - at first I thought your first paragraph was saying that I (the developer) had made some great changes that worked, but then broken them, and I gasped! LOL
Now I get what you're saying: You (the user) have your config all good one day, but then break it... but then to restore OSB (off site backup) means reverting to the previous day - losing the great work you'd done.
The solution you desire is already there, just falls amongst the "no user serviceable parts inside" category.
Here you are:
Code: Select all
sudo /root/nems/nems-migrator/offsite-backup.sh
That'll trigger an off site backup, on demand. If you already have a backup for that day, this will replace it (OSB allows one backup to be stored per day).
The process does not output anything to the terminal. To see if it worked, you can tail the log file after running it:
Code: Select all
sudo tail -n 1 /var/log/nems/nems-osb.log
You can learn about the log format in the docs here:
https://docs.nemslinux.com/features/nem ... or#backup1
Remember: Because your "normal" off site backup is scheduled to run at 11:30pm, the backup you create will be overwritten at that time. You may be wise to instead download a local backup from NEMS Migrator as a failsafe, which is created every 6 hours, and can also be manually created if desired with the following command:
Code: Select all
sudo rm /var/www/html/backup/snapshot/backup.nems && sudo /root/nems/nems-migrator/backup.sh