Log shipping requires a primary server and a secondary server. It works by creating a full database backup to a secondary server to back up the existed data in the primary server, and creating transaction logs with continuous updated data restoring from the primary to the secondary server.
Pro: Log shipping supports a delay parameter. If you catch a database error within the delay interval, the secondary can be used to help recover the database from the error.
Con: Users have to recover the back-up server, in another word, to stop log shipping to be able to retrieve the data from the secondary server.