TL;DR — Quick Summary

Aspel SAE Firebird backup fails from full disk, gbak errors, NTFS permissions, or connected users. Step-by-step fix to get a valid .fbk without data loss.

When Aspel SAE cannot finish a Firebird backup, the business risk is real: without a valid .fbk, disk failure or ransomware leaves accounting and invoicing unrecoverable. On Windows servers in Mexico, backup errors usually trace to a full disk, connected users, NTFS permissions, or a misconfigured gbak run.

Respaldo SAE Firebird

The Error

From Utilities > Backup/Restore > Backup, you may see:

Could not back up the database

Insufficient disk space

database file appears to be in use

I/O error during WriteFile

Sometimes the wizard finishes but the .fbk is 0 KB. Running gbak manually may report permission denied or database file is locked.

Root Cause

  1. Full system or destination drive — Firebird needs extra temp space during logical backup.
  2. Users still connected — Open SAE sessions lock the .fdb.
  3. NTFS permissions — Firebird service or backup folder lacks write access.
  4. Network/OneDrive target — Backing up directly to SMB or synced folders truncates files.
  5. Antivirus — Real-time scan blocks .fdb/.fbk writes.
  6. Firebird stopped or wrong version — Service down after SAE upgrade.
  7. Database corruption — gbak fails even when disk space looks fine.

Step-by-Step Fix

1. Check disk space

Inspect free space on the drive hosting Empresas and your backup folder:

C:\Program Files\Common Files\Aspel\Sistemas Aspel\SAE8.00\Empresas
C:\Program Files\Common Files\Aspel\Sistemas Aspel\SAE8.00\Respaldos

Rule of thumb: free space ≥ .fdb size × 1.3. If SAE80001.fdb is 6 GB, free at least 8 GB before backing up. Use Disk Cleanup for temp files and move old .fbk archives to USB or cloud after the new local backup succeeds.

2. Close all SAE sessions

  1. Close Aspel SAE on every workstation.
  2. End stuck SAE*.exe in Task Manager.
  3. Restart Firebird Server - DefaultInstance from services.msc only during a communicated maintenance window.

With multi-user licensing, confirm no phantom sessions remain on the Aspel License Server.

3. Fix folder permissions

On Respaldos and the new backup path:

  1. Right-click > Properties > Security.
  2. Grant Full control to SYSTEM, Administrators, and the Firebird service account (often Local Service).
  3. Use Replace all child object permissions if the folder was copied from another server.

Run SAE as administrator only for the backup test, not as daily policy.

4. Exclude Aspel/Firebird from antivirus

Permanent exclusions:

  • C:\Program Files\Common Files\Aspel\
  • C:\Program Files\Firebird\ (your installed path)
  • The local folder where .fbk files are written

Temporarily disable real-time protection only during the backup window if blocks persist.

5. Backup from SAE

Utilities > Backup/Restore > Backup, select companies, choose a local path with verified space, and confirm the .fbk size is non-zero.

6. Use gbak if the wizard fails

cd "C:\Program Files\Firebird\Firebird_2_5\bin"
gbak -b -v -user SYSDBA -password YOUR_PASSWORD ^
  "C:\Program Files\Common Files\Aspel\Sistemas Aspel\SAE8.00\Empresas\SAE80001.fdb" ^
  "D:\SAE-Backups\SAE80001.fbk"

Replace paths, version folder, and password for your site. Do not use default masterkey in production.

7. Validate the backup

  1. Confirm .fbk size in File Explorer (not 0 KB).
  2. Monthly, restore on a test PC or run gbak -c to a test database.
  3. Open SAE on the copy and verify catalogs plus a recent invoice.

Alternative Solution

If disk space cannot be freed on C:, attach a secondary local drive (D: or USB 3.0) and point backups there. Never rely on a single copy on the same volume as the live .fdb without off-site replication.

  • Backup wizard works but restore fails → see backup/restore database errors.
  • After server migration, SAE opens but backup path is wrong → update BDE alias and Firebird connection settings.
  • EEFFACE on open often appears when the base was damaged by an interrupted backup → fix backups first, then EEFFACE guide.

Prevention

  • Schedule backups when no users are connected.
  • Alert when system disk exceeds 85% usage.
  • Keep two generations of .fbk files.
  • Document .fdb path, Firebird version, and credentials.

Summary

  • SAE backup failures usually mean full disk, open sessions, or permissions on the .fbk path.
  • Backup to local disk first, then copy off-site.
  • gbak -b is the standard fallback when the SAE wizard fails.
  • If you recently migrated servers, also review Firebird connection errors.