|
|
| (8 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| 1Backup.bat is a batch file created by [[Tina Tenbergen]] that calls several other batch files that should be run together: (as part of what process? {{discussion}}
| | 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: |
| * [[Centralized backup.bat]] | | * [[Centralized backup.bat]] |
| * [[CC backup.bat]] | | * [[CC backup.bat]] |
| * [[MD 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) |
|
| |
|
|
| |
|
| Use updated compression utility to [http://en.wikipedia.org/wiki/7zip 7zip] (from PKZIP) to support long file names
| | 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. |
| * I am almost sure that 1Backup doesn't use it but the called batches may. In any case, don't think there is value in listing it here, that a level of detail best left to the batch files themselves. propose deleting this. Ttenbergen 14:59, 2014 April 30 (CDT) {{discussion}}
| |
|
| |
|
| == Must '''push''' before backing up == | | ==Location of Log file of 1backup== |
| 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.
| | Lives:? |
| * that needs to live in the process article for this, not the batch file article... Ttenbergen 14:59, 2014 April 30 (CDT)
| |
|
| |
|
| == check that backups work ==
| | * 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) |
| [[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)
| | ** 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) |
| * again, that needs to be a process, not part of the batch file article Ttenbergen 14:59, 2014 April 30 (CDT) | |
|
| |
|
| == Logs ==
| |
| {{Discussion}}
| |
| * 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. centralizedbackup 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)
| |
| *****opened the 1backup.bat in EDIT.........nothing there other than what you see above.[[User:TOstryzniuk|Trish Ostryzniuk]] 14:25, 2014 April 30 (CDT)
| |
| ****** Ah, sorry: the other batch files being called by 1Backup are what defines the logs. And that is likely already written in their articles, so probably best to remove from this article and just link to those.
| |
| *******very confusing trail to follow.[[User:TOstryzniuk|Trish Ostryzniuk]] 15:42, 2014 April 30 (CDT)
| |
|
| |
|
|
| |
|
| [[Category: 1Backup.bat]] | | [[Category: Legacy Data processing batch files]] |
| [[Category: Data processing batch files]]
| |
| [[Category: 2013 data upgrades]]
| |
| [[Category: Batch Files]]
| |