Home > Storage > PowerStore > Virtualization and Cloud > Dell PowerStore: Microsoft Hyper-V Best Practices > Cost and risk analysis
The most robust DR solutions might also be cost prohibitive. These solutions might require weighing the costs compared to the risks and determining the level of DR protection that is necessary. Factors to consider as part of a cost and risk analysis include:
Determine the recovery-time objective (RTO) for each application or service. In other words, the RTO is the time period that can something be down before the business impact becomes too great. Examples include:
Determine the recovery point objective (RPO). In other words, the RPO is the amount of data loss that is acceptable for a subset of data. If PowerStore snapshots are used to project a workload, and snapshots are taken every 24 hours, the RPO is up to 24 hours. An RPO of 24 hours means up to 24 hours of data loss might occur if the workload is recovered from the last snapshot. The frequency and retention of PowerStore snapshots can be increased to shorten the RPO as needed.
Determine the types of events that are most likely to occur in your area. For example, a coastal location might be prone to hurricanes or flooding.
Identify an alternate site that is distant enough so that the same event does not impact both locations.
Determine the cost (hardware, software, and staff) to design, implement, and support the necessary protections. Is the cost justified given the risk?