Transcript Federated MDBs with Multiple SQL Instances

Federated MDBs with
Multiple SQL Instances
Last Revision Date: September 6, 2006
Glossary
- The following terms and abbreviations are used in
this presentation:
- “HA” = Highly Available
- “UAPM” – Unicenter Asset Management Portfolio
- “USD” = Unicenter Service Desk
- “DSM” – Unicenter Desktop Server Management
- “eIAM” = CA eTrust Embedded Identity and
Access Management
- “MSCS” = Microsoft Cluster Server
- “NSM” = Unicenter Network System
Management
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Overview
Objectives
- The objective of this document is not to discuss MDB
Federation or what products should share MDB. For a
detailed discussion of MDB federation and deployment
choices consult the MDB Federation presentation instead
- The main objective of this presentation is to review the
implications of installing multiple SQL MDBs on a single
server having multiple SQL instances. Additional information
is provided regarding the install of multiple SQL MDBs in a
Microsoft cluster environment
- These discussions assume that you have already reviewed
the MDB Federation presentation and wish to pursue
federation on the same server or same cluster
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Why use multiple SQL instances?
- Reduce cost of ownership
- If correctly planned, the normal mode of
operation in a Microsoft Cluster environment can
include active SQL instances on different nodes
of the cluster. This provides federation without
overloading single cluster node.
- In the event of a failover both SQL instances can
potentially be active on the same node.
- This would not be classified as “normal” mode of
operation
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Default SQL Instance
- Some products do not support named SQL
instances. DSM is one of these, but it is targeted
to support named instances soon.
- Although DSM will install correctly using named
SQL instances, there are some issues with
named SQL instances
- Therefore, if DSM is being installed in an
environment using multiple SQL instances, one of
the SQL instances should be the default instance.
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Multiple MDBs – one Product
- Installing multiple MDBs for the same product on
the same server can cause the product to
malfunction and, in some cases, the install process
will prevent it from being installed.
- NSM install process prevents multiple MDBs from
being created on different SQL instances running
on the same server.
- Several NSM components caches repository
(MDB) details. If MDB location is changed
password and MDB details must be updated for
all of these components
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
NSM and Multiple MDBs
- NSM MDB has been locked down with named SQL
instance (SQLINSTA)
- Install processes attempts to create another NSM
MDB on a default instance
- Install process for subsequent NSM MDBs will
prevent override of the database server or SQL
instance details
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
NSM and Multiple MDBs
This shows multiple
NSM MDBs cannot be
created on the same
server
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
SQL Instances
This shows default
and named SQL
instances – each
with an MDB
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Multiple SQL Instances
This shows cluster setup with default and named
SQL instances each having an MDB spread across
different products
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Install Summary for
Cluster and Non-cluster
Configurations
Single Server - Multiple MDB Instances
SQL Named Instance
SQLINSTA
MDB
USD MDB
DSM MDB
NSM MDB
NSM Managers
NSM
SQL Default Instance
DSM
MDB
Default Instance
MDB
USD
eIAM – Ingres
Instance
Database
Server
Enterprise Mgt
WV Provider
Named SQL
Instance
This shows non-cluster
setup with multiple
SQL MDBs
NSM Worldview
Multiple MDB instances
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Single Server: USD – Default Instance
- Here USD MDB is installed on a default SQL
instance while NSM MDB exists on the named SQL
instance
- In addition, eIAM is selected (this will install
Ingres ET instance, as well)
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Single Server: NSM – Named Instance
- Here NSM MDB is created on named SQL instance
while USD MDB already exists in the default SQL
instance
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Single Server: SQL Instances
This shows two MDBs on
different SQL instances
installed on the same server
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Single Server: SQL Instances Services
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Cluster Setup
- This shows two SQL instances - default and
named. Each instance will have MDB based on the
MDB deployment choices discussed in the
Federation presentation
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Cluster Setup: DSM MDB Install
- This shows DSM MDB installed on the default SQL
Instance which it shares with USD and UAPM. NSM
MDB will be installed on a named instance
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Cluster Server: SQL Setup
- This shows two SQL instances, each with an MDB
in a Microsoft Cluster setup
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Gotchas
Considerations
- There should not be any special considerations for
installing multiple MDBs on the same server using
different SQL instances or for installing in a
Microsoft Cluster environment using multiple SQL
instances.
- The considerations listed in this section are not
specific to multiple MDBs on the same cluster or
server
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
USD and DSM Install order
- If USD and DSM will share an MDB, install DSM
first. Otherwise, you may experience 1603 error
(The setup here was USD 11.2 and DSM 11.1a
without C1 fix)
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
DSM Install MDB
- DSM may identify existence of previous MDB and
generate a dialog box which may be irrelevant for
SQL MDB
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
System Path
- Unicenter NSM install validates the system path
length, computing the length of system path
entry based on NSM products selected. If the
computed length exceeds 1024 bytes the install
will not continue
- If multiple products are installed, it is likely the
system path length will be exceeded
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
System Path Prior to Install
This shows system path prior to installing any
NSM components. The path entries listed
above include pre-installed DSM Agent +
Software delivery plug-in, eTrust Antivirus
option, and USD eIAM option
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Path Length Exceeded
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Circumvention
- To circumvent this potential problem, change the location of
CA Common Services from “\Program
Files\CA\SharedComponents” to “\CA\SharedComponents”
- Alternatively, shorten path length by changing existing
entries to short name (8dot3 format). For example:
- C:\Program Files\CA\eTrust Directory\dxserver\bin to
- C:\Progra~1\CA\eTrust~2\dxserver\bin
- User dir /X to option convert to 8dot3 format
- Remove duplicate entries
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Directory Name Shortened
Changed CA Common Services location from \Program
Files\CA\SharedComponents to \CA\SharedComponents
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.