Skip to content

Commit 0abaeea

Browse files
authored
Added information on how to prepare windows VMs for successful migrations with OCM
1 parent 159cb3c commit 0abaeea

File tree

1 file changed

+41
-0
lines changed
  • cloud-infrastructure/vmware-solutions/oracle-cloud-migrations/windows-migrations

1 file changed

+41
-0
lines changed
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,42 @@
1+
# Windows Migrations
12

3+
## Operating system preparations
4+
5+
In order to successfully migrate source environments based on the Microsoft Windows operating system you need to prepare the source environment.
6+
Microsoft Windows instances run on OCI Compute shapes using Paravirtualized drivers (VirtIO) for the Storage and Network interfaces. The drivers for these devices are by default not present and need to be installed before the migration to OCI in the source environment. If this is not done, the migrate instance will boot in OCI and fail with an “inaccessible boot device error” (Bluescreen error)
7+
and/or no networking interfaces presence.
8+
9+
### Installing the Oracle Paravirtualized drivers
10+
You can download the Oracle VirtIO drivers for Windows for oracle's e-delivery site:
11+
https://docs.oracle.com/en/operating-systems/oracle-linux/kvm-virtio/
12+
13+
**IMPORTANT**: Use the new VirtIO 2.0.1 or 2.1.0 Drivers, as the previous version (2.0) will result
14+
in an inaccessible boot device error.
15+
16+
### Replication issues with source instances running Microsoft Windows
17+
On every replication cycle, the OCM service will try to create a snapshot on the source
18+
virtual machine. The VMware environment will try to make the snapshot using filesystem
19+
and application aware quiescing.
20+
21+
There are sometimes issues where the VMware platform is not able to quiesce the filesystem properly,
22+
resulting in an replication error. The error could be something like: failed to open Virtual Disk. Open virtual Disk failed.
23+
The error code is 1. (Error code 1 means an unkown VMware error)
24+
25+
You can disable the application level quiescing, but be aware that the final replication cycle needs to
26+
be then run with a powered off source VM, else there could be a possibility of corrupted data.
27+
28+
### How to disable application level quiescing during snapshots of virtual machines
29+
https://kb.vmware.com/s/article/2146204
30+
31+
Disable VSS application quiescing using the VMware Tools configuration:
32+
- Open the file C:\ProgramData\VMware\VMware Tools\Tools.conf file using a text editor.
33+
- If the file does not exist at the location mentioned above, create it.
34+
- Add these entries to the file:
35+
```
36+
[vmbackup]
37+
vss.disableAppQuiescing = true
38+
```
39+
- Save and close the file.
40+
- Restart the VMware Tools Service.
41+
- Click Start > Run, type services.msc, and click OK.
42+
- Right-click the VMware Tools Service and click Restart.

0 commit comments

Comments
 (0)