Backups: Difference between revisions
Ttenbergen (talk | contribs) m →culling: clean-up |
Ttenbergen (talk | contribs) |
||
| Line 7: | Line 7: | ||
== Centralized data Backup == | == Centralized data Backup == | ||
They live on \\hsc1msfp0013\SHARED\WRHA_CCMED\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 | 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]] | * [[Pull down centralized data.vbs]] | ||
| Line 19: | Line 21: | ||
=== TISS28 === | === 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 | 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 \\hsc1msfp0013\SHARED\WRHA_CCMED\Backup 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. | 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. | ||