Nando,

Why does the connection string solve this, is there some kind of blocking
going on using the local connection?

If this is hte case, the backup and restore problems we have could be caused
by this - interesting. We thought they were just random / intermit.
problems.

ACj.
"Duilio Foschi" <dedalus@...> wrote in message
news:3.0.1.32.20020301130116.00769494@......

> Jason,
>
> Nando Dessena gave the right hint:
>
> >you should use a full connection string
>
> This solved the problem.
>
> Ciao
>
> Duilio
>
>
> At 19.15 28/02/02 -0000, Jason Chapman wrote:
> >He's backing up....
> >
> >We get this sometimes on backup, randomly with servers with plenty of

space.

> >We shrug and start teh backup again, it's like restores just stopping
> >without completing. We have never put the time is to try and work out

any

> >commonality.
> >
> >How many processors does your server have?
> >Did you run out of disk space on the backup drive?
> >
> >
> >
> >> > gbak -B -user SYSDBA -pas masterkey db.gdb db.bk
> >>
> >> you should use a full connection string (eg

server:drive:\path\database)

> >> for restore.
> >> If restoring to a local machine, you can omit the server designator,

but

> >> use a full path.
> >
> >
> >
> >
> >
> >To unsubscribe from this group, send an email to:
> >ib-support-unsubscribe@egroups.com
> >
> >
> >
> >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>