How to Map CloudBerry Drive for Windows and macOSCloudBerry Drive (now under the MSP360 brand) lets you mount cloud storage as a local drive on your computer so you can work with files using familiar apps without syncing everything locally. This guide walks through mapping CloudBerry Drive on both Windows and macOS, covers common configuration options, troubleshooting, performance tips, and security considerations.
What CloudBerry Drive does and when to use it
CloudBerry Drive creates a virtual drive letter (Windows) or mount point (macOS) that connects to cloud storage providers (Amazon S3, Backblaze B2, Azure, Google Cloud, Wasabi, and many others). Instead of syncing full copies, it streams data on demand or caches only requested files, saving local disk space while providing near-native file access for editors, scripts, and backup tools.
Use it when you want:
- Access to large cloud repositories without full sync.
- A simple way to let legacy applications read/write to cloud storage via standard file paths.
- Integration of cloud storage into workflows (e.g., backup, media editing) that expect a local drive.
Before you start — prerequisites
- A valid account with your chosen cloud storage provider and necessary credentials (access keys, secret keys, or OAuth tokens).
- CloudBerry Drive (MSP360 Drive) installed. There are free and paid editions — check the features you need (e.g., encryption, cache size limits).
- Windows: Administrator rights to install drivers and create virtual drives.
- macOS: Appropriate permissions; recent macOS versions may require additional approvals in Security & Privacy to allow kernel extensions or file system drivers (depending on version and product updates).
Mapping CloudBerry Drive on Windows
- Download and install
- Download the latest CloudBerry Drive / MSP360 Drive installer for Windows from the vendor website.
- Run the installer as Administrator and follow prompts. Approve any driver or filesystem requests.
- Launch and add a storage account
- Open CloudBerry Drive.
- Click “Tools” or “Storage Accounts” (interface labels may vary by version), then “Add New Account.”
- Select your cloud provider and enter required credentials (access key/secret key, application-specific token, or OAuth sign-in).
- Test the connection to confirm credentials are valid.
- Create a new drive mapping
- In the main window, click “Create New Drive” or the “+” button.
- Choose drive letter (e.g., Z:). Pick a descriptive display name.
- Select the storage account and the remote bucket/container/folder to mount.
- Choose access mode:
- Read/Write — full file operations.
- Read-Only — prevents accidental changes.
- Configure caching:
- Enable local cache for frequently used files. Set cache size and cache location.
- Choose cache behavior (aggressive vs. minimal caching) depending on disk space and performance needs.
- Optional: enable server-side or client-side encryption. For client-side encryption, set and securely store the passphrase — losing it will make data unrecoverable.
- Advanced settings (optional)
- Chunk size for reads/writes — increasing can improve throughput with large files.
- Concurrent connections — raising this can speed up parallel operations but may hit provider API limits.
- File locking and NTFS compatibility settings — useful for apps that expect specific file attributes.
- Finish and mount
- Click “Create” or “Mount.” You should see the new drive letter in File Explorer.
- Test by opening, creating, and saving files. Monitor transfer behavior to confirm streaming or caching is working as expected.
Mapping CloudBerry Drive on macOS
Note: Product behavior and driver requirements may differ on macOS. Recent macOS releases favor FUSE/OSXFUSE or system APIs; follow product docs for the best compatibility.
- Download and install
- Download the macOS installer from MSP360.
- Run the installer; macOS may require you to allow system extensions in System Preferences > Security & Privacy. Follow on-screen prompts and restart if requested.
- Add cloud storage account
- Open CloudBerry Drive for macOS.
- Click “Add Storage Account” and choose the provider.
- Authenticate (enter keys or perform OAuth sign-in). Test the connection.
- Create a new mount
- Click “New Drive” or “Mount New Drive.”
- Choose mount point (e.g., /Volumes/CloudBerryDrive or a custom folder). Give it a name.
- Select the remote bucket or container to mount and pick access rights.
- Configure caching:
- Choose local cache folder (on an internal SSD if possible).
- Set cache size and eviction policy.
- Optional encryption settings — enable client-side encryption if desired and store passphrases securely.
- Mount and test
- Click “Mount.” The drive should appear in Finder under Locations or the specified mount path.
- Test file operations (open, save, rename) with typical apps.
Common configuration tips
- Cache location: place cache on a fast local drive (SSD) for better responsiveness, especially with large files.
- Cache size: set a reasonable limit to prevent filling local disk. For example, 10–20% of free space or a fixed size (e.g., 10–50 GB) depending on use.
- Chunk size: larger chunks (8–64 MB) reduce overhead for large file transfers; smaller chunks help with many small files.
- Parallel connections: adjust to balance speed and API throttling. Start with 4–8 concurrent connections.
- File system semantics: enable appropriate compatibility settings if apps require file locking, attributes, or symlinks.
Performance considerations
- Latency: since files stream from the cloud, expect higher latency than local disks. Cache frequently used files to mitigate.
- Bandwidth: upload/download speed depends on your internet connection and cloud provider region.
- Large files: for media editing, ensure cache is large enough or prefetch files before editing.
- Background sync: some operations (like metadata listing) can be I/O intensive; schedule heavy tasks during off-hours when possible.
Security and privacy
- Use TLS/HTTPS for provider connections — this is standard for supported providers.
- Client-side encryption prevents the provider from reading your data; however, key management is your responsibility.
- Store access keys and passphrases securely (password manager or secure vault).
- Use least-privilege IAM credentials: create keys limited to required buckets and actions.
- Enable provider-side features like server-side encryption, versioning, and MFA for management consoles.
Troubleshooting
- Drive won’t mount:
- Windows: re-run installer as Admin; check driver signature enforcement or re-install the filesystem driver.
- macOS: allow system extensions in Security & Privacy, install/update FUSE if required, and restart.
- Slow performance:
- Increase cache size, use SSD, increase chunk size, or raise concurrent connections.
- Check network speed and provider region latency.
- File errors or corruption:
- Verify cache integrity, disable aggressive caching temporarily, and test with a different file.
- Ensure proper shutdown/unmount before disconnecting network or sleep.
- Authentication failures:
- Re-enter credentials, verify time sync on your machine, and confirm provider IAM permissions.
Example workflows
- Video editor: prefetch large media to local cache before editing, set large chunk sizes, and use an SSD cache.
- Remote backups: map the drive to point backup software at cloud storage without modifying backup app settings.
- Shared team folder: mount a shared bucket with read/write permissions and enable versioning on the provider to protect against accidental deletes.
Alternatives and when not to use CloudBerry Drive
- Use native sync clients when offline access to all files is required.
- Use S3/Cloud-native tools or rclone when you need scriptable CLI access or advanced sync rules.
- For extreme performance (low-latency, high IOPS), cloud-mounted drives may not match local NAS or SAN.
Final checklist before production use
- Verify credentials and minimal IAM permissions.
- Configure cache size and location.
- Test with typical file types and application workflows.
- Enable encryption and provider protections as needed.
- Document mount points and restart/mount procedures for other users or admins.
Leave a Reply