Tom,
The issue is that during the backup of the BI users are complaining that they get kicked off; they are complaining that they cannot get their shipments processed in a timely fashion, etc. I have told them that they just need to be aware that this is an iffy time period for processing. I do want to understand what can be done going forward. I viewed the last four years worth of database logs and found that the BI backup time has gotten progressively longer, from a few seconds to the current 4-5 minute time frame. I did notice a noticeable increase when the database was upgraded to Open Edge10.1C from 30 seconds to 90 seconds. I just don't want this to continue until it becomes a problem.
I did not speak clearly enough; QAD does not promote GL Report Writer with its current version (and for some time). We have support for the QAD product itself, and they will help us with issues, but the probability of getting them to dramatically change the way that the product works is unlikely. We could upgrade to OE based on needs like this, and I will consider this an option. This would occur if the solution lies within an upgrade, and the problem becomes bad enough to deem it worthy. Replication has been looked into in the past for fail-over purposes and was shot down. I do not think that this is a powerful enough argument to go to Replication now. The companies long-term plan is to go to SAP in 2015 and there will be little done to upgrade anything. However, users not being able to ship product is a priority no matter what, so anything is possible; just not probable.
Any dramatic change in storage design would not be ideal. I believe the storage space to not be the issue, but the coding. Plus, the entire GL Report Writer table and index sets are in their own storage area already.
I am interested in changing the cluster size and would welcome suggestions for correct sizing to achieve the desired results with acceptable OS and hardware impact. I am unfamiliar with the -Bp 100 parameter, but I will look that up to see its impact and use.
Thanks for your input!
David