Choosing where backups go
Machines sharing a repository also share deduplication, so protecting fifty similar workstations costs far less storage than fifty separate copies. Credentials are held encrypted and unlocked only to run a job you scheduled or a restore you asked for.
- Storage bought from us, currently kept in India. We set up a dedicated bucket for you, sized to what you need, and charge for it per GB. If you change your mind you can move it to a bucket of your own without paying us to hand it back
- S3-compatible object storage of your own: Amazon S3, Wasabi, MinIO or any S3-compatible service. Your account, your access rules, your bill from them. We hold nothing except the key needed to write to it, and that is encrypted
- A NAS shared folder. Fast restores, and Satkosh logs in to the share only while it works, so ransomware on a PC does not see it
- A local folder on a second disk or a USB disk on each PC, at the same drive letter on every machine
- We would not recommend a NAS or a local disk as your only copy, because storage in the same room as the servers it protects shares their fire, their flood and their burglary
- Each repository's page shows how much it holds against its capacity, which policies and machines use it, and any problem with its likely cause. Satkosh warns you before it fills up
- Expired backups release their space automatically, so storage does not grow quietly forever while the console shows a tidy list
- Backups are always encrypted. Managed by Satkosh is the default; zero-knowledge keeps the password only on your machines, and if it is lost nobody can restore those backups, including us
Locking backups against deletion
Switch on immutable backups for an S3 repository and every backup is locked for the days you choose. Until the lock ends, it cannot be changed or deleted by ransomware, by a compromised console account or by someone holding your stolen password.
- Governance mode (recommended): locked against deletion, but an account with special rights at the storage provider can remove a lock in an emergency, so a lock set too long by mistake can be put right. Satkosh storage uses this mode
- Compliance mode, on your own storage: locked for the whole period, and that cannot be undone by anyone, including you, us and the storage provider. You pay for the storage for the whole period, with no way to stop it
- On your own storage, give the key Satkosh uses only what it needs, and not the right to bypass retention (s3:BypassGovernanceRetention on Amazon S3). A key with that right can remove a Governance lock
- Your bucket must have Object Lock switched on, which most providers allow only when the bucket is created. Satkosh checks this when you save, and refuses the setting if it is not on
- Lock for at least 14 days, and keep it at or below the policy's retention, or you pay to store backups the policy has already expired
- A locked copy keeps using storage until its lock ends, and cannot be deleted early to bring a bill down. That is the whole point of it, so set the period deliberately rather than generously
- A NAS or a local disk cannot enforce a lock
- This is recovery you cannot destroy, not endpoint protection. Satkosh does not scan for or block ransomware on your machines; your antivirus does that