sureedge migrator 5.9.0 user guide - sureline …...site migrations or simply migrations. to address...

SURELINE SYSTEMS 2025 Gateway Place, Suite #480, San Jose, CA, 95110

© 2019 Sureline Systems. All rights reserved.

SUREedge® Migrator 5.9.0

User Guide

© 2019 Sureline Systems. All rights reserved. 2

Contents

1 Introduction ................................................................................................................................ 4

1.1 Deploying SUREedge Migrator .................................................................................................................. 4

1.2 SUREedge Migrator Licensing .................................................................................................................... 6

2 Getting Started ............................................................................................................................ 7

2.1 Accessing SUREedge Migrator User Interface ........................................................................................... 7

2.2 SUREedge Migrator UI Elements ............................................................................................................... 8

2.2.1 Header ................................................................................................................................................... 8

2.2.2 Menu Bar ............................................................................................................................................... 9

2.2.3 Workspace ........................................................................................................................................... 10

2.2.4 Footer .................................................................................................................................................. 18

3 Using SUREedge Migrator for Site Migration ............................................................................... 19

3.1 Migrating a Single Windows Server ......................................................................................................... 20

3.1.1 Adding a Single Windows Server ......................................................................................................... 20

3.1.2 Discovering a Single Windows Server .................................................................................................. 24

3.1.3 Starting Migration of a Windows Server ............................................................................................. 32

3.1.4 Recovering a Windows Server at the GCP ........................................................................................... 36

3.2 Migrating a Single Linux Server ............................................................................................................... 41

3.2.1 Pre-requisites ....................................................................................................................................... 41

3.2.2 Adding a Linux Server .......................................................................................................................... 43

3.2.3 Discovering a Single Linux Server ........................................................................................................ 44

3.2.4 Starting Migration of a Linux Server ................................................................................................... 49

3.2.5 Recovering a Linux Server at the GCP .................................................................................................. 53

3.3 Migrating Servers Using Plans ................................................................................................................. 57

3.3.1 Building Plans ...................................................................................................................................... 57

3.3.2 Discovering Multiple Servers in a Plan ................................................................................................ 68

3.3.3 Starting Migration of a Plan ................................................................................................................ 70

3.3.4 Recovering Plans and Server Groups at GCP ....................................................................................... 73

4 Advanced Features ..................................................................................................................... 77

4.1 Windows Discovery on the Client using Discover Utility ......................................................................... 77

4.1.1 Client-side Windows Discovery ............................................................................................................ 77

4.1.2 Client-side Windows Discovery using Command Line ......................................................................... 90

4.2 Bulk Server Additions ............................................................................................................................... 90

4.3 Image Caching .......................................................................................................................................... 95

4.4 Synchronization ....................................................................................................................................... 96


4.4.1 Synchronizing a Plan ............................................................................................................................ 97

4.4.2 Synchronizing Individual Servers ......................................................................................................... 99

4.5 Dealing with Failures ............................................................................................................................. 100

4.6 Tested .................................................................................................................................................... 106

4.7 Clearing Store Space .............................................................................................................................. 109

5 Contacting Support .................................................................................................................. 112


1 Introduction

The process of migrating data, applications or systems refers to relocating those components into

new and potentially disparate environments. P-to-V transformations and system relocation into a

public or private cloud are examples of system migrations. A given migration scenario can require

significant changes to the systems to be successful, such as transforming a physical system into a

virtual one; changing the hypervisor environment for a virtual system; relocating to a new site across

a WAN; changing data image formats; removing and/or installing drivers to match the new

environment; redefining system capabilities; etc. It may also require a carefully coordinated

migration of many complexly interdependent systems, such as with multi-tier web applications or

enterprise service infrastructure.

SUREedge Migrator® addresses the problems of system and application migration by automatically

handling these issues and complications within a well-defined, controlled and flexible workflow.

Customizable plans are built to specify exactly which transformations need to be applied to which

systems and how those systems are related so that they can be migrated successfully with a

minimum of downtime or unavailability. System capture is achieved without the need for installing

agents or extra software on the systems to be migrated and built into the process are points where

the captured images can be tested and tuned prior to cutting over to assure a quick and successful

migration. And the entire process can be carefully and accurately monitored to gauge progress,

immediately mitigate problems as they arise, and report results clearly.

1.1 Deploying SUREedge Migrator

An “instance” of SUREedge Migrator is a software appliance that can be installed within any virtual

environment to perform the critical functions of migration. At the most basic level each SUREedge

Migrator instance is capable of:

• Capturing a data-consistent image of a system without agents or additional software.

• Transforming that image so that it can be run in the desired virtualization environment.

• Instantiating the captured and transformed image within the target environment.

In some cases, a move involves transferring the data, applications and system images from one

location to another, such as between data centers across a corporate WAN; or to entirely new

virtualization environments such as public or private clouds. In these cases, the source and

destination environments are connected via a link of limited bandwidth, and the wholesale copying

of the volume of data is prohibitive (either by cost or time). Such cross-site moves are referred to as


site migrations or simply migrations. To address this scenario a pair of SUREedge Migrator instances

can be deployed, one at the source site and one at the target site, and images are transmitted

between the two instances. This takes advantage of SUREedge Migrator’s deduplication and

compression capabilities to significantly reduce the bandwidth requirements to move the images

from the source to the target site.

Figure 1: System Migration with SUREedge Migrator

Examples of migrations include moving systems between data centers or from a corporate data

center into a COLO center; moving physical and virtual systems into public and private clouds; and

moving systems and applications between incompatible clouds. The figure above shows a migration

of systems from multiple physical premises into a cloud computing environment by leveraging a

SUREedge Migrator instance in each site and in the cloud. Performing site migrations using the

SUREedge Migrator is described in Section 3

SUREedge Migrator is deployed in a manner specific to each environment:

In “local” virtualization environment via an installer that creates the SUREedge Migrator MC and

Store and for GCP with “one-click” or “blueprint” based installation via that GCP’s deployment

mechanisms. In these cases, there are no separate installers required to deploy the SUREedge

Migrator.

The specifics of deploying the SUREedge Migrator in a given environment is covered in an Install

Guide for that environment:

SUREedge Migrator 5.9.0 Install Guide for GCP: This guide helps user to install SUREedge

Migrator 5.9.0 on GCP using the Google Cloud Marketplace. Once you launch SUREedge

Migrator instance in GCP, user can download installers for other environment from home

screen.

SUREedge Migrator 5.9.0 Install Guide for Hyper-V: This guide helps user to obtain the

installer and to install SUREedge Migrator 5.9.0 on Hyper-V using installer.


You can obtain the installer(s) and installation guide(s) for your specific needs through your

designated contact at Sureline Systems or by contacting the Sureline Systems Support Team at

[email protected].

After deploying the SUREedge Migrator your instance will consist of two systems:

