How do admins manage RTO for sql server with large number of dbs?
Assuming I have 140 dbs and daily full and log backups.
The crash recovery process would be to restore each db one by one using the backups.
Therefore the RTO to get the system up ready will be high since the number of dbs is large.
How do experienced dbas manage RTO in such situations?
In such a scenario where you need to restore so many databases, you're best off creating scripts or application code to help automate the process.
There are also tools to help database and server management out there such as https://dbatools.io which are really powerful for automation and scripting.
Additionally, if a quick RTO (Recovery Time Objective) is required, this is where other DR (Disaster Recovery) solutions can be more helpful, such as https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server?view=sql-server-ver15 .