gbak regresion in FB3.0.10

[skopaliks]

Windows 10 x64, FB3.0.10 x64.
Installed over previous FB3.0.9 by installer.

In case that default service is running and try to restore DB by this command:
D:\ElektLabs\cebalsol\db>c:\fb\gbak.exe -R -VERBI 100000 -K -REP -PAGE_SIZE 16384 -use_all_space -SE service_mgr "D:\ElektLabs\cebalsol\db\2017_03_15_aerocan.fbk" D:\fbdata\2017_03_15_aerocan.fdb
gbak:opened file D:\ElektLabs\cebalsol\db\2017_03_15_aerocan.fbk
gbak:transportable backup -- data in XDR format
gbak: backup file is compressed
gbak:backup version is 9
gbak: ERROR:Database is probably already opened by another engine instance in another Windows session
gbak: ERROR: failed to create database D:\fbdata\2017_03_15_aerocan.fdb
gbak: ERROR: Exiting before completion due to errors
gbak:Exiting before completion due to errors

In case that service is stops, restore performs without error.
In case of FB3.0.9 restore performs without error with or without service running.

If I copy engine12.dll from FB3.0.9 into FB3.0.10, gbak works fine.

[AlexPeshkoff]

The best way for you to avoid the bug right now is to use xnet:// prefix in the command:

gbak.exe -R -VERBI 100000 -K -REP -PAGE_SIZE 16384 -use_all_space -SE xnet://service_mgr "D:\ElektLabs\cebalsol\db\2017_03_15_aerocan.fbk" D:\fbdata\2017_03_15_aerocan.fdb

[AlexPeshkoff]

BTW - using -SE service_mgr (i.e. w/o xnet://) makes absolutely no sense, you will get same (or 1-2 %%) better performance w/o it, restore anyway runs locally in embedded access process.

[livius2]

@AlexPeshkoff interesting, is this somewhere documented? When i read it, it have sense, but you know, it make sense after seeing it.

---

I have thinked that when i write
127.0.0.1:service_mgr i only write target service (its location) and i send to it only the command, and it work with fastest possible way when it talk with Firebird itself.
So is it really true that -SE xnet://service_mgr do anything with speed? compared to 127.0.0.1:service_mgr ?

[AlexPeshkoff]

xnet:// vs. 127.0.0.1: will sooner of all give better performance - xnet protocol is faster compared with tcp/ip. How big is that difference - depends upon how and where are you using them. In a case of service, restoring DB from backup located on server, better xnet performance is hardly visible, it affects only flow of verbose messages.

[livius2]

it affects only flow of verbose messages.

ty for explaining as i was curious about this aspect, if it affect all process or only communication between service messages

[AlexPeshkoff]

It may affect all data if you restore from stdin using services.

[AlexPeshkoff]

Was fixed by d0e33f1