• A Management Console or MC system that serves the SUREedge Migrator UI and performs all scheduling and coordination of operations.

• A Datastore or Store system that manages the deduplicated image store and does the data streaming for image capture and inter-instance transfers.

The two systems work in concert to perform the operations required to complete migrations.

1.2 SUREedge Migrator Licensing

Each source instance of SUREedge Migrator must be licensed to perform migrations. If you have not

received your license(s) you can obtain it (them) through your designated contact at Sureline

Systems or by contacting the Sureline Systems Support Team at [email protected].

For SUREedge instance on GCP license is not required to apply separately.

Once you purchase the SUREedge Migrator, you will get a permanent GUID license. These licenses

are tied to a specific SUREedge Migrator instance. To obtain your GUID licenses you will need to

supply the Appliance Serial Number to Sureline Systems for all your SUREedge Migrator instances

after they have been installed. Detailed instructions on getting your Appliance Serial Number(s),

obtaining your permanent licenses and applying them to your SUREedge Migrator instance(s) can be

found in your SUREedge Migrator Installation Guide(s).

Once you have license(s) for your SUREedge Migrator instance(s) they will need to be installed before

you can perform migration operations. Instructions for installing licenses on the SUREedge Migrator

instances can be found in the Installation Guide for your platform or in the sections describing

migration.

mailto:[email protected]



2 Getting Started

This section provides you a brief overview of the SUREedge Migrator user interface (UI) and

functionalities. It is through this UI that you will configure the SUREedge Migrator instance, add

servers, build plans, perform captures, test captures images, and instantiate images in the GCP

environment. If you are a new user or if you wish to enhance or refresh your knowledge about

system migration using the SUREedge Migrator, make sure that you thoroughly read this entire

section, including the subsections that follow.

2.1 Accessing SUREedge Migrator User Interface

The SUREedge Migrator UI is accessed by connecting to the Management Console (MC) component

of the SUREedge Migrator instance with a web browser (Mozilla Firefox is recommended). Simply

connect to the MC using by substituting its IP address or system name in this URL:

http://<ServerNameOrIP>/

This will bring up the login screen for the SUREedge Migrator instance.

To log in, you need to specify the username and password and, if the user account is Windows

domain-based, the domain in which the account is managed.


Note that every SUREedge Migrator user account can be given one of two levels of privileges:

➢ Super Administrator privileges: You get full access on the SUREedge Migrator appliance. ➢ Local Administrator: Your access on SUREedge Migrator is limited to tasks related to the

local environment.

Note: For completeness, the screenshots in this user guide are taken with super administrator privileges. If you are not a super administrator, some functionalities may not display for you or may display in disabled state.

2.2 SUREedge Migrator UI Elements

This section will walk you through the user interface of the management console. The following

screenshot displays the user interface (UI) of the SUREedge Management Console web application.

The UI has four main elements – the header, the tabbed menu, the working area, and the footer.

2.2.1 Header

The UI header contains information about the SUREedge Migrator instance where you are logged in.

In the middle, it contains the instance’s Appliance Name and Appliance Location, which are purely

informational attributes to help distinguish between the SUREedge Migrator instances. On the right


is the username under which you are logged in and a link to log out, the current date and time, and

the license status of the SUREedge Migrator instance:

‘Licenses Used’ refer to the number of servers migrated against the SUREedge Migrator license that

you procured from Sureline Support Team. The header displays how many server licenses are used.

For example, if you see Migration License used 2 of 35 in the header of the UI, then it means you

procured SUREedge license for migrating thirty-five servers and out of that you have used two

server’s worth of them.

2.2.2 Menu Bar

The tabbed menu bar gives access to the main functional areas of the SUREedge Migrator UI:

Each area involves operations with a focus: source management, plan creation and operation,

Recover and job monitoring, etc.

Some items have a submenu of items to choose from, indicated by a down arrow ‘ ’. The currently

selected tab is shown in a dark background and indicates which area of operation is accessible in the

main UI workspace:


2.2.3 Workspace

Workspace is the working area where you can explore information about the system and perform

operations. The contents and the structure of the workspace changes depending on the tab currently

selected. For clarity in referring to different workspaces, this user guide identifies a workspace with

the web page name, which is displayed in the upper left corner.

There are two main types of workspaces in the SUREedge Migrator UI: grids which contain lists of

information about an area of operation (such as servers, plans or jobs); and the dashboard which

presents an overview of the state of all sources and plans and allows details to be explored.


2.2.3.1 Grids

Grids are used to display lists of related objects, such as servers or jobs. While the specifics of any

grid depend on the type of information being displayed, there are many attributes common across all

grids:

• Grid toolbar and links: Wherever relevant, a workspace has an additional workspace toolbar based on the information being displayed or manipulated. The tool bar may contain icons or text links.

• Pagination: A grid may have to display a large volume of information. To avoid log waits associated with loading many records, large data sets are divided into pages. The number of records (rows) in a grid’s current page is and the total number of records in all pages is displayed at the bottom left. When there is more than one page of records, the grid pagination bar with appropriately enabled controls displays at the bottom.

• Scroll bars: Wherever a page’s size exceeds the height or width of the browser window vertical and horizontal scroll bars will appear in the workspace.

• Sorting within grids: Most grids can be sorted by column values. If a column can be sorted a pair of arrows will appear in the header for sorting in ascending or descending order.


• UI refreshing: The UI display updates periodically to reflect changes that occur in the system as jobs progress or events occur. To force the most recent information to be displayed most

workspaces have a UI Refresh icon to update the current page’s information:

• Searching on grids: Where appropriate, workspaces have text boxes for filtering and searching for specific records in a grid. You may enter a few characters of the item you want to search, and the workspace displays the records containing those characters. To clear the search, you need to clear the text in the search box.

• Combining Search Criteria: Wherever appropriate the workspace may allow specifying additional search criteria. For example, the screenshot below displays searching for the string “21.17” as well as additional time-related search options from the drop-down list. To clear the search, you need to clear the text in the search box.


• Time based search: Some workspaces allow searching for a specific record using time attributes like “between two dates”. You can specify the date(s) by clicking the “Calendar” icon in the search box. To clear the search, you need to clear the text in the search box.

• Schedule actions: When a job is scheduled, you can edit or delete it from Actions pane.


2.2.3.2 SUREedge Migrator Dashboard

When you log in to the SUREedge Management Console, it shows Dashboard as home page. It

provides a visual summary of status of the server migration and migration plans:

You can also access the dashboard anytime by clicking on the Dashboard tab.

The Dashboard is divided into two views of the current state of affairs:

• a Migration Status view, that displays the proportions of servers in various states across all

servers known to the system.

a Plan Details view, that shows the proportion of servers in the various states within each

plan.

The server-wise view is on the left and is represented by a donut-chart divided into several segments.

