| Subject | Re: [firebird-support] Firebird 1.5 to Firebird 1.0 |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-05-03T22:13:39Z |
At 09:20 PM 3/05/2005 +0000, you wrote:
to a lower one. So the prospect is to extract the metadata to a script,
recreate the DB on Fb 1.0 and pump the data.
Practically, if it's possible that the Fb 1.5 server has been connecting to
a Fb 1.0 database all along and they have never run on a restored backup,
then a filecopy taken from a shut-down server might be accessible by Fb 1.0.
Find out the ODS version of the DB - you can use gstat -h for this. ODS 10
is a Fb 1.0 database, ODS 10.1 is Fb 1.5.
the host that is running Fb 1.5. If it's a question of Windows server
licences, a Linux host would be the obvious solution. If you've done the
right thing with aliases in the Fb 1.5 development, the impact on client
code would be minimal or none.
Another alternative would be to co-install Fb 1.5 on the new server,
setting its service ports (gds_db and a RemoteAuxPort) to different values
than those being used by Fb 1.0. This might or might not be practicable,
since the port number would be required in the connection string for client
apps connecting to Fb 1.5. Easy if you are using runtime values for
logins, "work" if you are hard-coding them. A lot would depend on resource
usage, too.
Of course - as always - don't dive into such an exercise without testing to
death on copies and also making sure that you can take restorable backups.
./hb
>Hello,Theoretically, no. You can upgrade to a higher ODS but you can't downgrade
>
>We have a client that wants to move his database to another server.
>He is using Version 1.5 of Firebird but the new server is using
>Version 1.0.
>
>Is it possible to backup the database using 1.5 and then restoring
>to 1.0? I know we haven't used anything new in version 1.5 that
>isn't supported by version 1.0.
to a lower one. So the prospect is to extract the metadata to a script,
recreate the DB on Fb 1.0 and pump the data.
Practically, if it's possible that the Fb 1.5 server has been connecting to
a Fb 1.0 database all along and they have never run on a restored backup,
then a filecopy taken from a shut-down server might be accessible by Fb 1.0.
Find out the ODS version of the DB - you can use gstat -h for this. ODS 10
is a Fb 1.0 database, ODS 10.1 is Fb 1.5.
>To avoid a bunch of questions about why I need to do this ... TheIt does kinda beg the question, then, of why they are so desperate to kill
>new server has about 10 databases on it with about 20 gigs of data.
>They don't want to go through an upgrade to version 1.5 for a few
>weeks because of the time it will take to backup and restore all the
>databases.
the host that is running Fb 1.5. If it's a question of Windows server
licences, a Linux host would be the obvious solution. If you've done the
right thing with aliases in the Fb 1.5 development, the impact on client
code would be minimal or none.
Another alternative would be to co-install Fb 1.5 on the new server,
setting its service ports (gds_db and a RemoteAuxPort) to different values
than those being used by Fb 1.0. This might or might not be practicable,
since the port number would be required in the connection string for client
apps connecting to Fb 1.5. Easy if you are using runtime values for
logins, "work" if you are hard-coding them. A lot would depend on resource
usage, too.
Of course - as always - don't dive into such an exercise without testing to
death on copies and also making sure that you can take restorable backups.
./hb