AB's Useful Box - Backup Strategy
I searched high and low to find a sane method of performing backups.
Eventually I did find a very good method, but then lost the link, but following is the basics.
Backups should start with one main goal, what needs to be "restored"!
I needed a backup that could capture any changes made in the previous week, month and year.
I had been religiously backing up every day, but would over write each week day file. This was fine until I needed a file that had become corrupted possibly three months earlier. Alas that system has never been 100% since, despite best efforts.
Now driven by the previous short comings, a better solution was required, that was also able to be automated.
The following strategy was eventually implemented:
That is fine, but also needed a file naming convention, that from the filename, it could be ascertained when the backup was created.
The following naming was implemented:
yyyymmdd - being year, month and day.
Which results in the following schedule:
|