Each segment proportionally represents the number of servers in a given state (discovered, captured,

etc.). To the right of the donut, each server state is listed along with the number of servers in that

state and the percentage of servers in that state among all the servers that have been configured in

SUREedge Migrator instance. The colors of the text in the list of states correspond to the color of the

segments in the donut chart.


Hovering over a segment in the donut chart will display the state, which the segment represents as

well as the number of servers in that state:

Clicking on a segment in the donut chart displays a grid of the servers that the segment represents;

for example, clicking on the Ready segment in the example above would display a grid of all the

recovered servers in the system:

This grid can be searched and sorted to find information about a specific server.


On the right side of the Dashboard is the plan-wise view in the form of a bar chart. Each bar in the

chart represents a plan, and the segments of the bar proportionally represent the number of servers

in that plan that are in each state.

Hovering over a bar in the bar chart will pop-up a list of all the server states and the number of

servers within the plan that are in each state.

Clicking on a bar in the bar chart shows a donut chart for the servers in that plan along with a grid of

all the servers in the plan:


The donut chart and the list below it represents the number of servers within the plan that are in

various states. Like the server-wise donut chart, each segment’s size is proportional to the number of

servers in the state it represents versus the total servers in the plan.

Hovering over a segment will display the state name and the actual count of servers in that state. The

grid displays all the servers in the plan, and can be searched, filtered and sorted like any grid.


2.2.4 Footer

The UI footer has three sections: The appliance name and software version information are displayed

on the left side, and copyright information at the center. These are for information purposes and are

not interactive.

The right side is the jobs monitor icon ( ). Clicking this icon displays the Monitor Jobs Overview

popup:

You can click on View All Job Activities to bring up the Job Monitor page or click the Monitor tab and

select the Jobs item.


3 Using SUREedge Migrator for Site Migration

Site migration (or just migration) is the process of capturing a replica of data, applications or systems

from the source site and transferring them to the destination (target) site to be instantiated in a

different virtualization environment. This process includes any transformations required to address

differences between the environments - data and disk formats; networking characteristics; system

attributes; software requirements; etc. To achieve this an instance of SUREedge Migrator is installed

and licensed at each site and configured to perform efficient data transfers between them. The

process of migrating systems can then be begun.

Figure 2 Site Migration

Once the two instances of Migrator are installed and configured, the first step in site migration is to

configure the source instance with information about the systems to be migrated so that it can

connect to and capture data from those systems. Migrator then needs to validate the systems’

information and gather their characteristics. The systems can then be grouped into Plans, which

describe the migration process: order of recovery, recovered system characteristics, etc. Systems can

also be migrated individually, without grouping them into plans.

Once plans have been defined the actual process of migration can begin by executing the plans. This

step performs an efficient initial capture of all the data associated with the systems in the plan (“A”

in the figure above). Once capture has completed the transfer of images to the destination site

begins immediately (“B”). This is also the point when images can be instantiated at the source site for

testing or other purposes. Once system images have been transferred to the target site they can be

instantiated (“C”) for testing and validation in the new environment. Captured system images can be

instantiated at each site as many times as needed to assure complete testing and a successful final

“tested”.


If data movement or testing took any significant amount of time the source systems were very likely

left running and they accumulated changes to the data. Any changes that have been accumulated on

the original systems at the source site can be captured by synchronizing the plan, effectively

repeating steps “A” and “B”. This “recapture” can be thought of as an incremental update to the data

images already ingested and should take significantly less time to capture and transfer. The migrating

systems can then be re-instantiated at either site with the new data for further or incremental

testing. This process can be repeated as many times as necessary to validate a successful migration

will happen.

The following sections will take you through all the steps needed perform site migrations after you

have installed the SUREedge Migrator at each site. For instructions on installing the SUREedge

Migrator see the Install Guide appropriate for the environment at your source and target sites.

3.1 Migrating a Single Windows Server

Once the SUREedge Migrator instances are installed and configured at the source and target sites,

the server migration process can be started.

Migrating a single server involves following steps:

a. Adding a Windows server

b. Discovering that Windows server

c. Migrating that Windows sever

d. Recovering a copy of that Windows server at the target (GCP) site

The following sections explain these steps in details.

3.1.1 Adding a Single Windows Server

Adding servers and most other operations are performed on SUREedge Migrator instance running on

the source side – the site where the servers to be migrated currently reside. Server administration is

done under the Source tab:


1. To add servers to The SUREedge Migrator, click (Add New Server) icon. This will

display Add New Server pop-up.

2. Select Windows Server from the Type drop-down in Add New Server pop-up:

3. Populate the following fields:

▪ Server Name/IP: Enter the Server name or IP for Windows server to be migrated.

▪ Username / Password: Enter credentials for accessing the server. The account should

have privileges equivalent to those for a typical backup agent.

▪ Exclusion List: You can specify comma separated list of drives (e.g. E:\, F:\) which you

want to be excluded from Server Migration. The data on these drives will not be captured

or transferred to the target site and will not be present on the migrated server.


4. You can click Verify to validate the address and credentials that were entered. The status of

the validation will be displayed below the data entry area:

5. Click Submit to add the server to the Migrator configuration. The newly registered server will

then be visible in the Source grid.


3.1.2 Discovering a Single Windows Server

Once a server has been added to the source-side instance, the SUREedge Migrator needs to contact

that system to gather information needed to perform the migration. This process is called server

Discovery. This also serves as a validation of the server information that was supplied (host address

and credentials).

Until at least one successful discovery operation has been performed on a server, no other

operations will be available for that server and the other action icons for the server will be greyed

out.

If at any time the configuration of a server changes or the credentials needed to access it are

changed a SUREedge Migrator Discovery operation should be performed again to validate the

credentials and update the server’s information within the SUREedge Migrator instance.

To discover a Windows server:

1. Click Source tab.


2. Select the server from the list. Click (Discover) icon for the desired server to be discovered:

3. You can choose to run the discovery operation immediately or schedule it for a time in the

future. To run it immediately, select Run Now and click Submit. A confirmation dialogue box

will be displayed.

To schedule and run the discovery in future, select Run At and configure the future date and

time, and then click on Submit. This will add the operation to the run schedule to be executed

at the specified time.


When a discovery operation has been scheduled in the future you can view, modify or

remove the scheduled operation by selecting the server and clicking on the (Schedule) icon:

1. This will show the server’s schedule operations in the pop-up:


2. You can then edit the scheduled time using the “edit” icon.

3. You can delete the scheduled discovery by clicking on delete icon and then click on Submit

button which shows popup for confirmation.


4. Click Submit to delete the schedule.

When the discovery job executes, it connects to the server to gather the required

information, which can take several minutes. You can monitor its progress in the Monitor

Jobs Overview popup (which appears automatically when you specify a discovery to occur

immediately):


