OCI Foundations - Storage: Difference between revisions

From Smithnet Wiki
Jump to navigation Jump to search
m (5 revisions imported)
 
(2 intermediate revisions by the same user not shown)
Line 3: Line 3:


Persistent Storage / Non-Persistent Storage
Persistent Storage / Non-Persistent Storage
Local NVMe attached to an instance
* Local NVMe attached to an instance
Copied to a NAS -> Block Volume
* Copied to a NAS -> Block Volume
File Storage -> 2 Compute Instances can share files/directories
* File Storage -> 2 Compute Instances can share files/directories
Object Storage -> Photos, Videos, Log files typically accesible via HTTP
* Object Storage -> Photos, Videos, Log files typically accesible via HTTP


Data Migration Services:
Data Migration Services:
Line 115: Line 115:


== File Storage ==
== File Storage ==
Hierarchical collection ot documents organised into named directories.
Distributed file systems, using NFS or SMB.
OCI File Storage Service:
* Shared storage for compute instances
* Support NFS v3
* Data protection: snapshots
* Encrypted at rest and in-transit

Latest revision as of 04:53, 8 May 2024

Introduction

Persistent Storage / Non-Persistent Storage

  • Local NVMe attached to an instance
  • Copied to a NAS -> Block Volume
  • File Storage -> 2 Compute Instances can share files/directories
  • Object Storage -> Photos, Videos, Log files typically accesible via HTTP

Data Migration Services:

  • Data Transfer Disk: send disk to Oracle
  • Data Transfer Appliance: send larger system
  • Storage Gateway: on-premise

Durable: multiple copies

Object Storage

  • Ideal for unstructred/semi-structured data (photos, logs, etc)
  • Regional, public service
  • Objects: key/value pair + metadata
  • Flat heireachy, unique name in namespace
  • Namespace must have globally unique name
  • Namespace -> Bucket -> Object

Standard Tier (hot):

  • Instantaneous retrieval
  • Fast, immediate access
  • Most recent copy

Infrequent Access Tier (cool):

  • Min storage for 31 days
  • Retrieval fees
  • Lower storage cost
  • eg for backups

Archive Storage Tier (cold):

  • Seldom accessed
  • Min retention requirement of 90 days
  • Restore time: 1 hr
  • Downloaded to standard tier in 24 hours
  • remote tape access

Cannot change tier once bucket is created. Private or Public access. Pre-authenticated requests:

  • Bucket or Object level
  • Extra security token is used to access the resource
  • With a time expiry

Lifecycle Management, eg:

  • After 30 days standard -> archive
  • After 60 days, delete

Auto-tiering:

  • Can move between Stanard and Infrequent Access tier to reduce costs.

Auto-versioning

Encryption:

  • On by default
  • Can specify your own keys

Block Volume

Persistent and Durable Storage:

  • Create and attach disks
  • Detatch and delete disks
  • Keep data after the Compute Instance is deleted

Lower Cost tier:

  • Large sequential workloads
  • 2 IOPS/GB

Balanced tier:

  • Random IO
  • 60 IOPS/GB

Higher Performance Tier:

  • Most demanding IO workloads
  • 70 IOPS/GB

Ultra High Performance Tier:

  • eg database
  • 90-225 IOPS/GB

Auto-tune performance:

  • Reduced when volume is detatched
  • Reduces cost
  • Virtual Performance Units can be adjusted: min/max thresholds

Encrypted Block Volumes:

  • On by default
  • Can bring own key
  • At rest and in transit

Read/Write shareable:

  • Multiple VMs can access a Block Volume

Resizing:

  • Online, increase volume size

Replication:

  • From one region to another
  • Good for migration, disaster recovery

Volume Groups:

  • Group together
  • Can restore an entire VG from a backup

File Storage

Hierarchical collection ot documents organised into named directories. Distributed file systems, using NFS or SMB.

OCI File Storage Service:

  • Shared storage for compute instances
  • Support NFS v3
  • Data protection: snapshots
  • Encrypted at rest and in-transit