|
|
| (84 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| We are using two-tier backup schemes during data collection and again for the primary data repository.
| | '' see also [[:Category:Backup]] |
|
| |
|
| ==PDA Backup== | | == Laptop == |
| ===Manual Backup===
| | * [[News and backup]] |
| The data on the PDA is to be backed up manually using [[PDA Backup using Sprite Backup|Sprite Backup]] '''at least before each [[sync]]''', but preferrably more often. For the newer [[rx1950]] PDAs he backup is stored on an SD memory card; for the older PDAs still used by Vic Medicine, the backup is stored in internal non-volatile memory on the PDA.
| | * see [[CCMDB data.mdb restore from Regional Server]] |
| ===Automatic Backup during [[Sync]]===
| |
| 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
| |
| *\\Twister\ICU\L_HanDBase\GRA_MICU\backup
| |
| This location will keep the copies for the most recent '''ten''' [[sync]]s. 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]] and [[MedTMS]] data) Backup== | | == Centralized data Backup == |
| The primary data repository is backed up because copies of it always exist in two locations:
| | 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 |
| * on at least each of the 4 PCs in the [[:category:Main Office|main office]]. | | * [[Pull down centralized data.vbs]] |
| * on the network share "'''<where?>'''" | | * [[Push up centralized data.vbs]] |
| Whenever new data is available, [[Pagasa Torres|Pagasa]] copies updates to the 4 PCs' drives via batch file when .
| | * [[Copy here only centralized data.vbs]] |
| In addition to this, Pagasa runs a batch file daily that copies the data to the network as per [[Backups
| |
| #Backup Process|below]].
| |
|
| |
|
| === Master TMSX and MedTMS Database Backup Process === | | === Centralized backup locations === |
| * batch file copies [[TMSX]] data to '''<where>?''' on the network
| | Following directories: |
| * 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? [[User:Ttenbergen|Ttenbergen]] 11:05, 28 July 2008 (CDT)) | | * [[M:\]]Backup\Centralized_data |
| * batch file is run manually daily by [[Pagasa Torres|Pagasa]] | | * [[M:\]]Backup\PHI |
| * 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? '''[[User:Ttenbergen|Ttenbergen]] 11:22, 28 July 2008 (CDT) | | * [[X:\]]CCMDB\PHI\PHI_CSV_Archive |
|
| |
|
| == Problems with the current system == | | === Retention === |
| * Pagasa can only “push” files to PCs that are logged on, leading people at the main office to not log off
| | We only retain backups for a time. See [[Culling backups]] for details. |
| * 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=== | | == eHealth file shares == |
| *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
| | 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: |
| *we would be in compliance having it off the PC
| | {| class="wikitable" |
| *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
| | | colspan="2" | Daily |
| *we would be able to continue to use a 1-step process to disseminate the data
| | | colspan="2" | Bi-Weekly |
| *we would be able to eliminate local shares
| | | colspan="2" | Monthly |
| *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.
| | |- |
| | || 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 |
| | |} |
|
| |
|
| ==Additional Info Required== | | == Related articles == |
| * process/batch file copying out data from Pagasa to other 4 PCs.
| | {{Related Articles}} |
| * what do the other batch files on Pagasa's PC do?
| |
| {{Discussion}} | |
| ====Backups====
| |
| *To SANS from Pagasa's computer:
| |
| **'''[[CCbackup.bat]]'''
| |
| **'''[[Medbackup.dat]]'''
| |
| ***How often?
| |
| ***I do the back up everyday or if I did a lot of edits in a day.
| |
| ***What is included?
| |
| *** It includes the Registryx.dat,Pharmacy.dat,Apache.dat,Lab.dat and tiss.dat for ICU.
| |
| *** For Medicine Registryx.dat,Lab.dat,Apache.dat,ADL.dat,SAPSII.dat,SAPSXtra.dat and tiss dat.
| |
| *To Pagasa's C drive from Output folder on Regional Server
| |
| **'''[[Output backup.bat]]'''
| |
| ***How often?
| |
| *** Once a week.
| |
| ***Why is this back up done?
| |
| *** If we have a problem on [[TmpV2_1.mdb]], [[TASKS.mdb]] and [[greensheet.mdb]].
| |
| ***What is included in this backed up?
| |
| ***[[TmpV2_1.mdb]], [[TASKS.mdb]] and [[greensheet.mdb]].
| |
|
| |
|
| *To SANS from output folder on Regional Server
| | [[Category: Backup | *]] |
| **'''DataTwister mdb to SAN.bat'''
| | [[Category: IT Instructions]] |
| ***how ofter?
| |
| ***I do this every week after I moved the [[DataToTmp.bat]] or if I do changes on [[TmpV2_1.mdb]], [[TASKS.mdb]] or [[greensheets.mdb]]. This back up is for Julie.
| |
| ***It includes the [[TMPV2_1.mdb]], [[TASKS.mdb]], [[greensheets.mdb]] and [[Pending.mdb]].
| |
| [[User:PTorres|PTorres]] 15:28, 13 November 2008 (CST)
| |
| | |
| [[Category:stubs]]
| |
| [[Category:Data Processing]]
| |
| [[Category:IT Instructions]] | |