What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The dependable ZimaCube 2 setup is a sequence, not a single switch: connect it on your local network, initialize ZimaOS, create a data storage space, point computer backups to that space, verify local shares, then enable remote access only after securing accounts and the Remote ID. Finish by restoring a test file. The menu names below follow the current ZimaOS documentation and may change in a future interface update.
What you need before turning on ZimaCube 2
Prepare the ZimaCube 2, its power supply, an Ethernet cable, a router or network switch, and a computer on the same local network. You will also need storage drives supported by the current ZimaCube 2 hardware specification. The setup documentation used here does not verify particular drive models, bay formats, interfaces, or capacities for every ZimaCube 2 edition, so check the current specification before buying drives. A category such as NAS hard drives is appropriate; a specific model should not be assumed compatible without that check.
As an Amazon Associate I earn from qualifying purchases.
- Use Ethernet for the ZimaCube connection during initial setup. Wireless discovery is not the documented first-run path.
- Have a strong, unique password ready for the first ZimaOS account. That first account becomes the owner/administrator account.
- Decide which data needs protection beyond the NAS itself. RAID can keep an array available after certain drive failures, but it is not an independent backup.
- Plan an offsite or otherwise separate copy for irreplaceable files. ZimaOS documentation describes this as the third copy in a 3-2-1 approach.
Zimaspace Docs’ “Get Started with ZimaOS” (last updated September 22, 2026) states: “Your Zima device needs to be powered on and connected to the same network as the computer you are using for setup.”
Connect and initialize ZimaOS
1. Put the device and setup computer on the same network
- Connect ZimaCube 2’s Ethernet port to your router or switch.
- Connect power and turn the unit on. Allow time for ZimaOS to start.
- Connect the Windows or Mac computer you will use for setup to that same router or switch, either by Ethernet or the same trusted local Wi-Fi network.
The hardware quick-start also documents an IP-address method: when the device displays an address on a connected monitor, enter that address in a browser. This is useful when automatic discovery does not find the NAS.
#1 Best Overall
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance
- Store more and work faster with a NAS-optimized hard drive providing ultra-high capacity up to 16TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited warranty protection plan included and three year Rescue Data Recovery Services included
2. Discover the NAS with ZimaClient
- Install and open ZimaClient on the setup computer.
- Select the ZimaCube 2 shown in the discovered-device list.
- If no device appears, verify that the computer and NAS are on the same network and that the router has not isolated wireless clients from wired devices.
- Look in the router’s DHCP-client list for the ZimaCube IP address, then enter that address in a browser. The same browser route is described in the ZimaCube Quick Start documentation.
3. Create the owner account
Complete the first-run screen and create the initial account. It has administrative control, so do not share its password for ordinary file access. After setup, create separate ZimaOS accounts for family members, colleagues, or other devices that need access. Separate accounts let you manage permissions without handing out the owner credential.
Record the account recovery details in a secure password manager. Do not put the administrator password or Remote ID in a shared note, chat, screenshot, or public support post.
Configure storage before moving files
Do not start computer backups or copy your important files until a data storage space exists. In the documented interface, open Settings > Storage, select Combine to launch the disk-setup wizard, choose the desired configuration and drives, name the array or storage space, and confirm. When the wizard finishes, check the reported health and available capacity before using it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Menu labels can move as ZimaOS changes. If your screen differs, look for the Storage settings and the disk-combination or pool wizard rather than assuming that a missing label means the drives are faulty.
Choose a layout based on risk and capacity
| Layout | Drive requirement | Usable capacity | Drive-failure tolerance | When it fits | What it does not protect against |
|---|---|---|---|---|---|
| Single disk | One drive | Depends on the installed drive and filesystem overhead; no universal figure is stated in the setup guide. | None; a failed drive takes the storage space offline until replaced or restored. | Simple workloads, temporary data, or a user who already maintains a separate backup. | Accidental deletion, malware, theft, fire, and site loss. |
| RAID 1 | Two or more mirrored members, subject to the current ZimaCube 2 specification. | Less than the sum of all member capacities because data is mirrored; the exact result depends on the array. | Normally continued operation after one member fails, followed by a rebuild after replacement. | A common home or family starting point when availability and straightforward recovery matter more than maximum capacity. | It is not a historical backup and does not undo deletion or ransomware. |
| RAID 5 | Three or more drives. | Parity consumes part of the raw capacity; the result depends on drive sizes and the implementation. | Normally one drive failure. | More capacity-efficient protection for a multi-drive array when the owner accepts rebuild and management complexity. | Any event affecting more than the supported drive failures, plus non-hardware data loss. |
These are the layouts highlighted in the official ZimaOS storage setup guidance. The recommendation is not a universal prescription. Compare the capacity you can afford, the number of bays and drives available, replacement cost, rebuild risk, and how easily you can expand later.
Rank #2
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance.date transfer rate:6.0 gigabits_per_second
- Store more and work faster with a NAS-optimized hard drive providing 8TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited product warranty protection plan and three year Rescue Data Recovery Services included
Keep a separate copy of irreplaceable data off the ZimaCube. A practical 3-2-1 interpretation is three copies, on two kinds of media, with one copy offsite. A USB disk can be one destination, but one removable disk alone is not automatically sufficient for every theft, fire, malware, or account-compromise scenario.
Check the result before using it
- Confirm the storage space is shown as healthy or otherwise ready for use.
- Check that the capacity is plausible for the selected drives and layout.
- Give the space a clear name, such as
FamilyDataorWorkFiles, so backup destinations are unambiguous. - Do not select the ZimaOS system drive as the destination for computer data. Backups belong in a data storage space created for that purpose.
Back up a Windows or Mac computer
The documented workflow uses ZimaClient to connect the computer to ZimaOS, mount the storage, and select folders for backup. It is a folder-level backup workflow; it is not the same as a complete bare-metal image of a Windows installation.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Set up the first backup
- Install ZimaClient for Windows or macOS and open it.
- Connect to the ZimaOS device and sign in with an account that has permission to write to the chosen data space.
- Configure the storage mount so the ZimaOS storage is available in File Explorer or Finder.
- Open Backup and choose Add Backup Directory.
- Select the folders that matter, such as Documents, project folders, or Photos. Choose deliberately; backing up a temporary-download folder can consume space without adding useful protection.
- Choose the data storage space or RAID array as the destination. Do not choose the ZimaOS system drive.
- Start the first run and leave the computer and NAS connected until the initial transfer completes.
Later runs transfer changes rather than copying every unchanged file again. The computer-backup guide says interrupted backups resume, but you should still check the job status after a power or network outage instead of assuming completion.
Schedule and monitor the job
Use a schedule that matches how often files change. A daily job may suit documents and photos; frequently edited projects may need more frequent runs or an application-specific versioning system. Keep enough free space for growth and for any retained versions your chosen workflow creates.
Vendor documentation includes Wi-Fi and wired throughput estimates, but those are not guaranteed ZimaCube 2 performance figures. Actual speed varies with the router, distance, interference, Ethernet links, computer storage, and network configuration. Treat the first run as a baseline for your own network rather than a promise of a particular transfer rate.
Rank #3
- Available in capacities ranging from 2TB to 12TB
- For RAID-optimized NAS systems with up to 8 bays
- Designed for Continuous Operation
- Backed by World-Class Support and Warranty
- Tuned for NAS with NASware
Understand what recovery means
For a lost or damaged folder, open the ZimaOS storage in Finder or File Explorer and copy the needed files back to the computer. Restore at least one file and open it before you rely on the job. A successful copy operation is not proof that the file is usable; opening a document, image, or project verifies that the restored content is readable.
On a Mac, the guide also points to Time Machine Backup as an additional option for full-system recovery. Treat that separately from the ZimaClient folder backup: one protects selected data, while a system-recovery workflow is intended to rebuild a Mac installation and its broader state.
Make local file sharing work
ZimaOS storage spaces are shared across the local network by default and protected by the ZimaOS account. On macOS, connected folders appear in Finder; on Windows, they appear in File Explorer. This is the simplest way to share files with computers that are physically or logically on the same trusted home or office network.
Create accounts and permissions
- Open the ZimaOS account or user-management area.
- Create a separate account for each person or service that needs access.
- Give each account only the read or write permission it needs for the relevant storage space.
- Test the share by signing in as that user, not as the administrator.
Read-only access is appropriate for a media library or reference folder. Write access is needed for computer backups and collaborative folders, so grant it only to accounts and devices you trust.
If Finder or File Explorer cannot connect
- Confirm the ZimaCube is powered on and reachable from the same local network.
- Confirm the account name and password; an expired, mistyped, or wrong-user credential is a common cause.
- Check that SMB is running in ZimaOS.
- Remove an old saved credential on the client and sign in again if the computer keeps presenting the wrong account.
The official SMB troubleshooting guide covers Windows 10/11 and macOS. It includes a macOS credential-cache workaround for cases where a saved username prevents authentication. Because the example formatting and credentials on that page can change, follow its current steps rather than copying an example password or username into your own setup.
Rank #4
- Available in capacities ranging from 2 to 22TB(1) | (1) 1GB = 1 billion bytes and 1TB = 1 trillion bytes. Actual user capacity may be less depending on operating environment.
- For RAID-optimized NAS systems with unlimited number of bays
- Rated for 550TB/yr workload rate(2) | (2) Annualized Workload Rate = TB transferred x (8760 / recorded power-on hours). The maximum rated workload is specified for operating at typical temperature of 40C. Workload Rate will vary depending on your hardware and software components and configurations.
- Designed to handle the demands of high-intensity 24x7 multi-user NAS environments
- Western Digital partners with a wide range of NAS system vendors for extensive testing to ensure compatibility with most NAS enclosures
Enable and protect remote access
Remote access is a separate decision from local SMB sharing. The ZimaOS documentation describes ZimaClient remote access as a peer-to-peer encrypted connection configured during sign-in. That privacy and security description is a statement from the vendor documentation, not an independent security audit.
Turn on the documented ZimaClient path
- Open Settings > Network in ZimaOS.
- Enable remote access if it is not already enabled.
- Sign in to ZimaClient from the computer or phone you will use away from home.
- Confirm that you can see the intended storage space and that account permissions are still applied.
The computer-backup documentation specifically notes that remote access must be enabled in Settings > Network. If it is disabled there, a remote ZimaClient session will not work even if local sharing is configured correctly.
Protect the Remote ID
Find the Remote ID in Settings > Network. Treat it as sensitive: the vendor warns that exposure can allow shared folders to be exposed. Do not publish it, include it in screenshots, or paste it into a public forum.
If you believe the ID has been compromised, use the adjacent reset control. Resetting invalidates existing connections and shares, so every legitimate client must reconnect with the new ID. Plan this change when household or team members are available to sign in again.
When a self-managed protocol is preferable
The remote-access documentation lists Tailscale, WireGuard Easy, Firefly, and NetBird as open-protocol app options. These are alternatives for owners who want to manage protocol-based remote access themselves; they are not prerequisites for the standard ZimaClient flow. Each requires the user’s own account, keys, or network configuration. Use one only if you understand which devices are trusted, how access is revoked, and how updates are maintained.
Best Value
- Available in capacities ranging from 1-14TB with support for up to 8 bays.Data Transfer Rate:6Gbps.Specific uses: Business
- Supports up to 180 TB/yr workload rate | Workload Rate is defined as the amount of user data transferred to or from the hard drive. Workload Rate is annualized (TB transferred ✕ (8760 / recorded power-on hours)). Workload Rate will vary depending on your hardware and software components and configurations.
- NASware firmware for compatibility
- Small or medium business NAS systems in a 24x7 environment, Compatibility: Unlike desktop drives, these drives are specifically tested for compatibility with NAS systems for optimum performance.
- 3-year limited warranty
Prove that backups and access work
A setup is not finished when a dashboard says “connected.” Run a controlled test while the original file is still available.
- Create a small test folder containing a text file, a photo, and one document type you regularly use.
- Run the computer backup and verify that the files appear in the selected data storage space.
- Open the local share from Finder or File Explorer using a non-administrator account.
- Copy one test file back to a different local folder and open it.
- From a device on a different network, sign in to ZimaClient and confirm that remote access reaches only the folders that account is allowed to see.
- Delete the restored copy, repeat the restore later, and record the date and result in your backup notes.
For a stronger test, temporarily disconnect the client from the network during a backup, reconnect it, and check that the job resumes and reports completion. Do not simulate a drive failure on a live array unless you have a documented recovery plan and current backups.
Common setup problems and fixes
ZimaClient cannot discover ZimaCube 2
Check Ethernet, power, and network membership first. Put the computer and NAS on the same subnet, disable guest-network isolation, and consult the router’s DHCP list for the assigned IP. Enter that IP in a browser as described in the hardware quick-start.
The storage wizard shows the wrong capacity
Usable space is lower than the sum of raw drive labels because of mirroring, parity, filesystem overhead, and reserved system space. Confirm that the intended drives were selected, then check the health and capacity report after the wizard completes. Do not move important data into the space until the result matches your layout decision.
A backup job fails immediately
Verify that the destination is a data storage space rather than the ZimaOS system drive, that the mounted path is available, and that the signed-in account has write permission. If the first run was interrupted, restart or resume it and inspect the final status. A successful later incremental run does not prove that the initial full copy contains every required folder.
Local sharing works but remote access does not
Local SMB access and remote ZimaClient access use different paths. Confirm remote access is enabled under Settings > Network, sign in with the correct account, and check that the Remote ID has not been reset. If it was reset, reconnect every client with the new ID.
Quick Recap
A practical completion checklist
- ZimaCube 2 is connected by Ethernet and appears in ZimaClient or by its router-assigned IP.
- The owner account has a unique password, and ordinary users have separate accounts.
- A healthy data storage space is configured before any backup job begins.
- The chosen layout matches your capacity, drive-count, and availability requirements.
- Computer backups target the data space, not the ZimaOS system drive.
- A local Finder/File Explorer share works with the intended permissions.
- Remote access is enabled only when needed, and the Remote ID is private.
- At least one file has been restored and opened successfully.
- An offsite or otherwise separate copy exists for irreplaceable data.
Official documentation
- Get Started with ZimaOS (updated September 22, 2026)
- ZimaCube Quick Start: Unbox, Set Up, and Access ZimaOS (updated September 22, 2026)
- ZimaOS Storage Setup (storage layouts and 3-2-1 guidance)
- Mac and Windows Backup to ZimaOS
- ZimaOS SMB Setup and Troubleshooting
- ZimaOS Remote Access
- ZimaOS Features (updated October 13, 2026)
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
