PG News 8.7 Changelog

Assists Greatly with Development Costs
Status
Not open for further replies.

vpatel9202

Blitz 3rd Class
21
7
One consideration may be to employ "lite" backups which backup only app configurations rather than the entire app directory. Most of the apps only need a few files backed up and I don't think most people have any reason to backup things like logs and image caches, which can be rebuilt if you need to restore for whatever reason.

For example:

Code:
NZBGet -> nzbget.conf
Sonarr/Radarr -> nzbdrone.db, sonarr.ini, and config.xml (or let the app make backups and pull it from the backups folder since the db files are finnicky and easily corrupted)
Jackett -> serverconfig.json and indexers folder
NZBHydra -> nzbhydra.yml
qBittorrent -> qbittorrent.conf
This would make the backups a lot faster and make deploying multiple servers with identical settings much easier.
 

CyborgPirate

Blitz 1st Class
78
21
The reason this doesn't work is because the restore process becomes a night mare because not everyone choose a daily backup. If you ever want to recover an older backup, go-to the trashcan restore it and replace what's there. Good thought I'll keep in mind.
Is this because some programs will be backed up weekly and others daily and they may not match up to a date?
Well at the moment we have to specify which program to restore so what if the folder structure becomes more like this:
.../backups/plex/20190423/plex.zip
.../backups/plex/20190430/plex.zip
.../backups/radarr/20190425/radarr.zip

so then when you select plex to restore, the program can prompt you for a date from the list (pulled from the folder names within the plex directory) with a default of the latest if the user doesn't specify.

e.g.
Code:
Choose the backup of plex to restore:

1. 30/04/2019
2. 23/04/2019
z. cancel

default: 1 (latest)

$ 1
and example for radarr:
Code:
Choose the backup of radarr to restore:

1. 25/04/2019
z. cancel

default: 1 (latest)

$ 1
Thoughts?
 
Last edited:

Admin9705

Administrator
Original poster
Project Manager
5,818
2,006
Is this because some programs will be backed up weekly and others daily and they may not match up to a date?
Well at the moment we have to specify which program to restore so what if the folder structure becomes more like this:
.../backups/plex/20190423/plex.zip
.../backups/plex/20190430/plex.zip
.../backups/radarr/20190425/radarr.zip

so then when you select plex to restore, the program can prompt you for a date from the list (pulled from the folder names within the plex directory) with a default of the latest if the user doesn't specify.

e.g.
Code:
Choose the backup of plex to restore:

1. 30/04/2019
2. 23/04/2019
z. cancel

default: 1 (latest)

$ 1
and example for radarr:
Code:
Choose the backup of radarr to restore:

1. 25/04/2019
z. cancel

default: 1 (latest)

$ 1
Thoughts?
Could be possible but requires and extensive rewrite which would to be on another version and doesn't add much value against other fixes needed. The project can be forked and any can tackle it :D
 
  • Like
Reactions: CyborgPirate
Status
Not open for further replies.

Similar threads


Development Donations

 

Trending