Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Backup tool
Fri, Jan 2 2009 8:52 PMPermanent Link

John
Hello.

Does there exist any simple backup tool for DBISAM, that backups a remote database to a local folder (not on the remote server)?

Thanks,
John
Sat, Jan 3 2009 12:48 AMPermanent Link

"Robert"

"John" <eydunl@post.olivant.fo> wrote in message
news:9265B365-36E7-4691-A884-6307B9415C58@news.elevatesoft.com...
> Hello.
>
> Does there exist any simple backup tool for DBISAM, that backups a remote
> database to a local folder (not on the remote server)?
>

The backup command requires a destination folder name, which has to be
relative to the server. If the server can recognize your local machine by
name, then you should be able to backup to a local folder. Something like
the server knowing thaqt \\localmachine\ is your local backup folder.

Robert

> Thanks,
> John
>

Tue, Jan 6 2009 8:10 AMPermanent Link

John
Robert, thanks for the reply.

The point of taking a backup is often to get a copy of the databases of the server, in case the server should crash, and become unavailable. How
do you normally solve this issue with DBIsam? I would expect that someone has done a tool for backing databases up to a remote location?

Cheers,
John



"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote:


"John" <eydunl@post.olivant.fo> wrote in message
news:9265B365-36E7-4691-A884-6307B9415C58@news.elevatesoft.com...
> Hello.
>
> Does there exist any simple backup tool for DBISAM, that backups a remote
> database to a local folder (not on the remote server)?
>

The backup command requires a destination folder name, which has to be
relative to the server. If the server can recognize your local machine by
name, then you should be able to backup to a local folder. Something like
the server knowing thaqt \\localmachine\ is your local backup folder.

Robert

> Thanks,
> John
>
Tue, Jan 6 2009 10:58 AMPermanent Link

"Robert"

"John" <eydunl@post.olivant.fo> wrote in message
news:E80ABFB4-6DB1-4495-926E-FA0F97FF4EF5@news.elevatesoft.com...
> Robert, thanks for the reply.
>
> The point of taking a backup is often to get a copy of the databases of
> the server, in case the server should crash, and become unavailable. How
> do you normally solve this issue with DBIsam? I would expect that someone
> has done a tool for backing databases up to a remote location?
>

Well, as I indicated in the other posting, the server has to have access to
wherever the backup will be stored so if the server knows where
\\johnscomputer\databasebackups is at, then no problem. BTW I do only
"logical" backups, to make copies of the databse before I do any mass
changes. For physical backups that would allow for restore in case of a
crash, I let the user decide how to backup the whole server.

IMO DBISAM does not handle this well at all, but I already lost that
argument with Tim, so no point restarting it. I'm sure you can come up with
some way outside of DBISAM to copy the backup file. What I do (for what it
is worth) is that I require that my users have a subfolder with the EXACT
name BACKUP under the database folder. Then for C/S I get the database
folder as per the server (see my recent posting on how to do that) and for
file sharing I simply get the database directory, add the '\BACKUP' string
to it, and place the DBISAM backup there. If the user wants a backup stored
someplace else, they have to copy the file themselves outside of my
application. Not the most elegant solution, but works so far. Also it makes
it trivial to switch from file sharing to client server and back, which is a
requirement on all my applications. I can have a program doing a backup in
file sharing mode and another doing a restore in C/S, and both would find
the backup file in the same place.

Robert

>

Tue, Jan 6 2009 11:56 AMPermanent Link

John
Thanks for the explanation how you solve this issue. I appreciate it.



"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote:


"John" <eydunl@post.olivant.fo> wrote in message
news:E80ABFB4-6DB1-4495-926E-FA0F97FF4EF5@news.elevatesoft.com...
> Robert, thanks for the reply.
>
> The point of taking a backup is often to get a copy of the databases of
> the server, in case the server should crash, and become unavailable. How
> do you normally solve this issue with DBIsam? I would expect that someone
> has done a tool for backing databases up to a remote location?
>

Well, as I indicated in the other posting, the server has to have access to
wherever the backup will be stored so if the server knows where
\\johnscomputer\databasebackups is at, then no problem. BTW I do only
"logical" backups, to make copies of the databse before I do any mass
changes. For physical backups that would allow for restore in case of a
crash, I let the user decide how to backup the whole server.

IMO DBISAM does not handle this well at all, but I already lost that
argument with Tim, so no point restarting it. I'm sure you can come up with
some way outside of DBISAM to copy the backup file. What I do (for what it
is worth) is that I require that my users have a subfolder with the EXACT
name BACKUP under the database folder. Then for C/S I get the database
folder as per the server (see my recent posting on how to do that) and for
file sharing I simply get the database directory, add the '\BACKUP' string
to it, and place the DBISAM backup there. If the user wants a backup stored
someplace else, they have to copy the file themselves outside of my
application. Not the most elegant solution, but works so far. Also it makes
it trivial to switch from file sharing to client server and back, which is a
requirement on all my applications. I can have a program doing a backup in
file sharing mode and another doing a restore in C/S, and both would find
the backup file in the same place.

Robert

>
Wed, Jan 7 2009 8:45 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

John,

<< The point of taking a backup is often to get a copy of the databases of
the server, in case the server should crash, and become unavailable. How do
you normally solve this issue with DBIsam? I would expect that someone has
done a tool for backing databases up to a remote location? >>

You can write/use a server-side procedure to move the backup file back to
the client.  Normally, we expect that backups are moved to removable media
or a machine that is accessible to the server machine so that a server crash
is not an issue.

ElevateDB resolves this issue with the advent of remote stores and the
ability to copy files from remote stores to local stores, and vice-versa.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image