--- In firebird-support@yahoogroups.com, "Woody" <woody-tmw@...> wrote:

>
> From: "Adam" <s3057043@...>
> > > A> localhost:c:\myfb.fdb
> > >
> > > how do you manage network paths, if you do?
> >
> > You can't so I don't.
> >
> > If you were talking unc paths, you could resolve the database
> > hostname, but there would be no way to identify the path of the file
> > as seen by the database server from the client.
> >
> > On a side note, hopefully no-one is silly enough to leave their
> > database files exposed over a network share?
> >
>
> Actually, this isn't a hard thing to do at all. My own backup utility
> program converts mapped paths to the server and local path name

Hmmm.

Server:
-------

c:
cd\
md data\firebird\databases\mydb\
net share FBDB=c:\data\firebird\databases

Client:
------

\\server\fbdb\mydb\mydb.fdb

How does your client application magically figure out the details of
this share?

The only possible way your program could work is if it used the C$
share and which would allow you to conjur up something like:

\\server\c\data\firebird\databases\mydb\mydb.fdb

That is a huge assumption.

Actually, one other method would be to write a service that runs on
the server that the client could pass in the unc path and the server
could then run the backup on behalf of the client (as the server could
identify the true drive and path for a share.

. Although

> this sounds "dangerous", in my experience, most administrators have

access

> to all network directories for ease of maintainence, etc. When

doing remote

> backup/restore operations, it's much easier to pick files from the

open file

> dialog instead of typing in local pathnames when using a workstation to
> perform the actions. Most "normal" users don't have/need access to those
> directories but then again, most users won't be doing backup/restores
> either.

In my experience, administrators are told that the fdb file is off
limits, and direct file access to the database by backup software,
antivirus software or alike are a pretty reliable way to corrupt the
database.

They are getting a bat file (wrapper around gbak) to make their hot
backup. Most backup software can be configured to execute a task
before running, so the fbk file is simply created in the backup path.

Adam