HP BL680c HP Virtual Connect Enterprise Manager Data Migration Guide - Page 9

HP Virtual Connect Enterprise Manager data migration

Page 9 highlights

1 HP Virtual Connect Enterprise Manager data migration Introduction HP Virtual Connect Enterprise Manager (VCEM) simplifies the management of multiple HP BladeSystem enclosures that use Virtual Connect to control LAN and Storage Area Network (SAN) connectivity. This simplification can help organizations increase productivity, respond more quickly to business demands, and significantly reduce operating costs. Building on existing HP Virtual Connect technology, VCEM provides a single console to manage network infrastructure connections, a central resource pool for LAN and SAN address administration, and grouping capabilities that enable rapid server deployment and movement. Use VCEM in environments with multiple HP BladeSystem enclosures (typically four or more) to complete critical data center tasks quickly, reliably, and with minimal disruption to the production LAN and SAN. These tasks include: • Installing new blade servers • Performing fast and cost-effective server recovery • Scheduling planned system maintenance • Deploying large virtual connect installations • Rapidly migrating servers (such as moving servers from test to production environments or between data center locations) on the same network infrastructure VCEM delivers new levels of management and control for HP BladeSystem environments that use HP Virtual Connect for maintaining server, LAN, and SAN infrastructures. Subsequent versions of VCEM will provide expanded capabilities to further automate infrastructure management and server availability to defined service levels and operating criteria. VCEM users who have deployed VCEM 1.0 have done so using an integrated HP Systems Insight Manager (HP SIM) installation. If you plan to use VCEM 1.10 on an alternate platform running another instance of HP SIM, you will lose the mapping between the VC modules and the management platform. To avoid this situation and ensure VC management platform synchronization, HP created the Virtual Connect Enterprise Manager Data Migration Tool. For more information on VCEM, see http://www.hp.com/go/vcem. Prerequisites for data migration To perform a data migration, you must meet the following prerequisites: • You must have HP SIM administrator rights to use the VCEM Data Migration tool. • The destination platform cannot have been used to manage any VCs before the start of the migration process. • You must have a method of moving the snapshot file from the VCEM 1.0 system to the VCEM 1.10 system. • You must complete all Virtual Connect jobs before performing a migration. • No VC Domains are in the Authorized state. • HP SIM must be running on both systems. • HP SIM on the VCEM 1.10 platform must have completed an initial discovery following installation and discovered the Onboard Administrator for the enclosure containing the VC modules. • All VC Domains that are being managed on the VCEM 1.0 system must be discovered by HP SIM on the VCEM 1.10 system. • If your HP SIM installation on the VCEM 1.10 system connects to a database on a remote system, a temporary shared directory must be created on the database server to enable the migration tool to place the set of files containing the VCEM 1.0 database tables on a directory readable by the remote SQL server. The shared directory must be hosted by the database server and writable by the account that is running the migration tool. After the migration, you can delete this directory. Introduction 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12

1 HP Virtual Connect Enterprise Manager data migration
Introduction
HP Virtual Connect Enterprise Manager (VCEM) simplifies the management of multiple HP BladeSystem
enclosures that use Virtual Connect to control LAN and Storage Area Network (SAN) connectivity. This
simplification can help organizations increase productivity, respond more quickly to business demands, and
significantly reduce operating costs.
Building on existing HP Virtual Connect technology, VCEM provides a single console to manage network
infrastructure connections, a central resource pool for LAN and SAN address administration, and grouping
capabilities that enable rapid server deployment and movement.
Use VCEM in environments with multiple HP BladeSystem enclosures (typically four or more) to complete
critical data center tasks quickly, reliably, and with minimal disruption to the production LAN and SAN.
These tasks include:
Installing new blade servers
Performing fast and cost-effective server recovery
Scheduling planned system maintenance
Deploying large virtual connect installations
Rapidly migrating servers (such as moving servers from test to production environments or between
data center locations) on the same network infrastructure
VCEM delivers new levels of management and control for HP BladeSystem environments that use HP Virtual
Connect for maintaining server, LAN, and SAN infrastructures. Subsequent versions of VCEM will provide
expanded capabilities to further automate infrastructure management and server availability to defined
service levels and operating criteria.
VCEM users who have deployed VCEM 1.0 have done so using an integrated HP Systems Insight Manager
(HP SIM) installation. If you plan to use VCEM 1.10 on an alternate platform running another instance of
HP SIM, you will lose the mapping between the VC modules and the management platform. To avoid this
situation and ensure VC management platform synchronization, HP created the Virtual Connect Enterprise
Manager Data Migration Tool.
For more information on VCEM, see
ht
tp://w
w
w
.hp
.com/go/vcem
.
Prerequisites for data migration
To perform a data migration, you must meet the following prerequisites:
You must have HP SIM administrator rights to use the VCEM Data Migration tool.
The destination platform cannot have been used to manage any VCs before the start of the migration
process.
You must have a method of moving the snapshot file from the VCEM 1.0 system to the VCEM 1.10
system.
You must complete all Virtual Connect jobs before performing a migration.
No VC Domains are in the Authorized state.
HP SIM must be running on both systems.
HP SIM on the VCEM 1.10 platform must have completed an initial discovery following installation and
discovered the Onboard Administrator for the enclosure containing the VC modules.
All VC Domains that are being managed on the VCEM 1.0 system must be discovered by HP SIM on
the VCEM 1.10 system.
If your HP SIM installation on the VCEM 1.10 system connects to a database on a remote system, a
temporary shared directory must be created on the database server to enable the migration tool to
place the set of files containing the VCEM 1.0 database tables on a directory readable by the remote
SQL server. The shared directory must be hosted by the database server and writable by the account
that is running the migration tool. After the migration, you can delete this directory.
Introduction
9