3. I have long been an anti-proponent for automated save-alls and even
checkpoints. Your quandry is one of the best examples I can give to avoid
automating something so important as your control database backups.
Sorry, but I fail to see what is so great about this example:
The system
Is the Micro I/A similar to the CPs in that the current setpoints are only
saved to the database via upload? A checkpoint only saves the setpoint
and alarm parameters that are in the block at the time of configuration. To
save the current parameters that are changeable by the operator
Hi,
Upon resumption of power and station startup, the
system has strange setpoints for example that
were not there at the time of checkpointing.
Hints anyone ?
Are you probably using Setpoint Tracking?
best regards -
Marcel Sieling
Systems Technologies
List,
It seems to me that there are more ways to configure Apache than there are
people willing to do it. It has to be one of the most configurable
packages there is. I see a couple of options here
1) Configure your DNS so it has an alias for your AW, then configure Apache
so that any
Or, we could design the system in the first place to allow save-alls while the
configurator is running, and maybe prevent a save in the configurator to a
compound that is currently being saved. Or better yet, do away with all these
different database snapshots (save-alls, checkpoints, ICC
Thanks to all for all of your helpful suggestions.
Thanks to Alex for offering to examine my control database. Unfortunately,
his prognosis (It's fried!) was not what I wanted to hear.
Thanks to Bo for his suggestion of using check_db_sync. I didn't get around
to using it, but I'll have to make
