New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
IDrive E2 account review: recovery and migration planning
Hi,
I run a public-facing service that uses IDrive E2 as an S3-compatible object-storage backend. The storage account has been placed under a provider review and normal access is temporarily unavailable. I have completed the requested remediation steps and am working through the provider’s formal support channel.
I am not seeking a workaround, a way around the provider’s controls, or discussion of the underlying review. I am looking for operational advice for a clean and responsible recovery plan:
- While an S3 account is unavailable, which non-sensitive evidence or state should I preserve (rclone configuration, locally available object inventories, deployment configuration, and application logs)?
- After legitimate access is restored, what is a sensible way to inventory a large object store and replicate it to a second S3-compatible provider with minimal risk?
- For services that accept public uploads, what architectural patterns have you used to avoid an account-level vendor restriction affecting all normal users?
- Has anyone dealt with a legitimate IDrive E2 account-review escalation and found a path beyond first-line support?
I will not share credentials, bucket names, URLs, or incident-specific material. The goal is to improve resilience and plan a proper migration and recovery path—not to turn this into a complaint thread.
Thanks.
This discussion has been closed.
Comments
https://docs.aws.amazon.com/cli/latest/reference/s3/sync.html
be a big enough buyer and have an account rep to handle escalation.
Backblaze B2 and Mega S4 are both solid options.