At 01:57 PM 25/02/2009, you wrote:

>I´ve installed firebird server 2.1 on our server, instead of 1.5 (used by provider) is this a serious problem?..maybe this can cause this metadata bugs?..

Yes, it can. And they can be bugs of a non-obvious type, as well.

>I did this long time ago.

Then it is also a long time ago since you attempted backup and restore, I guess. But if you ever restored this database under Fb 2.1 then it is no longer of the correct on-disk structure to guarantee it will work properly with the software.

>..yes..i know i made a big mistake but i think that our provider is taking advantage of this...am i rigth? they said "sorry we can´t support you any more"

Taking advantage? I don't think so, at all. They dealt you a system that is designed to work with a database with on-disk structure 10 or 10.1 and you screwed it up by running a server designed to deal with databases with higher structures. If they are not willing to fix up your mess for free, they are quite justified. You broke the rules that constrain us all to respect the integrity of our databases.

Perhaps you should take a more reasonable approach, and ask them to quote you a price for repairing your database and reverting it to ODS 10.x. I guess it depends on how much you insulted them and how much "humble pie" you are willing to eat. ;-)

If you want to try to do it yourself (under the SAFE conditions previously described) you could retrieve the Fb 1.5 version of gbak and use it, under your running Fb 2.1 server, to make a -t[ransportable] backup of your database. You might then be able to restore that backup as a Fb 1.5 database, by restoring it under a running Fb 1.5 server.

If you have attempted to use any parts of nBackup on the live database during its existence on the Fb 2.1 server, I'd tell you that your chances of success are not good.

./heLen