+ Similar Entries
|
|
Annoying Domino URL ...Blog: Pascal DavidPascal David Updated  Ratings
0
Comments
0
|
|
|
Sametime Entry 8.5 C...Blog: AnythingAroun...Maurice Teeuwe Updated Ratings
0
Comments
0
|
|
|
8.5.1 UNFAIL - Part ...Blog: Erik BrooksErik Brooks Updated Ratings
2
Comments
0
|
|
|
8.5.1 UN-FAIL! The F...Blog: Erik BrooksErik Brooks Updated Ratings
0
Comments
6
|
|
|
maintain your consol...Blog: AnythingAroun...Maurice Teeuwe Updated Ratings
0
Comments
0
|
+ Bookmarks
+ Archive
+ Blog Authors
Resynching DAOS reference counts
For Domino 8.5, there is no background thread that automatically resynchs DAOS reference counts. My recommendation is to add a manual resync to your regularly scheduled maintenance routines, preferrably during non-peak hours. You can set up a program document as follows:
|
Ratings
1
|
| IBM Lotus Connections | Help | Tools | About |
|---|---|---|---|
Comments (3)
Hi Chad, How does DAOS work in a Cluster team ?
I've tested this in a two node Domino-cluster and the first server
I enabled and did the ncompact -C created the daos\0001 + daos\0002
directories and filled them up as expected.
when done I did the ndaosmgr resync and when that finished i
started the domino-server (node1)
I then did a full replication with node2, but all the db's at node2
where still filled with attachments and no files in the daos\*
tree.
I stopped node2 and did the ncompact -C there as well, but only got
a lot of error-messages like this:
09.01.2009 13:33:34 The database
C:\Lotus\Domino\Data\mail\eih24133.TMP was unable to write to file
D:\Lotus\Domino\Data\DAOS\0002\27BBC89450C120ABC12575390044FDEC2439127BBC89450P.nlo:
Release 8.5 HF1 December 29, 2008
I couldn't find any info on a proper procedure for clustered
servers.
Any tips ?
Dag, both server documents have to have DAOS enabled and Domino restarted. Then you should just need to compact -c the databases on both servers so that they can created the DAOS folders and objects.
One question - your log message is showing that Domino Data is both
on C: and D:. Is your D: drive a local drive or a file share on
node2? It appears that you're doing it right. Are there any
security restrictions in that daos tree on node2?
@1 - Make sure you have enabled DAOS on both servers and have restarted. We've already seen one PMR with a similar symptom where the restart was not done. Then run "compact -c -daos on" to move existing attachments to the DAOS repository. If that doesn't work, please review the suggestions in this document: http://tinyurl.com/8y6pze