Product Name > arcserve Replication and High Availability. arcserve RHA Task > Configuration. Components: XOSOFT Replication: 12.5, 15.

Transcription

1 Configure MS SQL Replication to an MS SQL 2005 Reporting instance in conjunction with CA XOsoft/arcserve RHA Replication and High Availability Scenario. Product Name > arcserve Replication and High Availability arcserve RHA Task > Configuration Components: XOSOFT Replication: 12.5, 15.0 Last Modified Date: 10/25/2010 Document ID: TEC Tech Document Title: Configure MS SQL Replication to an MS SQL 2005 Reporting instance in conjunction with CA XOsoft/ARCserve RHA Replication and High Availability Scenario. Description: An MS SQL Server can be used as either an OLTP (Online Transactional Processing) or an OLAP (Online Analytical Processing Server). An OLTP server is used to process business transactions, while an OLAP server is used for running queries against the DB's in the SQL instance to generate reports. The reports can be used to analyze historical trends used to make business decisions. The same MS SQL server can be used as both an OLTP and an OLAP server, however this can sometimes cause performance issues. Performance issue occurs when the same MS SQL instance is used as both an OLTP and OLAP server as a result of the nature of large queries run against the DB for OLAP purposes. This can impact performance for all users, including those trying to make OLTP updates to the Database. As a result, a common solution is to configure a separate host with MS SQL Server instance and copy the database to the reporting instance. This allows users to run resource intense queries against the DB on the reporting instance for OLAP purposes while users continue to use the production server for OLTP updates and minor queries. While this resolves the problem of offloading resource intense queries, it introduces the need to periodically copy the data from the OLTP server to the OLAP server in order to maintain current data on the OLAP server for reporting purposes. The data copy from the OLTP server to the OLAP server can be done several different ways. 1 / 7

2 Backups of the DB on the OLTP Server can be periodically restored on the OLAP server, however this is a manual process that can be both time consuming and cumbersome. As an alternative, customers who are running CA XOsoft/ARCserve RHA scenarios often attempt to use the DR/HA Replica as the SQL Server OLAP instance. This doc is to demonstrate how to configure a CA XOsoft/ARCserve RHA scenario to replicate MS SQL to a MS SQL 2005 reporting instance. Solution: Note: It is mandatory that you familiarize yourself with MS SQL Replication concepts prior to implementing this solution. Please refer to the section pertaining to "SQL Server Replication" in the "SQL Server Book Online". Configure SQL Replication Using a Push Replication Model I. Configure the Master server with the MS SQL Distributor Role 1. Open MS SQL Server Management Studio and connect to the Master Server. 2. Right-click the Replication tab and select Configure Distribution to launch the Configure Distribution Wizard. 3. Select "'<MasterServer>' will act as its own Distributor; SQL Server will create a distribution database and log." 4. Specify the snapshot folder. 5. Specify a name for the Distribution DB and the paths for the Database and Log files. 6. Enable the Master Server as the Publisher. 7. Accept the Configure Distribution default and continue by clicking NEXT. 8. Finish the Configure Distribution Wizard. II. Configure the Master server with the MS SQL Publisher Role 1. Open MS SQL Server Management Studio and connect to the Master Server. 2. Open the Replication folder, then right-click the Local Publications folder to open the options menu. 3. Select New Publication to launch the New Publication Wizard. 4. Select the Database(s) that you want to replicate to the SQL Reporting instance (OLAP) server. All published tables in transactional replication must contain a declared primary key. Existing tables can be prepared for publishing by adding a primary key using the Transact-SQL statement ALTER TABLE (Transact-SQL). Refer to the MS SQL Server Books Online for additional information on the requirements to publish a table for replication as well as the methods to create a Primary Key using either the MS SQL Server Management Studio GUI or the ALTER TABLE (Transact-SQL) command. 5. Select the Publication Type you would like to use for the publication. 2 / 7

3 6. Select the Tables within the Database(s) which you would like to replicate to the SQL Reporting instance (OLAP) server. 7. Configure filtering of table rows (optional). 8. Configure the snapshot agent. Here you can configure the initial snapshot to execute immediately, or you can schedule it to run during an off peak time. Data will not be available on the Reporting instance for queries until the snapshot has been executed and the Subscription Database has been synchronized with the Publication Database. 9. Configure Snapshot Agent Security. 10. Accept the Create Publication default and continue by clicking NEXT. 11. Define a Publication Name and select FINISH. III. Configure the MS SQL Reporting instance with the MS SQL Subscriber 1. Open MS SQL Server Management Studio and connect to the SQL Reporting Instance (OLAP) server. 2. Open the Replication folder, then right-click the Local Subscriptions folder to open the options menu. 3. Select New Subscriptions to launch the New Subscription Wizard. 4. Click the Publisher Dropdown and select "<Find SQL Server Publisher>". 5. Populate the Server Name field with the name of the Master Server. (This was previously configured as the Publisher in the previous set of steps) 6. Select the Publication(s). 7. Define the location of the Distribution Agent. This determines whether you are configuring the SQL replication to use 'Push' or 'Pull' Replication. Pull Subscriptions reduce overhead on the Distributor, which is your production server. 8. Define the Subscriber and the Subscription Database. You can opt to create a new Database. This will be the database that users query when running reports on the SQL Reporting instance. 9. Configure Distribution Agent Security i. You can opt to configure the Distribution Agent under a Windows Local or Domain Account, or the SQL Server Agent service account. Running under the SQL Server Agent service account is not considered an MS SQL server 'best practice'. Using a Domain Account can simply administration 3 / 7

