"The Cloud" allows you to pay for what you use, when you use it - but how do you solve the problem of USING it? You've got legacy platforms that can't be replaced just yet, and you need a plan for everything to keep running.
8. Solution Approach
1. Easy Wins – native replication or clustering
2. RTOs & RPOs
3. VMs – what can be protected as a portable unit?
4. Physicals
1. Are any pending virtualization?
2. Does it support recovering into a VM?
3. Does it require a matching physical system?
5. Networking
1. What carriers are required?
2. What does the data change rate look like?
6. “Where are the eyeballs?”
1. Is workspace needed to ensure consistent data flow?
7. Security
1. What frameworks must be adhered to?
15. Summary
1. Focus first on your Applications and
People
2. Derive RTOs and RPOs
3. Collect your data
4. Map requirements to infrastructure
and technologies to best fit those
individual needs
Hinweis der Redaktion
Mitigate Risk with Hybrid Disaster Recovery in the Cloud
Pragmatic Business Continuity for Non-Trivial Environments
Recover to someone else’s infrastructure
Only pay for what you use, when you use it!
Methodology
Your Applications
Drives IT infrastructure needs (network, compute, storage, security)
Consumed by employees and clients
People
“Where are the eyeballs”
RTOs & RPOs
Methodology
Your Applications
Drives IT infrastructure needs (network, compute, storage, security)
Consumed by employees and clients
People
“Where are the eyeballs”
RTOs & RPOs
Now that needs have been established, lets look at mapping to solutions
first, some applications are best served as live replicas, such as active directory. These take precedence
Next, look at the RTOs and RPOs for order of magnitude for the solution’s design.
VMs can offer portability and should be examined next
Physical – includes appliances, PBXes, DB servers, etc.
Networking – are we using an existing network? MPLS? Look at backup data in prod to understand the daily change rate and impact to WAN
Eyeballs – how do users interact with this environment? Do you need workspace to ensure local proximity?
Security – what frameworks must be adhered to? Is the org comfortable with shared resources?