最後更新: 2023-03-22

目錄

• Injecting SCSI controller device drivers into Windows
• VM Converter
• Veeam

---

Injecting SCSI controller device drivers into Windows

 

Driver

Windows 2008 and Windows 7 (LSI SAS)

Windows 2008 and Windows 7 have the LSI SAS driver installed by default

( C:\Windows\System32\Drivers\lsi_sas.sys )

but they require a registry key to activate it

( export & import HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS )

Windows 2003 (LSI Logic Parallel / vmscsi)

Windows XP / 2000 / NT (buslogic and vmscsi)

Server03 Step

[0] backup reg

 - %SystemRoot%\System32\Config

 - HKEY_CURRENT_USER are in the %SystemRoot%\Profiles\Username

[1]

Power on the source for the conversion.

Download the VMware SCSI Disk Controller driver diskette at:

http://download3.vmware.com/software/vmscsi-1.2.0.4.flp

Right-click vmscsi.inf and click Install. The VMware SCSI drivers are installed.

Restart the source to complete installation.

[2]

Windows 2003 (lsilogic and vmscsi)

* S03 只會有其中一類 Controller

Copy the LSI Logic disk controller driver file located at

%systemroot%\system32\drivers\symmpi.sys

to the source for the conversion.

Copy the VMware SCSI disk controller device driver file (if present) located in

%systemroot%\system32\drivers\vmscsi.sys

to the source for the conversion.

[3]

Click Start > Run, type regedit, and press Enter.

Browse to and export these registry keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\symmpi 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1000&dev_0030

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmscsi

The vmscsi service registry key may not exist if VMware Tools is not installed on the virtual machine

 

---

VM Converter

 

V6.0 with Server08

Failed at 98%
FAILED: Unable to find the system volume, reconfiguration is not possible.

原因

Inaccurate BCD configuration data

Fix

1)

1. Register the VM into inventory (ESXi)

2. Boot correct installation media (i.e. Server08 ISO)

3. Select the appropriate keyboard layout and language options and click Next

4. Click Repair your computer

5. Select the operating system to be repaired and click Next

6. Select "Command Prompt"

2)

cd /d c:\windows\system32

bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
displayorder            {current}
timeout                 0
resume                  No

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:                               # 錯誤時係 ...
path                    \Windows\system32\winload.exe
description             Windows Server (R) 2008 Standard
osdevice                partition=C:                               # 錯誤時係 ...
systemroot              \Windows
resumeobject            {?-?-?-?-?}

[Plan A]

bcdedit /set {bootmgr} device partition=C:
bcdedit /set {default} device partition=C:
bcdedit /set {default} osdevice partition=C:

[Plan B]

Bootrec /fixmbr
Bootrec /fixboot
Bootrec /scanos
Bootrec /rebuildbcd

3) Blue Screen

0x0000007B

Boot Server08 ISO > Command Prompt > regedit.exe

In the Registry Editor window,

1. go to the registry hive HKEY_LOCAL_MACHINE

2. Select "File" -> Load Hive

3. On the local server drive (don’t confuse it with the WinPE disk) select the file \Windows\System32\config\SYSTEM

    mount with name "p2v"

4. Locate the key HKLM\p2v\ControlSet001\services\LSI_SAS

    Set the value of the "start" type to REG_DWORD 0.

Remark

• Start=0 value means that the service will start at Windows startup.
• Start=3 means that the service will be started manually.

Summary

Atapi->start:    0
Intelide->start: 0
LSI_SAS->start:  0

 

---

Veeam

 

Veeam Agent for Microsoft Windows --> Veeam Backup and Replication -> ESXi 7.0.3

Version 配合

v11a -> 5.0

In Source, specific the FQDN/IP address of VBR. (10001/tcp)

Restore Backup to ESXi

Veeam console > Backups > Disk > restore >

Right Click Backup > Instant Recovery to VMware vSphere

Full Backup

 * Creating VSS snapshot 很久

21/3/2023 17:48:03 :: Initializing
21/3/2023 17:48:42 :: Preparing for backup
21/3/2023 17:48:50 :: Required backup infrastructure resources have been assigned
21/3/2023 17:49:02 :: Network traffic will be encrypted
21/3/2023 17:49:13 :: Creating VSS snapshot
21/3/2023 18:10:02 :: Calculating digests
21/3/2023 18:10:58 :: Getting list of local users
21/3/2023 18:11:19 :: Recovery partition (disk 0) (133.3 MB) 133.3 MB read at 13 MB/s
21/3/2023 18:11:32 :: \\?\Volume{X-X-X-X-X} (disk 0) (2.0 GB) 60.2 MB read at 60 MB/s
21/3/2023 18:11:34 :: OS (C:) (1014.6 GB) 506.3 GB read at 122 MB/s
21/3/2023 19:22:27 :: Saving GuestMembers.xml
21/3/2023 19:22:31 :: Finalizing
21/3/2023 19:22:40 :: Full backup created
21/3/2023 19:23:12 :: Processing finished at 21/3/2023 19:23:12

 

---