Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1056807" data-attributes="member: 18896">That is what Follw.it (for MovPic) and Trakt.tv (for MP-TVSeries) save me from, if I ever have to do a disaster recovery.&nbsp;Keep in mind that a corruption can occur at any moment, and unless you keep each individually nightly backup, your backup can get corrupted as well.&nbsp;A backup storage policy I use a lot is:<ul>
<li data-xf-list-type="ul">Daily of the week that overwrite themselves.</li>
<li data-xf-list-type="ul">Sunday (or whatever day of the week works for you) backup is copied in a week folder and last 4 versions are kept</li>
<li data-xf-list-type="ul">Every 1st of the month backup is kept as well for a maximum of 4</li>
<li data-xf-list-type="ul">Jan 1st and July 1st backup of the year are kept</li>
</ul>That way, unless a corruption went unnoticed for a very long ass time, I can still go back to a version that is 'clean', without hopefully too much changes lost. It does of course come with a larger requirement on storage to retain all the backups, but I only do it for the DB3 files, the Thumbs folder only needs a recent backup, because if a PNG or JPG got corrupted I just delete it on individual basis and the background scraper system will re-obtain it auto.&nbsp;Another trick to keep the mass amount of extra backups small is to use tools such as rsync and others, so that the Jan 1st backup is a full one, but the others are differential ones, where you only backup the 'changes'. Plenty of backup software solutions available (even open sourced ones) that do this process fully automatic. Personally I am a glutten for punishment, so I tend to write my own batch-script solution <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="RoChess, post: 1056807, member: 18896"] That is what Follw.it (for MovPic) and Trakt.tv (for MP-TVSeries) save me from, if I ever have to do a disaster recovery. Keep in mind that a corruption can occur at any moment, and unless you keep each individually nightly backup, your backup can get corrupted as well. A backup storage policy I use a lot is: [LIST] [*]Daily of the week that overwrite themselves. [*]Sunday (or whatever day of the week works for you) backup is copied in a week folder and last 4 versions are kept [*]Every 1st of the month backup is kept as well for a maximum of 4 [*]Jan 1st and July 1st backup of the year are kept [/LIST] That way, unless a corruption went unnoticed for a very long ass time, I can still go back to a version that is 'clean', without hopefully too much changes lost. It does of course come with a larger requirement on storage to retain all the backups, but I only do it for the DB3 files, the Thumbs folder only needs a recent backup, because if a PNG or JPG got corrupted I just delete it on individual basis and the background scraper system will re-obtain it auto. Another trick to keep the mass amount of extra backups small is to use tools such as rsync and others, so that the Jan 1st backup is a full one, but the others are differential ones, where you only backup the 'changes'. Plenty of backup software solutions available (even open sourced ones) that do this process fully automatic. Personally I am a glutten for punishment, so I tend to write my own batch-script solution :) [/QUOTE]

Verification