Oneshield Disaster Recovery Plan
OneShield lacks a proper disaster recovery (DR) plan. These plans involve a set of policies and procedures that enable the recovery of data, should it ever be destroyed or lost by natural, technical, or human-error-based disasters.
As IT systems have become increasingly critical to companies, the importance of ensuring the continued operation of those systems, and their rapid recovery, has increased. This is especially true for OneShield, who provides technology services for insurance companies. , There is a need to protect the data from loss.
We know from OneShield that these type of occurrences can and do happen, simply by looking at the company’s SANpocalypse incident we introduced before. Since OneShield doesn’t have a disaster recovery …show more content…
plan, they can’t get data recovered when backup site was destroyed together with the working system. If the office is destroyed by natural or human disaster, there would be a huge lost of the company.
We suggest that OneShield implement a disaster recovery plan.
OneShield has many offices. They can build the backup sites in different buildings and different offices in case that one office is destroyed by unexpected issues. For example, when the SANpocalypse incident happened, we could use the backup site in another building to retrieve lost data. It is rare to get both two buildings damaged at the same …show more content…
time.
As for disaster recovery plan, there are three types of backup sites, including cold sites, warm sites, and hot sites. The differences between the types are determined by the costs and effort required to implement each. A hot site is used when an organization can tolerate little or no downtime. It is a duplicate of the original site of the organization, with full computer systems as well as near-complete backups of user data. A hot site is current and online and data is replicated from one site to the other in near-real-time. When the primary system goes down, we can activate the backup system immediately with little to no downtime.
A cold site is best understood as one in which servers are configured and set up in a secondary site, however, they may not be powered on.
Backups of data are transferred to the cold site regularly, but infrequently. In the event that the primary site fails, the secondary site can be brought online, however, changes made since the last backup may be lost. Additionally, it will take some time to bring all services back online at the cold site. The benefit of a cold site is usually its relative cost.
A warm site is a blend between the other two options (hot and cold sites). In a warm site, data is replicated frequently, but not in real time. For example, data may be replicated once every 30 minutes. Additionally, the data is kept in an offline state. This means that in the event of a failure at the primary site, data would be lost since the last replication (in this case, 30 minutes of data). The secondary site would then need to power up the virtual machines, however, the VM hosts should remain in a powered-on state to allow for the data
replication.
One of the important decisions we have to consider is the selection of an appropriate DR site type. As with many IT decisions, we are faced with a cost vs. performance tradeoff. The more spent, the greater the capability of a site to quickly resume operations. There are not always disaster situations happened in business. We are not going to invest too much in DR plan. However, we don’t want that once the disaster appears that destroy the company’s business. To figure out the balance point, we will choose an appropriate site.
Cold sites are designed to provide coverage for long-term outages of the primary site, such as those caused by a building fire or other major disasters. When a disaster occurs, the company must acquire the hardware necessary to resume operations, build systems, install applications and load data from backup sites.The recovery time for cold sites would be days or weeks rather than in hours. For cold site, we can reserve space in a third-party cold site that will be available for use in the event of a disaster. And we can also create a cold site in a facility already owned by OneShield.
However, sometimes for OneShield the long activation time required to stand up a cold site presents an unacceptable risk. As for warm site, company can activate the warm site in a matter of hours. And hot sites build upon the warm site concept by taking it to the next level: ensuring that systems at the site are preloaded with operating systems, applications and the data necessary to resume operations. Hot sites are real-time recovery once the primary site fails. But the investment of time and money is huge.
To keep the system safe, to save money, we came out the disaster recovery plan that we should use a comprehensive plan made up by the three sites. For some important system, for example the core database in head office of OneShield in USA, we suggest that the company can use hot site to keep it safe. And for those normally used system and data, we suggest that OneShield uses cold and warm site while implementing the DR plan.
As IT systems have become increasingly critical to companies, the importance of ensuring the continued operation of those systems, and their rapid recovery, has increased. This is especially true for OneShield, who provides technology services for insurance companies. , There is a need to protect the data from loss.
We know from OneShield that these type of occurrences can and do happen, simply by looking at the company’s SANpocalypse incident we introduced before. Since OneShield doesn’t have a disaster recovery …show more content…
plan, they can’t get data recovered when backup site was destroyed together with the working system. If the office is destroyed by natural or human disaster, there would be a huge lost of the company.
We suggest that OneShield implement a disaster recovery plan.
OneShield has many offices. They can build the backup sites in different buildings and different offices in case that one office is destroyed by unexpected issues. For example, when the SANpocalypse incident happened, we could use the backup site in another building to retrieve lost data. It is rare to get both two buildings damaged at the same …show more content…
time.
As for disaster recovery plan, there are three types of backup sites, including cold sites, warm sites, and hot sites. The differences between the types are determined by the costs and effort required to implement each. A hot site is used when an organization can tolerate little or no downtime. It is a duplicate of the original site of the organization, with full computer systems as well as near-complete backups of user data. A hot site is current and online and data is replicated from one site to the other in near-real-time. When the primary system goes down, we can activate the backup system immediately with little to no downtime.
A cold site is best understood as one in which servers are configured and set up in a secondary site, however, they may not be powered on.
Backups of data are transferred to the cold site regularly, but infrequently. In the event that the primary site fails, the secondary site can be brought online, however, changes made since the last backup may be lost. Additionally, it will take some time to bring all services back online at the cold site. The benefit of a cold site is usually its relative cost.
A warm site is a blend between the other two options (hot and cold sites). In a warm site, data is replicated frequently, but not in real time. For example, data may be replicated once every 30 minutes. Additionally, the data is kept in an offline state. This means that in the event of a failure at the primary site, data would be lost since the last replication (in this case, 30 minutes of data). The secondary site would then need to power up the virtual machines, however, the VM hosts should remain in a powered-on state to allow for the data
replication.
One of the important decisions we have to consider is the selection of an appropriate DR site type. As with many IT decisions, we are faced with a cost vs. performance tradeoff. The more spent, the greater the capability of a site to quickly resume operations. There are not always disaster situations happened in business. We are not going to invest too much in DR plan. However, we don’t want that once the disaster appears that destroy the company’s business. To figure out the balance point, we will choose an appropriate site.
Cold sites are designed to provide coverage for long-term outages of the primary site, such as those caused by a building fire or other major disasters. When a disaster occurs, the company must acquire the hardware necessary to resume operations, build systems, install applications and load data from backup sites.The recovery time for cold sites would be days or weeks rather than in hours. For cold site, we can reserve space in a third-party cold site that will be available for use in the event of a disaster. And we can also create a cold site in a facility already owned by OneShield.
However, sometimes for OneShield the long activation time required to stand up a cold site presents an unacceptable risk. As for warm site, company can activate the warm site in a matter of hours. And hot sites build upon the warm site concept by taking it to the next level: ensuring that systems at the site are preloaded with operating systems, applications and the data necessary to resume operations. Hot sites are real-time recovery once the primary site fails. But the investment of time and money is huge.
To keep the system safe, to save money, we came out the disaster recovery plan that we should use a comprehensive plan made up by the three sites. For some important system, for example the core database in head office of OneShield in USA, we suggest that the company can use hot site to keep it safe. And for those normally used system and data, we suggest that OneShield uses cold and warm site while implementing the DR plan.