Subject | FB 2.1 vs. 2.5, differences in gbak command line requirements? |
---|---|
Author | lcampbell |
Post date | 2013-12-02T22:10:14Z |
We have a user that has had FB 2.1, and was running gbak with a command
line of the form:
"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.
Thanks
Lane Campbell
NW Software
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.
Thanks
Lane Campbell
NW Software