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

For Windows 2000, Migration fails if certain Update Rollup versions exist

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 130 highlights

For Windows 2000 1. From the Control Panel, double-click System. 2. In the System Properties window, click the Advanced tab. 3. Click Performance Options. 4. In the Virtual Memory section in the Performance Options window, click Change. 5. In the Drive column, select the drive that contains the paging file to be changed. 6. In the Paging file size for selected drive section, enter a new paging file size in the Initial size (MB) box. 7. Click Set. 8. Click OK until all windows are closed. Migration fails if certain Update Rollup versions exist A migration fails if Update Rollup 1 version 1 or 2 is installed on top of Windows 2000 SP4 on the source machine. To continue with the migration, the current version of the scsiport.sys file on the source machine must be rolled back to the version present in Windows 2000 SP4. To roll back the current version: 1. Rename the Scsiport.sys file to Scsiport.sys.old. This file is located in the %windir%\System32\Drivers folder. 2. Copy the Scsiport.sys file from Windows 2000 SP4 to the %windir%\System32\Drivers folder. For information about how to extract service pack files, see the Readme for Windows 2000 Service Pack 4 (ReadMeSP.htm) document at http://www.microsoft.com/windows2000/downloads/ servicepacks/SP4/ReadMeSP.htm. Migration fails to terminate if source server is shut down In some network, firewall, or router configuration scenarios, SMP might fail to recognize that the source server is no longer available during a migration and remain in migration mode. In this scenario, perform the following procedure: 1. Close SMP. 2. Open the Windows Services Manager, and then restart the SMP application service and the HP SMP Web Service. NTFS partitions cannot be resized from a Windows 2008 application station SMP does not resize NTFS partitions when migrating to an agent-based virtual machine host from a Windows 2008 application station. To resolve this issue, initiate the migration from a Windows 2003 application station. NTFS resize error message The following message might appear during the migration of certain NTFS volumes: The file system on source disk x, partition y could not be resized during migration. The NTFS volume information could not be read. Retry the migration without resizing this volume. Defragmenting the NTFS volume or performing a "chkdsk /f" prior to the migration may resolve this condition. The preceding message appears when SMP cannot process the NTFS meta information for this volume, and the volume cannot be resized during migration. To resolve this issue, do not resize the volume. Instead, perform a disk defragmentation or run chkdsk /f to resolve the issue. However, performing a successful defragmentation and disk check, does not guarantee the ability to resize. In this case, the volume can only be migrated without resizing. SMP migration fails during the disk cloning phase The following error message appears on the application station log (hpsmpsvc.log): com.hp.mx.smp.vmdisk.api.APIException: Not enough space for partition! This error might if the destination server disk has a Windows Logical Partition configured on it. 130 Troubleshooting

  • 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
For Windows 2000
1.
From the Control Panel, double-click
System
.
2.
In the
System Properties
window, click the
Advanced
tab.
3.
Click
Performance Options
.
4.
In the
Virtual Memory
section in the
Performance Options
window, click
Change
.
5.
In the
Drive
column, select the drive that contains the paging file to be changed.
6.
In the
Paging file size for selected drive
section, enter a new paging file size in the
Initial size (MB)
box.
7.
Click
Set
.
8.
Click
OK
until all windows are closed.
Migration fails if certain Update Rollup versions exist
A migration fails if Update Rollup 1 version 1 or 2 is installed on top of Windows 2000 SP4 on the source
machine. To continue with the migration, the current version of the
scsiport.sys
file on the source machine
must be rolled back to the version present in Windows 2000 SP4.
To roll back the current version:
1.
Rename the
Scsiport.sys
file to
Scsiport.sys.old
. This file is located in the
%windir%\System32\Drivers folder.
2.
Copy the
Scsiport.sys
file from Windows 2000 SP4 to the %windir%\System32\Drivers folder.
For information about how to extract service pack files, see the
Readme for Windows 2000 Service
Pack 4 (ReadMeSP.htm)
document at
ht
tp://w
w
w
.mic
r
o
s
o
f
t
.com/w
indo
w
s2000/do
w
nloads/
ser
v
icepac
ks/SP4/R
eadM
e
SP
.htm
.
Migration fails to terminate if source server is shut down
In some network, firewall, or router configuration scenarios, SMP might fail to recognize that the source
server is no longer available during a migration and remain in migration mode.
In this scenario, perform the following procedure:
1.
Close SMP.
2.
Open the Windows Services Manager, and then restart the SMP application service and the HP SMP
Web Service.
NTFS partitions cannot be resized from a Windows 2008 application station
SMP does not resize NTFS partitions when migrating to an agent-based virtual machine host from a Windows
2008 application station. To resolve this issue, initiate the migration from a Windows 2003 application
station.
NTFS resize error message
The following message might appear during the migration of certain NTFS volumes:
The file system on source disk x, partition y could not be resized during
migration. The NTFS volume information could not be read. Retry the migration
without resizing this volume. Defragmenting the NTFS volume or performing a
"chkdsk /f" prior to the migration may resolve this condition.
The preceding message appears when SMP cannot process the NTFS meta information for this volume, and
the volume cannot be resized during migration.
To resolve this issue, do not resize the volume. Instead, perform a disk defragmentation or run chkdsk /f to
resolve the issue. However, performing a successful defragmentation and disk check, does not guarantee
the ability to resize. In this case, the volume can only be migrated without resizing.
SMP migration fails during the disk cloning phase
The following error message appears on the application station log (
hpsmpsvc.log
):
com.hp.mx.smp.vmdisk.api.APIException: Not enough space for partition!
This error might if the destination server disk has a Windows Logical Partition configured on it.
130
Troubleshooting