Backups: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
 
(33 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'' see also [[:Category:Backup]]
'' see also [[:Category:Backup]]
'' see also [[Interchange]] for how we have been exchanging data and how we would like to do so in the future.
We are using two-tier backup schemes during data collection and again for the primary data repository.


== Laptop ==
== Laptop ==
* [["News and backup" batch file]]
* [[News and backup]]
* see [[SD Card]]
* see [[CCMDB data.mdb restore from Regional Server]]
* see [[Laptop data Restore from Regional Server]]


==Primary Data Repository ([[TMSX]] and [[MedTMS]] data) Backup==
== Centralized data Backup ==
*see [[:Category: Data processor batch files]]
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
*see[[TMSX MEDTMS Backup]] (this article will get moved to CC & MD backup article)
* [[Pull down centralized data.vbs]]
*See [[CC_backup.bat]]
* [[Push up centralized data.vbs]]
*See [[MD_backup.bat]]
* [[Copy here only centralized data.vbs]]


== Problems with the current system ==
=== Centralized backup locations ===
* Pagasa can only “push” files to PCs that are logged on, leading people at the main office to not log off.  (Pagasa can push data to PC's if main office staff arelogged off as long as their computer is not shut down completely).
Following directories:
* According to IT Policies patient data should not be stored locally on PCs due to security concerns
* [[M:\]]Backup\Centralized_data
* Sharing drives on PCs is a security concern and should be avoided. eHealth is looking at prohibiting and preventing the practice.
* [[M:\]]Backup\PHI
* If we can’t use shared folders any more, we will have to change our data management process from a “push” by Pagasa to a “pull” from the network by everyone prior to running the program. This would need to be set up, and would be time consuming every time the program is used.  Also when the network is down, as it does happen, we are held hostage and until it is back up.
* [[X:\]]CCMDB\PHI\PHI_CSV_Archive
{{Discussion}}
Will there be a second spot we can store and retrieve data from?
* Data at the data collector PCs is not being updated at all. The only site that gets data updates because they run quick report is: STB MICU/SICU, CCU & CICU.


===Recommendation===
=== Retention ===
*If the program could be changed so that the location from which to pull data is variable, we could put the data on the SAN. This way
We only retain backups for a time. See [[Culling backups]] for details.
*we would be in compliance having it off the PC
*we could have automatic off-site backups through the IT backup policy
*even without the backup policy, the data would probably be on the regional server at SBGH, and therefore even the live data would be off-site
*we would be able to keep the local installs on data collectors PCs up-to-date
*we would be able to continue to use a 1-step process to disseminate the data
*we would be able to eliminate local shares
*If we don’t want to trust IT with the backups, we could have back-up to a memory stick that could be kept in Trish’s office, detached from the PC to be safe from power surges and viruses. Since the server is at SBGH this should suffice as an off-site backup.
*concern re: memory stick.  Easy to misplace[[User:TOstryzniuk|TOstryzniuk]] 17:39, 6 February 2009 (CST)


==Additional Info Required==
== eHealth file shares ==
* process/batch file copying out data from Pagasa to other 4 PCs.  
All our file shares are backed up by eHealth. To restore any files missing from a file share contact the help desk. Their retention schedule as of 2019-12 is:
* what do the other batch files on Pagasa's PC do?
{| class="wikitable"
{{Discussion}}
|-
|
| colspan="2" | Daily
| colspan="2" | Bi-Weekly
| colspan="2" | Monthly
|-
|| Data Category
|| Backup Type
|| Retention Period
|| Backup Type
|| Retention Period
|| Backup Type
|| Retention Period
|-
|| DEFAULT - ALL local drives (default excludes below data categories)
|| I
|| 4W
||  
||  
|| F
|| 6M
|-
|| File Shared
|| I
|| 4W
||  
||  
|| F
|| 12M
|-
|| Databases
|| I
|| 2W
|| F
|| 4W
||  
||  
|-
|| Virtual Machines
|| I
|| 4W
||  
||  
|| F
|| 6M
|}


==Backups-Data Processor==
== Related articles ==
*SEE: [[:Category:Data processing backup | Data processing backup]].
{{Related Articles}}


[[Category: Backup | *]]
[[Category: Backup | *]]
[[Category: IT Instructions]]
[[Category: IT Instructions]]

Latest revision as of 12:16, 2024 January 15

see also Category:Backup

Laptop

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

Centralized backup locations

Following directories:

  • M:\Backup\Centralized_data
  • M:\Backup\PHI
  • X:\CCMDB\PHI\PHI_CSV_Archive

Retention

We only retain backups for a time. See Culling backups for details.

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. Their retention schedule as of 2019-12 is:

Daily Bi-Weekly Monthly
Data Category Backup Type Retention Period Backup Type Retention Period Backup Type Retention Period
DEFAULT - ALL local drives (default excludes below data categories) I 4W     F 6M
File Shared I 4W     F 12M
Databases I 2W F 4W    
Virtual Machines I 4W     F 6M

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Backups&oldid=160667"