Reading it back is the only feature that matters.
Most days it is one file someone deleted. Sometimes it is a folder tree. Sometimes it is everything that was on a machine that will not switch on again. The same restore points answer the first two outright, and get the third one’s data onto a machine that still works — open a restore point, look inside it, and decide where it lands.
Open any restore point and walk it like a filesystem — any folder, any depth. Filter, tick what you want, and the free space at the destination is checked before the restore starts rather than halfway through it.
before you commitA single file comes out of storage directly — no agent, no restore job, no waiting on the machine it came from. It works while that machine is switched off, lost, or in a box under someone’s desk.
no agent neededEvery path returns to exactly where it came from, or into one folder you choose — each source landing in its own subfolder, so two drives never merge into one heap. Existing files are overwritten or skipped, and you pick which before it starts.
one file, or all of itRestore one device’s data onto another device in the workspace. The machine it came from does not have to be online — or still exist. Point at one that is, and the data lands there.
any online deviceWhere a restore is allowed to land.
The same restore point answers all four. Which one you want depends on whether the machine it came from is still in the building.
Back in place
Every path returns to exactly the location it came from on the original machine. This is the ordinary Tuesday answer: somebody deleted a folder and wants it where it was.
Into a new folder
Everything lands under one folder you choose, each source in its own subfolder, so two drives never merge into a heap. Use it when you want the old copy beside the current one rather than instead of it.
Onto another machine
Restore one device’s data onto any other device in the workspace. The source machine does not have to be online, or to still exist. Point at one that is, and the data lands there.
Straight to your browser
A single file comes out of object storage to your browser — no agent, no restore job, no waiting on the source machine. It works while that machine is switched off or in a box under a desk.
Reading your own data back is free on every plan, including the trial. There is no egress charge, no exit fee, and no charge that only appears when you try to get your data out.
You choose what happens to what is already there.
The conflict mode is picked before the restore runs, not discovered afterwards. One of these three is always in force, and the console says which.
| Conflict mode | What it does at the destination |
|---|---|
| overwrite | Replaces existing files at the destination with the version in the restore point. |
| skip | Writes only the files that are missing, and leaves everything already there untouched. |
| mirror | Makes the destination match the restore point exactly — which means it deletes anything not in the backup. |
Each restore point is badged in the picker, so you can see which runs excluded locked files and how many files a run could not read before you choose one. A point flagged as unverified is labelled as such rather than shown as a clean success.
What a dead-server day actually looks like.
The honest shape of it, because this is the question every evaluation ends on and the answer is not the one a disk-imaging vendor gives.
Hour one: keep working
Restore that machine’s data onto a different machine in the workspace. The dead one never has to come back online. People get back to the files while the hardware question is still open.
The rebuild is yours
You install Windows and your applications from your own media. Comsky Backup does not image disks and does not restore an operating system, its installed software or its licences — and we will not imply otherwise.
Then the data goes back
Once the replacement is built, restore in place or into a folder you choose. The restore points are unchanged by any of this: they live in the vault, not on the machine that died.
If a one-click whole-machine rebuild is what you are shopping for, this is not the product for that job, and we would rather you knew now than in an incident.
About getting it back.
Can I see what is in a restore point before I restore it?
Yes. Open it and walk it like a filesystem — any folder, any depth. Filter, tick what you want, and the free space at the destination is checked before the restore starts rather than halfway through it.
Can I get one file back without touching the machine?
Yes. A single file comes out of object storage directly to your browser. No agent, no restore job, and no waiting on the machine it came from — it works while that machine is switched off, lost, or in a box under somebody’s desk.
Can I restore one machine onto a different one?
Yes. Pick the source device’s restore point and pick any other device in the workspace that is online. The machine the data came from does not have to be online, or to still exist.
What happens to files that are already at the destination?
Whatever you chose before it started. Overwrite replaces them, skip writes only the missing ones, and mirror makes the destination match the restore point exactly — which deletes anything not in the backup. The mode is picked up front, not discovered afterwards.
Does a restore cost anything?
No. Restores and egress are free on every plan, including the trial. There is no exit fee and no charge that only appears when you try to read your own data back.
Can I rebuild a dead machine from a backup?
Not to bare metal. This is file-level backup, not disk imaging — there is no volume restore and no recovery media. What you can do is restore that machine’s files onto a replacement machine in the same workspace, with the dead one never coming back online. For a lot of businesses that is the actual requirement; if it is not yours, you need an imaging product instead.
Every device name, path and figure on this page is demo data.
Start with Comsky Backup.
Grow into the ecosystem.
One account opens every Comsky product — and one invoice covers them, however many you run.