I hear you Paul. We too thought our save/restore strategy was just not
going to work with BRMS as we tried to quiesce certain operations while
leaving others running. For example, when you ran multi divisions, and
the backup as a whole took hours, why keep them all out for hours instead
of just quiescing each division as needed? It took some business changes
to open my eyes to BRMS:
- Database consolidation.
- Why quiesce the main system at all instead of just saving from the
Mimix, and Domino cluster, machines?
Prior to this we were doing a ragged save while active with not a care in
the world about referential integrity. No sync. If the sum of the order
detail didn't add up to the order header after a restore that was
considered an acceptable risk versus kicking out users to save thw
Rob Berendt
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
