Impact of Data Loss
Component | Impact | Criticality | Best Practice |
---|---|---|---|
/Work | If some of all of the work files are lost, any suspended workflows will fail.
When events are viewed, any links to associated files will not work, and when clicked, may throw an exception that the file is not found. |
Non critical | Regular Backups.
Point in time recovery possible by using disk replication. |
/Temp | No impact. | None | Ignore. |
/Received | Minimal impact, the files received from external systems are lost. All the files are already processed and in most cases, likely copied to another location in /Work directory. | Non critical | Regular Backups.
Point in time recovery possible by using disk replication. |
/Sent | Minimal impact, the files sent to external systems are lost. All the files are already processed and in most cases likely copied from another location in /work directory. | Non critical | Regular Backups.
Point in time recovery possible by using disk replication. |
/<enterprise specific directories> upload | The Data source list screen refers to these files. On clicking these files, an error will be displayed. | Non critical | Regular Backups.
Point in time recovery possible by using disk replication. |
Database files | Contains all critical data. | Critical | Regular Backups.
Point in time recovery possible by using standard database replication/hot standby practices. |
Configuration MQ_HOME/config, MQ_COMMON_DIR/<enterprise specific directory> | All customization and instance configuration. | Critical | Use a version control system and implement Disaster Recovery for the version control system. |
Configuration MQ_COMMON_DIR/standard | Can be extracted from the distribution provided by TIBCO. | None | Back up the distribution provided by TIBCO. |
Messages in queues | Some workflow requests will be lost and in progress workflows will fail. | Critical | Implement failover and disaster recovery for the JMS server. |
Copyright © Cloud Software Group, Inc. All rights reserved.