1Backup.bat: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
m Text replacement - "[[Category: " to "[[Category:"
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==also referred to as: 3 in 1 backup==
This is a legacy article only. Medicine is no longer being backed
Use Updated compression utility to [http://en.wikipedia.org/wiki/7zip 7zip] (from PKZIP) to support long file names
up because no longer used. Centralized backup gets taken care of
by the [[Pull down centralized data.vbs]] and
[[Push up centralized data.vbs]] scripts instead.


*back up centralized_data.
calls [[Centralized backup.bat]]


:run the critical care backup batch
----
calls [[CC backup.bat]]


:run the medicine backup
calls [[MD backup.bat]]


NOTE:  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.
1Backup.bat is a batch file created by [[p:Tina Tenbergen]] that calls several other batch files that should be run together:
* [[Centralized backup.bat]]
* [[CC backup.bat]]
* [[MD backup.bat]]


Running 1Backup.bat is part of the following processes:
* [[vetting]] actually it is not but that is the closest thing; turns out that 1Backup duplicates part of pulling and pushing... Ttenbergen 16:45, 2014 April 30 (CDT)




{{Discussion}}
NOTE: 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.accdb]] is not backed up.  
* There is a push/pull LOG file somewhere that can be checked however, at the moment it is not clear where it actually lives or what it is called. --[[User:TOstryzniuk|Trish Ostryzniuk]] 18:54, 2014 April 29 (CDT) 
** edit the file, if it generates a log then there will be a variable, something with the name log in it, that will tell where it logs to. Ttenbergen 13:31, 2014 April 30 (CDT)
***Not sure where the log goes. centralzied backup it says C, but in CC or MD backup its say the location for M.[[User:TOstryzniuk|Trish Ostryzniuk]] 14:14, 2014 April 30 (CDT)
**** edit the script itself, it will tell you if there is a log and where it goes. Ttenbergen 14:18, 2014 April 30 (CDT)


IMPORTANT NOTE:[[Data Processor]] must regularly (at least once per week) check if backup went to location expected or not.  In the past main office has experienced backup batch files that for some reason stopped working. Because no one did regular checks we had long period with with no backup![[User:TOstryzniuk|Trish Ostryzniuk]] 18:54, 2014 April 29 (CDT)
==Location of Log file of 1backup==
Lives:?


* Sorry.....I can't run to 3 different articles to find out where to log files lives for this batch file. Nice to see where it lives in this article. Had issues the other day and Pagasa has gone and we can't find it on Wiki.  [[User:TOstryzniuk|Trish Ostryzniuk]] 18:46, 2014 April 30 (CDT)
** I understand your point, but these are three different batch files that were grouped for convenience. Duplication of info on wiki - nuff said. If there is never a reason to run the batch files separately we could combine the actual files, in which case the log info would also be addressed in one place. However, considering that the whole concept will change once we move from Ed's I think we should just leave this as is for now. After the traffic relating to this over the last few days we should likely re-visit. However, it would be nice to have Pagasa's process documentation up-to-date first so we can make sure the automation fits as well as possible. Ttenbergen 21:57, 2014 April 30 (CDT)






 
[[Category:Legacy Data processing batch files]]
 
backup created by: [[Tina Tenbergen]]
 
 
[[Category: 1Backup.bat]]
[[Category: Data processing batch files]]
[[Category: 2013 data upgrades]]
[[Category: Batch Files]]

Latest revision as of 10:29, 30 July 2025

This is a legacy article only. Medicine is no longer being backed 
up because no longer used. Centralized backup gets taken care of 
by the Pull down centralized data.vbs and 
Push up centralized data.vbs scripts instead. 




1Backup.bat is a batch file created by p:Tina Tenbergen that calls several other batch files that should be run together:

Running 1Backup.bat is part of the following processes:

  • vetting actually it is not but that is the closest thing; turns out that 1Backup duplicates part of pulling and pushing... Ttenbergen 16:45, 2014 April 30 (CDT)


NOTE: 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.accdb is not backed up.

Location of Log file of 1backup

Lives:?

  • Sorry.....I can't run to 3 different articles to find out where to log files lives for this batch file. Nice to see where it lives in this article. Had issues the other day and Pagasa has gone and we can't find it on Wiki. Trish Ostryzniuk 18:46, 2014 April 30 (CDT)
    • I understand your point, but these are three different batch files that were grouped for convenience. Duplication of info on wiki - nuff said. If there is never a reason to run the batch files separately we could combine the actual files, in which case the log info would also be addressed in one place. However, considering that the whole concept will change once we move from Ed's I think we should just leave this as is for now. After the traffic relating to this over the last few days we should likely re-visit. However, it would be nice to have Pagasa's process documentation up-to-date first so we can make sure the automation fits as well as possible. Ttenbergen 21:57, 2014 April 30 (CDT)