I have a Windows Server running Firebird 2.5.4 on port 3050, and I have another Firebird Server older version on port 3051.
I use the 3051 server for compatibility reasons for another application. I turn it on when I need it, and most of the time it is off via windows services.
However, backups are now failing when using nbackup. The command is
nbackup.com -u sysdba -p PASSWORD -B 0 "C:\DATABASE.FDB" "X:\BACKUP.fbk"
When running this command it fails with:
[
PROBLEM ON "attach database".
unavailable database
SQLCODE:-904
]
Failure: Database error
Connecting via isql similarly generates the same problem.
isql -u sysba -p PASSWORD "C:\DATABASE.FDB"
Statement failed, SQLSTATE = 08001
unavailable database
However via the specific connection host & port it works fine.
isql -u sysba -p PASSWORD "localhost/3050:C:\DATABASE.FDB"
Applying this to nbackup fails since one needs local access to the database file.
nbackup.com -u sysdba -p PASSWORD -B 0 "localhost/3050:C:\DATABASE.FDB" "X:\BACKUP.fbk"
[
PROBLEM ON "nbackup needs local access to database file".
SQLCODE:-999
]
Failure: Database error
Is there some sort of environment variable or configuration that prevents nbackup from accessing the database file correctly? The Line of Business application has no problem connecting, and making changes to the database. No errors in firebird.log on both instances. Very weird.