Backups

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

PDA Backup

The data on the PDA is to be backed up manually using Sprite Backup at least before each sync, but preferrably more often. The backup is done to a memory card. Additionally, each sync generates a copy in the backup directory of the given location's directory under L_Handbase on the regional server, e.g.

• \\sbghnwfs0102\NSSVOL1\shared\ICU_DATA_COLLECTION\L_HanDBase\GRA_MICU\backup
• \\ (need to include the HSC gateway?

This location will keep the copies for the most recent ten syncs. The data for older syncs is discarded. Since the 10 sync copies are stored on the regional server, this provides off-site backup.

Primary Data Repository (TMSX MedTMS data) Backup

The primary data repository is backed up because copies of it always exist in two locations:

• on at least each of the 4 PCs in the main office.
• on the network share "<where?>"

Whenever new data is available, Pagasa copies updates to the 4 PCs' drives via batch file when . In addition to this, Pagasa runs a batch file daily that copies the data to the network as per [[Backups

1. Backup Process|below]].

Master TMSX and MedTMS Database Backup Process

• batch file copies TMSX data to <where>? on the network
• batch file is located <where>? (There is a shortcut on Pagasa's desktop to the batchfile that does the backup. Where does it link to? What do all the other batch files in that place do? Ttenbergen 11:05, 28 July 2008 (CDT))
• batch file is run manually daily by Pagasa
• Nobody does the Backup if Pagasa is not there. This might be OK as long as Pagasa is the only one who ever updates the TMSX data. Is this the case? Ttenbergen 11:22, 28 July 2008 (CDT)

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
• 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.
• Data at the data collector PCs is not being updated at all

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.

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?