Re: [foxboro] Save-all script Update

On Wed, Dec 10, 2008 at 09:09:24PM +0100, Ron Deen wrote:
> Hi Stan,
> 
> The current version of the save_all script is 2.2.1 and that does still 
> contain your additions that were related to the upload function. Very 
> valuable to many of the users.
> Your functionality was indeed added in 2000 (April 22nd release) and we have 
> no plans to take it out.
> 
> We would advise anyone using the script to move to version 2.2.1 if at all 
> possible because some functions were added and bugs fixed. This is all when 
> you have not made severe changes in earlier versions that prohibit the 
> upgrade.
> 

Sounds good. I will try to find the time to update the version on all of
our nodes.

On a 2nd issue, I saw another message talking about adding CSA saves to this
script. I am of 2 minds about this. First i generally believe in single
purpose tools that do one job, and do that job well. On the other hand, on
my whiteboard is a note reminding me that I need to automate saving the
following items:

CSA
sequence code
historian configuration

I would be embarrassed to tell you how long that note has been there, let's
just say that when I get it done I expect to have problems getting it erased
off of the whiteboard :-)

So, if those items _did_ get added to the functionality of this script,
then I would be able to accomplish this goals, by standing on the shoulders
of others, always a good thing!

In addition the same message talks about backing up to a remote location.
Let e describe how we handle this. We have the save_all script scheduled in
corn, so we get this data onto the AP or AW's hard disk. Then have an
Amanda backup machine which runs a backup of all the Foxboro machines that
are connected to the mill network (and many other *NIX machines0> The way
this software works is that it chooses whether to do a level 0 or level 1,
or above based upon user configurable rules. In our case the Amanda machine
then wries these backups to an LTO tape drive, and a large (6G) disk partition
on thta machine. Thus I have a copy thta is on tape for safety, and a copy
on disk for fast access.

Since the save_all script has put it's data onto the hard disk, i am
garuned to get a copy on tape every night that save_all runs, since it
will be a change to the disk image on the Foxboro machine.

This is solid enough even for someone as paranoid as I am :-)

-- 
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs.
 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: