Backups

see also Category:Backup

We are using two-tier backup schemes during data collection and again for the primary data repository.

Laptop

• News and backup
• see CCMDB data.mdb restore from the SD Card
• see CCMDB data.mdb restore from Regional Server

Primary Data Repository (TMSX and MedTMS data) Backup

• see Category:Data processing batch files
• See CC_backup.bat
• See MD_backup.bat

Problems with the current system

• 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).
• According to IT Policies patient data should not be stored locally on PCs due to security concerns
• Sharing drives on PCs is a security concern and should be avoided. eHealth is looking at prohibiting and preventing the practice.
• 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.

Template: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

• 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 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 misplaceTOstryzniuk 17:39, 6 February 2009 (CST)

Additional Info Required

• process/batch file copying out data from Pagasa to other 4 PCs.
• what do the other batch files on Pagasa's PC do?