4 ii. Define the account that is used to connect to the Distributor. 10. Configure the Agent Schedule. You can opt to impersonate the process account. Using a SQL Server Login. (This logon will need to be created within SQL ahead of time). 11. Configure when to Initialize the Subscription. 12. Create the Subscription. 13. Finish the New Subscription Wizard. Configure SQL Replication Using a Pull Replication Model I. Configure the MS SQL Reporting Instance (OLAP) server with the MS SQL Distributor Role 1. Open MS SQL Server Management Studio and connect to the SQL Reporting Instance (OLAP) server. 2. Right-click the Replication tab and select Configure Distribution to launch the Configure Distribution Wizard. 3. Select "'<Reporting Instance>' will act as its own Distributor"; SQL Server will create a distribution database and log." 4. Specify the snapshot folder. 5. Specify a name for the Distribution DB and the paths the Database and Log files. 6. Enable the Master Server as the Publisher. 7. Accept the Configure Distribution default and continue by hitting NEXT. 8. Finish the Configure Distribution Wizard. II. Configure the Master server with the MS SQL Publisher Role 1. Open MS SQL Server Management Studio and connect to the Master Server. 2. Open the Replication folder, then 'right-click' the Local Publications folder to open the options menu. 3. Select New Publication to launch the New Publication Wizard. 4. Select the Database(s) that you want to replicate to the SQL Reporting instance (OLAP) server. All published tables in transactional replication must contain a declared primary key. Existing tables can be prepared for publishing by adding a primary key using the Transact-SQL statement ALTER TABLE (Transact-SQL). Refer to the MS SQL Server Books Online for additional information on the requirements to publish a table for replication as well as the methods to create a Primary Key using either the MS SQL Server Management 4 / 7

5 Studio GUI or the ALTER TABLE (Transact-SQL) command. 5. Select the Publication Type you would like to use for the publication. 6. Select the Tables within the Database(s) which you would like to replicate to the SQL Reporting instance (OLAP) server. 7. Configure filtering of table rows (optional). 8. Configure the snapshot agent. Here you can configure the initial snapshot to execute immediately, or you can schedule it to run during an off peak time. Data will not be available on the Reporting instance for queries until the snapshot has been executed and the Subscription Database has been synchronized with the Publication Database. 9. Configure Snapshot Agent Security. 10. Accept the Create Publication default and continue by hitting NEXT. 11. Define a Publication Name and select FINISH. III. Configure the MS SQL Reporting Instance (OLAP) server with the MS SQL Subscriber Role 1. Open MS SQL Server Management Studio and connect to the SQL Reporting Instance (OLAP) server. 2. Open the Replication folder, then 'right-click' the Local Subscriptions folder to open the options menu. 3. Select New Subscriptions to launch the New Subscription Wizard. 4. 'Click' the Publisher Dropdown and select "<Find SQL Server Publisher>". 5. Populate the Server Name field with the name of the Master Server. (This was previously configured as the Publisher in the previous set of steps) 6. Select the Publication(s). 7. Define the location of the Distribution Agent. This determines whether you are configuring the SQL replication to use 'Push' or 'Pull' Replication. Pull Subscriptions reduce overhead on the Distributor, which is your production server. 8. Define the Subscriber and the Subscription Database. You can opt to create a new Database. This will be the database that users query when running reports on the SQL Reporting instance. 9. Configure Distribution Agent Security i. You can opt to configure the Distribution Agent under a Windows Local or Domain Account, or the SQL Server Agent service account. 5 / 7

6 Running under the SQL Server Agent service account is not considered an MS SQL server 'best practice'. Using a Domain Account can simply administration ii. Define the account that is used to connect to the Distributor. 10. Configure the Agent Schedule. You can opt to impersonate the process account. Using a SQL Server Login. (This logon will need to be created within SQL ahead of time). 11. Configure when to Initialize the Subscription. 12. Create the Subscription. 13. Finish the New Subscription Wizard. Configure a CA XOsoft/CA ARCserve RHA scenario 1. Open a web browser and connect to the CA XOsoft/CA ARCserve RHA Control Service Manager Name/IP>:8088' 2. Authenticate to the Control Service and launch the CA XOsoft/ARCserve RHA Manager 3. Create a New Scenario 4. In the Select Server and Product window, select "MS SQL Server" in the Select Server Type box. 5. Select "High Availability (HA)" in the Select Product Type section. 6. The Tasks on Replica section is optional. 7. Define the Master and Replica servers Master: Production Server Replica: HA/DR Replica server. (This is not the SQL Reporting instance) 8. Verifying that the version of the Engine is the same on both servers. You can choose to install which launches the remote Installation Wizard from this window to install or update existing versions. 9. In the Select Databases for Replication window, confirm that the "Distribution DB" is included and defined for replication. 10. Scenario, Master and Replica Properties are optional. Modify settings as needed. 11. In the Switchover Properties, enable Switch Computer Name in the Network Traffic Redirection Properties. Leave the With Reboot option set to ON 6 / 7

7 Powered by TCPDF ( 12. Configure the Switchover Initiation and Reverse Replication Initiation properties as desired. It is not recommended to set both Switchover Automatically and Start Reverse Replication automatically at the same time when replicating across a WAN. 13. Run the scenario and synchronize when prompted. MS SQL Server Scenarios MUST uses the Block Synchronization method. Leave the Ignore Same Size/Time Files option to OFF. TEC533446,"arcserve RHA "ARCKB / 7