Re: [foxboro] save_all scripts (was: Backup strategies - Best Practices?)

Hi Patrick,

Good to "see" you again.
To your questions:
No, an initialise is not mandatory but on the other hand, usually you perform 
a load_all to get a clean start so it would make sense in general.
> Are you suggesting that, although load_all completes without error, it
> might not have checkpointed?
I have it depends on the load the CP will encounter processing the compounds. 
I have witnessed checkpoints not completing and have picked up the habit of 
double checking.
Mind you, this is only with the script. ICC will warn you if it fails and you 
will get the option to retry.
As mentioned, the script could use some ruggedising but I never got around to 
it, just checked manually if the checkpoints worked.
I got the word from Marco ( the "other" save_all guy) he got your "check for 
for modified control databases" code that is likely going into the save_all 
script.
That could could be useful to go into the load_all.sh script too?

Anyway folks: Consider this your homework ;-)

Cheers

Ron Deen



On Thursday 29 January 2009 18:22:39 foxpat wrote:
> Ron,
>
> I use the save_all files created by your script reguarly to load compounds
> on our offline test system. I simply use opt/fox/ciocfg/api/load_all after
> adjusting the .Compound_dir file to my needs.
> It is not a must to initialise, is it?
>
> Are you suggesting that, although load_all completes without error, it
> might not have checkpointed?
>
>
> Regards,
>
> Patrick
>
> -----Oorspronkelijk bericht-----
> Van: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> Namens Deen, Ron
> Verzonden: donderdag 29 januari 2009 9:40
> Aan: foxboro@xxxxxxxxxxxxx
> Onderwerp: Re: [foxboro] save_all scripts (was: Backup strategies - Best
> Practices?)
>
> Hi Thom,
>
> Just in case you were talking about "our" infamous save_all.sh script.
> Below is the "code" for a load_all.sh companion.
> Hoping you will find it useful.
> We did not make too much noise for this one as it can be rather
> dangerous in the hands of the less informed.
> We have used it several times when performing day_0 upgrades where all
> CP's needed a load_all. It is very good for that.
>
> One issue I would like to address is the base tool as found in
> /opt/fox/ciocfg/api is somewhat "impatient" waiting for the checkpoint
> to complete. So after the load all you may have a good working CP but no
> checkpoint file!!
> It is a good idea to checkpoint manually in the end to make sure you
> will have something to reboot from.
>
> !!Of course all of you are free to enhance this example into something
> you really want to use!!
>
> Best regards
>
> Ron Deen
>
> Begin++++++++++++
> #!/bin/sh
> # load_all example script. use with the greatest caution!!!
> # Foxboro Nederland N.V. Ron Deen
> ########################################################################
> ###
> # 15-11-2001  Initial release
> #                   No real tests except load_all on prepared station
> #                   Just an example scripts. Use at your own risk.
> #                 UNSUPPORTED SOFTWARE!!!
> ########################################################################
> ###
> VERSION="Version 1.0 / UNSUPPORTED SOFTWARE / Use at you own risk"
> PROG=`basename $0`                # Returns this script's name without
> the path
> CURDIR=`pwd`                      # the current directory.
> SA_DIR="/opt/SAVEALLS"            # Location of save_alls.
> ########################################################################
> ###
> # Function to display command usage and exit
> ########################################################################
> ###
> usage_exit ()
> {
>    echo "$VERSION"
>    echo
>    echo "Usage: $PROG letterbug"
>    echo "Station must be initialized AND rebooted before this action"
>    exit 1
> }
> ########################################################################
> ###
> # If no options, show usage info and exit.
> ########################################################################
> ###
> if [ ! $# -gt 0 ]
> then
>    usage_exit
> fi
> ########################################################################
> ###
> # Start here
> ########################################################################
> ###
> echo "Warning: Station $1 must have been initialized and"
> echo "rebooted, prior to load_all"
> echo "Press Control_C to abort, any key to continue"
> read key
> echo "Load_all for $1 starting."
> echo "Please wait for status reply (can take some time)"
> cd /opt/fox/ciocfg/api
> # ./load_all $1 $SA_DIR/$1 >/dev/null 2>&1
> ./load_all $1 $SA_DIR/$1
> LAERR=$?
> if [ $LAERR -ne 0 ]
> then
>    echo "$PROG encountered errors:"
>    if [ -f /tmp/output* ]
>    then
>       cat /tmp/output*
>    fi
> else
>    echo "Load_all for $1 successfully finished"
> fi
> End++++++++++++
>
>
> Met vriendelijke groeten / Kindest regards,
>
> Ron Deen
> Technical Sales consultant
> Invensys Systems N.V.
> T: +31 (0)35 54 84 233
> F: +31 (0)35 54 84 175
> M: +31 (0)653 963 616
> E: Ron.Deen@xxxxxxxxxxxxxxxx
> www.ips.invensys.com
> FPAL Supplier Number: 10049469
>
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Chaiket, Thom
> Sent: woensdag 28 januari 2009 20:04
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] save_all scripts (was: Backup strategies - Best
> Practices?)
>
> Hi all--
>
> Just a quick follow up on save-all.
>
> We set our system up so that a copy of the save all files resides on the
> host workstation and another is backed up onto an external drive.  My
> interest is in restoring these files.
>
> Is it correct that I still need the save all files on floppies in order
> to perform a load all?
>
> I checked on support website and didn't see anything that says
> otherwise.
>
> Thanks,
>
> t
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Ron Deen
> Sent: Tuesday, December 09, 2008 2:42 pm
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] save_all scripts (was: Backup strategies - Best
> Practices?)
>
> Just out of curiosity: Since Duc finds our script the better one and I
> would
> run into you at a Fox gettogether, would I stand a chance in getting a
> beer
> too?
> You see, I mentioned the script was "free as in beer" but never had the
> chance
> to experience this...
>
> Just kidding
>
> Ron
>
> On Tuesday 9 December 2008 19:29:08 duc.do@xxxxxxxxxxxxxx wrote:
> > Corey, et al.,
> >
> > The two scripts are unrelated, though the basic action is one and the
>
> same,
>
> > of course.
> >
> > Ron's contribution, which is available from the Cassandra Project
>
> archive,
>
> > is the one with all the bells and whistles. Its best feature is the
> > archiving of multiple versions of the saveall files, which makes it
>
> the
>
> > better script in my opinion.
> >
> > My script, bsave, is not available from the Cassandra archive because
>
> I put
>
> > it up on my own Web site (http://www.thedos.org/foxia/utils/) before
>
> the
>
> > dawn of The Cassandra Project and never moved it. It is no frill, but
>
> it
>
> > works for my purpose (actually, Dow Corning's), and I'm glad it works
>
> for
>
> > you.
> >
> > Duc
> >
> > PS. I'm looking forward to that free beer, Corey.
> >
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
>
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
>
> > Behalf Of Corey R Clingo Sent: Tuesday, December 09, 2008 12:59 PM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: [foxboro] save_all scripts (was: Backup strategies - Best
> > Practices?)
> >
> > Out of curiosity, are Ron's script and Duc's script (on Cassandra)
> > related?  Or were they developed independently?
> >
> > I've never seen Ron's, but have used Duc's for quite awhile here.
>
> Thanks,
>
> > Duc!  If I ever see you at a Fox get-together, I'll buy you a beer --
>
> so,
>
> > yes, you can get free beers from a script.
> >
> >
> > Corey Clingo
> > BASF Corporation
>
> _______________________________________________________________________
> 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
>
>
>
> * 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_id=77&nav_id=80&prev_id=7
>7 .
>
> 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:             http://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 - www.avg.com
> Version: 8.0.233 / Virus Database: 270.10.15/1922 - Release Date: 01/28/09
> 19:24:00
>
>
>
> _______________________________________________________________________
> 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


 
 
_______________________________________________________________________
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: