Backups: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →culling: sp |
Ttenbergen (talk | contribs) m →culling: m |
||
| Line 13: | Line 13: | ||
=== culling === | === culling === | ||
{{ | {{discussion}} | ||
right now this process has generated over 100GB of dated files. We need to decide how to cull. I think I have this elsewhere on this wiki as well... | right now this process has generated over 100GB of dated files. We need to decide how to cull. I think I have this elsewhere on this wiki as well... | ||
I can't think of a good automated process for now, so I propose: | I can't think of a good automated process for now, so I propose: | ||
Revision as of 16:31, 20 May 2015
see also Category:Backup
Laptop
- News and backup
- see CCMDB data.mdb restore from the SD Card
- see CCMDB data.mdb restore from Regional Server
Centralized data Backup
Centralized_data.mdb and PHI.mdb live on an eHealth server and so are backed up by them (#eHealth file shares). We also created dated snapshot backups every time the data processor pulls data as part of vetting and then pushes it again. For details, see
culling
Template:Discussion right now this process has generated over 100GB of dated files. We need to decide how to cull. I think I have this elsewhere on this wiki as well... I can't think of a good automated process for now, so I propose:
- for a month, keep the latest file each day
- for a year, keep on file on days that divide by 10 (eg May 20).
- forever, keep the last one per year.
Trish, is that OK?
All our file shares are backed up by eHealth. To restore any files missing from a file share contact the help desk.