Subject | Re: Backup in a client PC |
---|---|
Author | Adam |
Post date | 2008-03-16T23:51:34Z |
--- In firebird-support@yahoogroups.com, "Gustavo" <gusm@...> wrote:
Helen was not too subtle :-) I know that I don´t have to use mapped
drives to access a Firebird database and I promise you (and of course
Helen) that I won´t do it. :-)
worked right. I repeat that I understand that I must not use mapped
drives to access a database. I also wanted to show that if I want to
make a backup of a local database, and generate the FBK file in a
network drive, I can do it writing the location of the FBK file (I
repeat, the FBK file, not the FDB file) using a mapped drive. Is this
a bad thing too?
No, the path of the fbk file (on either a backup or restore) can be
any legal filesystem location (including a network resource), although
you may find performance to be - lets just call it suboptimal. ;)
<snip />
So the right statement (executed from the client PC2) is:
"PC1:C\MyDataBases\MyDB1.FDB" "C:\MyBackups\MyDB1.fbk"
Does windows like that fdb path? Should it not rather be:
gbak -t -v -user SYSDBA -password <password>
"PC1:C:\MyDataBases\MyDB1.FDB" "C:\MyBackups\MyDB1.fbk"
This should work providing PC1 has Firebird installed/working, that
C:\MyDataBases\MyDB1.FDB is a valid database on **PC1**, and that
C:\MyBackups\MyDB1.fbk is a valid path on **PC2** (ie folder must
exist and have write permissions etc)
any parameters, to copy the files I need or, in another words, to
install the embedded server in the way I need. Is there a way to do that?
Well the embedded server is nothing special. It needs no registry keys
and does not install a service. We have one rich client we deliver
with an embedded database.
Innosetup support is beyond the scope of this list, but I am sure
there is a method to extract the files. ;)
This is literally what we put inside the base folder (based on 1.5.5
embedded):
aliases.conf
\doc\*.*
\firebird.conf
\firebird.log
\firebird.msg
\gds32.dll <-- Renamed fbembedded.dll
\ib_util.dll
\icudt30.dll
\icuin30.dll
\icuuc30.dll
\IDPLicense.txt
\intl\*.*
\IPLicense.txt
\msvcp71.dll
\msvcr71.dll
\Readme.txt
\udf\*.*
Plus our executable.
There is no magical installation procedure, extract the files, done.
Adam
>were really useful for me. I am very grateful to you because of that.
> Adam:
>
> I read with very much atention your post and Helen´s post and they
Helen was not too subtle :-) I know that I don´t have to use mapped
drives to access a Firebird database and I promise you (and of course
Helen) that I won´t do it. :-)
>wanted to show that I tried many posibilities just to see which one
> With the examples of gbak statements in my previous post I only
worked right. I repeat that I understand that I must not use mapped
drives to access a database. I also wanted to show that if I want to
make a backup of a local database, and generate the FBK file in a
network drive, I can do it writing the location of the FBK file (I
repeat, the FBK file, not the FDB file) using a mapped drive. Is this
a bad thing too?
No, the path of the fbk file (on either a backup or restore) can be
any legal filesystem location (including a network resource), although
you may find performance to be - lets just call it suboptimal. ;)
<snip />
So the right statement (executed from the client PC2) is:
>gbak -t -v -user SYSDBA -password <password>
"PC1:C\MyDataBases\MyDB1.FDB" "C:\MyBackups\MyDB1.fbk"
Does windows like that fdb path? Should it not rather be:
gbak -t -v -user SYSDBA -password <password>
"PC1:C:\MyDataBases\MyDB1.FDB" "C:\MyBackups\MyDB1.fbk"
This should work providing PC1 has Firebird installed/working, that
C:\MyDataBases\MyDB1.FDB is a valid database on **PC1**, and that
C:\MyBackups\MyDB1.fbk is a valid path on **PC2** (ie folder must
exist and have write permissions etc)
> So now I only have the question I made in my previous post about theway to call Firebird-2.0.1.12810-0-Win32.exe (or another file) with
any parameters, to copy the files I need or, in another words, to
install the embedded server in the way I need. Is there a way to do that?
Well the embedded server is nothing special. It needs no registry keys
and does not install a service. We have one rich client we deliver
with an embedded database.
Innosetup support is beyond the scope of this list, but I am sure
there is a method to extract the files. ;)
This is literally what we put inside the base folder (based on 1.5.5
embedded):
aliases.conf
\doc\*.*
\firebird.conf
\firebird.log
\firebird.msg
\gds32.dll <-- Renamed fbembedded.dll
\ib_util.dll
\icudt30.dll
\icuin30.dll
\icuuc30.dll
\IDPLicense.txt
\intl\*.*
\IPLicense.txt
\msvcp71.dll
\msvcr71.dll
\Readme.txt
\udf\*.*
Plus our executable.
There is no magical installation procedure, extract the files, done.
Adam