What Is IDrive e2?
IDrive e2 is S3-compatible object storage for backups, archives, and cloud application data. OurClone can connect IDrive e2 for transfer, sync, encrypted backup, and mount workflows.
Official website: https://www.idrive.com/e2/
- Good for S3-compatible backup storage with access-key setup.
- Useful for encrypted repositories and cross-cloud copies.
- Works with bucket paths and credentials created in the IDrive e2 console.
What OurClone Supports for IDrive e2
| Operation | How it works in OurClone |
|---|---|
| Sync | Keep a folder on IDrive e2 synchronized with another cloud storage account or a local folder. OurClone compares file changes and updates only what needs to change. |
| Transfer | Copy or move files between IDrive e2, your Mac, and other connected cloud providers. Transfers run through your local computer, so you stay in control of the data path. |
| Backup | Create an encrypted backup repository on IDrive e2, then save snapshots of local folders. Later snapshots are incremental, so unchanged files do not need to be uploaded again. |
| Mount | Mount IDrive e2 as a local directory in macOS or Windows, then browse and manage remote files from the operating system file manager. |
IDrive e2 Upload and Download Limits
These limits come from the storage provider or protocol, not from OurClone. OurClone still has to respect provider file-size caps, API quotas, bandwidth rules, account storage quota, and server-side throttling.
| Upload limits | Most S3-compatible providers use multipart upload rules. A common practical pattern is single-request uploads up to about 5 GB and multipart uploads for larger objects; the exact maximum depends on the provider. |
| Download limits | Downloads usually depend on object size, request rate, egress policy, and account bandwidth. The provider may throttle requests or charge for outbound traffic. |
| OurClone tip | IDrive e2 is S3-compatible, but provider-specific quotas may differ from AWS. Confirm bucket, object, and bandwidth limits in your IDrive e2 account before large OurClone jobs. |
How to Add IDrive e2 in OurClone
IDrive e2 connects through S3-compatible access keys in OurClone.
- Sign in to the IDrive e2 console.
- Create or locate an Access Key ID and Secret Access Key for the bucket you want OurClone to use.
- Use the endpoint and region details shown for your IDrive e2 bucket.
- Open OurClone, click Add Storage, select IDrive e2, enter the credentials, and connect.
Sync and Transfer Workflow
After IDrive e2 is connected, open the Migrate area in OurClone. Choose IDrive e2 as the source or destination, select the folders you want to work with, then choose the task mode.
- Copy duplicates files while keeping the source unchanged.
- Move transfers files and removes them from the source after completion.
- Sync keeps the destination aligned with the source folder.
Task progress is visible in the Task tab, including completed, skipped, and failed files.
Backup Workflow
For backups, first create a backup repository on IDrive e2. A repository needs a name, a storage path, and an encryption password. Keep this password safe because it is required for both future snapshots and restores.
- Open Backup and create or choose a repository on IDrive e2.
- Open the repository and click New Backup.
- Select local folders such as
~/Documents,~/Pictures, or a project folder. - Start the snapshot. The first run uploads the full selection; later runs are incremental.
- Use Restore from a backup record when you need to recover files to a local directory.
Mount IDrive e2 as a Local Folder
OurClone can mount IDrive e2 as a local operating-system directory. This is useful when you want to browse cloud files in Finder or File Explorer, open files from desktop apps, or copy files with the same habits you use for local folders.
- Open the mount area in OurClone and select your connected IDrive e2 account.
- Choose the remote path you want to expose locally.
- Pick a local mount point, then start the mount.
- When finished, unmount cleanly from OurClone before disconnecting your network or shutting down.
Best Practices for IDrive e2
- Use a clear folder naming convention such as
/ourclone-backups,/sync, or/archive. - Confirm that your IDrive e2 account has enough storage before running a large migration or backup.
- Run a small test sync or restore before relying on a new workflow for important files.
- For large first-time jobs, keep your computer awake and connected to a stable network.
- If authentication fails later, reconnect the account or refresh the token before restarting the task.