A site where one or more Bravura Security Fabric servers is installed is offline
A destroyed or offline site should be immediately detected by network monitoring systems in general. Detecting disasters is not a function of Bravura Security Fabric , although symptoms will be evident.
What stops working | What continues to work | Possible Causes | Data loss | Resolution |
---|---|---|---|---|
If the site is destroyed, assuming that there are Bravura Security Fabric servers running in at least one other physical site, this is equivalent to the failure in Single Bravura Security Fabric server fails . If the site is just knocked offline (for example, all connectivity temporarily lost), this is equivalent to a combination of User loses connectivity, Link between two Bravura Security Fabric servers goes offline or Link between Bravura Security Fabric servers and proxy servers goes offline. | Users at other sites can still access data from Bravura Security Fabric servers at other sites, as described in DB COMMIT SUSPEND mode . Operations on some target systems will continue, from servers at other sites to target systems for which those servers are responsible. Users at an off-line site can still access local systems at their local site. They can even access data for systems at other sites, but obviously cannot connect to those other sites. | A complete data center goes offline. This may be due to power outage, fire, flood, earthquake, hurricane, tornado, or something else. The site may be permanently damaged or simply taken offline for a while; for example, digging equipment cuts all network links to the site. | None, unless an extremely unlikely race condition takes place:
| If the problem is site-wide connectivity and it can be resolved quickly. See Time available to fix problems , wait for the site to come back on-line. If the site was physically destroyed, see Removing a node from replication for instructions on removing affected servers from replication and ultimately building and initializing replacement servers. |