Subject | Re: IBBackupService |
---|---|
Author | Adam |
Post date | 2006-01-19T23:49:07Z |
--- In firebird-support@yahoogroups.com, Robert martin <rob@c...>
wrote:
I doubt this has anything to do with spaces. You can not connect to a
Windows Classic server via direct file access like you can with
Superserver. You must instead use a TCP Loopback connection.
I do not know if the spaces are handled incorrectly by IBX, or
whether your problem is some name resolution issue. A better approach
may be to use aliases, so the connection string is independent of
where the database sits, (which may change from time to time as new
partitions are added etc).
Adam
wrote:
>working
> Hi
>
> We have been using IBBackupService to do backups. This has been
> fine. We just swapped from SS to Classic and we now get errors.We set
> the DatabaseName to 'c:\path with spaces\DbName.fdb'. In SS thisworks
> fine, in classic we get a DB not found 'C:\path'. It seems to notbe
> able to handle spaces in the file name. What can I do about this?I
> also note that in SS Gbak from the command prompt I can specify myServerName:c:\path
> source db as above however in classic I need to use
> with spaces\DbName.fdb. I tried using this format for databasenamebut
> it fails (in SS and classic).Rob,
>
> Help !
I doubt this has anything to do with spaces. You can not connect to a
Windows Classic server via direct file access like you can with
Superserver. You must instead use a TCP Loopback connection.
I do not know if the spaces are handled incorrectly by IBX, or
whether your problem is some name resolution issue. A better approach
may be to use aliases, so the connection string is independent of
where the database sits, (which may change from time to time as new
partitions are added etc).
Adam