Backups: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
 
(100 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 ==
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. 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.
* [[News and backup]]
*\\sbghnwfs0102\NSSVOL1\shared\ICU_DATA_COLLECTION\L_HanDBase\GRA_MICU\backup
* see [[CCMDB data.mdb restore from Regional Server]]
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==
== Centralized data 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.  
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
In addition to this, [[Pagasa Torres|Pagasa]] runs a batch file weekly that copies the data to the network.  
* [[Pull down centralized data.vbs]]
* [[Push up centralized data.vbs]]
* [[Copy here only centralized data.vbs]]


==Previous Docu as of May 5 2006 needs updating==
=== Centralized backup locations ===
Backups for the CCMDB Program
Following directories:
* [[M:\]]Backup\Centralized_data
* [[M:\]]Backup\PHI
* [[X:\]]CCMDB\PHI\PHI_CSV_Archive


===Currently===
=== Retention ===
*CCMDB data is stored locally on the 4 PCs in the office on shared drives
We only retain backups for a time. See [[Culling backups]] for details.
*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===
== eHealth file shares ==
*There are PHIA concerns with us taking the backups off-site. However, not taking a backup off-site risks loosing data.
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:
*According to IT Policies patient data should not be stored locally on PCs due to security concerns
{| class="wikitable"
*According to IT we will soon not be able to use shared folders on PCs any more.
|-
*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
| colspan="2" | Daily
*Data at the data collector PCs is not being updated at all
| 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
|}


===Recommendation===
== Related articles ==
*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
{{Related Articles}}
*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==
[[Category: Backup | *]]
* '''''on what day does this happen
[[Category: IT Instructions]]
**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
**
 
* '''''who does this if Pagasa is not here'''''
**Nobody .
 
 
 
[[Category:stubs]]
[[Category:Data Processing]]
[[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: