HP ProLiant DL185 HP Insight Server Migration Software for ProLiant User Guide - Page 27

Deploying SMP Agents, Deploying SMP Source Agents, SMP Agents

Get HP ProLiant DL185 - G5 Server PDF manuals and user guides View all HP ProLiant DL185 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

3 Deploying SMP Agents Deploying SMP Source Agents Before starting a migration, SMP Agent must be running on the source and destination servers. Therefore, verify the proper agent is applied to the source and destination server. To launch SMP Agent, you must have administrative rights to connect to the source server. Before performing a migration, remove CDs, floppy disks, USB keys, or other detachable media from the source server. You can deploy SMP Agent using one of the following methods: • Using the Central Management Server (CMS) with HP SIM installed • Using the application station with stand-alone SMP installed • Using executables located on the SMP application station • Using Install SMP Source Agent on autorun of the HP SMP 3.70 CD (Windows migrations only) NOTE: Source agents cannot be deployed to Windows 2008 servers using the Deploy Agent tab on the application station wizard. You must either manually copy the hpsmpagent.exe from the \Agents\SMP folder to the source server or connect the SMP installation CD to the source server, and then install the SMP Source Agent by clicking Install SMP Source Agent in the auto run window of the SMP application. SMP Agents The following SMP Agents are available: • Windows VM Host Agent-This agent must be launched on a target virtual machine host running on a Windows operating system that is used for P2V or V2V migrations. This agent must be applied when a destination virtual machine is created on an agent-based virtual machine host running a Windows operating system. This agent runs as a service on the virtual machine host and does not need to be reapplied for multiple migrations. However, if a migration is started to a virtual machine on this virtual machine host, then other simultaneous migrations to any other virtual machine on the same virtual machine host are queued. To determine whether your virtual machine host is agent-based, see the HP Insight Server Migration software for ProLiant Support Matrix or see the "Agent-based hypervisors" section. • Linux VM Host Agent-This agent must be launched on a target virtual machine host running on a Linux operating system that is used for P2V or V2V migrations. This agent must be applied when a destination virtual machine is created on an agent-based virtual machine host running a Linux operating system. This agent runs as a service on the virtual machine host and does not need to be reapplied for multiple migrations. However, if a migration is started to a virtual machine on this virtual machine host, then other simultaneous migrations to any other virtual machine on the same virtual machine host are queued. To determine whether your virtual machine host is agent-based, see the HP Insight Server Migration software for ProLiant Support Matrix or see the "Operating system" section. • SMP Windows Source Agent-This agent must be launched on the Windows source server or virtual machine before performing a migration. This agent does not run as a service on the source server and must be applied for each migration. • SMP Linux Source Agent-This agent must be launched on the Linux source server or virtual machine before performing a migration. This agent does not run as a service on the source server and must be applied for each migration. Deploying SMP Source Agents 27

  • 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
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
3 Deploying SMP Agents
Deploying SMP Source Agents
Before starting a migration, SMP Agent must be running on the source and destination servers. Therefore,
verify the proper agent is applied to the source and destination server.
To launch SMP Agent, you must have administrative rights to connect to the source server.
Before performing a migration, remove CDs, floppy disks, USB keys, or other detachable media from the
source server.
You can deploy SMP Agent using one of the following methods:
•
Using the Central Management Server (CMS) with HP SIM installed
•
Using the application station with stand-alone SMP installed
•
Using executables located on the SMP application station
•
Using
Install SMP Source Agent
on autorun of the HP SMP 3.70 CD (Windows migrations only)
NOTE:
Source agents cannot be deployed to Windows 2008 servers using the
Deploy Agent
tab on the
application station wizard. You must either manually copy the
hpsmpagent.exe
from the
<installation
dir>
\Agents\SMP folder to the source server or connect the SMP installation CD to the source server, and
then install the SMP Source Agent by clicking
Install SMP Source Agent
in the auto run window of the
SMP application.
SMP Agents
The following SMP Agents are available:
•
Windows VM Host Agent
—This agent must be launched on a target virtual machine host running on a
Windows operating system that is used for P2V or V2V migrations. This agent must be applied when
a destination virtual machine is created on an agent-based virtual machine host running a Windows
operating system. This agent runs as a service on the virtual machine host and does not need to be
reapplied for multiple migrations. However, if a migration is started to a virtual machine on this virtual
machine host, then other simultaneous migrations to any other virtual machine on the same virtual
machine host are queued. To determine whether your virtual machine host is agent-based, see the
HP
Insight Server Migration software for ProLiant Support Matrix
or see the
“Agent-based hypervisors”
section.
•
Linux VM Host Agent
—This agent must be launched on a target virtual machine host running on a Linux
operating system that is used for P2V or V2V migrations. This agent must be applied when a destination
virtual machine is created on an agent-based virtual machine host running a Linux operating system.
This agent runs as a service on the virtual machine host and does not need to be reapplied for multiple
migrations. However, if a migration is started to a virtual machine on this virtual machine host, then
other simultaneous migrations to any other virtual machine on the same virtual machine host are queued.
To determine whether your virtual machine host is agent-based, see the
HP Insight Server Migration
software for ProLiant Support Matrix
or see the
“Operating system”
section.
•
SMP Windows Source Agent
—This agent must be launched on the Windows source server or virtual
machine before performing a migration. This agent does not run as a service on the source server and
must be applied for each migration.
•
SMP Linux Source Agent
—This agent must be launched on the Linux source server or virtual machine
before performing a migration. This agent does not run as a service on the source server and must be
applied for each migration.
Deploying SMP Source Agents
27