Centralized backup.bat: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Legacy article only, this is now taken care of | |||
by the [[Pull down centralized data.vbs]] and | |||
[[Push up centralized data.vbs]] scripts instead. | |||
Centralized_backup.bat is run by the [[data collector]] to back up [[Centralized data.mdb]]. | Centralized_backup.bat is run by the [[data collector]] to back up [[Centralized data.mdb]]. | ||
Line 17: | Line 22: | ||
[[Category: 2013 data upgrades]] | [[Category: 2013 data upgrades]] | ||
[[Category: | [[Category:Legacy Data processing batch files]] |
Revision as of 14:10, 25 August 2014
Legacy article only, this is now taken care of by the Pull down centralized data.vbs and Push up centralized data.vbs scripts instead.
Centralized_backup.bat is run by the data collector to back up Centralized data.mdb.
It is usually run when it is called by 1Backup.bat to run the centralized, cc and med backups sequentially.
Uses 7Zip.
Template:Discussion What process triggers this? Needs to be cross-linked.
Must push before backing up
If an error message shows; cannot find a file, must check if Pull down centralized data.vbs to local desktop. The backup must only be run AFTER Push up centralized data.vbs, otherwise Centralized data.mdb is not backed up.
- that needs to live in the process article for this, not the batch file article... Ttenbergen 14:59, 2014 April 30 (CDT)
Future Plan
Set up a automated Scheduled Task to do this
- probably not necessary; eHealth does regular backups. I think the manually triggerred backup should coincide with pushing and pulling, which those files already do. We probably have duplication... Ttenbergen 16:41, 2014 April 30 (CDT)