On Mon, 02 Dec 2013 14:10:14 -0800, lcampbell <lcampbell@...>
wrote:

> We have a user that has had FB 2.1, and was running gbak with a command
> line of the form:
>
> >"C:\Program Files\Firebird\Firebird_2_1\bin\gbak.exe" -backup -verify
> -Y "C:\ATBackup\AUCTIONTRACKER.LOG"
> "C:\Tracker\Auct-Tr\AUCTIONTRACKER.FDB" "C:\ATBackup\AUCTIONTRACKER.FBK"
>
> Note: Did not require -user or -password.
>
> When he upgraded to FB 2.5, this command line format would no longer
> work. It now requires the -user and -password switches with valid
> username & password.
>
> I've got a WinXP box set up with FB2.1, and a Win7 box set up with
> FB2.5. I've run tests with successful backup under 2.1 with no
> user/password; then ran it on my Win7/FB2.5 box and got the same result
> as the user. Command line would only work with a valid user/password.
>
> In neither case were the ISC_USER or ISC_PASSWORD enviornment variables
> set.
>
> What's changed? Has the new version of gbak become more stringent? Any
> clues appreciated.

Most likely it is due to changes in assigning SYSDBA rights. See the
release notes:
"Under v.2.5, although the modes are unchanged, configuring 'mixed' or
'trusted' mode no longer confers SYSDBA privileges on Windows domain
administrators automatically by default. Please read the notes in the
Administrative Features chapter regarding the new RDB$ADMIN role in ODS
11.2 databases and auto-mapping SYSDBA privileges to domain
administrators."

(
http://www.firebirdsql.org/file/documentation/release_notes/html/rlsnotes252.html#rnfb25-fbconf-authent
)

Mark