Scribd
Upload
84 views4 pages

Control-M Server V9 MSSQL AlwaysOn

Control-M Server version 9.FP2 will provide support for MS SQL Server Always On availability groups, including both single-subnet and multi-subnet clusters. A new utility called "always_on_config" allows customers to configure Control-M to work with Always On availability groups, maintain the required ODBC data source, and change the database server name to the availability group listener. When enabling or disabling Always On support, the "always_on_config" utility must be run to appropriately configure Control-M and update required files and registry settings.

Uploaded by

Carolina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
84 views4 pages

Control-M Server V9 MSSQL AlwaysOn

Control-M Server version 9.FP2 will provide support for MS SQL Server Always On availability groups, including both single-subnet and multi-subnet clusters. A new utility called "always_on_config" allows customers to configure Control-M to work with Always On availability groups, maintain the required ODBC data source, and change the database server name to the availability group listener. When enabling or disabling Always On support, the "always_on_config" utility must be run to appropriately configure Control-M and update required files and registry settings.

Uploaded by

Carolina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

MS SQL Server Always On Support by Control-M Server

August, 2016
Starting from Control-M Server V9.FP2 Always On will be supported on both
single-subnet as well as multi-subnet SQL Server clusters.

CTM V9.FP2 contents related to Always On support


 A new utility “ALWAYS_ON_CONFIG” will help the customer prepare for AlwaysOn.
 Control-M mirroring will not be supported when using AlwaysOn. This restrictions will
be documented, but not enforced in code.
 OneInstall is out of the scope of AlwaysOn.
 RebuildDB will not be supported in AlwaysOn.
 Restore database will not be supported in AlwaysOn.

CTM V9.FP2 internals related to Always On support

 A new ODBC DSN called “CTM_ALWAYS_ON” will be configured and maintained by


the “ALWAYS_ON_CONFIG” utility.

 The utility “always_on_config” allows the customer to configure Control-M to work


with AlwaysON on or off, build the required ODBC DSN, and to change DB Server
name to the newly created AGL.

Note: Very Slow network may fail a connection to the Availability group listener.
Control-M Server assumes that a connection to the Availability Group Listener
Takes up to 15 seconds. On a regular network connections usually take about 1 to 2
seconds.

1
Installation flow for an MS AON customer

 A user is installing V9 GA on the Always On Cluster . The database is, by default, is


created on the current Primary Node of the cluster (the database, for now, is a regular
standalone database).
 The customer now installs V9.FP2 or a higher patch.
 The customer does any migration that is required.
 Shuts down CTM
 The customer asks the site DBA to load the standalone database into Availability
Group.
 Customer is asking the site DBA to grant “VIEW SERVER STATE” to the new login
created,
 Customer activates always_on_config and executes the following commands:
 always_on_config set mode=Y
(This will update DBU_params.dat, registry, and create ODBC)
 always_on_config set pass=<ctmpaswd> server=<NEWAGL>
(To change the name of the SQL Server name, for example, the make the
Availability Group Listener, as the new Server name)

HA note: When installing the secondary Control-M Server, the above two set
commands should also be executed after the installation.

Customer now Starts CTM and is working in full AON mode.

Turning off ALWAYS_ON


 User is requesting DBA to take his database off the Availability Group
 Shuts down CTM
 Customer activates always_on_config and executes the following commands:
 always_on_config set mode=N
 always_on_config set pass=<ctmpaswd> server=<Physical server>

2
The always_on_config utility
The utility is working in an interactive or command line mode. It updates the mode as well as DB Server
name in all the required files.

Command line mode syntax


Always_on_config help
Always_on_config status pass=<DB password>
Always_on_config set mode=y/n
Always_on_config set pass=<DB Password> { servername=<servername>}

Always_on_config status

Warns if no “VIEW SRVER STATE” privilege.


Product is {EM / Control-M} Server
AlwaysOn status is Y/N
DB Server name is <db server name>
The database <is>/<is not> is part of the Availability Group <AG name>
{The db_server_name is a virtual name, currently connected to <current active db server>}
(Warning printed if no “VIEW SERVER STATE” privilege assigned to the db login.

Mode field handling


 Changes the value of ALWAYS_ON in the file “DBU_params.dat” to Y/N.
 Changes the value in registry SYSPRM value of ALWAYS_ON to Y/N.

DB Server name handling - List of changes


1. Updates the value of SERVICE_NAME in the file “DBU_params.dat”
2. Updates the registry SYSPRM value of SQLSRVRNAME.
3. Updates the server name in the ODBC system DSN called CTM_ALWAYS_ON

3
DBA section – How Site DBA loads the installed database into the AG

1. Grant VIEW SERVER STATE to all logins involved


2. Change all databases involved to Recovery FULL
3. Apply Full backup to all databases
4. Create SQL Server logins on the Read-Only Replicas
a. These logins should match the login built during the installation.
5. These logins should have the same SID as the one created on the Primary replica.
This requirement is not specific to CTM or EM Server, but is known as a general good
practice for an Always On DBA.
a. The login (example ‘ctmuser’) should has the same SID on all replicas
b. The site DBA may want to use the 'sp_help_revlogin' stored procedure
That can be downloaded from the MSDN support site, in order to properly create
the right logins.
c. After login creation, the site DBA will have to run the command
sp_changedbowner @loginame = 'ctmuser', (See step #9).
d. After the above activities all logins are physically identical on all the replicas.
6. Create a new AG
a. Either one AG for both products
b. Or one AG for every product
7. Go to the Primary and add the databases to the AG.
8. Decide whether AGL will be used
a. If yes, verify AGL responding
9. Failover the Cluster to every Secondary Node, and attach the Active Replica to its
owning login. (See 5C above)
10. Failback to the Original Primary
11. Test connectivity

You might also like