What Backupinsta does, and what it does not
Backupinsta backs up whole drives, file by file, from Windows servers and laptops into per-device encrypted cloud storage. A small agent runs on each machine. Backups are scheduled, versioned and managed from one console.
What it covers
- Whole-drive, file-level backup. Every file on the drives you select, kept as a versioned history rather than a mirror of the current state.
- Per-device encryption. Data is encrypted on the machine before upload, under a key belonging to that device.
- Deduplication and compression, applied before anything leaves the machine.
- Scheduled and manual runs, with retention by both age in days and number of recovery points.
- Four restore destinations: back in place, into a new folder, onto another machine, or downloaded through your browser.
What it does not do
These are deliberate exclusions, not gaps waiting to be filled. If a backup product you are comparing against offers them, it is a different category of tool.
- No disk imaging, volume restore, bare-metal recovery or recovery media. Backupinsta restores files. It does not rebuild a machine from bare metal.
- No macOS or Linux agent. Windows only.
- No WORM, object lock or “immutable” storage. What protects your backups is that the agent’s storage credential has no permission to delete backup data — a different and, in practice, stronger guarantee than a retention lock.
- No fleet-wide deduplication. Every device has its own repository and its own key, so identical files on two machines are stored as separate data. This is a consequence of the per-device key design.
- No bandwidth throttling, GFS retention, recovery drills, read-only seats, or an audit log of administrative actions.
Two things worth being precise about
Shadow copy is conditional. On Windows, open files are read through a shadow copy. If the shadow-copy service cannot start, the run continues without one, locked files are skipped, and the job is flagged. A backup is never silently incomplete — but it can be incomplete.
Device isolation is cryptographic, not access-scoped. A device credential can list and read the whole workspace bucket; cross-device restore depends on it. What separates two devices is that neither holds the other’s repository key.
These pages are a starting point written against the shipping product. If a step here does not match what you see in the console, trust the console and tell us at support@comsky.in.