Re: [foxboro] Save-all script Update
- From: "foxpat" <foxpat@xxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 10 Dec 2008 20:47:19 +0100
Hi Marco!
As you know we're a very satisfied user of the save_all.sh as you've installed
it at our site yourselve!
Just some thoughts;
1) We have a number of scheduled scripts for all kinds of things. Most (if not
all) create some sort of log file like the savel_all.log. The practical issue
with these log files is that, as everything runs un-attended, no one bothers to
look at them. Some sort of notification mechanism would be welcome ONLY if
things FAIL. I could think of a number of ways but I guess it will not be so
simple to satisfy all users.
I would be satisfied if a very simple save_all.status file would be created
which simply says: 'OK' or 'FAILED'. The first thing to do would be to set this
to FAILED and only set it to OK if finished without errors.
Or you could maybe specify a C:B.P which would be set if things fail.
Or Some users may be able to send e-mail from I/A.
If a save_all.status file would be available one can do with it whatever he/she
likes. In our case I would read the save_all.status file from our scheduled VBA
application which runs every day anyhow. From this VBA machine I can send
e-mails. We use this kind of mechanism to inform us whenever a disk partition
exceeds 90% anywhere on the system. Also MAC_RESETS are checked in similar ways.
2) Last time you were at TRN we installed it on two P91's. You created a
save_all.cmd (Ron has a copy) file for this purpose which is called by the
standard windows scheduler. It would be nice if you would update the manual on
how to do this.
3) An optional second back-up location (in our case another physical disk (F:)
(or maybe even another machine) would be nice although this would most likely
be covered by your overall back-up strategy.
4) Save_all.cmd also takes care of the CSA backup. This was done in a most
efficient but quick and dirty way. Maybe this could be added in the save_all.sh
although you could argue if this is the correct place or even required if you
have a proper overall backup strategy.
Kind regards,
Patrick Martens
-----Oorspronkelijk bericht-----
Van: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] Namens
de Waal, Marco
Verzonden: woensdag 10 december 2008 12:01
Aan: foxboro@xxxxxxxxxxxxx
Onderwerp: [foxboro] Save-all script Update
Hello,
As we see on the list, the Save-all script (
http://www.thecassandraproject.org/archive/save_all.html ) is still very
much used, therefore we have decided to create an update of this script.
The last update was about 5 years ago.
Changes will that we will try to implement:
- Save device-files used in the CP (modbus port/device, profibus, FDSI
xml files, etc)
- Save scripts executed by sequences
- Add an option to only make a save-all when something is changed since
the last save-all (thanks to Patrick Martens for the suggestion)
- Change date/time format of archives for better sorting
- Bug fixes
If any of you has a suggestion of what would be a great feature/add-on
to the script, please let us now and we will see if we can implement
this.
Don't pin us on a deadline yet, since we will do it in the (little)
spare/free time we have ;-)
Regards,
Marco de Waal
* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual or
entity to whom they are addressed. Please do not copy it or use it for any
purposes, or disclose its contents to any other person. Further, this e-mail
and any associated files may be confidential and further may be legally
privileged. This email is from the Invensys Process Systems business unit of
Invensys plc which is a company registered in England and Wales with its
registered office at Portland House, Bressenden Place, London, SW1E 5BF
(Registered number 166023). For a list of European legal entities within the
Invensys Process Systems business group, please click here
http://www.invensys.com/legal/default.asp?top_nav_idw&nav_id€&prev_idw.
If you have received this e-mail in error, you are on notice of its status.
Please notify us immediately by reply e-mail and then delete this message from
your system. Thank you for your co-operation. You may contact our Helpdesk on
+44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail
and any attachments thereto may be subject to the terms of any agreements
between Invensys (and/or its subsidiaries and affiliates) and the recipient
(and/or its subsidiaries and affiliates).
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.16/1840 - Release Date: 9-12-2008 16:53
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
