How to initialize subscription through database backup

Initialize subscription:

1. Use the page to create a release item on the Publishing Server. Check "create snapshot now and make the snapshot available to initialize the subscription ". That is, @ immediate_sync = n'true'

2. Use the interface to modify the "allow initialization from backup file" of the release item to true. That is, @ allow_initialize_from_backup = n'true'

3. All the databases in the previous release have one full backup, and one transaction log is backed up by 'd: \ dbbak \ REPL. trn'

4. The Subscriber server restores a subscribe database in the norecovery state from the full backup of the Publishing Database, and then restores the published log backup, status recovery

5. Use the script command sp_addsubscription to add a subscription. Note the following parameters: @ sync_type = n' initialize with backup'. Two parameters must be added:

@ Backupdevicetype = 'disk', @ backupdevicename = 'd: \ dbbak \ REPL. trn' -- this is the directory of the Publishing Server and the log backup of the publishing library.

6. Do you seem to have to worry about not for replication? It is found that as long as a publishing item is created for the table, whether or not there is a subscription, the publishing table will be added with not for replicaction?

Refer:

How to: initialize a transactional subtasks from a backup with multiple backup files