Rob Kirkland commented on Dec 6, 2012

Re: Archiving and recovering IBM Lotus DAOS-enabled databases

When you make an archive or a replica or a copy of a database on the same server as the original, the new database has the same properties as the original. That's why the new database will have pointers to .nlo files just as the original did. If before you make the archive/copy/replica you disable DAOS on the original database, the new database will include all attachments in the database itself, not in the DAOS repository. Alternative to making an archive/copy/replica of the original, you could simply run compact -c -DAOS off against the original, which would move all attachments back into it, prior to, say, moving the original permanently off the server to tape archive. If the database is going to be compressed on its way to archive, you could also (I don't know if it would be helpful or not) add the -N and -V switches to your compact command to internally decompress the database's design and data preparatory to archiving. Or you could disable design and data compression in advanced properties of the original before making an archive/copy/replica of it.

Paul Thomas Lan2Lan commented on Nov 2, 2012

Re: Archiving and recovering IBM Lotus DAOS-enabled databases

Restoring NLOs - Database restored to a different server

Using a dedicated restore server for each and every server is not practical. I think this needs a serious rethink.

Leaving the customer to magic up some process to handle restoring encrypted NLOs in an enterprise environment is not good practice for an enterprise platform.