in this video you'll see how you can get
started with aws elastic disaster
recovery or aws drs
with this service you can configure
replication servers and launch drill and
recovery instances that help to minimize
downtime and protect against data loss
in the event of operation disruption
to get started let's navigate to aws
elastic disaster recovery
as the admin user of the aws account
we'll begin by reviewing the default
replication settings
the replication server configuration
establishes the staging area where our
data will be replicated
we can define the staging area subnet
and the amazon elastic compute cloud or
amazon ec2 instance type to use for the
replication servers
in the volumes section we can specify
our preferences for the amazon elastic
block store or amazon ebs volume and
encryption types
aws elastic disaster recovery creates
its own security groups but we can apply
additional groups if necessary
we can apply data routing and throttling
controls and revise the point in time
policy which by default retains
snapshots for seven days
we can also apply tags
we'll save the settings which will
initiate the service and create the
required iam permissions
let's return to the source servers page
next we'll install the aws replication
agent on our new source server
using linux we'll apply the code to
download the agent from an amazon simple
storage service or amazon s3 bucket
then we'll run the installation script
we'll supply the name of the aws region
we want to replicate to which is the one
where our account is located
we'll also provide the aws access key id
and secret access key
now we can choose which disks to
replicate we'll replicate all of them
as you can see the new source server has
already appeared and is initializing
let's close the linux window and view
the new elastic disaster recovery server
on the recovery dashboard tab we can
review the progress of the replication
sync
the server info tab contains information
about the server including its ip
address identification hints hardware
components and operating system
we can also manage and edit any tags
we've assigned and review the disk
settings
from the replication settings tab we can
review and if needed adjust the default
settings for this specific server
and in the launch settings tab we can
review how elastic disaster recovery
will replicate the server in the event
of a manufactured drill or actual
disaster
we can edit the server's ec2 launch
template to create a new template
version
for instance we can choose a different
instance type and which key pairs to be
granted access
we can revise the basic network settings
including the subnet and security groups
and enter advanced network
configurations such as an extra network
interface
we can also configure additional storage
and add resource tags
there are many more advanced details we
could select to ensure the server is
functional for our needs
we can even utilize user data for this
machine to automatically run scripts
when it fails over
let's move forward with the default
settings and create the template version
now that we've created a new template we
need to save and apply the latest
version to our server
let's select the templates hyperlink
we'll take the action to set a default
version
then we'll choose the latest version
number and set it as the default
now that our server is set up we can
return to the elastic disaster recovery
console and initiate a drill
this is an essential step to verify that
the server functions properly before a
real-life recovery is necessary
we'll choose the server initiate a
recovery job and then initiate a drill
here we can select from several recently
captured point in time snapshots we'll
use the most recent data available note
that performing a drill or failover does
not affect the source machine or its
replication to the staging area let's
initiate the drill
the server's last recovery result is now
pending
we can monitor the drill's progress more
closely on the recovery job history page
here's the job that we just started
the recovery drill has been successfully
completed we can view a log of the job
events and calculate the recovery time
let's go to the recovery instances
page we'll select the instance we just
ran
let's view the instance in amazon ec2
we can see here that the instance is in
a running state
let's go back to the elastic disaster
recovery console
if this had been an actual disaster we'd
now start the fail back process to our
source machine
in this case we'll terminate the drill
instance
this is a best practice for avoiding
service usage and fees and does not
disrupt the source replication
we'll select the instance and first take
the action to disconnect from aws
now we can delete the recovery instance
you've just seen how you can get started
with aws elastic disaster recovery
you can learn more about this topic in
the description and links for this video
thanks for watching now it's your turn
to try