---
title: "Comment by Arqum Younus on \"Web Hosting for Developers: 12 Pre-Launch Checks\" | Hashnode"
description: "check 8, testing backups by restoring them, is the one that decides how a bad update goes, since “daily backups included” says nothing about restore time. (clou"
url: "https://hashnode.com/posts/web-hosting-for-developers-12-pre-launch-checks/6aa7f1041a3ee954114238b7/comment/6afc54e1f701928eeaa22876"
---

[Discussion](https://hashnode.com/posts/web-hosting-for-developers-12-pre-launch-checks/6aa7f1041a3ee954114238b7)

Comment [Web Hosting for Developers: 12 Pre-Launch Checks](https://hashnode.com/posts/web-hosting-for-developers-12-pre-launch-checks/6aa7f1041a3ee954114238b7)

[Arqum Younus](https://hashnode.com/@arqum)

[1d ago](https://hashnode.com/posts/web-hosting-for-developers-12-pre-launch-checks/6aa7f1041a3ee954114238b7/comment/6afc54e1f701928eeaa22876)

check 8, testing backups by restoring them, is the one that decides how a bad update goes, since “daily backups included” says nothing about restore time. (cloudways team here, so biased) on our flexible plans you can take an on-demand backup of an app’s files and database before a risky change and clone the app to staging to rehearse it, which fits check 12’s rollback rehearsal. do you set a different recovery time target per site when you manage several?