You can track the progress of discovery operation in the Monitor Jobs Overview, or by

navigating to Monitor > Jobs.

If discovery is in progress status will be “Probing”. Once the discovery operation has completed

successfully, the job will show a status of Completed and the server will appear in the Source tab.

It is possible for a discovery operation to fail. This can happen for many reasons: incorrect server

information or credentials, network problems, internal issues of the server, etc.

When a failure occurs, the job representing the discovery operation will have a “Failed” status. You

can investigate the cause of the failure by examining the details of the discovery job.

Navigate to Monitor > Jobs and click Job Details icon to view job details.


Click icon next to Prerequisites to display prerequisite checks with results.

Take the recommended action to pass the status for step as required.


Note: In some cases, it is not possible to perform the Discovery operation from the SUREedge

Migrator’s MC instance. This is usually due to firewall rules on the client, network-based security

measures, and other connectivity factors. In these cases, it is possible to download and install

Migrator’s Discovery Tool software from the Migrator instance to the server to be migrated and run

it directly on that system. This will generate a similar report as a Discovery operation run from the

MC that details the failures and gives advice on correcting issues that could not be remedied

automatically.

Refer the section Windows Discovery on the Client using Discover Utility for details on performing

discovery directly on the system.


3.1.3 Starting Migration of a Windows Server

Once a server is in “ready” state, you can capture images of the server.

• Complete images can be captured from the selected server using the Migrate operation.

• Once the capture operation for a server completes, a transfer triggers immediately and automatically starts transmitting the image to the target site.

To start Migration of a single server, navigate to the Source tab and select the checkbox of the server

which is to be migrated and then click on the (Migrate) icon.

This will bring up a pop-up to confirm and schedule the operation.


Choose Run Now and click Submit to start Migrate operation instantly.

Choose Run At to schedule Migrate operation in future as per scheduled time.

Here you can specify the schedule on which to start migration of the sever. Click Submit to start a

capture operation for selected server, followed by a transfer operation (and any local validation

operations, if configured).

To see any operations already scheduled for a server, select the server and click the (Schedule)

icon from the action pane, which will bring up the operations scheduled for that server:


You can modify scheduled times or delete operations. Click Submit to save any changes.

To check the status and progress of running operations, navigate to Monitor > Jobs:


You may further click on the information icon for a job to check its detailed progress.

Once capture is completed, transfer operation automatically starts.


3.1.4 Recovering a Windows Server at the GCP

Once an image for a server has been transferred by the source site, you can recover it in the cloud.

To do this you can click on the Recover tab, which will be redirected you to the target site Migrator

instance running in GCP. You should then log into to the target Migrator instance using the proper

credentials. (You can get these from the Migrator deployment information via the GCP console.)

When connected to the target site Migrator UI the tab bar only shows tabs appropriate for cloud-side

operations:

Once source images have been transferred to the target site, they can be instantiated in the target

environment for testing or for final cutover.

Once you have logged in to the target site recoveries are performed under the Recover tab. Choose

the Server item to recover individual servers or choose the Server Groups item to do Plan-based

recoveries.


Selecting the Server sub-menu of the Recover tab displays all the server images that are available for

recovery on GCP-side SUREedge Migrator instance. Here you can select a specific image representing

a point in time that you wish to recover to target hypervisors.

You can search for the server you wish to recover by sorting the list by clicking on the arrows in each

column header, or by specifying a search string in the Search box.

To recover a specific image, click on the (Recovery) icon in the “Actions” column of the image. The

Recovery window will appear:


The following table describes the parameters for recovery:

Job Details

Job Name The name of the job.

Image Details

Change: Image If you wish to change the capture image, click on the Image button.

Target Location

Project The GCP project where the VM should be recovered.

Region The GCP region where the VM should be recovered.

Zone The GCP zone where the VM be recovered.

VM Details

Name The name for the Virtual Machine.

Number of VMs The number of copies of the recovered system to create.

Instance Type The GCP machine type for the VM to be created.

Access Scope The GCP access scope for the recovered system.

Storage

Disk Type Storage type for the disk(s) of the recovered server.


Preserve Partitioning/LVM

Select to preserving the original system’s partition and/or LVM configuration; otherwise each original filesystem/partition will be created as a separate virtual storage device.

Network

Network Select a network from the drop-down list to which the named virtual NIC will be attached.

Subnetwork Select a subnet from the drop-down list to which the virtual NIC will be attached.

Post Recovery

Operations You can specify a post-recovery operation to be run on the server created from the image after it has been instantiated. To do this, click on Add link next to Post Recovery > Operations in the above image.

Once you have specified the recovery attributes click Submit to start the recovery process. The

SUREedge Migrator will start the recovery, spawning a recovery operation for the server. The

recovery process can take some time depending on the amount of data to be recovered, the number

of servers, etc. You can track the progress and status of the recovery jobs by navigating Monitor >

Jobs.


Once recovery is completed, the status for the server will be Recovered when viewed on the Source

tab.


3.2 Migrating a Single Linux Server

Once the SUREedge Migrator instances are installed and configured at the source and target sites,

the server migration process can be started.

Migrating a single server involves following steps:

a. Adding a Linux server

b. Discovering that Linux server

c. Migrating that Linux sever

d. Recovering a copy of that Linux server at the target (GCP) site

3.2.1 Pre-requisites

Before migrating a Linux sever, check that all prerequisites have been met by downloading the

prerequisite checking utility and executing it.

This utility helps to check Linux prerequisites.

1. From Web UI, navigate to Settings > Download Utility > Linux Prerequisite.

This begins the download process for the prerequisite checking tool.

2. Give “execute” permission to execute downloaded utility by executing this command:

chmod a+x precheckForLinuxMachine.sh

3. Run the utility to check whether prechecks are configured on source machine or not:

./precheckForLinuxClient.sh -username <username> [-u]

where:

<username> is the username with you want to add/protect source machine

-u: Specify if you want the utility to try and modify the system to meet the prerequisites

Example:

./precheckForLinuxMachine.sh -username sureline -u

Following screen shows the typical output of the command:


3.2.2 Adding a Linux Server

1. Click the (Add New Server) icon.

2. This will display the Add New Server pop-up; select a server type of Linux Server from the

Type drop-down list.

3. Supply the following attributes:

▪ Server Name/IP: Enter the Server Name or IP Address of the server.

▪ Username/Password: Enter the credentials that will be used for accessing the server for

capturing data.

▪ Port: The port via which the server should be contacted via SSH; by default, it is 22.

▪ Exclusion List: You can specify comma separated list of mount points (e.g. /data, /test)

which you wish to be excluded from Server Migration.


4. Click Verify to validate the data that has been entered. Click Submit to add the server. Added

Linux server can be viewed in the grid list.

3.2.3 Discovering a Single Linux Server




and credentials, system accessibility, etc.).

