Principles
Environment Manager Personalization Server replication requires one database to be the master, and the other databases to be subscribers, in replication terms. The following Microsoft SQL Servers can be used:
· Microsoft SQL Server 2008 R2
· Microsoft SQL Server 2008
· Microsoft SQL Server 2005
· Microsoft SQL Server 2000
If the Microsoft SQL Servers are a mix of versions, the SQL Server hosting most current version must be set up as the master.
Microsoft SQL Express and MSDE databases are not supported for database replication. |
It is important to realize that when a subscriber system is first added, all the existing data is deleted and replaced with data from the master. After replication is set up, data can be created on the subscriber and merged with the master regularly. | ||||
Prerequisites
The setup files required can be found, for a default installation on Drive C:, in the folder C:\Program Files\AppSense\Environment Manager\Personalization Server\Replication on any personalization server. This folder should be copied to the master Microsoft SQL Server database machine, if it is not a personalization server itself.
Initial Steps
Ensure that remote access is enabled for your Microsoft SQL Server 2008 and Microsoft SQL Server 2005 instances. To do this use:
· Microsoft SQL Server 2008 SQL Server Configuration Manager.
· Microsoft SQL Server 2005 Surface Area Configuration Tool.
For further information refer to the Microsoft SQL Server documentation. |
Ensure that Personalization Server databases have been created on all servers, by installing Personalization Servers connecting to the databases.
Ensure that any firewall software allows remote access to SQL Server.
For further information on Microsoft Server 2008 systems refer to the Microsoft Help. |
The master database requires that the replication folder is shared, as the scripts ConfigAC.sql, ConfigDC.sql, DataDC.sql and DataAC.sql are accessed through this share. Ensure the share is set up before starting the setup process. The setup file will ask for the UNC path of the share. For example \\Server1\Replication.
If this is a SQL Cluster, the share specified here must be a clustered file share resource so it is available to all cluster nodes.
The SQL Agent service on the master must be running under an account that has sysadmin database access to all servers via Windows Authentication, this is not the default. This can be changed with the Services applet in Administrative Tools.
To run the setup procedure you must be logged in to an account that has sysadmin database access to all servers via Windows Authentication.
Performing the Setup
The two command files used are:
· SetMasterUp.cmd - Run to set up the master and the first subscriber.
· AddSubscriber.cmd - Run to add an additional subscriber. Do not run until SetMasterUp.cmd has been run.
These files can be found in either the SQL2008, SQL2005 or SQL2000 subfolders of the Replication folder and are always run on the master database machine. However, in the case of an SQL Server Cluster, the scripts may be run on any cluster member. Select the correct subfolder for your master and run the files either by opening a command prompt and entering the name of the file when in the current directory, or simply double-clicking on the files from Windows Explorer.
SetMasterUp.cmd supports cluster installation and contains guidance on how to install in this scenario. |
SetMasterUp prompts for the following information:
· Server instance name and personalization database name of the master database
· Path for the snapshot folder - This is a scratch folder used by replication. The command file should offer a standard default which is OK to accept.
· UNC Path for the drop/add constraint scripts. This is the share from step 4 in the Initial Steps.
The command file then sets up the master and for convenience automatically runs AddSubscriber.cmd which prompts for the following information:
· Server name, Server database instance name and personalization database name of the slave to be added
To add further subscribers, use AddSubscriber.cmd on the master. When run in this way, it asks for the instance name and database name for the master database as well as the subscriber details.
Post Setup Steps
After setup Synchronize Site Databases on the Tools ribbon page > Replication group in the Environment Manager console, will not work unless the normal logon used by the Personalization Server is given appropriate privileges in the database. Synchronize Site Databases causes replication of user data to occur immediately, normally it is replicated at midnight. The setup procedure intentionally does not set this up because of the possible security implications.
To Synchronize Site Databases to work you have to identify the login used by the Personalization Server, which will have been set up by the Server Configuration Utility at time of installation, and change it using Management Studio/Enterprise Manager as follows:
SQL 2008: The login needs to be added to the SQLAgentOperatorRole in the msdb database.
SQL 2005: The login needs to be added to the SQLAgentOperatorRole in the msdb database.
SQL 2000: The login needs to be added to the sysadmin server role.
No comments:
Post a Comment