Zoolz copies selected files from a computer, attached storage, or mapped network drive into cloud backup storage. The desktop program watches the selected paths and uploads their data according to its schedule. Zoolz divides retrieval behavior between Instant Storage and Cold Storage: Instant data is ready for direct access, while Cold Storage trades immediate retrieval for archival storage. A backup selection is not a synchronized working folder, and deleting or editing the original does not make the cloud copy a substitute for checking restore behavior.
Paths define the backup
The Data Selection window lets Zoolz choose folders from internal and external drives. A network share must appear as a mapped drive before the desktop program can select it in the normal browser. If the mapping changes letters or disappears at sign-in, the stored path no longer points to the intended location.
Plans that contain both storage classes show separate Instant and Cold Storage selection areas. Selecting the same file in both does not make two cloud copies. Zoolz gives Instant Storage priority. A file meant only for archival pricing must therefore appear exclusively under Cold Storage rather than in both lists.
Cold means waiting
Zoolz can browse Cold Storage data in the web console, but a restore request needs preparation before bytes begin downloading. Official restore guidance sets that wait at three to twelve hours. The service sends an email when a browser download is ready, while the desktop restore program waits and continues the job when the archived data becomes available.
The web console also limits Cold Storage retrieval to one gigabyte per day. A larger recovery needs the Zoolz Restore desktop program. During that restore, the computer must stay awake and the user must remain signed in. Restarting, signing out, or letting the machine sleep can interrupt the transfer, which matters when a failure leaves only a narrow maintenance window.
Hybrid keeps a local copy
Hybrid+ writes another copy to a local server, external disk, or network drive while Zoolz sends the cloud backup. Restore checks that local repository before it retrieves the cloud object, reducing both delay and Internet transfer when the local copy still exists. This local layer is separate from Instant Storage and does not change a Cold Storage object into instant cloud data.
A size limit controls the Hybrid+ repository. When the local allocation fills, Zoolz removes older local copies to make room for newer ones. The corresponding cloud backup remains, but recovery can fall back to the slower cloud path. The local repository therefore needs monitoring if quick restoration of older files matters.
Sessions affect scheduling
Zoolz Home expects installation under an administrator account. Logging out of that Windows account stops its backup activity, and signing in resumes it. A schedule that appears correct can still miss an overnight window when the machine logs the user out or enters sleep.
Bandwidth throttling caps upload use so backup does not consume the entire connection, but the same cap extends the initial upload. A large first selection may need several scheduled periods. External and network drives must also remain available when the scheduled pass reads them; choosing a folder once does not make a disconnected drive available later.
Restore before relying
Zoolz can restore the latest copy, an older version, or an item marked as deleted. Those choices depend on what the account still retains and which storage class holds the data. Sharing also has a storage boundary: Cold Storage objects cannot become shared links until they occupy a supported instant area.
A small restore test checks the account password, storage path, download method, and decryption choice before an emergency. Testing one recent file and one archived file exposes the difference between immediate access and the Cold Storage preparation queue without waiting for a full-disk failure.
