Data Migration - Overview

So we're going to divide this in a few portions, and the first portion that we're
going to talk about is your planning your data migration to OCI.

This is very important to start. So when you decided to make that movement,
you decided to get all the data ready on premises and move that to OCI, you
have to have a good understanding of what kind of applications database you
actually want to move, identify their versions, their dependencies, have a good
overview of what exactly is actually up and running and how that's going to be
translated to OCI, as well.

So we have other lessons that we cover database options and some of the
matrix around versions that can be supported in OCI. It's very good to
understand that, to understand what the version supported, how can you
translate your version of Oracle database on premises to OCI, how you can
bring your own license, all those options available so you can succeed on your
migration.

Another aspect of the planning is understand the regulatory compliance. So if

your environment is under some compliance directives, for example, HIPAA or
FedRAMP, or even PCI, so you have to understand how the nature of their data
is hosted on their own premises and how that's going to be hosted in OCI.
Understand how you architect the application, how you architect the
environment in order to support that data and respect the compliance that you
have to use.

Around the storage, too, so what kind of type of storage you have? Are you
using code, are you using hot storage? Well, how big is the data? How big is the
storage that you're using today? What's the amount of data you have? This is
really important to understand in planning to actually have a good planning
capacity plan when you move that to OCI.

Another one is the networking portion. A very good aspect is how you're going
to transfer that data over to OCI. Are you going to use that through public
internet? Are you going to transfer to using VPN connectivity or FastConnect?
So what kind of methodology are you going to use? What kind of network
connectivity are you going to implement to make sure your on premises data
center can talk to the OCI, and how are you going to transfer that data over?
Still around in the planning is again, understanding our environment. Once you
get all that information about the environment, you start deciding what kind of
environment I want to move. Do I want to move my production environment
first, or I think will be better if we start moving what we call the low risk
environments, development environment, testing applications, Q&A, so things
that have less tied in terms of integration and data, so you can get comfortable
with the platform? You can get comfortable migrating that data over, so then
you can make better decisions when you decide to move your production
environment.

So how critical is the business you're trying to move over to OCI? What kind
environment do you want to try first? And one of the third options, which is
part of the planning, too, if you want to just to a disaster recovery in the first
place.

Some companies, they decided to-- they don't have a disaster recovery plan
today for the on premises environment. They want to start that with OCI and
created a disaster recovery plan to host all the data there, and then eventually
ended up moving some of the production environment over to OCI to host that
on the cloud environment. And then they have all the disaster recovery across
regions, and so forth.

So this is another thing you have to think about it, and how you start planning
the migration and collecting all that information to make the best decision
when you start looking to move your data to OCI.

So on the next portions of the video, we're going to talk about two different
types of migrations. We're going to talk about offline migration and online
migration. This is just an overview for now of how that's going to look like.
So if you're talking about offline migration and we're going towards a data
transfer service and some options you can use there in order to move the data
from one premises to OCI. And we're going to talk about online migration,
which is using what we call the stage Gateway, that it can copy data over to a
storage gateway. And send it over to, OCI as well. Of course, there's other ways
to do online migration, like through FastConnect, or IPsec VPN. We touched
some of your things there too but we're going to tell about those two services
data transfer there's a transfer service and storage gate.

Data Migration – Offline

Hello, everyone. My name is Flavio Pereira. I'm part of the Oracle Cloud
Infrastructure on the Technical Enablement team, and this is the second portion
of the data migration. So on this second portion, we're going to talk about
offline transport. We're going to cover Data Transfer Appliance and Data
Transfer Disk.

So if you are planning to move a good amount of data-- a huge amount of data
from your own premises to OCI, you have two options that you can use to
accomplish that. You can use Data Transfer Disk or Data Transfer Appliance.

So the Data Transfer Disk is a service that you can just ship a hard driver to
Oracle Cloud Infrastructure, and these hard drives can be a SATA disk or USB
disk that you can hook up to your servers on your on premises environment,
you can copy the data inside of those disks, and then send that disk over to us.
Then we're going to copy that data to an object storage that was specifically
dedicated to you, so you're going to give us which object storage you want to
put that data on, and then we're going to copy the data there. And then you're
going to have access to that data on that object storage, then you can copy that
over to your block storage or your local machine that you have up and running
inside sort of OCI.

So the Data Transfer Appliance, instead of you providing the hard driver, we're
going to send you an appliance. We're going to send an appliance to you. You're
going to copy that data inside of that appliance and send that appliance back to
Oracle. And then we're going to copy the data to Object Storage and then give
you access to that data, right?

So what's the difference between those two? The Data Transfer Disk, you can go
up to 100 terabytes of data and you can send 10 disks per transfer package. So
the limit capacity is 100 terabytes. You can divide that in 10 disks and then send
that over to us, and then we copy that data there for you.

So Data Transfer Appliance, the capacity is 150 terabytes. So if you go beyond

100 terabytes and you will have to send in multiple hard drives, you can just ask
for the appliance. It's easy to ask through the OCI console. We can send the
appliance over to you, and then you get that, you put the data inside of the
appliance, and you encrypt that data, right, and then send that over to us.

OK, so those two options are available, very easy to use, very easy to get these
requested through the OCI console. And then you can send that data over to
OCI.
So just to give an idea of the Data Transfer Appliance specification, right-- so the
hard drive, you can use the hard drive. You can have one hard drive today on
your own premises, but for the Transfer Appliance, you might need to
understand what's the specifications of the hardware that we're going to send it
to you, right? So just a couple of things to highlight here. You can see the
appliance weight is 38 pounds, and 64 pounds if you're counting the shipping
case, the shipping case that will be going with the appliance towards you.

You have to remember that the appliance-- the only thing that's exposed to
you, as a customer, to plug on the appliance is the power, the network, and the
zero console. So those are the three things that will be available for you to
actually plug on that appliance. You can hook up that appliance on your rack,
right, on your data center. It's a 2u device, so you can just put it on top of the
table, or if you have a rack, you just can hook up that on the rack, and then
connect the network, connect the power, connect the serial console if you need
it to start copying the data over there.

Data security-- there is AES 256 encryption. So when you copy the data inside of
the appliance, we're going to use the utilities to make sure that you apply the
encryption on that data. And then when you ship that back to us, the data will
be encrypted all the way from your location until it gets to the OCI, right?

Network connectivity is a 10 gigabit network that's available. So if you have a 10

gigabit network connectivity on your local networks, so that's going to take
advantage of it, right? So those are the few specifications and information
about the hardware that you need to understand. Also, the management
interface is an NFS V3, V4, or 4.1. So that's how you actually going to mount the
device and connect to the device so you can start copying the data over there.

So what about encryption, right? I touch-- the encryption that you have to
encrypt the data. But whether you're using the appliance or the disk, right, so the
encrypted data is going to be at rest with AES 256-bit encryption. And all the
encryption password is actually stored on OCI, which is separated from the
Transfer Appliance or Disk. So when you create the encryption password to
actually seal the disk or seal the appliance, that would be copied directly on OCI,
and then it's not going to be traveling with the disk when you're shipping that
over to us.

So if someone, perhaps, you know, the shipping company just lost the disk or
lost the hard drive, that's not a problem. No one will be able to actually get
access to the data you put it over there, right? Because they don't have the way
to decrypt your encryption and then get access to the data, OK?

And then once you land that data in the OCI bucket on the Object Storage, it's
also encrypted as well. It's encrypted at rest. So there is an encryption of the
data on the Object Storage too, OK?

So how do you put actually the encryption on the disk, right? Using Data
Transfer Utility, that's actually a command line or a software that you can install
on your machine that's going to help you to prepare to transfer disk and prepare
all the data-- encrypted data for the shipment, and then you can send that over
to OCI.

So there's a few requirements here in terms of the operating system that you
can install that, Java version as well. So I highly recommend you might want to
use a virtual machine just to have this Data Transfer Utility installed. Then you
can get access to the data and then copy the data over to your Data Transfer
Disk or Data Transfer Appliance and using the machine just to encrypt the data
and finalize that for shipment.

There are some firewall requirements as well so you can get access to the
Object Storage later on to get access to your data. So make sure you have some
of those-- so have the firewall configuration enabled so that way, you can get
access to the data once that's moved to OCI.

So another option in terms of command line for preparing the data-- you can
use the Command Line Interface-- The OCI CLI-- which has a DTS functionality
on the OCI CLI to actually help you to prepare the appliance and, you know, all
the data to ship that to OCI, OK? That will help you with encryption, too. And
you have to use that on the Linux machine. So the only thing is if you're using
Command Line Interface, that's only available on Linux operating system. So
then you can use that as an option to encrypt the data and send that data over
as well.

OK, so how the Data Transfer works-- what's the workflow for that, right? You're
going to create a Transfer Job. You can use that to the OCI console or the
Command Line Interface, you can create that Transfer Job. You can request one
or more appliances. So if you're willing to do the Data Transfer Appliance, you
can request that to the console. Then once you request, you're going to receive
the appliance. Once you receive it, you connect the applies to the network,
connect that to the applies via serial console or IP, so it depends how you want
to connect to it.

Then you're going to use one of the utilities-- the Data Transfer Utility or the
Command Line Interface to prepare the appliance, to create the encryption,
right, and the data sets. Once you've copied everything there, you're going to
seal the data set using the manifest file that will be generated through the Data
Transfer Utility or the OCI CLI. And then you're going to finalize that transfer,
right? You're going to finalize the transfer, which is going to be to ship that Data
Transfer Appliance back to Oracle or send the Data Transfer Disk to Oracle, and
then we're going to copy that data to the Object Storage. So those are the six
steps on the high level.

So if you're still thinking about why should I use the offline transport, right,
what's the advantage of it? So this is just one quick table to show you if you
want to send data-- and let's say you have a link of 10 megabits per second and
100 or 1 gigabits per second-- this is the amount of time that's going to take
depending on the data size, right?

So let's see one example. If you're using 100 terabytes-- which is ideal for Data
Transfer Disk, right-- if you decided to send that over the internet and you have
100 megabits per second network bandwidth on the internet, that's going to take
roughly 101 days to do it, right? So that's going to take a lot of time. And if you
do that using Data Transfer Services, you're going to get this done in one week.
OK?

So same thing if you're going to 500 terabytes or 1 petabyte of data, right,

depends on the connectivity you have. It's better if you do that with the Data
Transfer Services. So sending one petabyte of data, even if you have a 1 gigabits
network using FastConnect, it's going to take 101 days, too. So in two weeks,
you're going to have that data available to you, OK? So those are just to give an
idea of the data sets and how long it would take if you decided to send through
a public interface or using Data Transfer Service. OK?

So that concludes our portion. The next video, we're going to talk about online
transport. And we're going to use some of the options for, like, Storage
Gateway or using-- you have your FastConnect connected, your VPN
connectivity, so what are the options you have for online transport? Thanks for
watching.

Data Migration – Online

Hello, everyone. My name is Flavio Pereira. I'm part of the technical enablement
at Oracle Cloud Infrastructure. And this is portion 3 of the data migration.

We are talking about data transfer services and Storage Gateway. So on this
part, we're going to cover the online transport. We're going to cover pretty
much those storage gateway site.
So for online transport, there's a couple ways you can do in order to move data
from your on-premises environment to the cloud. When we're talking about
online transport, it relies over to internet connectivity or bandwidth that you
might have on your on-premises environment to allow you connection from
your location to the cloud. So there's three options you can use.

You can use VPN over internet. You have a VPN connectivity from your on-
premises to OCI, and then you can send data through the VPN connection. You
can also use FastConnect, which allows you to give a dedicated link from your
location to OCI. It goes to the high speed. You can get from one gigabit per
second [INAUDIBLE] 10 gigabits per second on a network.

Another option to use is a Storage Gateway. So a Storage Gateway is considered

online transport, because the Storage Gateway is going to use your internet
connectivity to connect to your on-premises environment to an object storage,
and then allow you to copy data from your on-premises environment to that
Storage Gateway. And then synchronize the data to the Object Storage in OCI.

So what exactly is Storage Gateway. We're going to cover Storage Gateway

here. So Storage Gateway is an appliance that you can install in your on-premises
environment, and then have your applications connecting to that appliance, and
then sending data over to NFS file system.

So this appliance is a virtual machine. You can install that on any virtual machine
you might have inside of your on-premises environment. This is a Docker
container. You can easily install that on top of Linux environment, and then
bring that up on your environment.
So then the Storage Gateway will have connectivity to the Object Storage, which
is the OCI Object Storage that's up and running on your account. So that makes
things easier to copy it over. So if your application is copying the data inside of
the Object Storage through an NFSv4 the Storage Gateway recognizes when the
data landed on a specific mounting point. And then we will start copying the
data from that mount point to the Object Storage.

So what's the main use case for the Storage Gateway? So the main use case is
the two of them is the hybrid cloud. You have on-premise supplication using the
storage in OCI. And there's a few hybrid environments that we can walk
through, and cover some of those details here.

Another one is one-time data migration. So if you just need to do migration of

the data from your on-premises to OCI, you can take that over internet
connectivity. So you might want to use Storage Gateway just to start copying the
data to that NFS mounting point, and then allow that to start to synchronize over
to the OCI object storage.

How Storage Gateway Works

Storage Gateway is installed in an Oracle Cloud Infrastructure compute instance or as a
Linux Docker instance on one or more hosts in your on-premises data center.
Applications store and retrieve objects from Oracle Cloud Infrastructure Object Storage
through file systems that you create in Storage Gateway.
Storage Gateway exposes an NFS mount point that can be mounted to any host that
supports an NFSv4 client. The Storage Gateway mount point maps to an Object Storage
bucket.

There is file to object transparency between Storage Gateway and Object Storage:
So those are the two main use cases. But as you can see on the slide, there's
other things we're going to talk to, like cloud tiering, backups, archives. So I'm
going to cover some of those [INAUDIBLE].

So this is an option that you can use for hybrid cloud-- what we call tiering using
Cloud Sync feature. So that's going to give you the ability to connect to any local
NAS that you have on your on premises environment. And Cloud Sync feature
we'll keep monitoring and watching any change on that specific file system or
that specific folder.

And then Storage Gateway will recognize that and start copying the data from
your NAS to a Storage Gateway, and then from there is going to send that over
to the Object Storage. So it's a really cool feature if you have multiple NAS
storages around your on-premises environment. Or if there is a machine where
you want to-- every time some application copies the data of that specific file
system, you want to Cloud Sync to detect that, and then you start copying the
data from that NAS to the Storage Gateway.

And then later on, that's going to be copied over to the Object Storage. So you
can run multiple sync jobs in parallel. You can have multiple sync jobs watching
the storage of your NAS, and then leverage that feature to start copying the
data to OCI.

Another option is using for content repositories. So you can just have the Storage
Gateway on your own site. And then all the data that's actually put onto the
Storage Gateway, we send it over to the Object Storage. And then from there,
you can access using pre-authenticated URL for all those files. So if you're just
looking for a host, some files inside of your on-premises environment, like files--
or even reports or images, and you want to create it as a content repository,
that's a great use case to use Object Storage and Storage Gateway for.

Another one is backup copies. So usually, traditionally, like on-premises

environment, they use this 3-2-1 strategy for backups. What exactly that is.

So at least three copies of the data, that's one of the requirements. And then
you have to use two types of different storage, and at least one copy has to be
put off-site of your location. So you can use cloud environment for that.
You have three copies. You can have one copy on your on-premises
environment. And two of the copies can be placed on the cloud environment.
And use two different types of storage.

So cloud storage or Object Storage or Archive Storage counts as a different type

of storage for them. And then one of the copies will be placed off-site. You can
even put it on different regions inside of OCI. So you might have copies across
regions on your cloud environment.

So 3-2-1 strategies use tapes vaulted on-premises. Sometimes, it is a chip, but

actually keep the vaulted remotely. That's where the cost will go up.

So if you use cloud storage for that, it's cheap. That's a better way to keep your
data secure. There's all the encryption for the Object Storage, too-- the REST
encryption that we provide to you. So you have all that data, your backups, and
all the data you're putting over there on a security way.

Another option is using for cold disaster recovery. So if you have a standby, you
might want to create a standby environment in a cloud-- in OCI in this case. And
then if there is something wrong, the Storage Gateway is copying your data
from your on-premises to the Object Storage. And then you can easily access
that data from the Object Storage to recreate your environment in a cloud
environment. So it's easy to use that for cold disaster recovery.

So here's some of the options for tuning and pinning for frequently-used data.
So as you know, Storage Gateway will synchronize the data from the Storage
Gateway appliance, all the way to OCI Object Storage. So if your application or
user is accessing files, and need to retrieve some of the files, the file got
retrieved from the OCI Object Storage to the Storage Gateway.

If these files are a frequently retrieved type of data, storage data will recognize
that and cache that file locally. So that way, you don't have to always request
the data from the Object Storage to be placed in the Storage Gateway to give
you access to your application. So that's going to have a cache locally inside of
this Storage Gateway.

And you could also do some pin on some files. So if you have a file that you
know your application will access every time-- it's going to be frequently
accessed by applications and users, you can pin those files. And then they'll have
a copy, always have a copy, locally inside of this Storage Gateway, so the
application doesn't have to retrieve the data from the OCI Object Storage to
access that. So those are really cool options for access will be sending over to
the cloud. And then if your application is to retrieve and get access to those files,
so you don't have to wait-- traverse all the bandwidth, internet connectivity, to
get access to those files, as you have a copy locally inside of the Storage
Gateway.

For Storage Gateway performance-- and that's one thing you need to
understand. So Storage Gateway is going to use your internet connectivity. It
depends on your bandwidth. Then it can sustain some of the uploads and
downloads speed here.

So as you can see on this slide, we have 10 gigabits beats per second on the
FastConnect. And then if you have files that range from 10 gigabytes to 50
gigabytes, the upload speed is going to be from 450 to 500 megabytes per
second, and download is going to be 700 to 750 megabytes per second. So you
have to understand that. It depends on your internet connectivity, how you
connected from your on-premises to OCI. And then the size of the file is really
important to you. So your Storage Gateway will perform better if you have bigger
files than actually putting a lot of small files inside of the storage.

So here's some of the limits on the Storage Gateway resources. You have to
understand that the Storage Gateway doesn't exceed 10 file systems per Storage
Gateway. If we need more than 10, the recommendation is to spin up another
Storage Gateway, a second Storage Gateway, to bypass this limit.

Another one is the local storage for file system cache, which is important to
understand, as you're going to cache someone files locally on the Storage
Gateway. We recommended that you have 500 gigabytes on the space for your
Storage Gateway installation. Then just support the file assistant cache.

The other one is the limit of number for files that you're going to put [? into the
?] cache. So the amount is 20,000. So we can have 20,000 files on the cache. So
just keep aware of that number as well.

And of course, to improve all the performance, like I mentioned in the slide
before, try to compress the files, zip the files. Even if they're small, just combine
them and zip them, so it would be better. It reduces the number of objects on
the namespace, so it's easy for Storage Gateway to synchronize data from the
Storage Gateway to the Object Storage.

Here's some of the Storage Gateway FAQ questions, and some of the common
questions that customers will ask when they're using Storage Gateway. And one
common question is if you can use Storage Gateway as a general purpose
Network Attached Storage server. And the answer is no.
It's not meant to be a NAS inside of our environment. It's actually just synchronize
the data from your NAS environment to your Storage Gateway, and then send it
over to the Object Storage. It's not meant to be a NAS storage server per se.

And how much does Storage Gateway cost? So it's free with the OCI subscription.
So if you have an OCI subscription, Storage Gateway is free. You can just
download the Docker file and install that on the Linux machine, and then bring
it up to Storage Gateway as well.

[? Another ?] question is, do I need to use Object Storage REST APIs to use the
Storage Gateway? No, you don't have to use that. Storage Gateway will perform
all the tasks for you behind the scenes. So all you have to understand is how you
mount those Storage Gateway as an NFS file system.

And then all the communication from Storage Gateway to Object Storage will be
executed to the REST API. But the Storage Gateway will translate that for you.
There's more information on FAQ. If you click on the link, you're going to find all
the information there.

So let me do a quick Storage Gateway demo and show you how you can create
a file system on the Storage Gateway map to an OCI a storage bucket, and then
how you can map to your VM. So this is my OCI account. I'm logging in my OCI.
And then I have a Storage Gateway installed in my OCI account that's going to
copy files from my virtual machines to the Storage Gateway, and then sending
that over to the OCI Object Storage.

So if you go on the Compute Instances, I do have a VM, which is the Oracle

Linux VM. And then after installing Oracle Linux, I downloaded the Docker
container for Storage Gateway. And then I installed a Storage Gateway to here
on that VM.

So once you install-- once you go through a command line and install the
Storage Gateway using the Docker container, then you will be able to access a
web page. And that web page you're going to walk to through to set up the
Storage Gateway to talk to your Object Storage. So I have that configured here.

I set up this Storage Gateway web page. And then I'm accessing through a local
host here on these [? port. ?] And I'm going to log in with my username and
password, which is the [? admin. ?]
Then once I do it, this is the home page of the Storage Gateway. So I do have
two file assistants that I created here already. I have the FSDATA and the SYNC
one. Notice the url of storage gateway

But if you want to create a new file system, all you have to do is click Create File
System. And you're going to give a name for the file system-- for example, TEST-
FS. And you can select-- if you want that file system to be connected to a
standard OCI Object Storage or archive OCI object storage.

So it depends on your use case, or what you're trying to achieve here. So if you
want to just archive data, you can connect, actually, Archive bucket. If you want
to do just extender Object Storage, you can select the first one.

Then you have to enter the API Endpoint of the OCI Object Storage. If you don't
know, that's fine. If you click here on API Endpoints, that's going to redirect you
to the documentation of the Object Storage.
And then it's going to provide you the Storage Gateway API Endpoint right here.
So it depends on your region. And then you can get the region you want to
create your Object Storage, and then use all one of those API endpoints there.

So once you do it-- let's just pick one here. For example, let's do Phoenix 1. I'm
just going to copy that back here.

Once I entered the API Endpoint, it's going to ask me to enter the Compartment
OCID, the Tenant OCID, the User OCID, the Public Key's Fingerprint, and the
Private Key. So this is actually how the Storage Gateway will authenticate to your
account. You're going to specify the compartment where the OCI bucket will be
created, then the Tenant OCID. The User OCID [INAUDIBLE] make the
authentication.

And then you have to create the fingerprint here-- provide the public fingerprint
here on that option. That's going to come up with the Private Key that you're
going to generate as well. So if you created a Private Key already for your
dynamic group, or for your OCI CLI, that's exactly the same steps that you're
going to use here.

So once you do that, there's a couple of advanced options for file system
configuration. So you can define who can actually access the NFS mounting
point. So you might have-- I want it just specific to a specific subnet address, or
I'm going to give access to everyone.
Some of the export options as well, Concurrent Uploads and Sync Policy. So this
is actually a couple things you can do to make the performance a little bit better
on this Storage Gateway as well. So once you have that, you save. And once you
save, then that is going to start creating the file system.

So once you do that, what's going to happen is, I'm going to just go back to my
FSDATA. You're going to have information like that where you have the mount
command that you can use to start mounting the NFS file system on your local
environment. So let's just show real quick how that works.

So I have here my terminal, and I have a dev instance that I'm up and running
here. And on that dev instance, I have a mounting point call SGW DATA. So
there's no files here. So I'm going to mount-- let's just get the command here
real quick.
Yeah, so I'm going to mount the NFS file system. So 172.16.2.11 is the IP
address of my Storage Gateway. And I do have the FSDATA. This is the file
system name that I created here on Storage Gateway. And this is the mount
point that I want to use-- so SGW DATA.

So before I do the mount, let me just go back here to the OCI account and show
you the Object Storage. So there is an Object Storage associated to this FSDATA
that I created on the Storage Gateway, which is that bucket here. And then you
can see, that bucket, there is one file saying the version of my Storage Gateway.
So this bucket is associated to the Storage Gateway. So every file I've copied
over will show up here on the bucket.
So let's do a quick test. Let's just mount this here. Then now, I go to the SGW
DATA. So if I create a file-- let's say touch flavio.txt. And then we're going to see
if that file will show up here in a minute.

So let's just go back here in the matrix. Just go back to the objects. And there
you go. So you can see, we've already synchronized the file from Storage
Gateway to my Object Storage. So I can see the file here.

Of course, this is a small file. There's nothing on it. But once you start copying
directories or zip files over to the mount point, all the data will start to
synchronize over there.

So if you go back to the Storage Gateway page, you can see some activity
information. So that will show you the activity of synchronized files here. It is
just a new one. I don't have any completed uploads. Just refresh and getting the
data from there.

You can change some of the settings as well. So after the fact. So if you want to
change the compartment or change the Object Storage, you can do that too. So
the you have to do is to disconnect the file. And then there's options to change,
then, after you disconnect.

So this is how this Storage Gateway works. Pretty straightforward. So if you

want to use the Cloud Sync option, which has synchronized the data from my
specific NAS-- and then once that happens, you start copying data over to the
OCI Object Storage, [INAUDIBLE] Cloud Sync can start creating the job.

And then once you do it, you provide the Source and the Target Path. So where
exactly is the Source and the Target. And then Storage Gateway will monitor
that, and then start to synchronize data from one location to another one.

So this is a quick demo of how Storage Gateway works. And I hope that helps
you to actually start moving the data from your location to OCI. This is one of
the options to use to start moving your data. Thanks for watching.