Using the Database Verification Server and Account Authentication screen

If you want to defer specification of the database verification server (or if you do not plan to perform database verification at all), do the following:

1. Select the "Select a verification server later using the Options menu" dialog box.
2. Click Next.
3. Go to Step 5.

Later, if you want to specify a verification server outside of the Configuration Wizard, go to the menu bar and select Options > Database Verification Settings. For a detailed description of the Verification Settings dialog box, see Appendix C, Configuring SnapManager Application Settings.

Otherwise, to specify a verification server now, go to the Verification Server field and select the SQL Server instance you want to use to perform database integrity verification.

Note
It is recommend that, for optimal performance, you use a different SQL Server as the verification server.

If this is a MSCS environment, you cannot select an SQL Virtual Server as the database verification server.

In the Connection panel, choose the security authentication method to be used to connect to the SQL Server.

• Windows authentication
• SQL Server authentication

If you choose Windows authentication mode (the default selection), users with a valid Windows account can log in to Microsoft SQL Server without supplying a user name and password. Windows Authentication relies on the user being authenticated by the operating system and takes advantage of Windows user security and account mechanisms.

Note
Windows Authentication is the authentication mode recommended by Microsoft.

If you selected SQL Server authentication, you must also specify the login name and password.

For more information, see SnapManager service account requirements.

Click Next.

Result

The Configuration Wizard proceeds to the Where to Move Databases screen.