When you create a Microsoft SQL Server database, you must configure it correctly to support vSphere Replication.
Before you begin
Verify that the SQL Server Browser service is running.
About this task
You use SQL Server Management Studio to create and configure an SQL Server database for vSphere Replication.
This information provides the general steps that you must perform to configure an SQL Server database for vSphere Replication. For instructions about how to perform the relevant steps, see the SQL Server documentation.
- Select Mixed Mode Authentication when you create the database instance.
The vSphere Replication appliance and the database server run on different hosts, so you must use mixed mode authentication and not Windows Authentication.
- Use either a named instance or the default instance of SQL Server.
If you intend to use dynamic TCP ports, you must use a named instance of SQL Server.
- Enable TCP on the database instance.
- Set a TCP port.
Static TCP port
Set the TCP port to the default of 1433.
Dynamic TCP port
Use a named instance of SQL Server. You can only use dynamic ports with a named instance of SQL Server.
Select the Show DB URL check box in the virtual appliance management interface (VAMI) of the vSphere Replication appliance.
Modify the DB URL value. Replace port=port_number with instanceName=instance_name in the URL.
Use the PortQuery command from a remote machine to check that the port on which the SQL Server Browser service runs is not blocked by a firewall. The SQL Server Browser runs on port 1434. Type the PortQuery command in a terminal window.
PortQry.exe -n Machine_Name -p UDP -e 1434
- Verify that the firewall on the database server permits inbound connections on the TCP port.
- Create the vSphere Replication security login.
- Create the vSphere Replication database and set the vSphere Replication security login as the database owner.
- Keep the dbo user and dbo schema settings.
Because the vSphere Replication security login is the database owner, it maps to the database user dbo and uses the dbo schema.