Satkosh

Calls: Monday to Saturday, 9 AM to 7 PM IST

Book a demo
Documentation

Getting started

The path from nothing to a restore you have watched work. About half an hour for the first machine, about five minutes for each one after that.

Last updated 7 November 2026

Do not skip the last two steps: a backup you have never restored from is a guess.

  1. Sign in to the console

    Go to console.satkosh.com and sign in with your email and password, or use Sign in with Microsoft if your organisation has connected Microsoft 365. Turn on two-factor authentication from Settings. Setup checks your authenticator app before it switches on, so a half-finished setup cannot lock you out of your own console. Keep the single-use recovery codes somewhere that is not the machine you are about to protect.

  2. Add a backup repository

    A repository is where backups are stored. Add one first, because a policy has to point somewhere. There are three kinds, and the Backup repositories page covers how to choose between them.

  3. Add the first machine

    Open Devices and click Add devices. Generate a token, install the agent with it, and watch the machine appear in the Connect step. There is no backup server to buy or rack first. Budget about five minutes.

  4. Build a policy

    Pick the machines, the folders and databases that matter, how often to back them up and how long to keep each copy. Apply it to one machine or to many.

  5. Run it once by hand

    Use 'Run backup now' rather than waiting for the schedule. A manual run takes exactly the same path as a scheduled one, so a manual run that works proves the scheduled one will. Follow it under Monitoring, in Activities.

  6. Restore something, before you need to

    Take the backup you just made, restore a single file to a separate folder, and open it. This is the only step that proves the whole chain end to end. Every step before it proves only that data left the machine.

  7. Turn on email alerts

    Under Settings, Notifications, enter who should hear about problems and from which severity. A shared mailbox is better than one person. Do this on day one, so a failing backup reaches someone the same day.