That's odd that you LOST space...??

Actually, I believe you would need to un-daosify all of the databases to
pull the files between 64k and 1MB back INTO the .nsf. Then you'd need to
prune and then re-daosify so that only the files >1MB are daosified. But
what you've done now is still leaving the existing 64k+ size objects in
DAOS and only new files >1MB would be put into DAOS. At least this is my
understanding of how it would work.


---------------------------------------------------

Thanks,
Chris
Personal Blog: http://cwhisonant.dtdns.net <http://cwhisonant.dyndns.org/>
Work Blog: https://www.socialbizug.org/blogs/lotusnut

On Wed, Dec 24, 2014 at 9:56 AM, <rob@xxxxxxxxx> wrote:

Changed the DAOS items from a minimum size of 64,000 bytes to the
recommended 1,048,576 bytes.
Ran an offline copy style compact on all Domino servers on this machine.
Fired up the servers and ran “tell daosmgr prune 15"
When that was done, tell daosmgr resync.
We're now at:
Auxiliary storage:
System ASP . . . . . . : 1435 G
% system ASP used . . : 85.8605

And we were down to 70% used.

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/daos-best-practices


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


--
This is the Lotus Domino on the IBM i (AS/400 and iSeries) (Domino400)
mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.