Interview Questions.

Q1. How Do I Determine If Objects Are Going Into Daos?

You can appearance in the DAOS directory to look that NLO files are being created. Under the DAOS listing are subdirectories for the boxes. Each subcontainer holds forty,000 NLO documents with the aid of default. 

Q2. If I Make The Minimum Participation Size Larger, Will Attachments Stored In Daos Be Moved Back Into The Nsf?

Yes, but not automatically. Changing the minimum participation size inside the DAOS tab of the server document will have an effect on the garage vicinity of any attachments written from that point ahead. If you run a replica-fashion compact (compact -c somefile.Nsf) on an NSF this is already participating in DAOS, attachments which can be in DAOS however not meet the minimum participation length could be saved inline within the resulting NSF. The reference count for the NLO record could be decremented to mirror this. If the ensuing reference count reaches 0, the NLO record becomes a candidate for deletion. 

Q3. Do I Need A Special Client Version To Use Daos?

No. DAOS is a Domino server feature, and is trparent to the purchaser. Any patron (older Notes variations, internet, mobile, and so on.) could be able to study and write attachments to an NSF with DAOS enabled on the Domino server. In eight.5.1, a brand new characteristic become introduced to the Notes purchaser that takes benefit of DAOS to dispose of trmitting attachment records that already exists in the vacation spot DAOS server repository. Other customers will nevertheless work, but they cannot take benefit of this, and could continually trmit the attachment statistics. 

Q4. How Do I Troubleshoot Daos Related Database Problems?

In order to troubleshoot a DAOS related problem off line, or for help to diagnose the problem, the database at the side of all NLO files will want to be furnished. You can achieve a listing of all NLO documents referenced via a database by going for walks the command 'inform daosmgr listnlo ' 

Note that that is most effective vital if the hassle is with the attachment. Otherwise a resync of a database with lacking attachments will bring about 'Ghost' entries within the DAOS catalog, allowing for diagnosis of problems now not associated with the attachments. 

 

Q5. Why Can't I Open Attachments When I Open A Daos Enabled Database Locally?

The DAOS references are best resolved via the Domino server. When you open the database regionally and also you try to open a DAOS attachment you will get the mistake “The item shop database is disabled. : Could now not store to document c:tmpnotesEA312Ddaosdb.Nsf” 

Q6. Why Are Nlo Files Not Being Deleted?

NLO files are wiped clean up (deleted) through the DAOS Prune system this is scheduled to run nightly at 2:00 AM. NLO documents are best eliminated while the DAOS catalog is in a 'Synchronized' kingdom, the NLO refcount is 0, and the NLO became marked deleted longer than the prune c program languageperiod ago. 

You also can run Prune from the console with the command 'inform daosmgr prune prune c program languageperiod'. An c program languageperiod of zero will motive all NLO documents with a refcount of 0 to be deleted without delay. Use caution while right here as you may potentially delete attachments that have never been subsidized up. 

Q7. What Is Lotus Domino?

An IBM server utility platform used for business enterprise email, messaging, scheduling and collaboration. Lotus Domino changed into previously known as Lotus Notes Server and changed into initially the server factor of Lotus Corp's patron-server messaging era.

Q8. Why Do I Get Error When Compacting A Large Database Out Of Daos?

If the ensuing database would exceed the 64GB NSF obstacle with the attachments in-lined within the NSF you then can't compact the database out of DAOS. 

Q9. Why Am I Getting The Error "record Not Found" When Replicating A Daos Enabled Database?

If an NLO report is lacking on one system and that report is replicated, the replicator will document this mistake. This will purpose the replicator to preserve to try to replicate this record on each replication. If this mistake is encountered three times in a row the replicator will abort replicating the database. This can be avoided via setting DEBUG_REPL_TOLERATE_ERRORS but does now not resolve the problem. 

There are two methods to clear up this problem:

Restore the NLO document.

Run 'fixup -j -D' to delete the record referencing the missing NLO.

Q10. Why Don't I See The "use Domino Attachment And Object Service" Option Under File -> Application -> Properties?

If you are not jogging a Notes eight.Five consumer or later you will now not see that option. 

If the database is not ODS 51 or greater you will no longer see that alternative. Make sure CREATE_R85_DATABASES=1 is set within the notes.Ini and compact -c the database. Adding the '-DAOS on' flag will at once allow DAOS before the compact. 

Q11. Why Are Some Daos Nlo Files Missing?

One possible cause is the Anti-virus software discovered an endemic and 'quarantined' the record. This can manifest whilst compacting a database into DAOS and a virus is observed on an attachment in the database. 

You ought to set your anti-virus settings to match you records directory. 

Also deleting NLO documents from the OS will cause problems with DAOS. 

Q12. Is There One Nlo File Per Nsf, Or One Per Attachment, Or...?

There is one NLO file created for each specific attachment some of the NSF documents collaborating in DAOS on a single server. Each NLO file carries the records for a unmarried precise attachment. If there are more than one attachments in an NSF, or even in a unmarried file, a separate NLO record will be created for each particular one.

