Subject | Re: Backup database with spaces in path, does not work |
---|---|
Author | Dan Cooperstock |
Post date | 2007-12-18T21:10:25Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...>
wrote:
Solution 1 is a problem if you are backing up remotely, because there's
no reliable way for one computer to know what another computer's 8.3
filenames are.
Solution 2 doesn't seem to work - I get error messages like:
gbak: ERROR:Unable to complete network request to host "'C".
Solution 3 would work for the database file, but not for the backup
file or the log file (to be specified with -y).
Would using the Services API eliminate all of these problems? Or is
gbak just showing me the same problems the Services API would have?
wrote:
> 1. If it is on a FAT32 disk or partition that has been formattedI'm having the same problem.
> under an older version of Windows (NT 3 or 4, or Win9x) you will need
> to use the old M$ 8.3 format for long or "illegal" pathnames, i.e.
> D:\CLIENT~01\etc., without quotes.
>
> 2. If it is an NT 5 or higher NTFS partition, try it with single
> quotes in lieu of double quotes around the path.
>
> 3. Try setting the path as an alias (in aliases.conf, no
> quotes). You can then use the alias instead of trying to pass the
> difficult path string in the command line.
>
> ./heLen
Solution 1 is a problem if you are backing up remotely, because there's
no reliable way for one computer to know what another computer's 8.3
filenames are.
Solution 2 doesn't seem to work - I get error messages like:
gbak: ERROR:Unable to complete network request to host "'C".
Solution 3 would work for the database file, but not for the backup
file or the log file (to be specified with -y).
Would using the Services API eliminate all of these problems? Or is
gbak just showing me the same problems the Services API would have?