Hi

I just returned from Africa, where I installed a DBISAM multiuser
application for 10 concurrent users. It will be an interesting test
about DBISAM's robustness: power fails often, there is only one UPS for
the server, users don't have much experience using computers, there is
no technical staff around, low network reliability, some old hardware,
etc.. I wonder how long till the first support call requiring table
repairs or index rebuilds...

--
Fernando Dias
[Team Elevate]

Fernando,

<< I just returned from Africa, where I installed a DBISAM multiuser
application for 10 concurrent users. It will be an interesting test about
DBISAM's robustness: power fails often, there is only one UPS for the
server, users don't have much experience using computers, there is no
technical staff around, low network reliability, some old hardware, etc.. I
wonder how long till the first support call requiring table repairs or index
rebuilds... >>

Very interesting.  Please keep us posted on what happens.  As long as the
data is on a file server or database server, then the chance of corruption
should be pretty low given the UPS on the server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> As long as the
> data is on a file server or database server, then the chance of corruption
> should be pretty low given the UPS on the server.

I hope so
I'm using C/S, with a customized DBISAM server to automate backups.
The database is automatically backed up every 8 hours to another HD on
the server.

--
Fernando Dias
[Team Elevate]

Fernando,

<< I hope so
I'm using C/S, with a customized DBISAM server to automate backups. The
database is automatically backed up every 8 hours to another HD on the
server. >>

That's a good idea, and should help quite a bit also.  If the database isn't
too large, you could probably get away with backing it up more often also.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> That's a good idea, and should help quite a bit also.  If the database isn't
> too large, you could probably get away with backing it up more often also.

The database isn't large; it's only 24Mb by now, and I expect it to grow
to around 80Mb to 120Mb in a year.
The backup strategy is to do a backup at 7:00, before they start
working, another one at 15:00 and a final one at 23:00 after the end of
the working day. Each backup overwrites the previous within the same
day. So, only the last backup of each day is preserved.


--
Fernando Dias
[Team Elevate]

Fernando Dias [Team Elevate] wrote:
> Tim,
>
>> That's a good idea, and should help quite a bit also.  If the database
>> isn't too large, you could probably get away with backing it up more
>> often also.
>
> The database isn't large; it's only 24Mb by now, and I expect it to grow
> to around 80Mb to 120Mb in a year.
> The backup strategy is to do a backup at 7:00, before they start
> working, another one at 15:00 and a final one at 23:00 after the end of
> the working day. Each backup overwrites the previous within the same
> day. So, only the last backup of each day is preserved.
>

I would prefer to keep at least one backup (e.g. from the previous day).
 If a backup stops working midway, you may be left with no complete backup.

--
Aage J.

Aage,

> I would prefer to keep at least one backup (e.g. from the previous day).
>  If a backup stops working midway, you may be left with no complete backup.

But, that's what I'm doing.
Every morning, at 7:00, a new backup file is created. This new file is
overwritten at 15:00 and again at 23:00. The next morning a new backup
file will be created leaving the previous backup untouched.
This way I always have a complete snapshot at 23:00 of each working day
since the server started and in addition, with some luck, a complete and
"good" snapshot of the same day with, in the worst case 8 hours old.

--
Fernando Dias
[Team Elevate]

Tim

So far so good - only one support call, but not related to DBISAM.
Everything is working good, no corruption, no need to restore from
backups, nothing! (And I'm sure they are using the app .
DBISAM rocks!

--
Fernando Dias
[Team Elevate]

Fernando,

<< So far so good - only one support call, but not related to DBISAM.
Everything is working good, no corruption, no need to restore from backups,
nothing! (And I'm sure they are using the app . DBISAM rocks! >>

Cool.  I'm glad everything is working okay.

--
Tim Young
Elevate Software
www.elevatesoft.com