Log shipping to fix unintended deletion? I am reading the book 'Pro SQL Server 2019 Administration' from Carter:

In a scenario in which a user accidentaly deletes data; he mentions that we can recover the data (from the DR server) and then &quot;repopulate the production server&quot;.
Then he adds &quot;This means that you do not need to restore a backup to recover the data.&quot;
What he means by 'repopulate'? and how is this better/different than a backup/restore?
Because the database at the DR site is in read_only mode, you can export the data from the DR table where the deletes occurred on the primary and 'repopulate' the primary server for just that one table using the data exported from the DR site.  This would be especially useful if the database is extremely large, because you would not have to restore the entire database to get just that one table recovered.
This, of course, assumes the log records containing the deletes have not been applied to the DR database.