Backups: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 12: | Line 12: | ||
==Additional Info Required== | ==Additional Info Required== | ||
* '''''on what day does this happen | * '''''on what day does this happen | ||
* '''''where is the data sent to | * '''''where is the data sent to | ||
* '''''and where is the actual batch file | * '''''and where is the actual batch file | ||
* '''''who does this if Pagasa is not here''''' | * '''''who does this if Pagasa is not here''''' | ||
Revision as of 14:23, 26 March 2008
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.
Additional Info Required
- on what day does this happen
- where is the data sent to
- and where is the actual batch file
- who does this if Pagasa is not here