Computer Associates SQLSTQ99000600 Diagnostics Guide - Page 33

Apply the Cure and Document the Solution, Troubleshooting Installation and Migration

Get Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 PDF manuals and user guides
UPC - 757943257441
View all Computer Associates SQLSTQ99000600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 33 highlights

Apply the Cure and Document the Solution The new UDSM components are installed independently of previous versions of those components. They can then run in parallel on either separate hardware or co-hosted on the same hardware, giving you the option of keeping your current hardware/software investments. Each product included in UDSM can be migrated individually and with a phased approach to minimize disruption to the operating environment. Considerations include: „ installation of management infrastructure may include design of new physical implementation or topology - which may necessitate new hardware and software. „ early identification of which data to migrate - and to where. You should always start running data migration tools on the managers first before rolling out the agents. because those agents that are already managed by r11 will not be offered the option of data migration „ careful consideration of agent infrastructure installation. To maintain consistency, once the agent data has been migrated to the new UDSM domain, no further management should be done using the old pre-r11 infrastructure. Phase 2, data migration, is independent of infrastructure migration. UDSM provides several tools, such as manually launched post install tasks, that can move the existing data into the MDB. These tools provide support for different database and operating system configurations, including: „ Microsoft SQL Server and Ingres data bases „ local and remote databases „ Windows to Windows „ Windows to Linux „ Linux to Windows „ Linux to Linux In realigning data from the old to new infrastructure you may need to merge or split the existing data. For example, if you are moving from multiple Unicenter Software Delivery Local Servers to a single Domain Server, you will need to merge existing data sources. On the other hand, you may need to consider splitting an existing Unicenter Asset Management r.0 domain into multiple UDSM domains in order to accommodate future growth and improve performance. In order to manage either of these options, the UDSM installation includes the concept of "migration scope" - selectively migrating agents from pre-r11 databases based on user groups. If selected, only agents that are members of that user group will be considered for migration. If the migration scope is left empty, ALL agents managed by that legacy manager will be considered for migration. Keep in mind that: Chapter 5: Troubleshooting Installation and Migration 5-3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
Apply the Cure and Document the Solution
The new UDSM components are installed independently of previous versions of
those components.
They can then run in parallel on either separate hardware
or co-hosted on the same hardware, giving you the option of keeping your
current hardware/software investments.
Each product included in UDSM can
be migrated individually and with a phased approach to minimize disruption to
the operating environment.
Considerations include:
installation of management infrastructure may include design of new
physical implementation or topology - which may necessitate new
hardware and software.
early identification of
which data to migrate - and to where. You should
always start running data migration tools on the managers first before
rolling out the agents.
because those agents that are already managed
by r11 will not be offered the option of data migration
careful consideration of agent infrastructure installation.
To maintain
consistency, once the agent data has been migrated to the new UDSM
domain, no further management should be done using the old pre-r11
infrastructure.
Phase 2, data migration, is independent of infrastructure migration.
UDSM
provides several tools, such as manually launched post install tasks, that can
move the existing data into the MDB.
These tools provide support for different
database and operating system configurations, including:
Microsoft SQL Server and Ingres data bases
local and remote databases
Windows to Windows
Windows to Linux
Linux to Windows
Linux to Linux
In realigning data from the old to new infrastructure you may need to merge
or split the existing data. For example, if you are moving from multiple
Unicenter Software Delivery Local Servers to a single Domain Server, you will
need to merge existing data sources.
On the other hand, you may need to
consider splitting an existing Unicenter Asset Management r.0 domain into
multiple UDSM domains in order to accommodate future growth and improve
performance.
In order to manage either of these options, the UDSM
installation includes the concept of "migration scope" - selectively migrating
agents from pre-r11 databases based on user groups.
If selected, only agents
that are members of that user group will be considered for migration.
If the
migration scope is left empty, ALL agents managed by that legacy manager
will be considered for migration.
Keep in mind that:
Chapter 5: Troubleshooting Installation and Migration
5–3