Step 2. Specify Connection Settings
At the Connection Settings step of the wizard, provide the connection settings for the selected database.
- Specify the database engine, Microsoft SQL Server or PostgreSQL
- Specify an instance and a database name to which you want the Veeam Backup & Replication installation to connect.
- For the Microsoft SQL Server, specify an instance name in localhost\instanceName format.
- For the PostgreSQL, specify an instance name in localhost\instancePort format.
Both local and remote Microsoft SQL Server and PostgreSQL instances are supported. Microsoft SQL Server instances available on the network are shown in the Instance name list. If necessary, click Refresh to get the latest information.
If a database with the specified name does not exist on the selected Microsoft SQL or PostgreSQL instance, it will be created anew.
If you change the database to which Veeam Backup & Replication must be connected, make sure that the database to which Veeam Backup & Replication is currently connected is available. If not, you must stop the Veeam Backup Service on the machine where Veeam Backup & Replication is installed.
- Select the authentication method that will be used for database connection:
- If you plan to use the Microsoft Windows authentication, consider that the current service account will be used (that is, the account under which the Veeam Backup Service is running).
- If you plan to use the Microsoft SQL Server or the PostgreSQL native authentication, provide a login name and a password. To view the entered password, click and hold the eye icon on the right of the Password field.
When you migrate the configuration database to another server, you must use the Microsoft SQL Server credentials that have CREATE ANY DATABASE permission on the target Microsoft SQL Server. For details, see Microsoft Docs.
After database creation this account automatically gets a db_owner role and can perform all operations with the database. If the current account does not have this permission, a Database Administrator may create an empty database in advance and grant the db_owner role to the account that will be used for migration of the configuration database.