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. 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

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 Backup

The primary data repository is quasi backed up because copies of it always exist on at least all the PCs in the home office at HSC. In addition to this, Pagasa runs a batch file weekly that copies the data to the network.

Backups for the CCMDB Program

as per Previous Docu as of May 5 2006 needs updating

Currently

• CCMDB data is stored locally on the 4 PCs in the main office on shared drives
• Pagasa updates it to these locations when new data is available.
• Everyone has to be logged in and the directories must be shared for Pagasa to be able to copy files there
• Manual/Batch backup to the HSC SAN

Problem

• 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.
• Pagasa can only “push” files to people who are logged on
• 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

• on what day does this happen
  • I do the back up every day.

• where is the data sent to
  • The data goes to the SANS and to my D drive
  • But yesterday discussion I wont do anymore back up on my D. drive,July 24/08.

• and where is the actual batch file
  • 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)

• who does this if Pagasa is not here
  • Nobody.

PTorres 13:10, 25 July 2008 (CDT)