MVBase 2.0, all updates. Sometimes the power drops down there on the
weekends, have a UPS but only for 10 minutes, when we bring the system
back-up we have lost data for like the past week or so. I have
back-ups but I do not understand why it is losing data....no other
sites do...

HELP!!!, any input would be appreciated...thanks

Get a larger UPS and/or tie the UPS to the host with software that monitors
the UPS status. Issue an orderly shut down when UPS power becomes low. It
will take some time to perform the shut down. Be sure to include that time
in your reserve power calculations.

Slamming shut U2 data files causes corruption. It may not be readily
apparent that a data file is corrupt. This is because only a small portion
of the file may be missing records or have incomplete records.

I'm glad you have a data back-up plan in force. So many shops don't.


<shaun (AT) jitmall (DOT) com> wrote

I can rapidly shutdown any other system I have and this does not happen

When I lose data I mean, I lost a program a wrote a week ago....It is
not just that it has to be in a stat file or something

Albino Timberwolf wrote:

I don't recall what flushing mechanisms are available for mvBASE but
it's obvious that the database isn't flushing memory to disk.
1) Look into getting the Windows box to flush more often - check the
SysInternals.com website for free utilities. (Get um while they're
hot, SI/WI was acquired by Microsoft)
2) Check your event log, I'll be it's bulging with info about what's
been happening.
3) Check with RD, something is really wrong with your configuration.
I'm guessing mvBASE is running with non-admin permissions that prevent
it from writing to the file system (very weird).
4) Until the real problem is fixed, shutdown/reboot the system
manually once per day/evening, or automate the process with a script:
have mvBASE shutdown at 3am and have a Windows scheduled task boot it
at 3:30, or something similar. See if it's mvBASE that's not flushing
or if it's Windows. You may need to reboot Windows periodically too.
5) Backup, Backup, Backup, oh, and I forgot... Backup every night.

HTH
T

"shaun (AT) jitmall (DOT) com" wrote:

Shaun, if you can power off other systems and (apparently) not lose data,
something is different between those systems. Find the difference. One thing
you might check is something Tony mentions. Check your cache settings.
"Write through" is not the same as "write back". Flushing the system
nightly, as Tony suggests, should clear all temporary storage areas and
force all pending writes.

A rapid shutdown isn't quite the same as a power failure. A rapid shutdown
should close open files and flush buffers to disk. A power failure won't do
that.

Tony, I don't know if you said it loud enough. BACK UP EVERYTHING EVERY
CHANCE YOU GET.

And now it's time to preach:
Losing only one day's worth of data = production hours lost multiplied by
the avereage hourly wage of the users. Let's see now...50 users multipled by
10 dollars per hour multiplied by 14 hours (8 hours lost plus 6 hours lost
to re-enter the lost data)... is $7,000.00. (A conservative estimate of a
small scale loss.) That could pay for a VERY nice backup solution. And, as
a fringe benefit, you get to keep your job. Some backup software will even
compare the current data vs. the data on the backup device. If you have this
feature, use it. Backup, verify the backup, then take a copy off site.

"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote