Migration Flashcards

1
Q

6Rs - Rehosting - lift and shift

A
  • Migrate entire VM
    • AWS VM import/export
    • AWS Server Migration Service
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

6Rs - Replatforming

A
  • Migrate your DB to RDS

- Migrate java app to beanstalk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

6Rs - Repurchase

A
  • Move to different produce while moving to the cloud
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

6Rs - Refactoring & Rearchitecture

A
  • Decoupling using SQS/SNS
  • Move to serverless
  • Use S3 for storing files
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

6Rs - Retire stuff not needed

A
  • Helps reducing surface attack
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

6Rs - Retain

A
  • Do nothing to migrate to cloud
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

AWS Storage Gateway

A
  • Bridge between on-prem and cloud data in S3

- Helps with disaster recovery, backup & restore, tiered storage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

AWS Storage Gateway File Gateway

A
  • You get a FG appliance - VM, that is a bridge between NFS mount and S3 bucket
  • Cached, saves trips to S3 and costs
  • Can be accessed using both NFS and SMB
  • Requires IAM access to S3 Service
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

File Gateway Use cases

A
  • FG mounts for on-prem and EC2 to facilitate migration
  • Second read-only mount, low latency get files
  • Files in FG can go through Lifecycle policies, cost savings
  • Can have file version control, if S3 versioning enabled
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

File Gateway - WORM

A
  • Object lock

- If there are changes, File Gateway creates a new version without affecting original locked or prior versions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Volume Gateway

A
  • iSCSI - backed by S3
  • Cached Volumes: low latency access for most recent on-premise, full data on S3 - 1TB per volume
  • Stored Volume: Entire dataset is on premise, scheduled backups to S3 - 0.5TB per volume
  • To access data create EBS snapshots from volumes and restore a EBS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Tape Gateway

A
  • To access data need to restore entire tape

- Virtual Table Library protocol backed by S3 Glacier

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Snowball Edge

A

For compute on the data:

  • Supports EC2 AMI
  • Lambda
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

DB Migration Service

A
  • Quick, secure, resilient, self healing
  • Source DB remains available during migration
  • Oracle to Oracle
    • Oracle to MySQL (Schema Conv Tool)
    • Oracle to Redshift (SCT)
  • Continuous Data Replication using CDC (Streams changes)
  • Requires EC2 to perform replication tasks
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

DBMS Network

A
  • VPC Peering, VPN (site-2-site, software), DXConnect
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

DBMS Blobs

A

Only if Blobs have primary key

17
Q

Snowball + DMS

A
  • Using SCT download to Snowball Edge
  • Ship Edge device to AWS
  • Load data to S3
  • DMS to replicate from S3 to target DB
  • CTC to apply deltas since snowball got shipped
18
Q

AWS Application Discovery Service

A
  • Gather info about on-prem data centers
  • Agentless: open virtual appliance pkg on VMware host
    • OS agnostic
  • Agent: system configuration, network connections
  • Results expored in CSV or viewed in AWS Migration Hub
  • Can query data using Athena
19
Q
  • Server Migration Service
A
  • Rehosting, entire VM, improvement over EC2 import/export

- One time migrations or replication of live on-prem servers every interval

20
Q

Disaster Recover

A
  • RPO - Data Loss.

- RTO - Downtime

21
Q

Backup and Restore

A

High RPO and High RTO

- Regular backups lowers RPO

22
Q

Pilot Light

A
  • Still cost effective, for critical systems

- Lower RPO and Lower RTO

23
Q

Warm Standby

A
  • Full system running, but at minimum size
  • Upon disaster can scale to production load
  • More costly
  • Lower RPO and Lower RTO
24
Q

Hot Hot Mutli Side

A
  • Most expensive

- Lowest RTO and RPO

25
Q

EFS Source of Data

A

EFS cannot use an S3 bucket as a source of data

26
Q

Snowball sizes

A

Snowball has two types of device model: 50 TB and 80 TB, you can only store a total of 42 TB and 72 TB respectively based on their usable capacity limits. You have to use AWS Snowball Edge instead.

27
Q

The maximum size of a single file that can be delivered through Amazon CloudFront is

A

20 GB