Submitted by Vladimir Tankhimovich on Nov 12, 2011 9:23:58 AM

Re: Create_R85_Log

I agree with Duco. I followed the instructions last night, and now, after 16 hours, my server is still recovering, running consistency checks on mail files. Most major tasks are affected.

Submitted by Duco Bergsma on Jun 1, 2010 4:47:16 AM

Create_R85_Log

The procedure to "Bring down the server. Back up existing transaction logs, then delete them. Set Create_R85_Log=1 in the server NOTES.INI and restart the Domino server to have new logs created using the updated format." is incomplete and even dangerous. I performed this on a bad preforming as/400 that had a need for disk cache battery replacement. This might have caused delayed write operations pending in the Translogs when Domino was shut down. Removing the TXN files and starting Domino caused may database corruption beyond repair (restore needed from back-up).

In my opinion, it would be a better procedure to disable Transactional logging (notice a small shutdown delay) and removing the TXN files and enabling Transactional logging.

I don't know yet if this has issues for servers running DAOS.

Submitted by TG Sullivan on Sep 20, 2009 7:30:14 PM

Please elaborate on the value of the option and issues

Does "updated" mean that 8.5 will auto-adjust to a block size detected somehow? Why is a block size different than 512 be better? Should this process take additional time or number of reboots? How does SAN usage for the TranLogs impact this? Does this change the base format in way that would impact backup solutions like Symantec BackupExec or TSM?

Submitted by Thomas T. Hampel on Sep 5, 2009 10:06:45 AM

Concerns?

The document should also describe any possible concerns, (if any) e.g. for backup software

Submitted by Daniel Silva on Apr 7, 2009 12:56:24 AM

I/O block alignment

Can you elaborate on the advantage that properly aligned I/O blocks have over the previous format?

Thanks!