Hey all,
We're currently considering replacing our 2 very large AIX TSM servers with
a large number (maybe 10 or so) of smaller, Linux based servers. The reason
for the change is to reduce the impact of hardware failure, allow for
database maintenance within a reasonable window and (less important
to the client, to sort through and decide what to back up.
With millions of entries (which it appears you have), it can take awhile. We
had a situation with a terribly fragmented DB, where this pause was lasting
10-15 hours on some boxes. We did an unload/load, and they have all but one
gone back to &
the client, to sort through and decide what to back up.
With millions of entries (which it appears you have), it can take awhile. We
had a situation with a terribly fragmented DB, where this pause was lasting
10-15 hours on some boxes. We did an unload/load, and they have all but one
gone back to &quo
fragmented DB, where this pause was
lasting 10-15 hours on some boxes. We did an unload/load, and they have all
but one gone back to "normal" (the one that didn't has 5.5Million entries,
and does not have enough memory on the client box).
On Tue, 8 Jun 2004, Anderson, Matt wrote:
>
I'm experiencing behavior on some NT nodes where, in the middle of a
scheduled backup, there will be a long pause where no activity seems to
occur. It would appear to occur after the backup of one drive finishes, but
before the next one starts. For example, see this log excerpt from this
morning:
