Docs Menu
Docs Home
/ /

Direct from S3 Restore in Ops Manager

Direct from S3 Restore allows backup agents to download snapshot data directly from your S3 snapshot store instead of streaming data through Ops Manager application servers. This feature provides the following benefits:

  • Reduces load on Ops Manager during large restore operations

  • Improves restore times for deployments backed up to S3

  • Uses pre-signed URLs so backup agents do not need S3 credentials

중요

이 기능 사용하려면 Ops Manager 8.0.19 이상이 필요합니다.

Direct from S3 Restore supports the following configurations:

  • Backup type: Continuous or scheduled backups that use an S3 snapshot store (managed or imported)

  • Restore type: Snapshot restores where the delivery method is Automation Agent (restores into a managed deployment)

Direct from S3 Restore does not apply to the following scenarios:

  • Manual download restores (HTTP download of snapshot data), which continue to stream data through Ops Manager

  • Backups that use filesystem or MongoDB blockstore snapshot stores

  • Ad-hoc mongorestore workflows that run outside Ops Manager

If any of these scenarios are critical for your environment, continue using the standard restore path for those workflows.

After you enable Direct from S3 Restore:

  • Ops Manager plans the restore as usual.

  • Ops Manager generates pre-signed S3 URLs for each snapshot block using its configured S3 credentials.

  • Ops Manager instructs the backup agent to fetch snapshot data directly from S3 using those pre-signed URLs.

  • The backup agent downloads, decompresses, and writes snapshot data to disk.

Backup agents do not need S3 credentials. Ops Manager manages all S3 authentication through pre-signed URLs.

참고

Direct from S3 Restore applies only to snapshot data. Oplog handling follows the existing flow.

Before you enable Direct from S3 Restore, verify the following requirements.

Each backup agent host that performs restores must be able to:

  • Resolve the DNS name of the S3 or S3-compatible endpoint

  • Establish outbound HTTPS connections to that endpoint

  • Download data using S3 pre-signed URLs that Ops Manager generates

Backup agents do not require S3 access keys or IAM roles. Ops Manager generates pre-signed URLs using the S3 credentials configured for the snapshot store.

Direct from S3 Restore works with:

  • Managed S3 snapshot stores configured in Ops Manager

  • Imported S3 snapshot stores on Ops Manager 8.0.19 or later

To configure Direct from S3 Restore, complete the following tasks:

  1. Enable the system-level feature flag.

  2. Enable Direct from S3 Restore on an S3 snapshot store.

1

Set the mms.featureFlag.backup.directS3Restore property to enabled in the Ops Manager configuration.

1

In Ops Manager, click Admin, Backup, Snapshot Storage.

2

Find the S3 blockstore where you want to enable Direct from S3 Restore.

3

In the store configuration, select the Direct from S3 Restore option.

4

Click Save to apply the configuration.

중요

Enabling this option does not change existing restore jobs. New restore jobs can use Direct from S3 Restore only if the snapshot store has the option enabled when you create the job.

After you enable the feature, use the standard restore workflow. The data path changes automatically.

1

In your project, go to Continuous Backup (or Backup, Continuous).

2

Locate the deployment and snapshot you want to restore. The snapshot must be stored in an S3 store with Direct from S3 Restore enabled.

3

Click Restore to open the Restore Wizard.

4

Select a snapshot. Direct from S3 Restore applies only to snapshot data.

5

On the delivery method step, click Automation Agent to restore into a managed deployment.

Do not select Download. Download restores continue to stream data from Ops Manager and do not use Direct from S3 Restore.

6

Complete the remaining steps and submit the restore job.

Consider the following performance characteristics:

  • Ops Manager load: Restores generate less network and CPU load on Ops Manager application servers.

  • Agent hosts: Restore throughput depends on CPU, disk I/O, and network capacity on the hosts that run backup agents.

  • Network path: Restore throughput depends on the network path from the backup agent to S3, not from Ops Manager to S3. For large clusters, confirm that your S3 endpoint, VPC endpoint, or proxy can handle the expected concurrency.

Direct from S3 Restore uses the following permissions model:

  • Ops Manager permissions: Ops Manager backup application servers require S3 read access (and list access where required) to the buckets and prefixes configured on your S3 snapshot stores. Configure this access through the IAM role or access keys you specify for those stores in Ops Manager.

  • Backup agent permissions: Backup agents do not have S3 credentials. Ops Manager generates pre-signed S3 URLs for each snapshot block, and agents download blocks directly from S3 using those URLs.

  • Least privilege: Restrict the IAM role or access keys that Ops Manager uses to only the buckets and prefixes required for backup and restore.

  • Immutability: If you use S3 Object Lock, Direct from S3 Restore reads from immutable objects using pre-signed URLs. The feature does not bypass retention or delete protections.

If you restore from imported S3 snapshot stores, such as immutable backup buckets, verify the following:

  • You run Ops Manager 8.0.19 or later, which includes Direct from S3 Restore support for imported snapshots.

  • You configured the imported snapshot store correctly under Admin, Backup, Snapshot Stores.

  • The S3 credentials configured for that store in Ops Manager have read access to the imported bucket and prefix.

  • Backup agents on target hosts have network connectivity to the S3 endpoint. Agents use pre-signed URLs that Ops Manager generates and do not require additional IAM roles or keys.

돌아가기

단일 데이터베이스 또는 컬렉션

이 페이지의 내용