AIB BackupCheck backs up your databases on a schedule, restores every backup into a test database to prove it works, keeps copies where you choose, and tells you when anything goes wrong.
1. Install
- Run
AIB-BackupCheck-Setup.exeon the computer that runs your database (Windows 10, 11 or Server 2019 and newer). - Choose Dashboard and backups on this computer.
- Tick Allow other servers to connect only if you will look after other servers from this one.
- When it finishes, the dashboard opens at http://localhost:8585. Create your sign-in.
BackupCheck runs as a Windows service, so backups happen whether or not anyone is signed in to Windows.
2. Add a destination
Destinations → Add destination. Start with a folder on a different disk from the database, or a network share
(use \\server\share, not a mapped drive letter: services cannot see mapped drives).
For an off-site copy (Pro), add a cloud bucket:
| Provider | Endpoint | Notes |
|---|---|---|
| Cloudflare R2 | https://<account-id>.r2.cloudflarestorage.com |
Region auto. Create an API token with Object Read & Write. No download fees. |
| Backblaze B2 | https://s3.<region>.backblazeb2.com |
Use an application key limited to the bucket. |
| Wasabi | https://s3.<region>.wasabisys.com |
Files are kept (and billed) for at least 90 days. |
| Amazon S3 | (leave empty) | Set the bucket's region. |
Press Test: BackupCheck writes, reads back and deletes a small file.
SFTP: enter the server, user and password (or a private key). The first successful test saves the server's fingerprint; if it ever changes, BackupCheck refuses to connect and tells you.
Google Drive: needs a free OAuth client from your own Google Cloud project: 1. console.cloud.google.com → new project → APIs & Services → enable Google Drive API. 2. OAuth consent screen → External → add your Google account as a test user. 3. Credentials → Create credentials → OAuth client ID → Desktop app. Copy the ID and secret into BackupCheck. 4. Press Connect Google account (on the computer running BackupCheck), allow access, then Test and Save. BackupCheck can only see the files it creates, in a BackupCheck folder in your Drive.
3. Create a backup job
Backup jobs → New job.
- Which database? Pick the type and enter the server. For SQL Server use the same name as in Management Studio,
for example
.\SQLEXPRESS. Press Test connection and tick the databases. - When? Every night is a good start. If the computer is off at that time, the backup runs when it is back on.
- Where? Pick one or more destinations. Two is best: one local, one off-site.
- Checks and encryption. Keep Full test restore unless disk space is tight. If you turn on encryption, write the passphrase down away from the server: without it nobody can open the backups.
- How long to keep backups? The defaults keep 7 daily, 4 weekly and 12 monthly copies.
Press Run now to try it straight away, and watch it under History.
SQL Server sign-in
With Windows login (user name left empty), BackupCheck connects as the service account, Local System. Since SQL Server 2012 that account cannot back up or create databases by default. Either:
- use a SQL login with the
sysadminrole (simplest), or - give Local System the rights, in Management Studio as an administrator:
CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS; -- skip if it exists
ALTER SERVER ROLE dbcreator ADD MEMBER [NT AUTHORITY\SYSTEM];
-- then in each database to back up:
CREATE USER [NT AUTHORITY\SYSTEM] FOR LOGIN [NT AUTHORITY\SYSTEM];
ALTER ROLE db_backupoperator ADD MEMBER [NT AUTHORITY\SYSTEM];
The restore check needs permission to create (and drop) a temporary database whose name starts with bc_verify_.
PostgreSQL and MySQL
BackupCheck uses the database's own client tools (pg_dump/pg_restore, mysqldump/mysql). They are found
automatically in the usual install folders. If not, set Client tools folder under Advanced connection settings.
Use client tools of the same version as the server, or newer.
4. Set up alerts
Alerts → Add alert. Telegram takes two minutes:
1. In Telegram, message @BotFather, send /newbot, and copy the token.
2. Send your new bot any message.
3. Open https://api.telegram.org/bot<token>/getUpdates in a browser and copy the chat → id.
4. Paste both into BackupCheck and press Send test.
Email works with any SMTP server; for Gmail or Outlook create an app password. Webhooks work with Slack, Discord, Microsoft Teams workflows and Google Chat.
You can choose to hear about failures, warnings, every success, and a daily summary.
5. Restore
Restore → choose the job → Restore next to the backup you want.
- Restoring into a new name (the default) is safest: compare it with the live database, then switch over.
- Replace the database disconnects everyone and overwrites it. You must type its name to confirm.
- For an encrypted backup made before you changed the passphrase, enter the old passphrase.
You can also restore by hand, even on a computer without the dashboard. A .bcbk file holds a normal SQL Server
.bak, pg_dump archive or .sql dump; unpack it with:
"C:\Program Files\AIB BackupCheck\BackupCheck.Service.exe" unpack D:\Backups\PosDb_20261120-020000Z.bcbk
It asks for the passphrase if the backup is encrypted, checks every block, and writes the dump next to the file.
6. Look after several servers (Pro 2+ servers, Agency)
- On the dashboard computer: Settings → Allow remote access → Save → Restart now. The installer opens port 8586.
- Servers → Add server, name it, and copy the pairing code.
- On the other server, run the same installer, choose Agent only and paste the code.
- It shows as Online within a minute. Create jobs for it as usual.
The agent only trusts your dashboard's certificate. The code works once and expires after 24 hours.
7. Licence
Settings → Licence key → Activate. Keys start with BC1- and are checked on the server, with no call home.
Your licence keeps working for ever; it includes 12 months of updates. Versions released after that need a renewal.
Troubleshooting
| Message | What to do |
|---|---|
| Could not reach SQL Server | Check the server name, that the SQL Server service runs, and that TCP/IP is enabled (SQL Server Configuration Manager). |
| SQL Server refused the login | Wrong user/password, or the Local System login is missing (see SQL Server sign-in). |
| This login is not allowed to back up | Give the login db_backupoperator in that database, or use a sysadmin login. |
| SQL Server cannot write to … | Give the SQL Server service account write rights on its backup folder, or set SQL Server backup folder. |
| The test restore failed: … cannot create databases | Give the login the dbcreator role, or switch the job to Quick check. |
| Not enough disk space | The restore check needs room for one copy of the database. Free space or use Quick check. |
| pg_dump on this computer is older than the server | Install PostgreSQL client tools of the server's version or newer. |
| The bucket does not exist / access key is not recognised | Check endpoint, region, bucket name and that the key has read and write access. |
| The SFTP server's identity changed | If you rebuilt the server, press Forget next to the fingerprint and test again. Otherwise investigate. |
| Google no longer accepts this connection | Press Reconnect Google account. |
| Forgot the dashboard password | On the server, as administrator: "C:\Program Files\AIB BackupCheck\BackupCheck.Service.exe" reset-password |
Logs are in C:\ProgramData\BackupCheck\logs. When asking for help, send the latest log to
[email protected] or WhatsApp +92 335 684 6600.