Q13. How Do I Determine Which Databases Are Daos Enabled?

Run the command 'inform daosmgr dbsummary'. It will display the listing of DAOS enabled databases, their ticket counts and their DAOS nation. 

Q14. How Do I Determine When The Daos Catalog Needs Resync?

When the DAOS catalog tritions to the kingdom of "NEEDS RESYNC" a DDM occasion is fired a good way to perceive the database that first brought on the catalog to go into this state. This records can be determined inside the DDM database or in the log.Nsf. 

The following is a list of operations that motive the DAOS catalog to trition to the kingdom of "NEEDS RESYNC": 

replica a DAOS enabled database into the records directory from the OS

delete a DAOS enabled database from the OS

rename a database from the OS

delete an NLO from the OS (will trition to "NEEDS RESYNC" while the NLO is tried to be opened.)

restore a database without delay to the records directory

If you can't decide what motion brought on the catalog to "NEEDS RESYNC" and it maintains to occur, debug code have to be enabled. Setting 

DAOS_LOGGING=c:debugdaos.Txt STATE_CHANGE 

will log all DAOS nation change hobby. Also enabling DAOS_LOGGING will reason DAOS to output the decision stack to the server console that precipitated the catalog to trition to this country. That need to receive to guide along with the daos.Txt record to assist troubleshoot the hassle. 

To clear the "NEEDS RESYNC" state run a resync through getting into the command 'inform daosmgr resync'. Note that at the same time as the catalog is in this country DAOS will preserve to operate usually. However deletion of NLO files by means of the PRUNE undertaking could be postponed till the catalog is in the "SYNCHRONIZED" nation once more. 

Q15. Why Can't I Compact A Database Containing Tickets With Missing Attachments?

This can manifest because of the reasons above. When you come upon this trouble you may want to run 'fixup -j -D'. The -j transfer is for traction logged databases and the -D switch will motive documents with DAOS tickets pointing to invalid or missing NLO documents to be deleted. These files are deleted with out a deletion stub so they may mirror back in. 

Q16. Why Are New Attachments Added To A Database Not Creating New Nlo Files?

Verify that the database is DAOS enabled and the fame is Read/Write. This is carried out through getting into the command 'tell daosmgr dbsummary dbname' 

It is also possible that the attachment does no longer meet the minimal DAOS length requirement. Remember that the size of the object is in comparison to the DAOS Minimum after it's far compressed. 

The attachment already exists. Attachments are written to a brief NLO file in order that the MD5sum may be calculated. If that checksum matches an current NLO, the transient document is deleted. In this example the refcount for the item is incremented.

A trouble turned into encountered while creating an NLO record. In this case the fallback is to at once create a trendy, inline NSF attachment. If anything is going wrong along the way (cannot create NLO file because of out of disk area, write blunders, permission, and so on.), the DAOS operation returns manipulate to the regular NSF attachment handling code. Worst case, it will get in-lined in the database. 

Q17. I Have Clustered Servers, And They All Have Daos Enabled. Can I Share A Single Daos Repository Between Clustermates?

No. Each server collaborating in DAOS must have its personal separate DAOS garage direction.

Q18. How Can I Enable Daos Automatically For All New Mailfiles?

To permit DAOS on all new mailfiles created on the server, modify the mail85.Ntf (template) to have 'Use Domino Attachment and Object Service' enabled in the advanced homes. When you pick out the mail85.Ntf, it'll routinely consist of settings. This putting will not take effect till a database is at ODS 5@To create databases through default as ODS fifty one, allow the parameter 'Create_R85_Databases=1' within the server's notes.Ini record. (While you are modifying the template, it is a good idea to enable the 'Use LZ1 compression for attachments' property additionally to shop even more area.) 

Q19. How Do I Troubleshoot Non-daos Related Database Problems?

A DAOS enabled database will function commonly so long as attachments are not opened. So in case you are troubleshooting a trouble that is not DAOS associated you do not need to provide the NLO files. 

Q20. Why Does Daos Require Traction Logging To Be Enabled?

Storing attachments in DAOS involves coordinated movements for three extraordinary documents: the Notes database receiving the attachment, the DAOS report, and the daos catalog (index). Traction logging is used to guarantee that we will put those distributed portions of the traction again into a regular state after a server crash (T/L redo) or catastrophic failure (get better roll T/L forward). Traction logging is a requirement for DAOS and you actually cannot use the characteristic without it. Overall, the use of traction logging increases the consistency and integrity of all NSF information. 

The one vicinity where T/L is elective with DAOS is mail boxes (e.G. MAIL.BOX). T/L mail packing containers is non-obligatory. There is a performance enhancement that lets in optimized routing of messages with attachments to DAOS enabled mail files. 

Not permitting T/L on mailboxes does now not have an effect on the disk area financial savings from the use of DAOS. It most effective disables a performance optimization.