What is an RPO and RTO? and why you NEED to understand them as a Solutions Architect

When designing IT systems as a Solutions Architect you need to design in the ability to recover against failure. Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are how clients/customers can inform you on their demands for recovery ... both in terms of minimising data loss and improving recovery time. If you're a Solutions Architect ... you HAVE to understand both of these terms.

FOLLOW ME 😺

OTHER VIDEOS AND PLAYLISTS 🎞

All rights reserved © 2022 Adrian Cantrill

[stevezhang]

This video is the best one explaining RPO and RTO for an IT noob like me. Thanks for sharing.

[jebinsamuel]

Very nicely explained. As always, Adrian you are the best 🎉🔥

[readonlylogin]

Clear explanation and awesome visualisation. Thanks a lot!

[epap]

Fantastic video, well done. I wanted to hear more about what to do with lost data between RPO and RTO, how to deal with that.. manual? Or accept loss? or?

[YAskool]

Thanks for your clarification, may i know under which course this video?

[miar]

Hi Adrian! First, thank you so much for all of your valuable and high quality content! I truly appreciate it. I am interested in becoming aws csc account manager. I know you have previously said that you recommend that people start at the AWS Certified Solutions Architect Associate. Would that be the case with me as well? I have zero cloud/aws experience and I am looking into breaking into that role. Any advice is genuinely appreciated. ps: do you also have instagram or facebook acct? I tried finding you and couldn't find you. Thank you so much!