I've got a 2-computer network with \\SERVERA and \\CLIENTB.  CLIENTB accesses a database
on SERVERA through a remote session S1.  I want to use CREATE BACKUP to backup some tables
onto CLIENTB's disk.  When I use EDBManager to create a local store on CLIENTB under S1,
the file dialog shows me CLIENTB's folders and I select one, e.g. C:\BACKUPEDB.  But when
the CREATE BACKUP command executes, the backup file is actually placed in SERVERA's disk
(creating C:\BACKUPEDB on SERVERA if necessary).

If I specify \\CLIENTB\BACKUPEDB when creating the local store, the CREATE BACKUP command
fails, saying that I haven't provided the proper username/password (to access CLIENTB from
SERVERA).  Maybe I could get around this on my home network by fiddling with permissions
and the guest account, but that won't be an option in the final application.

When I open a local session S2, the local stores really are local, but then CREATE BACKUP
complains that the database doesn't exist (since it is defined in the remote session S1).

Am I misunderstanding the meaning of "local store"?  Is there some trick or option I
should be using to persuade EDB that the local store belongs on the computer that is
running EDBManager (or the final application)?

Thanks in advance for anyone's help.


(Also, a minor documentation error:  in RESTORE DATABASE, the [TABLES...] and [INCLUDE
CATALOG] options are incompatible, but the syntax diagram doesn't separate them with the |
character).

Charles,

> onto CLIENTB's disk.  When I use EDBManager to create a local store on
> CLIENTB under S1,
> the file dialog shows me CLIENTB's folders and I select one, e.g.
> C:\BACKUPEDB.  But when
> the CREATE BACKUP command executes, the backup file is actually placed in
> SERVERA's disk
> (creating C:\BACKUPEDB on SERVERA if necessary).

The dialog always show the local directory structure, so it's almost useless
when dealing with remote connections.
Independently of  what the dialog shows, when using remote sessions paths
are *always* relative to the server.

> Am I misunderstanding the meaning of "local store"?  Is there some trick
> or option I
> should be using to persuade EDB that the local store belongs on the
> computer that is
> running EDBManager (or the final application)?

No, no tricks are needed. What you must do is:
- Create a local store, say "Server-Bk" using the *remote session*. This
store will be located in the server and will be used as the destination for
backups.
- Create a local store, let's call it "Client-Bk", using a *local session*
in the client computer.
- Create a remote store, "BKatServer", pointing to the "Server-Bk" store at
the server, using the *local session* in the client computer.

To execute the backup :
- Use BACKUP DATABASE ... TO STORE "Server-Bk" through the remote connection
to create the backup in the server store
- Execute a COPY FILE .... using the local session to move the backup from
the store "BKatServer" to the store "Client-Bk"
Note that you must have a configuration file local to the client computer
just to hold the definitions of the stores.

--
Fernando Dias
[Team Elevate]

Charles,

<< Am I misunderstanding the meaning of "local store"? >>

Yes.  You cannot access local stores on the client machine from a remote
session.  It has no idea that they even exist, since a remote session is not
using any local catalogs at all.  If you want to make backup and then
transfer it to a client, you need to do the following:

1) Make sure that you have a local store and remote store defined on the
client machine using a local session.  Likewise, make sure that you have a
local store defined on the server machine using a remote session.

2) Backup the database to the local store *on the server* using a remote
session.

3) Using a local session and the local and remote stores defined on the
client machine, copy the backup file from the remote store down to the local
store.

4) You will now have a backup file on the client machine in the path pointed
to by the local store.

<< (Also, a minor documentation error:  in RESTORE DATABASE, the [TABLES...]
and [INCLUDE CATALOG] options are incompatible, but the syntax diagram
doesn't separate them with the | character). >>

Why do you think that they are incompatible ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks to Tim and Fernando for the explanations.



> << (Also, a minor documentation error:  in RESTORE DATABASE, the [TABLES...]
> and [INCLUDE CATALOG] options are incompatible, but the syntax diagram
> doesn't separate them with the | character). >>

> Why do you think that they are incompatible ?

Using both clauses throws this error:
ElevateDB Error #1301 Error restoring the database mem (Restoration of individual tables
is not permitted when also restoring the database catalog)

Charles,

<< Using both clauses throws this error:
ElevateDB Error #1301 Error restoring the database mem (Restoration of
individual tables is not permitted when also restoring the database catalog)
>>

Yes, but only if you don't specify *all* of the tables in the database.  I
know it sounds stupid, but there's an internal reason for it.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> je napisal v
sporoèilo news:7FB5327A-4A26-4D07-A87C-E5336C7EF1C0@news.elevatesoft.com ...
> Charles,
>
> << Am I misunderstanding the meaning of "local store"? >>
>
> Yes.  You cannot access local stores on the client machine from a remote
> session.  It has no idea that they even exist, since a remote session is
> not using any local catalogs at all.  If you want to make backup and then
> transfer it to a client, you need to do the following:
>
> 1) Make sure that you have a local store and remote store defined on the
> client machine using a local session.  Likewise, make sure that you have a
> local store defined on the server machine using a remote session.
>
> 2) Backup the database to the local store *on the server* using a remote
> session.
>
> 3) Using a local session and the local and remote stores defined on the
> client machine, copy the backup file from the remote store down to the
> local store.
>
> 4) You will now have a backup file on the client machine in the path
> pointed to by the local store.
>

Tim,

as you stated  in 1) there must be defined two stores, local and remote on
local side and one store as local store on remote side. When defining the
local store on remote side there is no room for password which is required
if you access remote store from client side. Which password for access
remote store is to be used?

Iztok Lajovic

Iztok,

<< as you stated  in 1) there must be defined two stores, local and remote
on local side and one store as local store on remote side. When defining the
local store on remote side there is no room for password which is required
if you access remote store from client side. Which password for access
remote store is to be used? >>

The login username and password required for a remote store are actually any
valid login that you would normally use for logging in a session.   What EDB
does "under the covers" is simply instantiate a remote session that it uses
to contact the EDB Server, using the information that you provided when you
created/altered the remote store.

--
Tim Young
Elevate Software
www.elevatesoft.com