Hi Robert, I guess this is pretty well documented elsewhere on the
Ibphoenix site, but you will face a number of issues, all quite easy to
resolve. In no particular order you need to address:
UDFs they are different and have a suffix .so, not .dll.
visibility of the database - who 'owns' it is different in Linux.
what tools do you use to maintain the database? Flamerobin is popular,
but others are available; I use Ibexpert, paid for, but there is a free
version. You would run this on a Windows machine targeting a remote
database.
As an example, I copied a customer database to a Raspberry PI running a
version of Linux from a dual Xeon machine running MS Server and after
about 1/2 hour it was all up and running. It just took a bit of
investigation about user rights, udfs.
Good luck.
Alan
Alan J Davies
Aldis
On 26/02/2016 12:20, robert robert@redcor.ch [firebird-support] wrote:
> Hi there,
> this is my first post to this list.
>
> I will be charged with the task to move a firebird database running on
> windows to some other means.
> I know nothing much yet, as the original developer is not easily available.
>
> Now I have a number of questions:
> - is it possible to move a database from one os to an other?
> - could this be done by just moving files or by creating a dump /
> restore cycle?
> - If moving from windows to linux is not easily feasible would it be
> possible to move the database from a remote
> windows server to a local windows box?
>
> I very much appreciate your help
> robert
>
> [Non-text portions of this message have been removed]
>
>
Posted by: Alan J Davies <alan.davies@aldis-systems.co.uk>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu there.
Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
No comments:
Post a Comment