Yes, I understand that and the function that CSA serves. I forgot that, as you
are well aware, the systems at this site are old and that also puts us at a
higher risk. Although my inquiry was directed at an AW70 WinNT system, do the
check_db_sync and csa_save utilities also exist on a UNIX V6.5 system; same
logic.
Thanks for your blessing... :-)
Sent from my iPhone
On Apr 28, 2016, at 7:28 PM, Boulay, Russ
<Russ.Boulay@xxxxxxxxxxxxxxxxxxxxxx> wrote:
No harm in doing it. For parameter changes useless. So only if compounds or
blocks have been added.
Sent from my iPhone
On Apr 28, 2016, at 10:22 PM, Joseph M. Riccardi <Joe@xxxxxxxxxxxxx> wrote:
Thanks Russ... I understand all of that but why could it not also be used
as part of a proactive* maintenance program. We are a GMP site so we do not
make many ICC changes (usually just small projects) but I am proposing that
after every ICC change we run csa_save and backup that file just in case?
Assuming we have a good check_db_sync, now would be the time to start. With
the clone Node we use here to test all changes and then implement them on
the production Node, I just fear that there is a potential to get files/CPs
out of synch. That would be disastrous at a GMP site. So I ask why not, is
there any harm in doing it?
* (www.merriam-webster.com/dictionary/proactive - controlling a situation by
making things happen or by preparing for possible future problems.)
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Boulay, Russ
Sent: Thursday, April 28, 2016 6:57 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CSA_Save
csa_save is for the intent to move CSA hosting to another machine.
Where you have confirmed by check_db_sync is good and you are upgrading a
host or just moving csa to a higher version of software.
Those saves become useless if your CP and workfile are ever out of sync They
are only good if csa gets corrupted somehow and what you csa saved has had
no changes to workfile or CP since that save
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: Thursday, April 28, 2016 9:51 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CSA_Save
Last chance to comment on my CSA_Save plan before I do something stupid
Friday... :-)
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: Wednesday, April 27, 2016 10:37 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Or would saving the entire /opt/fox/csa folder be a better approach?
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: Wednesday, April 27, 2016 10:20 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Same site, same AW70 WinNT Node; different question... CSA_Save. I built a
clone Node for use as a development and testing Node, disconnected from the
production Node. We try to keep the 2 Nodes in synch but I have always been
concerned with the ICC workfiles and the CPs getting out of synch. Is the
CSA_Save utility intended to be used as a preventative measure? If I
understand how it works it is useless once the ICC workfiles and the CPs are
out of synch. My plan has been to periodically run CSA_Save and back up
those files, just in case. Is this the intent of CSA_Save? If it is, I
cannot see why this procedure would not be in everyone's periodic
maintenance procedure, just in case? What am I missing?
And I just want to make sure running it will not cause any problems on
existing host's CSA files.
Thanks
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which it
is addressed. This e-mail is confidential and may well also be legally
privileged. If you have received it in error, you are on notice of its
status. Please notify the sender immediately by reply e-mail and then delete
this message from your system. Please do not copy it or use it for any
purposes, or disclose its contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally
privileged. If you have received it in error, you are on notice of its
status. Please notify the sender immediately by reply e-mail and then delete
this message from your system. Please do not copy it or use it for any
purposes, or disclose its contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
