
Explanation:
Section: Deploy and migrate applications
Step 1: Perform a tail-log backup.
A tail-log backup captures any log records that have not yet been backed up (the tail of the log) to prevent work loss and to keep the log chain intact. Before you can recover a SQL Server database to its latest point in time, you must back up the tail of its transaction log. The tail-log backup will be the last backup of interest in the recovery plan for the database.
Step 2: Restore a full backup.
Backups must be restored in the order in which they were created. Before you can restore a particular transaction log backup, you must first restore the following previous backups without rolling back uncommitted transactions, that is WITH NORECOVERY:
The full database backup and the last differential backup, if any, taken before the particular transaction log backup.
Step 3: Restore the log backups.
Log backups must be applied in the sequence in which they were created, without any gaps in the log chain.
Step 4: Restore the tail-log backups.
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-a-transaction-log-backup-sqlserver
https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/tail-log-backups-sql-server