Backup automation

[tms-epcc]

• This is backup of the large static archives once a year (i.e. 1 and parts of 3 at http://pepy.roe.ac.uk/bin/view/WFAU/BackupsStrategy).   This material does not change regularly if at all this is important for bus factor and also easing work load
• next step was to build a schedule for DB backups by examining old reports but network glitch in March resulted in backup failures that actually require manual intervention to resolve.  If the backups had been automated then these would have attempted to carry on  and so resulted in even more failures. 
• Doing it manually whilst it means more work, the back up quality will be better because 
  1. if something goes wrong, it is not constantly creating more and more back backups, and
  2. means Rob has to examine what needs backups and so if new products have been added then Rob will add these manually.

[tms-epcc]

29/MAY/24

• as agreed previously, will not create a timetable for backups but rather will do manually when necessary
• there will therefore be no automation so this can be closed