This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Bella Frofanalyetsi
Jun 10, 2014, 7:17 AM
32 Posts
topic has been resolvedResolved

DAOS - Copy NLOs for a sepecifid database

  • Category: Administration
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags: DAOS NLO COPY
  • Replies: 2

Hi,

My Domino is currently R7, and I am forced each year to split my application because of the large size of the attachments. Last year the attachment size grows in a way that I had to split my application twice during the year.

I am planning to upgrade my client to Domino 9.x in order to benefit from DAOS.

I have read some documentation about DAOS and users' feedback and it seems pretty reliable and efficient.

However, one issue that I am still worried about, that I would like to share for feedback.

Let's say when I enable DAOS, my database size for this year (nsf) grows to 1 GB only while the NLOs files size is 100 GB.

I have other databases on the same server and many NLOs files not related to this database.

I have 2 scenarios here:

  1. If I decided to move this database to a new test server. I cannot bring back NLOs from DAOS into the nsf because the size will exceed 64 GB and the db will crash :) Is it possible to copy only NLOs for this database and move to the new server? as I don't want to end up with 1 TB of data that I won't be needing.
  2. If I won't to create a new copy of this database on the same server, the NLOs will be shared, right? in this case is it totally safe to work on this new copy and manipulate attachments without worrying that the original ones are corrupted?

Let me know what you think and should I make this move to DAOS or implement my own archiving mechanism by creating many nsf databases for attachments only each 30 GB of size and programmatically splitting.

 

thanks,

Samer

~Sven Nimgerosterflar
Jun 10, 2014, 1:10 PM
46 Posts
Response
Answers below:


1.        If I decided to move this database to a new test server. I cannot bring back NLOs from DAOS into the nsf because the size will exceed 64 GB and the db will crash :) Is it possible to copy only NLOs for this database and move to the new server? as I don't want to end up with 1 TB of data that I won't be needing.

Answer:  Yes it is possible to copy NLOs from one server to another but careful there is a catch.  NLOs are by default encrypted with the server id. You must disable nlo encryption if you want to be able to copy them from one server to another.  You can disable encryption by using the notes.ini parameter DAOS_Encrypt_NLO = 0 .  You can generate a list of NLOs associated with this db by using the "Tell DAOSMgr ListNLO " more info here http://www-12.lotus.com/ldd/doc/domino_notes/9.0/help9_admin.nsf/f4b82fbb75e942a6852566ac0037f284/cb50bcc32337e41885257b19005b51fc?OpenDocument

2.        If I won't to create a new copy of this database on the same server, the NLOs will be shared, right? in this case is it totally safe to work on this new copy and manipulate attachments without worrying that the original ones are corrupted?

Answer:  I am not sure I understand the question fully.  If a copy or a replica is created on the same server then the attachments will be shared.  However, if the attachment is truly corrupted then even the copy or the replica will have the corrupted attachment as it is shared between the databases.
If your question is more related to what if I create a copy or replica and modify one of the attachments, what happens to the original database and original attachment?  The answer is that when the attachment is modified a new NLO is created.  The new copy will reference this newly modified attachment while the original database will continue to reference the original NLO.

Daos is a great tool but ensure that you properly tune the space needed for the attachments.  Make sure you keep an eye on the DAOS catalog and that it is kept in sync (when the catalog is not in sync pruning of old attachment stops) and make sure you disable daos encryption if you want to be able to move NLOs between servers.  

 

~James Revelulyader
Jun 10, 2014, 7:19 PM
145 Posts
Some thoughts
1) You could enable DAOS on the other Server and then create a new replica of your current database onto the other server and it will work putting the attachments directly into the DAOS store on the second server...  

2) That should work just fine... The copy of the database is made... As you change attachments in the copy, it will create a new attachment and store it in DAOS as a new .nlo... The original replica still has the intial attachment and it remains in DAOS...  Matching attachments are ref-counted in the DAOSCAT.NSF and will not be pruned until that count goes to zero and the prune interval expires....

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal