On Sun, 10 Aug 2025 09:08:12 -0000 (UTC), Duncan wrote: >> Since the DB contains servers, group and article, a corrupted DB means >> a restart from scratch (unless you have a backup). > > Backups are good, particularly when running experimental-branch database > code! =:^)
Seems like one of two (or possibly both) options would be good here. 1. Pan creates a backup of its own database on startup. From a time perspective, though, this takes longer as the database grows, of course, and might not be ideal for everyone (maybe a setting to enable this as built-in behavior, with a number of backups to keep). 2. Users using a wrapper script can make a copy of the database prior to launching pan and manage that separately. For use cases like yours, I would tend to agree that leafnode would be a better "long-term" archive solution; but I can see how getting your existing data back into a leafnode instance might be a challenge. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits _______________________________________________ Pan-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/pan-users
