Microsoft SQL Server

Public Check Items

Check the database environments of the production end and the DR end where databases reside.

1. For an SQL Server cluster, set the different SQL Server network names when creating production cluster and DR cluster to ensure name uniqueness.
2. For a WSFC cluster, grant the Authenticated Users permission to SQL Server databases.
   1. On the database management page, select Security > Logins, right-click New Login.
   2. In the dialog box that is displayed, click Search.
   3. In the Select User or Group dialog box that is displayed, select Authenticated Users.
   4. Click OK.

Check Items at the Production End

1. Check the authentication method of SQL Server databases at the production end.

   Hybrid authentication must be adopted for SQL Server database, or the connection to the database fails.

2. Ensure that the name, user name, and password of the SQL Server database at the production end meet the following requirements:
   • The database name can contain only letters, digits, and special characters including _ - @ # $ *
   • The database user name can contain only letters, digits, and special characters including _ - @ # $ *
   • The database password can contain only letters, digits, and special characters including ~ ! % _ - @ # $ *

3. Check the VSS service status of the application host where the production SQL Server database resides.

   The eReplication Agent uses the VSS service to ensure consistency between SQL Server databases. Therefore, the VSS service must be enabled.

4. Check the database files at the production end.
   • Data files and log files in databases must be stored on storage array LUNs.
   • The disk resources where database files reside must be in Maintenance mode in the cluster manager before the database test or recovery, or the disk resources may fail to be mounted when the database is being started.

5. Grant the connect permission to database user guest.
   

   The permission granting is applicable only to the production environment where SQL Server 2012 (either in standalone or cluster mode) is in use.

   1. On the database management page, select the database that you want to configure and click Properties.
   2. In the Database Properties dialog box that is displayed, click Permissions.
   3. Click Search.
   4. In the Select Users or Roles dialog box that is displayed, enter guest and click Check Names to check the name validity.
   5. Click OK.
   6. On the Explicit tab page, select Connect.

Check Items at the DR End

1. Check the database environment at the DR end.
   

   If the database environments at the DR end and production end are not the same, the user should deal with it to make sure that the DR end and production end have the same database environments.

   Table 1 lists configuration requirements.

   Table 1 Configuration requirement of the DR databases

   Check Item	Configuration Requirement
   Installation	The operating system type and version run by SQL Server databases are the same as those at the production end.
   	The SQL Server database version is the same as that at the production end.
   Database	The names, instance names, user names, and passwords of databases are the same as that at the production end.
   	Paths to data files and log files of the databases are the same as those at the production end.
   SQL Server cluster	The names of the resource group and the disks in the resource group are the same as those at the production end.
   	Names of failover clusters on the same network are unique.
   	The disk resources where database files reside must be in Maintenance mode in the cluster manager before the database test or recovery.
   	The disk resources where database files reside must be in Maintenance mode in the cluster manager before the database test or recovery, or the disk resources may fail to be mounted when the database is being started.
   	After the DR cluster host restarts or resets, or cluster services reset, check the status of all resources in the failover cluster manager. For disk resources whose status is Offline and database disk resources for which database DR will be performed, set the status to Maintenance.

2. Set databases at the DR end offline.
   

   Do not close instances to which the databases belong.

Check Items at the Storage End

1. Perform the checks on storage at the production and DR ends.

   If you use storage array remote replication to implement DR protection for the database, establish a remote replication relationship on the storage device management software page between the production end and DR end and ensure that the replication status is normal.

2. Perform the checks on storage at the DR end.
   1. After setting up the application environment for the DR end, remove host mappings of the LUNs or volumes that store data files, control files, and log files of the applications.
   2. Delete the LUNs mapped to the DR or test hosts to ensure the corresponding disk drive will not be occupied by other LUNs.
   

   In the SQL Server cluster, the cluster must be in Maintenance mode before demapping LUNs.