Deprecated: Function WP_Dependencies->add_data() was called with an argument that is deprecated since version 6.9.0! IE conditional comments are ignored by all supported browsers. in /data/dbchefs.com/wp-includes/functions.php on line 6131

DBChefs | 24×7 Global Database Management & Optimization

Backup Process

Backup Process

  1. Prepare the AWS Environment
  1. Create an S3 Bucket:
    • Log in to the AWS Console.
    • Navigate to S3 > Create bucket and follow the wizard.
    • Note the bucket name and region.
  2. Set Up Permissions:
    • Assign permissions to the bucket using an AWS IAM Role or User.
    • Attach a custom policy for necessary actions:

{ “Version”: “2012-10-17”, “Statement”: [ { “Effect”: “Allow”, “Action”: [ “s3:PutObject”, “s3:GetObject”, “s3:DeleteObject”, “s3:ListBucket” ], “Resource”: [ “arn:aws:s3:::your-bucket-name”, “arn:aws:s3:::your-bucket-name/*” ] } ] }

  1. Obtain AWS Credentials:
    • If using an IAM User, generate the Access Key ID and Secret Access Key.
  1. Configure Ops Manager
  1. Access Ops Manager:
    • Log in to your Ops Manager instance.
  2. Add the AWS S3 Blockstore:
    • Navigate to Admin > Backup > Blockstore Settings.
    • Click Add a Blockstore and select Amazon S3.
    • Enter the following:
      • S3 Bucket Name.
      • Bucket Region.
      • Path (if applicable).
      • Access Key ID and Secret Access Key.
    • Test the connection to ensure Ops Manager can access the bucket.
  3. Configure Backup Daemons:
    • Verify that the Backup Daemons are running on their designated servers.
    • Assign the S3 blockstore to these daemons.
  4. Set Snapshot Schedule:
    • For each MongoDB deployment to be backed up:
      • Enable Backup under Deployment > Backup.
      • Configure the snapshot schedule.
  1. Verify Backups
  • Monitor the Backup Jobs under Backup > Jobs in Ops Manager.
  • Check the S3 bucket for uploaded snapshots.

Restore Process

  1. Identify the Snapshot
  • In Ops Manager:
    • Navigate to Backup > Snapshots.
    • Locate the snapshot you want to restore.
    • Note the Snapshot ID and details.
  1. Initiate the Restore
  1. Select Restore Option:
    • Choose between:
      • Point-in-time Restore: To restore to a specific timestamp.
      • Snapshot Restore: To restore a specific snapshot.
  2. Configure Restore Target:
    • Select whether to restore to the original deployment or a new one.
    • Provide the target cluster or host details.
  3. Start the Restore:
    • Ops Manager will retrieve the snapshot from S3 and initiate the restoration.
  1. Verify the Restoration
  • Monitor the Restore Jobs under Backup > Jobs in Ops Manager.
  • Test the restored deployment to ensure data integrity and consistency.

Best Practices

  1. Encryption: Enable S3 bucket encryption (AWS KMS or S3-managed keys) to secure data.
  2. Versioning: Turn on bucket versioning for extra protection.
  3. Monitoring: Use AWS CloudWatch for bucket activity and Ops Manager logs for backup/restore status.
  4. Test Restores Regularly: Validate the process by performing periodic test restores to ensure readiness for disaster recovery.

These steps outline a robust process for backup and restore using MongoDB Ops Manager and AWS S3.

Scroll to Top