Backups

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

• Pull down centralized data.vbs
• Push up centralized data.vbs
• Copy here only centralized data.vbs

culling

Tina has a reminder to manually cull the backups as follows because they had generated >100GB of files. Would be nice to automate eventually, but leaving for now. As agreed with Trish:

• for a month, keep the latest file each day
• for a year, keep on file on days that divide by 10 (eg May 20) and first of month.
• forever, keep the last one per year.

TISS28

TISS28 is not part of our backup process right now. OK for now, because backed up by eHealth, but for consistency we should start sending dated copies to M:\ like the rest of our core data.

I was going to add it the push/pull process but then realized that I am not at all sure that Pagasa doesn’t use TISS on one PC while in pull state on the other. So, we can’t be pulling TISS28 at that spot until we have worked out how Pagasa does this.

We talked the other day about changing Pagasa’s setup to use only one PC. This might be the time to re-visit that, too. So, likely Trish, Tina and Pagasa need to talk before I can integrate this.

Scheduled for 2015-May-25

eHealth file shares

All our file shares are backed up by eHealth. To restore any files missing from a file share contact the help desk.