Caresoft · backup operations
CareVault is a centralised backup management platform for hospital database servers. It runs a full backup after midnight and incremental backups every four hours, transfers each file to a dedicated backup server over SFTP or FTPS, deletes files older than seven days, and writes a dated success or failure log for every run.
Built for the 1,000+ hospitals already running Caresoft HIS across India and 12 countries.
A scheduled job on a hospital server either ran or it did not. Nobody finds out which until a restore is needed.
A backup sitting on the same disk as the database is not a backup. It fails with the machine it was meant to protect.
Every hospital configured slightly differently, on a different SQL Server version, with no shared record of what happened last night.
How it works
The agent is a signed script registered with the Windows Task Scheduler, or a cron entry on Linux. It wakes on a fixed cadence, runs only the slot that is due, and reports every step back with a timestamp.
A full backup shortly after midnight, then an incremental every four hours. SQL Server writes the file natively; the agent never streams data over the network.
RESTORE VERIFYONLY confirms the file is readable before anything else happens, and a SHA-256 checksum is recorded so the copy can be proven identical later.
Transfer to your dedicated backup server over SFTP, FTPS or FTP, retried on failure, with the remote file size checked against the local one.
Files older than seven days are removed locally and remotely. A safety floor stops the last full backups being deleted, whatever the rule says.
Every run is written to the CareVault database with the database name, backup type, size, duration, transfer speed, remote path and exact timestamp. Failures are recorded the same way, with the step and the error.
Coverage
2008 R2 through 2022, Express to Enterprise, on-premises or on a cloud VM.
Consistent logical dumps with binary-log incrementals, driven by cron, reporting into the same console.
Backups still run and still transfer locally. Console messages queue on disk and are sent when the link returns, so the record stays complete.
Cloud and on-premises servers sit side by side in one dashboard. Nothing about the agent changes between them.
Time slots, local folder, storage connection, retention and database selection are all set per server from the console.
The agent caches its configuration. If the console is unreachable it keeps running last known good settings rather than stopping.
Security
Every call from an agent is signed with HMAC-SHA256 over the method, path, timestamp, a one-time nonce and a hash of the body. Replays are rejected.
Database and storage credentials are stored with AES-256-GCM. Clients who prefer it can keep credentials only on their own server and share nothing with the console.
A client administrator sees only their own organisation. Caresoft administrators see the estate. Every configuration change is written to an audit trail.
Questions
By default CareVault runs one full backup shortly after midnight and an incremental backup every four hours. Both the full backup time and the incremental slots are configurable per server from the client console.
Yes. The agent detects the SQL Server major version and edition at run time and adapts. Backup compression is used where the edition supports it and skipped on Express editions, so a single agent covers SQL Server 2008 R2 through 2022.
Each backup file is transferred to a dedicated backup server over SFTP, FTPS or FTP. The protocol, host, port, credentials and remote folder are configured per client and can be changed without reinstalling the agent.
Local and remote retention default to seven days and are set per server. A safety floor prevents the agent from deleting the last full backups even if a retention rule would otherwise remove them.
The failure is written to the CareVault database with the exact step that failed, the error code, the error message and the timestamp. An alert is raised on the admin dashboard and sent to the configured recipients.
The backup still runs. Log entries are queued in a local spool file and posted to the console when connectivity returns, so no run is lost from the record.
Yes. Client admin logins are scoped to one organisation and can see only their own servers, schedules, logs and alerts. Caresoft admin logins see the full estate.
Get started
Send the number of database servers and where they sit. We will come back with a rollout plan and a walkthrough of the console using your own estate as the example.
support@caresoft.co.in
+91 22 4970 0000