Page History

...

• SQL Server - Select a registered SQL Server. 
• Database - Create a new database or select the database that receives the transaction log restores. To create a new database, type directly the database name in the Database field. If you want to select an existing database, click Select to access the list of databases available on the selected instance. 
• Initialization - Determine the initial state of the secondary database that receives the transaction log restores. By default, this field is set to Initialize database with a newly generated full backup. (copy only). When you click Change , a window for Database Initialization options opens where you can choose:
  • Do not initialize - Database exists and has received the most recent full backup of a primary database.
  • Initialize database with a newly generated full backup  - Selected by default. This is the only option available when SQL Safe detects the primary database was previously configured to use the simple recovery model. Since database backups using the simple recovery model lack log checkpoint information necessary for subsequent log restores, the  database requires a new full backup to initialize the secondary database. 
  • Initialize database with these backups -  If you enable this option, you can specify the location of the backups and add encryption settings. In this section you can:
    • Add - type the UNC or local backup file path path.
      
    • Add from repository - select this option, and click Load Backups.
  • Database File Locations - You can also click  Database File Locations to  choose where to store your database files. SQL Safe displays each database file (by logical name) and the directory where each will be stored. Filenames will be dynamically generated using the file type and destination database name. 

...