Den 2011-07-14 08:49 skrev Thomas Steinmaurer såhär:

> is anybody using nbackup in high load environments successfully? I have
> a report of a guy, which has ~ 400 clients on Classic (although not all
> connected at the same time) and nbackup seems to be culprit for database
> corruption, especially corrupting medium-sized active tables at the time
> of nbackup is doing it's job. He went the 2.1 route up to 2.1.3,
> although he had no chance to upgrade to 2.1.4 yet.

I have FB 2.1.x (not sure which) and the database is about 55 Gbyte in
size with two tables containing onver 150 million records each (and
several other tables). The load is low - only an internal web app with
about five concurrent users.

During devel I tried using nbackup, but when running a batch job against
this database during nbackup lock state, I received some kind of error
about transaction commit. Don't remember the details now unfortunately,
but I still have the need to du file based backup during operation, so I
will investigate it closer sooner or later. I'll let you know if I get
the error again and find any reason, workaround, or reproducible test case.

> I know that nbackup wasn't that reliable from the beginning and improved
> over each release. Basically I wanted to get some user feedback, if
> nbackup is reliable in rather high load environments.

Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64