i have the same issue with our document-imaging backups. this is due to
zillions of itty-bitty files being backed up, see below. btw, the
TXNGROUPMAX option only applies to files being backed up, not moved or
reclaimed. [...]
Sounds like this could very well be my problem. Thanks!
Shame I can't fix it for extant data. I might not be able to fix it at
all: if the content managment system sends just a page, or just a
packet of metadata, the txngroupmax will be irrelevant: transaction
size = 1.
- Allen S. Rout