Until at least one successful discovery operation has been performed on a server no other operations

will be available for that server and the other action icons for the server will be greyed out.

If at any time the configuration of a server changes or the credentials needed to access it are

changed a SUREedge Migrator Discovery operation should be performed again to validate the

credentials and update the server’s information within the SUREedge Migrator instance.

To discover a Linux server,

1. Click Source tab.


2. Select the server from the list. Click the (Discover) icon for the server to be discovered:


3. You can choose to run the discovery operation immediately or schedule it for a time in the

future. To run it immediately, select Run Now and click Submit. A confirmation dialogue box

will be displayed.

To schedule and run the discovery in future, select Run At and configure the future date and

time, and then click on Submit. This will add the operation to the run schedule to be executed

at the specified time.

4. To confirm, modify or remove the scheduled discovery operation, select the server and click

on (Schedule) icon. Refer section 3.1.2 to understand the flow to modify or delete the

scheduled operation.


5. This will show the server’s schedule operations in the pop-up:


6. You can then edit the scheduled time using the “edit” icon or delete the scheduled discovery

via “delete” icon.

When the discovery job executes, it connects to the server to gather the required

information, which can take several minutes. You can track the progress of discovery

operation by navigating Monitor > Jobs.

If discovery is in progress status will be “Probing”. Once the discovery operation has

completed successfully, the job will show a status of “Ready” and the server will appear in the

Source tab.

7. It is possible for a discovery operation to fail. This can happen for many reasons: incorrect

server information or credentials, network problems, issues internal to the server, etc.

When a failure occurs, the job representing the discovery operation will have a “Failed”

status. You can investigate the cause of the failure by examining the details of the discovery

job.


3.2.4 Starting Migration of a Linux Server

To start Migration of a single server, navigate to the Source tab and select the checkbox of the server

which is to be migrated and then click on the (Migrate) icon. Server should be in the Ready state in

order to start capture.

This will bring up a pop-up to set up operation scheduling.


Here you can specify the schedule on which to start migration of the sever. Click Submit to start a

capture operation for selected server, followed by a transfer operation (and any local validation

operations, if configured).

To see any operations already scheduled for a server, select the server and click the (Schedule)

icon from Action Pane, which will bring up the operations scheduled for that server.

You can edit the operations, modifying the scheduled times or deleting operations. Click Submit to

save any changes.


To check the status and progress of running operations, navigate to Monitor > Jobs:

Once the job status is “Completed”, you can do recovery.

You may further click on the information icon for a job to check its detailed progress.


Once the capture is completed, transfer operation gets launched. Once transfer operation is

completed, recovery of the server can be started.


3.2.5 Recovering a Linux Server at the GCP

Once an image for a server has been transferred by the source site, you can recover it in the cloud.

To do this you can click on the Recover tab, which will be redirected you to the target site Migrator

instance running in GCP. You should then log into to the target Migrator instance using the proper

credentials. (You can get these from the Migrator deployment information via the GCP console.)

When connected to the target site Migrator UI the tab bar only shows tabs appropriate for cloud-side

operations:

Once source images have been transferred to the target site, they can be instantiated in the target

environment for testing or for final cutover.

Once you have logged in to the target site recoveries are performed under the Recover tab. Choose

the Server item to recover individual servers or choose the Server Groups item to do Plan-based

recoveries.

Selecting the Server sub-menu of the Recover tab displays all the server images that are available for

recovery on the local the SUREedge Migrator instance. Here you can select a specific image


representing a point in time that you wish to recover to target hypervisors. Depending or target, user

can select different options specific to that target.

To perform recovery of specific server images, navigate to Recover > Server. This brings up the lists

of all the images, which can be recovered:

You can search for the server you wish to recover by sorting the list or by clicking on the arrows in

each column header, or by specifying a search string in the Search box.

To recover a specific image, click on the (Recovery/Create VM) icon in the “Actions” column of the

image. The Recovery window will appear:


Once you have made the desired adjustments to the recovery with attributes, click on Submit to start

the recovery process. The SUREedge Migrator will start the recovery process, spawning a recovery

operation for the server. The recovery process can take some time depending on the amount of data

to be recovered, the number of servers, etc. You can track the progress and status of the recovery

jobs by navigating Monitor > Jobs.


3.3 Migrating Servers Using Plans

Migration Plans are collections of servers which are captured, transferred and recovered as a group,

along with the attributes changes that will be applied to them during recovery. The use of migration

plans streamlines and automates the migration process. Servers may be grouped into plans for any

number of reasons: common administrative responsibility or functionality; common migration time;

common location etc.

3.3.1 Building Plans

Plan creation is performed on the source side of the migration by logging into the SUREedge Migrator

instance running in the same environment as the servers to be migrated. Migration plans are created

and managed under the Plan tab in the SUREedge Migrator user interface. To create a new plan, click

on (Create New Plan) icon.

This will open the Plan Creation wizard, which takes you through the steps of creating a new plan.

The first page of the wizard specifies the plan attributes:


You should fill the following fields:

Name: Specify a name for the plan.

Click Next to view “Server Selection”. This allows you to select the servers to include in the plan being

created.

Select the servers to be included in the plan by checking the checkbox to the left of each server you

wish to be part of the plan. By default, only servers that are not currently part of a plan are displayed

in the list; to see all the servers known to Migrator (including those already in plans) enable the Show

All Servers checkbox at the upper right corner. You can also sort the list by clicking on the column

headers, and filter the servers using the search box in the upper right corner.

Click Next to define Server Groups and the sequencing of recovery operations.


The servers within a plan can be subdivided into Server Groups which are collections of servers within

the plan that can be treated as one for the purpose of performing operations such as recovery. While

it is not required that you create server groups there can be many reasons for doing so – common

time for recovery, common functionality, etc. By default, all servers are in the same recovery set

(named Default).

A server’s Recovery Sequence Number can be set to determine the order that servers are instantiated

within a Server Group when a Plan undergoes recovery. At the time of instantiation, images will be

brought up in ascending numerical order of their Recovery Sequence Number. All servers with the

same Recovery Sequence Number will be recovered in parallel, and all will be instantiated before the

any servers with the next Recovery Sequence Number are recovered – i.e., all “1” numbered servers

will be instantiated before any “2” numbered servers, etc.

Server Groups are instantiated in parallel, and the servers within each server groups are instantiated

in Recovery Sequence Number order.

To create a new “Server Group”, select the “Add Server Group” drop-down. This will bring up the

Create Server Group pop-up:


Specify the name for the server group you wish to create and click on Submit to create the server

group or Cancel to cancel the operation.

To change the server group for a server, simply choose one from the drop-down in the Server Group

column.

A server’s Recovery Sequence Number can be specified in the Recovery Sequence column.

Once you have specified the recovery information for the servers in the plan, click Next. This shows

the VM Details screen.

Each server’s virtual machine can have certain attributes specified, such as the number of virtual CPU

cores and memory size. You can also specify the target VM’s name If the default is not satisfactory.

If a server has undergone discovery by SUREedge Migrator, then the CPU count and memory size will

be filled in with the discovered values from the source server. Any discovered values can be changed,

allowing servers to be resized as part of the migration process.


Click Next to move on to the Storage configuration page:

You can specify each system’s storage configuration as follows:

Disk Type Storage type for the disk(s) of the recovered server.

Access Scope The GCP access scope for the recovered system.

Preserve Partitioning/LVM Select to preserve the original system’s partition and/or LVM configuration; otherwise each original filesystem/partition will be transformed into a separate virtual storage device.


Once storage characteristics for all servers are have been set, click Next to bring up the VM

Configuration page:

The VM Configuration page allows the specification of Project, Region, Zone, Instance Type, Network

and Subnetwork characteristics and sole-tenancy options for the virtual machines created during

recovery. You can specify each virtual machine’s configuration as follows:

Project The GCP project where the VM should be recovered.

Region The GCP region where the VM should be recovered.

Zone The GCP zone where the VM be recovered.

Network Select a network from the drop-down list to which the named virtual NIC will be attached.

Subnetwork Select a subnet from the drop-down list to which the virtual NIC will be attached.

Sole Tenant Node (Optional)

Sole Tenant Node should be enabled only if you have Sole Tenant Node features configured for your Project and you wish this system to be migrated there.

BYOL BYOL option is enabled only for Widows Servers when there is a Sole Tenant Node in a GCP Project.

To ease the specification of the VM Configuration attributes in a plan for many servers you can

perform bulk editing by clicking on the Bulk Edit icon in the upper right corner:


This brings up a tool that allows you to simultaneously change the information for multiple of

servers in the plan. Changes can be applied to all the servers in the plan, or list of servers that are

selected. This allows, for example, a large number of servers to be moved to a new subnet in just a

few clicks.

First, select the systems whose configuration you’d like to modify as a group using the check buttons

if the left column. You can filter this list using the Server Group drop down.

Then choose the values for the parameters you’d like to change for those servers in the parameter

list at the top. These are the values that will be applied to the selected servers.


Once you are done click on Apply to change the parameters you specified on the systems you

selected and go on to make other changes; or choose Apply & Close to apply the settings and close

the bulk-edit window.

Once you have specified all the information for the plan, click Next to bring up the Capture

Operations screen:


Here you can specify operations to be performed immediately before and after images are captured

on each server. This allows control over how the capture operation is performed and/or the state of

the image that is captured. For example, you may wish to turn off backup operations during the

Migrator capture process in order to avoid conflicts between the two processes. Or you may want to

stabilize an application’s state so that the restored image is in a well-known state when a recovery is

performed in the target environment.

There are two operations that can be specified for each server:

Pre-Capture Operations: This will be executed on Source Machine before capture is initiated

(e.g. Stopping Antivirus Software during Capture)

Post-Capture Operations: This will be executed on Source Machine after Capture is done (e.g.

Start Antivirus Software that was stopped during Capture)


To specify an operation, click on the Browse button in the Pre- or Post-Capture Operation column

for the server. You are presented with a filesystem browser; select the script or executable you wish

to have executed and click Open.

Note: For Windows server, script should be .bat file format and for Linux server, script should be in .sh or .pl file format.

When you are done specifying any capture operations click Next to review the plan configuration:

This page summarizes the plan to be created. Review the plan and click Submit to create the plan.

The new plan will now appear in the list of plans under the Plan tab:


Under the Plan tab the existing plans can be managed using the icons in the action pane on the right:

Icons

Discover

Migrate

Sync Plan

Test Plan

Tested

Completed

Notes

Schedule

Information

Edit Plan

Delete Plan


3.3.2 Discovering Multiple Servers in a Plan

If a plan contains servers that have not undergone the discovery process, then the plan cannot be

migrated. Discovery for the undiscovered servers (or for servers that require discovery be

reperformed) can be initiated from the Source tab on a per-server basis, or a discovery operation for

all the servers in a plan can be performed from the Plan tab.

To perform a discovery operation on all the servers in a plan, click on the Plan tab, select the plan

you wish to discover then click on (Discover) icon.

This shows Action: Discover pop-up:


You can choose to run the discovery operation immediately or schedule it for a time in the future. To

run it immediately, click on Run Now and click Submit. To schedule the discovery, click on Run At

and choose the date and time when the discovery should be performed. A confirmation box will be

shown at the right-hand side top corner of the screen as below:

The progress for a running job can be tracked and examined by navigating to Monitor > Jobs.


3.3.3 Starting Migration of a Plan

To start the migration of all servers in a plan, navigate to the Plan tab on the source-side SUREedge

Migrator instance select the Plan (or Plans) for which you wish to start migration and click on

(Perform full capture/transfer) icon in the Actions pane:

This will bring up a pop-up Action: Migrate to set up operation scheduling:

To start operation immediately, click on Run Now and click Submit. This will show the Monitor Jobs

Overview pop-up with information about each of the new jobs:


Detailed job tracking can be viewed by navigating Monitor > Jobs:


To start the operation at a time in the future, click Run At and define a time when the operation

should start, then click Submit to set the schedule. Scheduled jobs can be examined by selecting the

Plan(s) and clicking the Schedule icon in the Actions pane, or by clicking the All Plans Schedule icon

at the upper right.


3.3.4 Recovering Plans and Server Groups at GCP

To perform recovery, navigate to Recover > Server Group on the target Migrator instance’s UI to

view a grid of all the defined plans and server groups. (If you click Recover on the source-side

Migrator UI, you will be redirected to the target side.)

Each plan has action icons in the rightmost column:

Icons Description

Recovery – perform a recovery/create vm operation at the Target site

Server Group Info – displays the plan’s attributes

To recover the entire server group, click on the (Recovery) icon. This will initiate recovery

operations for all the servers in the selected plan from the most recently captured images.

The result will a set of virtual machines created from the captured images representing each of the

servers in the plan with the changes indicated in the plan applied.


Clicking the ( Recovery) icon displays the Recovery pop-up:


The Recovery pop-up displays the list of all the systems in the plan that will be instantiated as well as

details of the virtual machines that will be created. All of these attributes are taken from the values

specified when the plan was created; they are available for modification in this dialog, including using

the Bulk Network Edit feature to assign network configurations for multiple servers at the same time

(see Section 3.3.1 “Building Plans” for details).

You may also assign post-recovery operations to each server that will be run after the virtual system

has been created and instantiated. Post-recovery Operations are useful for automating tedious tasks

that are needed when a system is cloned or duplicated, such as dealing with licensing issues,

installing or removing custom components, performing system readiness tasks, etc.

To add a post-recovery script, click on Add link for the virtual machine on which the script should be

run after it is recovered. As a result, Add Operation prompt will be shown:

In the Add Operation window, click Browse and navigate to and select the script file to be executed

and then click on Open. This will upload the specified file and display it in the Add Operation

window.

If you wish to remove a post-recovery script for a virtual machine, simply click the delete icon ( )

next to the script to be removed.

Once you have made any desired changes to the recovery attributes for the plan click Submit. The

SUREedge Migrator will start the recovery process, spawning a recovery operation for each server to


be recovered in the order specified in the plan. The recovery process can take some time depending

on the amount of data to be recovered, the number of servers, etc. You can track the progress of the

recovery jobs by navigating Monitor > Jobs. Refer to section 3.1.4 for a complete description of the

server recovery process.


4 Advanced Features

This section explains some advanced features available in SUREedge Migrator.

4.1 Windows Discovery on the Client using Discover Utility




and credentials).

In some cases, it is not possible to perform the Discovery operation from the SUREedge Migrator’s

MC instance. This is usually due to firewall rules on the client, network-based security measures, and

other connectivity factors. In these cases, it is possible to download and install Migrator’s Discovery

Tool software from the Migrator instance to the server to be migrated and run it directly on that

system. This will generate a similar report as a Discovery operation run from the MC that details the

failures and gives advice on correcting issues that could not be remedied automatically.

4.1.1 Client-side Windows Discovery

To perform Discovery directly on a Windows system follow you need to download the software

bundle via Migrator’s UI, install it and execute it.

1. Connect to the Migrator Web UI from the client system and navigate to Settings > Download

Utility > Windows Discover and save the offered zip file to the system to be added.

2. Unzip the saved file to extract the Discovery Tool installer.

3. Double click SSDiscoverUtilitySetup application file to run the installer:


4. Click Next.


5. Click Install.


6. If you don’t wish to perform Discovery on the server at this point, click Finish to complete the

installation. You can come back later and execute the file <path> to perform the server

discovery at your convenience using “SUREedge Discover Utility”.

7. If you wish to run Discovery now, select ‘Discover this server to a SUREedge Migrator instance

now’ checkbox and click Finish. This starts the discovery process.


8. Click Next.


9. Enter data in the Server Details pop-up for discovery and click Next.


10. Enter the data in the SUREedge Details pop-up and click Next. This will start the validation

and Discovery process.

When the process completes the results will be displayed:

Precheck result

Precheck result is displayed at the bottom of the screen. The result can be pass, warning or

fail. Following is the criteria to decide precheck result:


a. Pass – If all tests have result as “Pass” then Precheck Result shows “Pass”.

b. Warning – If test(s) shows warning as displayed below, precheck result shows “Warning”.


Click Next to continue discovery.


c. Fail – If any test(s) shows fail, precheck result shows “Fail”.

Check the failed test and take the appropriate action to overcome the failed test. Click on

Rerun to run precheck again.


11. Click Next after “Pass” or “Warning” precheck result shows following screen.

12. At this point the server has undergone discovery. If the system has not yet been added to a

SUREedge Migrator instance you can do that now by selecting the checkbox marked “Add this

server to the SUREedge Migrator instance at …” and clicking Next. If you do not wish to add

the server at this time, make sure the checkbox is unchecked and click Next.


13. Click Finish.


4.1.2 Client-side Windows Discovery using Command Line

To perform Discovery using command line, you need to download the software bundle via Migrator’s

UI and install it.

1. Connect to the Migrator Web UI from the client system and navigate to Settings > Download

Utility > Windows Discover and save the offered zip file to the system to be added.

2. Unzip the saved file to extract the Discovery Tool installer. It contains following files:

• SSDiscoverUtilitySetup.exe

• sureedge_config.conf

3. There are two methods to run discovery using command line:

a. Execute following command on the client machine on elevated command prompt before

start client discovery from Migrator UI. This will not check required precheck. SSDiscoverUtilitySetup.exe /s

b. Update sureedge_config.conf file and then execute the discovery command. This will

automatically start discovering server.

Config file changes:

auto_discovery=True

server_password=client_server_password

mc_password=MC_server_password

exclude_list=Comma separated list

command on client machine SSDiscoverUtilitySetup.exe /s

4.2 Bulk Server Additions

To ease the process of adding many servers, SUREedge Migrator can use a spreadsheet document

(formatted as a Windows Excel .xlsx) to import server information in bulk.

To obtain a spreadsheet of the proper format you can export existing server data from The SUREedge

Migrator. On the right-hand side corner click on (Bulk Export) icon and save the Excel spreadsheet

file to your computer.


The resulting file is an Excel spreadsheet in a format that SUREedge Migrator can use for importing

server information. The spreadsheet is populated with information about servers that have already

been defined, as shown below:

In the spreadsheet, each row represents one server and contains columns as defined below.

Please note that the list is exported to obtain proper format of spreadsheet. Leave fields blank

wherever applicable.

Column Description ip_address IP address of the server.

typeName Type of Server (e.g. Windows Server, Linux Server)

user_name Username to be used to access the host

Password Password of Username

port_number Enter SSH port number (for Linux servers)

exclude_list A comma-separated list of drive or mount points to be excluded from migration

The spreadsheet should be filled in with information about all the servers you wish to add to the

SUREedge Migrator. Once the spreadsheet is completed, you can perform a bulk import by clicking

on the (Bulk Import) icon.


This opens an Import File pop-up:

Click Browse and select the Excel spreadsheet file to be imported, and then click on Open.


Once the file is uploaded, it will be processed to extract the server information so that it can be

presented for confirmation. During this time the progress and status will be displayed as shown

above.

Once the data has been processed you can choose which servers’ information to import. Select YES

for each server to confirm that it’s information should be imported (either as a new server or as an

update to an existing server, as indicated in the “Confirmation” column); or select NO to not import.

Once you have selected the data to import, click Import at the bottom of the pop-up to perform the

import. A confirmation pop-up will appear confirming that the server information was successfully

imported.

New servers added via the Bulk Import operation will now appear in the grid list.


4.3 Image Caching

If “Image Caching configuration” is enabled by navigating to Settings > Instance > Image Caching

configuration at target site, image caching operation triggers automatically and you can “create VM”

at target site.

Following screen shows image caching configuration. By default, it is disabled.


4.4 Synchronization

While data movement and testing occur, the original servers are still running and accumulating

changes to the data that is being migrated. To capture these changes for further testing or for the

final cutover to the target site you can synchronize the systems being migrated.

This step is like an incremental backup: only changed data on the source systems is ingested which

should be smaller than the overall system image.

In combination with prior captured images this would represent the latest complete image of the

system(s). Synchronization images are also automatically transferred to the target site after each

system’s changes have been captured.

Synchronization can be performed at the server or plan level; synchronizing a plan will simply

perform a synchronization operation on all the servers in the plan.


4.4.1 Synchronizing a Plan

Plan synchronization is done using the Plan tab:

To start a plan synchronization, first select the plan that need to be sync and then click on the Sync

icon in the Actions column. This will bring up a confirmation dialog:

Choosing Run Now will trigger the sync job to execute immediately, whereas Run At will schedule

the job for a future time.


Starting a synchronization on a plan will trigger a synchronization operation for each server in the

plan, followed by a transfer of the captured data to the target site. The synchronization process can

take some time, depending on the amount of changed data since the last synchronization or capture.

The progress of the synchronization operations and the image transfers can be tracked by navigating

to Monitor > Jobs. After the synchronization capture is complete, the job information will indicate

the size of the changed data that was ingested:


4.4.2 Synchronizing Individual Servers

The Sync Server option triggers another capture job for already migrated server. This captures the

changes to the server’s data that have occurred since the prior transfer. If the server has no prior

captured images this option will perform a Full Capture. To start a sync, select the server by checking

the check box of that server and the click on (Sync) icon:

Like the Sync Plan operation, you can either run the operation right away or schedule it for a future

time.


4.5 Dealing with Failures

Various operations performed as part of migration are subject to failure for many different reasons.

The most frequent problem is a network failure of some kind, but there can also be misconfiguration,

system reboots or resets, errors occurring in applications being migrated, etc.

A failure in a migration step for a server is indicated by a sever being marked as being in the Failed

state on the dashboard and in the source list:

Plans with failed servers can be found by looking at the Plan bar chart on the dashboard.


Click the Failed segment of the donut chart, it will show a grid with the failed servers:


Click on Failed segment of a bar chart will show the list of servers from respective plan as shown in

the following screen:

A server that is placed in the failed state implies that an operation being performed as part of that

server’s migration has failed, and the job information for that operation will contain the details.

The status of failed jobs can be seen by clicking on the word Failed in the Status column, which will

bring up the Monitor > Jobs screen filtered to show only the failed job(s).

You can also display all failed operations by navigating directly to the Monitor > Jobs screen and

choosing Failed from the status filter in the upper right corner. The other filter fields can also be used

to find a failed job by searching for a system name, job type, time span, etc.

On the Monitor > Jobs page selecting the Job Details icon ( ) from the Actions column on the right

of a Job’s row you will show the details of the job, including why the failure occurred. Frequently,

these details will identify the exact reason for the failure:


Note that the Job Details dialog shows the job’s details with a separate status for each step

performed. Click Close to dismiss the dialog.

Discovery Job Failure

For discovery failures you can click on the icon in the Prerequisite field to view a detailed status for

the discovery operations performed and prerequisites that are checked as part of discovery.

For any job you can click on the (Check log) icon in the Status field to view the logs for that job.

You also have the option to Download Error Logs or Download All Logs for the failed job:


Click Close to dismiss the Logs dialog box.

Retrying Jobs

For most types of jobs if a job fails you can retry it rather than having to re-specify the job from

scratch. For example, if a capture job fails you can simply retry it, rather than navigating to the

Source or Plan tab and re-specifying the operation there. This is especially useful if an inter-site

image transfer or image caching operation failure occurs, since those jobs cannot normally be

initiated by the user (they occur automatically after a capture has completed or an image has

successfully transferred.)

To retry a job:

1. On the Monitor > Jobs screen find the failed jobs that you wish to retry:

2. Click the (Retry Job) icon for a job to retry. This shows following pop-up for confirmation:


3. Click the Submit to restart the failed job.


4.6 Tested

This is the last step in a site migration to the target environment. This usually involves:

• Placing the source systems in a state where no further data changes will occur.

• Kicking off a final sync in the SUREedge Migrator to capture the last set of data changes from the source systems.

• Once the transfer of the final sync image has occurred the target systems are instantiated, and the source systems can be shut down and retired.

There also may be some coordination with external processes or entities (DNS name changes, etc.)

required to transfer operations from the source servers to the migrated servers in the target

environment.

To represent that a set of servers are in the process of being cut over a Plan can be put into the

“Tested” state. This state will then be reflected in the dashboard and other grids and reports to

indicate the plan’s status. To place a plan in the “Tested” state log into the source SUREedge

Migrator instance and navigate to the Plan tab. In the Plan tab, select the plan by checking the check

box in front the plan and then in Action column, click on (Tested) icon. By Default, the state is Off:

This will show Action: Mark As Tested pop-up.


Click Submit to mark the plan as tested. The plan will now be shown as in the tested state as shown

below:

User can also click on Dashboard and confirm all the servers those are in Tested state.


Similarly, if you are migrating individual server, you can mark a single server as being in the tested

state from the Source tab.


4.7 Clearing Store Space

In some scenarios it may be necessary to clear space from the Deduplicated Store to make room for

new images to be captured. This typically occurs when many servers are being migrated in waves to

reduce the storage needed by SUREedge Migrator. By moving in waves, you only need to allocate

enough storage for one wave to the Store; that space can then be “recycled” for the next wave.

To reclaim space in the Store, the images that occupy that space must be deleted. Migrator can then

reclaim that space as part of an occasional automated cleaning operation. Such cleaning operations

appear in the Monitor > Jobs tab.

You may also wish to immediately begin reclaiming space, and/or have finer control over exactly

which images to delete to free up space. This can be done using the Storage Space Cleanup dialog.

1. From Web UI, navigate to Settings > Store Space Cleanup.

2. Once you click Store Space Cleanup, the Store Space Cleanup dialog appears.


3. Select images you wish to delete to free up space. To delete all images for a server simply

navigate to the server and click its checkbox. To choose individual images for deletion

navigate to the server for that image and expand it; this will display all images for that server.

You can then select images to delete. To delete the selected image and start the cleanup

process click the Cleanup.

Note that it is not required that you delete images; there may be space that has become

unreferenced though other mechanisms (deleting servers, etc.) that can be reclaimed

immediately rather than waiting for the next automated cleaning pass. To reclaim space

without deleting any images simply click Cleanup without selecting any images or servers.


4. Once you click the Cleanup, following confirmation pop-up is displayed:

5. Click Submit to start cleanup job. You can navigate to the Monitor > Jobs page to view status

of the cleanup job.


5 Contacting Support

The Sureline Systems website (http://www.surelinesystems.com) provides a support page wherein

you can submit your issues and a ticket will be automatically generated and the support team will

contact to you.

Email us: You can also send an email to [email protected] with a detailed description of

the issue, which will automatically create a ticket in the ticket generation system. Our customer

support team will reach out to you.

Telephone Support: Call 408–331-8750 to speak with a Sureline Systems Engineer.

http://www.surelinesystems.com/


sureedge migrator 5.9.0 user guide - sureline …...site migrations or simply migrations. to address...

Documents