Problem Recovery (DR) requires some plans and procedures that enable the restoration of important business information and allows the IT infrastructure to be repaired to a previous state. DR was formerly seen as the domain of the IT team who were given obligation for mitigating the risk. To reduce the risk, system copies were scheduled often and intense DR options that involved host cool start techniques and data backups were implemented.
The goal was to displace the infrastructure to the past place where the data have been copied (at enough time, an average of on tape). The acceptable DR practices at the time permitted the IT program to be rebooted once the service energy was finally restored... Unless it had been in a flood zone or the off-site copy storage facility had already been impacted. Either way, the operation of the facility might be disrupted for some time period and the data restoration was also potentially at risk depending on where copies were stored lowest price.
Now let's roll the schedule ahead... As technology evolved therefore did the Tragedy Healing methods, which cause new methods that changed to certain requirements for a Business Continuity solution as a means of mitigating risk. Still seen as the domain of IT, as technology transferred towards answers like darkness machines, distributed information places and top speed majority data sign with hyper connectivity. Data no more needed to be "recovered", it really had to be linked in distributed places where maybe it's remotely accessed. Business Continuity mitigated the risk of information loss and allowed a business to recoup a great deal more easily and effortlessly from the Black Swan occasion because its servers never went completely down.