Migrating Windows 2008R2 Servers To OCI - v5-1

Uploaded by

MWANAHAWA BAKARI

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

111 views6 pages

Migrating Windows 2008R2 Servers To OCI - v5-1

Uploaded by

MWANAHAWA BAKARI

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 6

JULY 2023

MIGRATING WINDOWS 2008R2 TO OCI

RACKWARE INC
VERSION 5
Contents
1 Overview ............................................................................................................................................... 3
2 Importing the Windows 2008R2 Image from RackWare ...................................................................... 3
3 Using the Windows 2008R2 Image for Autoprovision of Targets ......................................................... 5
3.1 Using a .csv File ............................................................................................................................. 5
3.2 Using GUI ‘OCI Options’ Tab ......................................................................................................... 5

2
RackWare Inc • Proprietary and Confidential
1 Overview
Since OCI does not provide images for Windows 2008 R2 instances, migrations must be done using
Custom Images. While you could create your own custom image, or use one of the deprecated
Windows 2008 images provided by OCI, you can also use one provided by RackWare. The Windows
2008 image provided by RackWare will support the E3.Flex shape, whereas the ones provided by OCI do
not. The procedure in this document describes how to use the custom Windows 2008 image provided
by RackWare.

You first will need to import the image provided by RackWare and then save it in your environment. If
using the autoprovision feature, you simply give the image name, the image username and the image
password in the wave file or on the GUI. If pre-provisioning your servers, you will then create an
instance from that imported image, modify the instance, then use it as the target of a sync. After the
sync completes the target instance will be an exact replica of the source Windows 2008R2 server.

2 Importing the Windows 2008R2 Image from RackWare

The procedure for importing a custom image using the OCI Console is described at

https://docs.cloud.oracle.com/en-us/iaas/Content/Compute/Tasks/imageimportexport.htm#Importing

The steps from that document are summarized below:

1. Log in to your OCI account

2. Click on the 3 horizontal lines in the upper left and go to Compute - Custom Images
3. Select your target region
4. Select your target compartment
5. Click Import Image.

In the Create in Compartment list, select the compartment that you want to import the image to. This
should be the same compartment as the one that will contain the instances of the migrated servers.

6. Enter a Name for the image. This name can be anything you choose, subject to OCI name restrictions.
In the example below, win2k8-image-from-RackWare is used
7. Operating System: Windows
8. Operating system version: Server 2008 R2 Standard
9. Check the box for “I certify that my use of this OS complies with Microsoft licensing requirements.”
10. Select "Import from an Object Storage URL”, then paste this URL into the Object Storage URL field:

https://objectstorage.us-phoenix-
1.oraclecloud.com/p/Qh4VwRWxaih1F2j5eyp0Sj2XkfYkflxNs01XkhtHR5Ztjk6mnG_90wKjsofaLBnH/n/a5
01635/b/templates/o/Win2008R2-opc-R@ckware!123

11. In the Image Type section, select the format of the image as QCOW2 and select Paravirtualized
mode

3
RackWare Inc • Proprietary and Confidential
12. Click Import Image.

After you click Import Image the imported image will show in the Custom Images list for the
compartment, with a status of IMPORTING. To track the progress of the operation, you can monitor the
associated work request. For more information, see Using the Console to View Work Requests.

When the import completes successfully, the status changes to AVAILABLE. This will take several
minutes. If the status does not change, or no entry appears in the Custom Images list, the import
failed. If the import failed, ensure you have read access to the Object Storage object.

4
RackWare Inc • Proprietary and Confidential
3 Using the Windows 2008R2 Image for Autoprovision of Targets
The RMM can automatically use and perform all necessary operations to use this image for the
autoprovision functions. All that is necessary is to give the image name, target username and password
during the wave file creation. The wave can be created either through a .csv input file or through the
GUI fields on the OCI Options tab when adding a sync.

When creating the instance, the RMM will choose a shape, number of cores, and an amount of memory
that best matches the source server. In most cases, a VM.Standard.E3.Flex shape will be chosen, with
the amount of cores and memory to match the source server.

3.1 Using a .csv File

If you are using a .csv file to create your wave, then fill in the fields as specified below:

1. Image Name - This is the name of the imported image you created in section 2
2. Target Username - opc
3. Target Password - R@ckware!123

If you are doing a staged sync, put the name of what you wish the captured image to be called in the
Clonename column.
It is not necessary to put in values for Shape, cores, or memory, as the RMM will chose the values that
best match the source server.

Fill in the Origin Name, Origin IP, ‘ssh only’, and Target Name fields as you would for any other sync.

Then upload the wave file. Once the wave has been associated with a clouduser, the OCI Options tab
containing the Image Name (called OCI Image Name on the GUI), Target Username (called Image
Username on the GUI), and Target Password (called Image Password on the GUI) will be visible.

3.2 Using GUI ‘OCI Options’ Tab

When setting up the Autoprovision parameters, on the OCI Options tab, select the OCI Image Type to be
Name. Then set the OCI Image Name to be the name chosen when the image was imported (‘win2k8-
image-from-RackWare’ in this case), the Image Username to be ‘opc’, and the Image Password to be
‘R@ckware!123’.

The Provision Disk Type should be set to ‘Paravirtualized’. This is the default value.