Re Change DAOS Minimum object size
Re Change DAOS Minimum object size
Hello Khandakar
Increasing the DAOS attachment size
is often needed when there are too many attachments in the catalog
You want to change the Attachment Size
within DAOS e.g. from 64K to 1 MB
Make sure that you take a backup of
your databases and Nlos before applying these settings .
It could be that your last backup was
a while ago and not all nlos are up to date.
Make sure there are no unreferenced
*.nlo files before you start
1.- Do a DAOS resync.
to re-count all the references to NLO files.
This takes a lot of system resources.
Schedule it so that it will have the least impact on production operations.
2.- Tell DAOSMgr Prune 0
[0 = number of days old - today ]
This command deletes all DAOS un-referenced
objects encrypted with the local server key
3.- There still could be un-referenced
nlo file left after this operation.
Pruning will only delete nlo files encrypted
with the local server key
When nlo files have been copied
manually from a different server, then they are un-referenced
Make a backup of the un-referenced nlo
files
Delete the un-referenced nlo files
4.- Change the attachment size in the
Admin client > config tab > DAOS tab > Minimum size of objects
before Domino will store in DAOS
Note:
- Do not use special characters such
as commas or periods when entering the minimum size.
- Run the server console command
'Tell DAOSMgr Status' to make sure that the new attachment size value
is recognized by the server. If the new size is not shown yet, check
it after the server restart
- Restart the Domino server to enable
the new minimum size.
5.- Run Compact - C on all DAOS participating
database
via the Admin client : Files
> [ ctrl + shift ] to select multiple db's > tools : compact
: Copy-style compact (compact -c) will cause a write of all
attachments.
Running copy-style compact (compact
-c) results in attachments of both the old and new size
to be stored in the NSF : e.g. the 64 k and the 1 MB
The old 64 K NLO files will be
marked as deleted, and will be removed by prune.
6.- All files participating in
DAOS will need to be compacted if you want to apply the new size
everywhere.
Run 'tell daosmgr dbsummary' to
get a list of all the participating NSF files, and ensure that copy-style
compact was run on all of them.
Sometimes mail.box (and/or mail1.box,
mail2.box, etc) can be overlooked .
7.- Run the prune command again to remove
the small nlo files
Wait for the "object deletion"
interval to pass for prune to remove the small .nlo files.
If you have taken a recent backup and
would like to delete the small files more immediately you can run the following
command:
tell daosmgr prune <#_of_days_since
_last_full_backup>
Hope this helps
TomOC