On 1/14/2025 8:12 PM, Kalpesh Patel wrote:
See https://storware.eu/blog/grandfather-father-son-gfs-backup/ for very
popular backup scheme. I advocate backing up the entire system - not just bits
here and bytes there. Even with modern electronics in the hard drives (spinning
platter ones or the solid state ones), they normally fail to tell you in time
when they go bad and believe me they do go bad.
Do note that while I have been discussing DATA back-up you will likely
be wanting "systems" back-up also.
But are some BIG difference. You need to do DATA back-up frequently
because your data is constantly changing. How frequently you need to be
doing SYSTEMS back-ups depends on how you are allowing systems and
programs to change. SOME of us allow "automatic upgrades" in which case
your software is changing unpredictably. Others of us do "builds" and
only change programs and systems at some definite time. We only need to
back up systems and programs before a "build" and do not necessarily
have to back up everything, just what was changed << but then we need to
keep documentation>>
The second big difference is that we can LOSE data (that has changed
since the last data back-up) but usually can replace software from where
we got it in the first place. If you are NOT writing software, your need
to back up programs is less >
I do "builds", so only back up programs when some have changed. But what
I write, I back up immediately upon completion (and the again any time
in the future when I change them.
Michael D Novack
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.