What is the difference between running NSD and NSD -info?

Technote (FAQ) Problem What is the difference between running "NSD" and "NSD -info"? Solution The difference is in the information that is collected: NSD -info Running an "NSD -info" on a Domino server displa s:

s stem information notes!ini environment variables data and program director contents dis" drive s stem memor statistics!"

#ottom line: When ou want to collect onl s stem information$ run "NSD -info"! NSD Running "NSD" captures:

all the s stem information that ou get with "nsd -info" as well as the current processes that are running
#ottom line: When ou see a performance issue and need to get a sense of both the s stem information and what is running$ run an NSD! Another way to position the distinction To get the list of processes that are running$ NSD uses %"touches"& the '(D!N#) file$ which is the 'rocess (D table of all Notes*Domino processes! The "NSD -info" does not touch the "pid!nbf" file! )or more information on the pid!nbf file$ refer to the technote titled$ "What is the '(D!N#) file?" %+,--./,,& Troubleshooting Windows NSD: When NSD is not generating a "!log" file successfull $ it is a good idea to run "NSD -info"! Running NSD -info avoids touching the "pid!nbf" file! (f it runs to completion$ it shows that the nsd e0ecutable is capable of running! 'erhaps there is a problem with the '(D!N#) file! Refer to the technote titled$ "What is the '(D!N#) file?" %+,--./,,&!

What is the PID.NBF file?

Technote (FAQ) Problem What is the '(D!N#) file? Solution The '(D!N#) file is the 'rocess (D table of all Notes*Domino processes! )or the lifetime of a Notes client*server$ each process start or shutdown causes the process (D %'(D& to be added to or removed from the '(D!N#)! (n a Win/- environment$ NSD uses the pid!nbf to determine$ in case of a crash$ if the failing process is a Notes*Domino process! The '(D!N#) file is also used b Domino in a partitioned server environment! The file allows the processes associated with each partitioned server to be identified! The '(D!N#) is located in the Domino1Data director ! The '(D!N#) file can be renamed or deleted! The file is recreated the ne0t time the Domino server is restarted! (f the '(D!N#) file is deleted while the Domino server is running$ NSD will be unable to determine the Notes processes to attach to until the server is restarted %when the new '(D!N#) is created&!

How does the Compact function behave when using Database Properties

Technote (FAQ) Problem (n 2otus Domino3$ if ou use the )ile menu --4 Database --4 'roperties -4 (nfo tab --4 5ompact option$ how does 5ompact wor" and behave? Solution When triggered from the Database 'roperties (nfo panel$ three "inds of compacting can occur: cop -st le compaction %-2&$ in-place compaction %-b&$ and in-place with file si6e reduction compaction %-#&! Note the casesensitivit of the commands! NOT : 5ompacting a database does not necessaril reduce its si6e! Types of compacting: -- (f the Notes database re7uires structural changes %t picall a change of 8DS 9on-dis" structure:&! then a cop -st le compaction will be performed %e7uivalent to -2&! -- (f the Notes database is logged %Transactional 2ogging enabled&$ then a simple in-place compaction will be performed %e7uivalent to -b&! -- (f the Notes database is not logged %Transactional 2ogging disabled&$ an in-place with file si6e reduction compaction will be performed %e7uivalent to -#&! NOT : (n Domino ; releases$ the re7uest from the Notes 5lient to compact a database was changed! This functionalit is now handled b the <pdate tas" so that the connection to the Domino server is not tied up waiting for a mail file to be compacted! The <pdate tas" places the 5ompact re7uest in a deferred 7ueue and processes it when it has free c cles!

Com act o eration not erformed immediatel! on a bus! ser"er

Technote (FAQ) !uestion =ou want to e0ecute a compact operation on a 2otus Notes3*2otus Domino3 database from within Notes! (n the Notes database$ from the )ile menu$ ou choose Database --4 'roperties --4 (nfo panel --4 5ompact! The following message appears in the status bar: "#our re$uest to compact this database is now being carried out%" >owever$ after waiting several minutes$ ou notice that the si6e of the database reported on the 'roperties (nfo panel has not changed! =ou verif that the Notes database is not logged %Transactional 2ogging is enabled& and that ou have access to the 5ompact button %manager access in the ?52& since these could be reasons wh the database si6e has not reduced! Answer This issue was reported to @ualit Angineering as S'R+ B2#SC@DT?) and has been addressed in Domino release ;!E!/! A0cerpt from the 2otus Notes and Domino Release ;!E!/ FR fi0 list %available at http:**www!ibm!com*developerwor"s*lotus&: S'R+ B5>NCGFCH. - ?dded the new Notes!ini variable "DebugI5ompactI(mmediatel " to allow compact re7uests from clients to be performed immediatel %li"e in RC& rather than 7ueued! %Regression in ;!E!& Refer to the <pgrade 5entral site for details on upgrading Notes*Domino! Additional &nformation (n Domino ; and J releases$ the re7uest from Notes to compact a database was changed! This functionalit is now handled b the <pdate %updall& tas" so that the connection to the Domino server is not tied up waiting for a mail file to be compacted! The <pdate tas" places the 5ompact re7uest in a deferred 7ueue and processes it when it has free c cles! 8n a bus Domino server$ the <pdate tas" might ta"e from minutes to hours to process re7uests for compacting$ especiall during pea" hours! =ou can issue the following Domino console command %without 7uotes& to see how man compact re7uests were e0ecuted b <pdate: "show stat <pdate!'ending2ist!'rocessed!5ompactions" (n some cases$ increasing the number of <pdate tas"s and configuring <pdate to use a separate thread to do full te0t inde0ing reduces the time involved! To enable multiple <pdate tas"s$ add the following parameter to the serverKs notes!ini file: 'pdaters ( ) %number of desired <pdate tas"s to run on the server&! To configure <pdate to use a separate thread to do full te0t inde0ing$ add the following parameter to the serverKs notes!ini file: <pdateI)ullte0tIThread L ,! NOT : )or the <pdateI)ullte0tIThread parameter$ setting this variable to , allows use of a separate thread to do full te0t inde0ing so that long full te0t

inde0es donKt dela view updates! # default$ view updates and full te0t inde0 updates are driven b the same thread! Giew updating will still wor" in "updall!"

What is a Notes database?

A Notes database is a single file that contains multiple documents. A database generally contains information about a particular area of interest, such as the forms and policy documents for a department, or it might contain documents of a similar type, such as e-mail messages. In addition, some companies create "discussion databases," where employees can post responses to particular topics. Documents in Notes databases contain rich text, pictures, objects, and many other types of information. ost databases are stored on one or more Domino ser!ers, accessible by many users. "hese are called shared databases. Databases that are used only by you and reside on your computer are called local databases. Notes comes with templates you can use to create your own databases. "hese templates ha!e the file extension N"#. "he Notes databases ha!e the extension N$#. Notes databases also ha!e access control lists %A&'s( that control the actions people, groups, and ser!ers can perform in the database. #or example, one person may be able to create and read documents in a database, where another person may be allowed only to read documents in the same database.

#nown limitations of Notes and Domino $.%

Technote (FAQ) Problem What are some of the "nown limitations of Notes and Domino ;!0? 'lease refer to this document for similar information in Notes*Domino C!0: "Dnown limitations of Notes and Domino C!0" %+,,M.,J;&! Solution

The following tables summari6e the "nown ma0imum limits of various Notes and Domino ;!0 features as noted in the Notes*Domino documentation! Note: Specificall $ the first table originated in the Notes ; 5lient >elp! The second table originated in the Domino ; Designer >elp$ and has been edited to contain onl uni7ue items that are not also listed in the Notes 5lient table! * TT&N* STA+T D ,imits of Notes &tem What is the ma0imum si6e of a database? What is the ma0imum si6e of te0t fields? What is the ma0imum si6e of a rich te0t field? What is the ma0imum si6e of a single paragraph in a rich te0t field? ,imit The ma0imum 8S file si6e limit %up to CNH#& /-D# %storage&O /-D# displa ed in a viewKs column 2imited onl b available dis" space up to ,H# CND#

What is the ma0imum amount of CND# Te0t %Summar & data per document? >ow man levels of responses in /, levelsO /EE$EEE documents a hierarchical viewO how man documents at each level? >ow man columns can be included in one table? CN

>ow man rows can be included -MM in one table? >ow man views can be added to No limitO however$ as the number of views a database? increases$ the length of time to displa other views also increases >ow man columns are allowed in a view? >ow man documents can be imported into a view? >ow man cascading views are allowed in a database? -J. ten-character columnsO dependent upon + or characters per column Documents totaling at least /MED -EE

What is the ma0imum value %in --!;M inches& ou can enter for margin si6e? What is the ma0imum value %in inches& ou can enter for page si6e cropping? NC

What is the ma0imum point si6e -ME ou can select*print? >ow man documents are allowed in one view? <p to the si6e of the database$ with a ma0imum of CNH#

What is the ma0imum number of 2imited onl b available dis" space documents that can be e0ported to Tabular Te0t? What is the ma0imum number of P.ME names %total ?52 si6e is limited to entries in an ?ccess 5ontrol 2ist? /-;C; b tes& What is the ma0imum number of ;M Roles roles in an ?ccess 5ontrol 2ist? WhatKs the ma0imum password length allowed on an (D? CN b tes %C/ characters for single-b te character sets but onl -, characters for some double-b te languages&

What is the ma0imum number of /-D of names in the Fembers te0t field

contacts allowed in a group in the 'ersonal ?ddress #oo"? What is the ma0imum number of )or individual names and private groups recipients in a single mail which e0pand locall $ ,MD#O for public message? groups which e0pand on a server$ MF#

APP,&-AT&ON D S&*N Table of Notes and Domino .nown limits The following table summari6es the "nown ma0imum limits of various Notes and Domino features! &tem 5haracters in names /a0imum limit Database Title: .C b tes )ilenames: 8n Windows3 and <N(Q3 platforms minimum of -MM and*or 8S limitsO on local Facintosh wor"station /, )ield names: /Giew names: CN )orm names: /?gent names: /P /EEE %limited to P CND total length for all field names&! =ou can enable the database propert "?llow more fields in database" to get up to --$J./ uni7uel -named fields in the database! 2imited onl b database si6e! NC NC -ME <p to the ma0imum si6e of the database 2imited onl b available dis" space J users P-,$EEE entries

)ields in a database

)orms in a database Fargin si6e %in inches& 'age cropping si6e %in inches& 'oint si6e to select or print Documents in a view Documents that can be e0ported to tabular te0t ?uthori6ed users on a multiple password (D 8utline entries in an outline

Notes allows ou to paste a ma0imum of -MM rows into a table! A0ceeding this limit will ield the error$ "No more than -MM rows allowed in a table"! +elated information Dnown limitations of Notes and Domino C!0

-ross +eference information Segment Product -omponent Platform 2otus Domino Designer 1ersion ;!E dition

Fessaging 2otus ?pplications Domino

Support R downloads 4

#nown limitations of Notes and Domino &.%

Technote (FAQ) Problem What are some of the "nown limitations of Notes and Domino C!0? 'lease refer to this document for similar information in Notes*Domino ;!0: "Dnown limitations of Notes and Domino ;!0" %+,---JE;&! Solution The following table summari6es the "nown ma0imum limits of various Notes and Domino C!0 features as noted in the Notes Domino documentation: &tem Database si6e Te0t field si6e Rich te0t field si6e /a0imum limit The ma0imum 8S file si6e limit -- %up to CNH#& /-D# %storage&O /-D# displa ed in a viewKs column 2imited onl b available dis" space up to ,H#

Response levels in a /, levelsO /EE$EEE documents hierarchical viewO number of documents per level 5haracters in names Database Title: .C b tes )ilenames: 8n Windows3 and <N(Q3 platforms minimum of -MM and*or 8S limitsO on local Facintosh wor"station /, )ield names: /Giew names: CN )orm names: /?gent names: /P /EEE %limited to P CND total length for all field names&! =ou can enable the database propert "?llow more fields in database" to get up to --$J./ uni7uel named fields in the database! CN -MM No limitO however$ as the number of views increases$ the length of time to displa other views also increases 2imited onl b database si6e! -J. ten-character columnsO dependent upon + or characters per column

)ields in a database

5olumns in a table Rows in a table Giews in a database

)orms in a database 5olumns in a view

Documents imported Documents totaling at least /MED into a view 5ascading views in a -EE database Fargin si6e %in inches& NC

'age cropping si6e %in NC inches& 'oint si6e to select or -ME print Documents in a view Giews are architecturall limited to ,/EH#! >owever$ since databases are limited to CNH#$ the views cannot grow larger than the db! So in practice$ views can grow as large as the db si6e limit of CNH#! 22 Documents that can be e0ported to tabular te0t Antries in an ?ccess 5ontrol 2ist %?52& Roles in an ?ccess 5ontrol 2ist 2imited onl b available dis" space

P.ME names %?52 si6e is limited to /-;C; b tes& ;M Roles

Results of the First Server Setup

)unning the setup of the first ser!er modifies the notes.ini file so that it contains all of the re*uired information to start the ser!er. It also creates se!eral files, Domino databases, and Domino documents. "he following tables outline in more detail what is created, where it is stored, and what its purpose is. "he following tables discusses some of the settings that are added by the setup program to the notes.ini file+ Setting Example Notes,rogram NotesProgram=c:\progr am files\ lotus\domino Directory=c:\program Directory files\lotus\ domino\data $er!er.ey#ileN ServerKeyFileName=ser ver.id ame Domain=Adventure Domain $er!er"as/s
ServerTasks=Update, Replica, Router, Stats, AMgr, Adminp, Sched, CalConn, RunJava ISpy, HTTP ServerTasksAt1=Catalog, Design

Description -xecutable directory name.

Data directory name %for non-partitioned ser!ers(. $er!er ID file name. Domain name. "as/s to start at ser!er startup.

$er!er"as/sAt x Port ,orts Disabled,orts 001as'an,ort 'og

"as/s to run once per day at scheduled times. &onfiguration settings for the port dri!er.

TCPIP=TCP, 0, 15, 0 Ports=TCPIP

-nabled ports. DisabledPorts=LAN0,SP Disabled ports. X,COM2,COM4,COM5 $$HasLanPort=1 "he ser!er has or does not ha!e a 'AN port.
Log=LOG.NSF,1,0,7,40000

$ettings for the log file+ file name, log option %default is 2, log to the console(, 3 %the third setting not used at this time(, number of days to retain log information, maximum number of bytes log file can contain. 'e!el of detail to be logged for that tas/. 'e!el of detail to be logged about networ/ connections, including passthrough connections

'456task

Log_Replication=1

,assthru6'og'e Passthru_LogLevel=0 !el

"he setup creates the following Domino databases, all stored in the data directory+

Database &ertification 'og Domino Directory $er!er 'og )eports

File Name Description certlog.ns 'ogs all registrations of ser!ers and users. f names.nsf log.nsf 7sed to administer the Domino networ/. $tores the log of messages that ha!e been displayed on the ser!er console in the last se!en days. 5enerates and stores mail usage reports. "he first administrator8s mail database is also created, in a sub-folder of the data directory called mail. "he file name is based on the administrator8s name.

reports.ns f Administrator8s mail\msmit h.nsf %for mail file example(

"he following documents are created in the Domino Directory+ Document ,erson document $er!er document 5roup document 5roup document Description ,erson document for the first administrator. $er!er document for the first ser!er. 5roup document for the 'ocalDomainAdmins group. "he name of the first administrator is automatically added to this group. 5roup document for the 'ocalDomain$er!ers group. "he name of the first ser!er is automatically added to this group. Any additional ser!ers registered later will also automatically be added to the group. "he group type is initially set to " ultipurpose". "his should be changed to "$er!ers". 5roup document for the 4therDomain$er!ers group. "his group is initially empty. It is intended to list ser!ers in other Domino domains that connect with this domain. "he group type is initially set to " ulti-purpose". "his should be changed to "$er!ers".

5roup document

&ertifier document &ertifier document for the organi9ation. &ertifier document &ertifier document for the first organi9ational unit. "his document is only created if the option to create an 47 was selected.

"he following IDs are created+

ID

Stored in the...

4rgani9at Data directory ion 4rgani9at Domino ional 7nit Directory, attached to the &ertifier document $er!er Data directory Administr Domino ator Directory, attached to the ,erson document. ay also be stored as a file, if that option was selected

Default File Name cert.id

Description

&ertifier ID for the entire Domino organi9ation.

oucert.id &ertifier ID for the first 47. "his file is only created if the option to create an 47 was selected.

server.id $er!er ID for the first ser!er. user.id 7ser ID for the first administrator.

"he following tables describe the options you can use with the &ompact ser!er tas/. "he first column lists the options as they appear when you run &ompact using the "as/ - $tart tool or the #iles tab in the Domino Administrator. "he second column lists the e*ui!alent commandline options that you use when you run &ompact using a console command or using a ,rogram document.

ompact ! "asics

#ption &ompact only this database or folder %"o specify databases to compact using the #iles tab, select the databases in the files pane.(

ommand!line e$uivalent database path $pecify any additional options after the database path.

Description "o compact a database in the Domino data folder, enter the file name, for example $A'-$.N$#. "o compact databases in a folder within the data folder, specify the database path relati!e to the data folder. #or example, to compact all databases in the folder DA"A:$A'-$, specify $A'-$. If you choose "&ompact all databases" %or don8t specify a database path at the command line( &ompact compacts all databases in the data folder and in folders within the data folder.

#or more information on database path, see %2()unning &ompact using a console command.

ompact ! #ptions
#ption ommand!line e$uivalent Description &ompacts all databases with a specified percent of unused space. #or example, if you specify 23, databases with 23; or more recorded unused space are compacted. Note that the unused space calculation is not always a reliable measure of unused space. Discards built !iew indexes. 7se this option to compact databases just before you store them on tape, for example. Does copy-style compacting. &ompacts databases without con!erting to the current release file format of the ser!er that stores the databases or re!erts databases in the current release file format to the pre!ious release file format. #or example, on Domino < and more recent ser!ers, this option compacts Domino = databases without con!erting them to the Domino < file format and con!erts Domino < databases to the Domino = file format. "his option uses copy-style compacting.

&ompact database only if -$ percent unused space is greater than x percent

Discard any built !iew indexes

-D

.eep or re!ert database to pre!ious format

-)

ompact ! St%le

#ption In-place %recommended(

ommand!line e$uivalent -b

Description 7ses in-place compacting and reco!ers unused space without reducing the file si9e, unless there8s a pending structural change to a database, in which case copy-style compacting occurs. "his is the recommended method of compacting. 7ses in-place compacting, reco!ers unused space and reduces file si9e, unless there8s a pending structural change in which case copy-style compacting occurs. If you use transaction logging, do full database bac/ups after compacting completes. 7ses copy-style compacting. 7se this option, for example, to sol!e database corruption problems. -nables users to continue to access databases during compacting. If a user edits a database during compacting, compacting is canceled. "his is useful only when copy-style compacting is done. -nables compacting to continue e!en if it encounters errors such as document corruption. 4nly used for copy-style compacting.

In-place with file si9e reduction

->

&opy-style

-c

&opy-style+ Allow access while compacting

-'

&opy-style+ Ignore errors and proceed

-i

ompact ! &dvanced
"he ad!anced compact options are not a!ailable through the &ompact tool in the #iles tab of the Domino Administrator.

#ption' Document table bitmap optimi9ation+ 4ff

ommand!line e$uivalent -f

Description Disables "Document table bitmap optimi9ation" database property. Does copy-style compacting. -nables "Document table bitmap optimi9ation" database property. Does copy-style compacting. Disables "Don8t support speciali9ed response hierarchy" database property? in other words, support speciali9ed response hierarchy. Does copy-style compacting. -nables "Don8t support speciali9ed response hierarchy" database property? in other words, do not support speciali9ed response hierarchy. Does copy-style compacting. Disables transaction logging.

Document table bitmap optimi9ation+ 4n

-#

Don8t support speciali9ed response hierarchy+ 4ff

-h

Don8t support speciali9ed response hierarchy+ 4n

-1

-nable transaction logging+ 4ff -nable transaction logging+ 4n

-t

-"

-nables transaction logging. 7se &ompact - " when a database is open or closed. If you use &ompact - " on a database that is closed, logging is enabled but the &ompact is not logged until the database is opened? therefore, logging is not a!ailable until you reopen the database. Disables "Don8t maintain unread mar/s" database property? in other words, maintain unread mar/s. -nables "Don8t maintain unread mar/s" database property? in other words, do not maintain unread mar/s.

Don8t maintain unread mar/s+ 4ff

-u

Don8t maintain unread mar/s+ 4n

-7

@ $elect "$et ad!anced properties" before you enable or disable any of these properties.

ompact ! &rchive
Ahen you use the document archi!ing tool to archi!e and delete documents in a database, you can use the following &ompact options to archi!e documents if the database is located on a ser!er and you8!e chosen the ad!anced archi!ing option "Automatically on ser!er." #or more information on the ser!er archi!ing option, see Archi!ing locally or on a ser!er if you ha!e installed 'otus Notes B 1elp. 4r, go to www.lotus.comClddCdoc to download or !iew 'otus Notes B 1elp.

#ption' Archi!e only

ommand!line e$uivalent -A

Description Archi!es and deletes documents from a database without compacting the database. Archi!es and deletes documents from a database and then compacts the database. Deletes documents from a database and then compacts the database.

Archi!e and then compact

-a

Delete and then archi!e

-j

@"he &ompact tool in the #iles tab of the Domino Administrator pro!ides only the option "Archi!e database?" this option archi!es and then compacts. See also %D( Aays to compact databases %E( &ompacting databases %F( Database properties that optimi9e database performance %=( )unning &ompact using a console command

.TXN Files
-ontent 2otus Domino supports transaction logging and recover ! With this feature enabled$ the s stem captures database changes and writes them to the transaction log! Then if a s stem or media failure occurs$ ou can use the transaction log and a third-part bac"up utilit to recover our databases &/PO+TANT: nabling transaction logging can impro3e ser3er performance in most cases% Transaction logging saves processing time because it allows Domino to defer database updates to dis" during periods of high server activit ! Transactions are recorded se7uentiall in the log files$ which is much 7uic"er than database updates to random$ nonse7uential parts of a dis"! #ecause the transactions are alread recorded$ Domino can safel defer database updates until a period of low server activit !

What is transaction logging4 Transaction logging "eeps a se7uential record of ever operation that occurs to data! (f a database becomes corrupted$ ou can "roll bac"" the database to a point before it was corrupted and repla the changes from the transaction log! ? single transaction is a series of changes made to a database on a server -- for e0ample$ a transaction might include opening a new document$ adding te0t$ and saving the document! Transaction logging provides three main benefits: - (n most situations$ ou no longer need to run the )i0up tas" to recover databases following a s stem failure! A0cluding )i0up results in 7uic"er server restarts$ since )i0up must chec" ever document in each database$ while transaction log recover applies or undoes onl those transactions not written to dis" at the time of the s stem failure! - Transaction logging saves processing time because it allows Domino to defer database updates to dis" during periods of high server activit ! Transactions are recorded se7uentiall in the log files$ which is much 7uic"er than database updates to random$ nonse7uential parts of a dis"! #ecause the transactions are alread recorded$ Domino can safel defer database updates until a period of low server activit ! - <sing transaction logging simplifies our dail bac"up procedure! =ou can use a third-part bac"up

utilit to perform dail incremental bac"ups of the transaction logs$ rather than perform full database bac"ups! &/PO+TANT: Transaction logging wor"s with databases in format 8DS N, or higher but not with databases that use formats from earlier releases %8DS -E will not wor"&! ?fter ou enable transaction logging$ all databases are automaticall logged! To chec" database formats$ use the )iles tab in Domino ?dministrator! NOT : To use all of the features of transaction logging and recover $ ou need a third-part bac"up utilit that supports Domino transaction logging!

What is considered a transaction4 ? transaction is a single ?'( call! (t includes creating$ modif ing$ reading %unread mar"s change& or deleting documents! ? transaction is considered 58F'2ATA when the change has been saved to dis" b the user! )or e0ample$ if a user ma"es a change to the database$ and does not save that change before the server crashes$ that transaction is not considered 58F'2ATA! The transaction would have been 58F'2ATA onl if the user had saved the change before the server had crashed! 58F'2ATA transactions are "commited" to the transactional log!

What is a Transaction log4 ? transactional log is a binar file where transactions are written! The transactional log has a !t0n file e0tension! These !t0n files should never be deleted! The ma0imum si6e of each log e0tent %!t0n file& is CN F#! =ou can have several !t0t logs based on the si6e specified in the Server document! The ma0imum total of !t0n files is N H#!

What is the Database &nstance &D 5D6&&D7 When ou enable transaction logging$ Domino assigns a Database (nstance (dentifier %D#((D& to each Domino database! When Domino records a transaction in the log$ it includes the D#((D! During recover $ Domino uses the D#((D to match transactions to databases %it identifies which database the changes should be applied to&! The D#((D is stored in the file header$ along with the database (D and the Replica (D! Note: There is no relation to the Replica (D or the D#(D! Some database maintenance activities$ such as compaction with options$ cause Domino to assign a new D#((D to a database! )rom that point forward$ all new transactions recorded in the log use the new D#((DO however$ an old transactions still have the old D#((D and no longer match the databaseKs new D#((D! ?s a result$ Domino cannot restore these old transactions to the database! To a3oid losing data8 you should immediately perform a full database bac.up whene3er a database recei3es a new D6&&D% When ou perform this bac"up$ ou capture all the database transactions up until that point and ensure that Domino needs onl the new transactions %with the new D#((D& to restore the database! (f the D#((D changes and a bac"up is not ta"en after the fact$ the database cannot be successfull restored %bac"up will have the old D#((D and the transactional log will not ""now" the old D#((D! N8TA: The D#((D has no relation to the RA'2(5?(D or D#(D! Domino assigns a new D#((D to Domino databases when: =ou enable transaction logging for the first time! - S stem logging is disabled then re-enabled! - The database is compacted using cop -st le compaction! - The database has had )i0up -B applied to it! &/PO+TANT NOT S:

(f a database is logged$ the default for 5ompact with no switches is -b %lowercase& (f a database is un-logged$ the default for 5ompact with no switches is -# %uppercase&! 5ompact with no switches and 5ompact -b %lowercase b& are the onl times 5ompact does not change the D#((D!

The D#((D changes when a database is cop -st le compacted because a cop -st le essentiall creates an entire new NS) with a new structure$ which basicall does not match the structure in the logs for the "old" NS) an more! Note: -2$ -c$ and -i are switches that enable cop st le compaction! -# at times uses cop st le compaction! 5ompact -# ma change the D#((D! This option uses in-place compaction unless there is a pending structural change in which case cop -st le compacting occurs! So when using this option and transaction logging$ do full database bac"ups after compacting completes! Note: )or additional information on the compact tas"s switches refer to: Switches for 58F'?5T Server Tas" for Domino %+,EJN/JJ&

)i0up is forced on the database %fi0up -S& =ou move a Notes database from one logged server to another logged server or from an unlogged server to a logged server!

N8TA: 5hanging the log path or ma0imum log si6e %after initial set up and use& does not trigger a D#((D change!

9ow to set up Transaction logging

,!

Ansure that all databases to be logged reside in the Domino data director $ either at the root or in subdirectories! )rom the Domino ?dministrator$ clic" the 5onfiguration tab! (n the "<se Director on" field$ choose the serverKs Domino Director ! 5lic" Server 5onfiguration$ and then clic" 5urrent Server Document! 5lic" the Transactional 2ogging tab! 5omplete these fields$ and then save the document! nter 5hoose Anabled! The default is Disabled! 'ath name location of the transaction log! The default path name is 128HD(R in the Domino data director $ although it is strongl recommended to store the log on a separate$ mirrored device$ such as a R?(D %Redundant ?rra of (ndependent Dis"s& level E or , device with a dedicated controller! The separate device should have at least ,H# of dis" space for the transaction log! (f ou are using the device solel for storing the transaction log$ set the "<se all available space on log device" field to =es! The ma0imum si6e$ in F#$ for the transaction log! Default is ,.-F#! Fa0imum is NE.CF# %NH#&! Domino formats at least / and up to CN log files$ depending on the ma0imum log space ou allocate!

-! /! N! M! C! :ield

Transactional 2ogging 2og path

Fa0imum log space

<se all available space on log device 5hoose one:

=es to use all available space on the device for the transaction log! This is recommended if ou use a separate device dedicated to storing the log! (f ou choose =es$ ou donKt need to enter a value in the "Fa0imum log space"

field!

?utomatic fi0up of corrupt databases

No to use the default or specified value in the "Fa0imum log space" field!

5hoose one:

Anabled %default&! (f a database is corrupt and Domino cannot use the transaction log to recover it$ Domino runs the )i0up tas"$ assigns a new D#((D$ and notifies the administrator that a new database bac"up is re7uired! Disabled! Domino does not run the )i0up tas" automaticall and notifies the administrator to run the )i0up tas" with the -B parameter on corrupt logged databases!

Runtime*Restart performance

This field controls how often Domino records a recover chec"point in the transaction log$ which affects server performance! To record a recover chec"point$ Domino evaluates each active logged database to determine how man transactions would be necessar to recover each database after a s stem failure! When Domino completes this evaluation$ it:

5reates a recover chec"point record in the transaction log$ listing each open database and the starting point transaction needed for recover ! )orces database changes to be saved to dis" if the have not been saved alread !

5hoose one:

Standard %default and recommended&! 5hec"points occur regularl ! )avor runtime! Domino records fewer chec"points$ which re7uires fewer s stem resources and improves server run time performance! )avor restart recover time! Domino records more chec"points$ which improves restart recover time because fewer transactions are re7uired for recover !

2ogging st le

5hoose one:

5ircular %default& to continuousl re-use the log files and overwrite old transactions! =ou are limited to restoring onl the transactions stored in the transaction log! ?rchive %recommended& to not re-use the log files until the are archived! ? log file can be archived when it is inactive$ which means that it does not contain an transactions necessar for a restart recover ! <se a third-part bac"up utilit to cop and archive the e0isting log! When Domino starts using the e0isting file

again$ it increments the log file name! (f all the log files become inactive and are not archived$ Domino creates additional log files!

9ow to disable Transaction ,ogging for a specific database (n most cases$ disabling Transaction 2ogging %on a server or database level& is not recommended because ou lose all of the benefits of transaction logging %there are no ill side effects of disabling$ ou simpl lose the benefits&! 8ne of the benefits of transaction logging is fast server restart! Disabling transaction logging will cause )i0up to run on the database %or all databases on the server&$ creating the potential for slow restart! ?fter ou set up transaction logging$ all databases that are in Domino Release M or higher format are logged! =ou can disable transaction logging of specific databases! ?ttachments are transactionall loggedO however$ attachments are logged redo onl ! Therefore$ if the database is recovered using media recover ou will get bac" the last cop of the attachment %once the are done the sta done&! (f$ however$ the server crashes with uncommited attachment updates$ the will not be undone since an undo record is never created for them ! Giews are not logged$ so after media recover $ ou will need to rebuild views! )irst$ perform an of the following:

When creating a new database$ choose "Disable transaction logging" on the ?dvanced Databases 8ptions dialog! )or an e0isting database$ choose "Disable transaction logging" on the Database 'roperties bo0$ #eanies tab! (n Domino ?dministrator$ select a database on the )iles tab$ choose Tools - Database ?dvanced 'roperties$ then choose "Disable transaction logging" <se the 5ompact tas" with the -t parameter!

Second$ ensure that all users have closed the database! Ne0t$ use the D#5?5>A command with the "flush" parameter to close the database in the database cache! )inall $ open the database!

9ow to schedule bac.ups or Transaction logs and logged databases #ac"ups are essential for recovering from a media failure$ which is a failure of the serverKs dis" or dis"s! (f ou have a third-part bac"up utilit $ ou should: - Schedule dail incremental bac"ups of the transaction log! <se the bac"up utilit dail to bac" up the transaction log! - Schedule archiving of transaction log files! (f ou use the archive logging st le$ use a third-part bac"up utilit to schedule archiving of log files! - Schedule wee"l full database bac"ups! Aach wee"$ it is recommended to run the 5ompact tas" with the option to reduce file si6e! #ecause this compaction st le changes each databaseKs D#((D$ ou should schedule compaction with a full database bac"up!

9ow to fi0 corrupted databases 5orrupted databases donKt occur fre7uentl when ou use Release M or higher databases and transaction logging! When ou use transaction logging to log changes to Release M or higher databases$ a server automaticall uses the transaction log to restore and recover databases after a s stem failure$ for e0ample after server failures or power failures! (f a dis" failure occurs$ ou use the transaction log along with a certified bac"up utilit to restore and recover the databases!

'sing Transaction logging for reco3ery

Transaction logging is an integral part of recovering from s stem and media failures! ? s stem failure causes the server to stop and re7uires ou to restart the server! During restart$ Domino automaticall performs database recover ! The s stem uses the transaction logs to appl or undo database transactions not flushed to dis" for databases that were open during the s stem failure! Domino also runs the )i0up tas" on databases that use formats from earlier releases$ databases that are in Release M or higher format but have transaction logging disabled$ and on corrupt databases if ou have the "?uto fi0up of corrupt databases" field in the Server document set to =es!

:i0up -; 5auses )i0up to run on databases that are enabled for transaction logging! )i0up -S should onl be run if a database is corrupt and ou have no bac"up of the database to roll forward from! Without this -S option$ )i0up generall doesnKt run on logged databases! The )i0up tas" interferes with the wa transaction logging "eeps trac" of databases! (f ou are using a bac"up utilit certified for Domino$ itKs important that ou schedule a full bac" up of the database as soon after )i0up finishes as possible!

Notes%ini parameter: Translog<Status The T+ANS,O*<Status N8TAS!(N( parameter is used to enable transaction logging for all databases on the server! "E" is disabled$ "," is enabled!

-ontent Transactional ,ogging and 9ow it Operates Transactional 2ogging is a new feature in Domino RM! (t is essentiall a new method of writing out database changes to improve performance and to ensure data integrit ! (ts main purpose is three-fold:

to improve performance on the RM server through se7uential writes to the Transactional 2ogs better data integrit b avoiding inconsistencies and data corruption faster server restart and crash recover

? Transactional 2og is simpl a binar file where transactions are written! The transactions are saved in log e0tents that have a !TQN e0tension! Aach log e0tent is CNF# and will fill before a new e0tent is created or a spare one reused! Fultiple log e0tents collectivel can grow to a ma0imum si6e of NH# with circular logging or available dis" space for archive logging! Performance &mpro3ement When transactional logging is enabled on the server$ the performance improvement is mainl due to the nature of how transactional logging operates! The writes to the Transactional 2og are se7uential! This is faster since there is less head movement and there is never a need to search for a place on the dis" to write as there is in RN or if transactional logging is not enabled! The Transactional 2ogs must be on a separate ph sical drive for there to be an performance improvement! (t is not sufficient to simpl redirect the logs to a separate partition or a separate logical drive! (n general$ if the transactional logs are on a separate drive$ a ,E--ET improvement should be seen! >owever$ if the logs are put on the same drive$ it is li"el that there will be appro0imatel a CET degradation! (n RN$ writing to dis" was time consuming! Fodifications could occur across multiple databases or different parts of one database! ?s a result$ the head

had to move over various areas of dis" to change or update data! This means there was a significant amount of transaction time committing data to the actual NS) %database&! Without the benefit of transactional logging in RN$ fi0up relies on the fact that ..!.T of the data is present in the NS) to correct integrit problems! (n RM$ when transactional logging is enabled$ complete transactions are "committed" to the Transactional 2og! ?ll writes are done to the transactional log before the are ever written to the database! The writes are done se7uentiall at least after each transaction so the Transactional 2og is up to date generall to the hundredth of a second! ?gain$ since the writes are se7uential$ there is less (*8 and performance is improved! 'lease note that view inde0es are not transactionall logged in RM so views ma need rebuilding after a restart or media recover ! ?ttachments$ however$ are transactionall logged! (t is important to note that attachments are logged redo onl $ so if the database is recovered using media recover $ ou will get bac" the last cop of the attachment %once done the sta done&! (f$ however$ the server crashes with uncommitted attachment updates$ the will not be undone since an undo record is never created for them! When transactional logging writes transactions to the logs$ an undo record and a redo record are usuall committed for each transaction! )irst an <ND8 log record is generated in the event of a s stem outage! This is done before a change is written to a database! #efore committing a transaction$ a RAD8 record is also generated! (t is used to re-appl a transaction from the transactional log to the database in the event that it did not get flushed to the NS) before a server outage! <ndo and redo records ensure that if a change is half done it will be full undone$ and if a change was completel done then it will be full re-done to the NS)! :lushing and 9ardening 8nce changes are put into the Transactional 2og$ the changes must also eventuall be hardened to the database! This occurs through a process called flushing! ?n open database has an in-memor version of the database that is held in the <#F %<nified #uffer Fanager&! )lushing moves all changes that were made to the database but onl "ept in memor %<#F&$ to the actual NS) file! There is no set interval for this as the <#F determines when flushing will occur! (t is usuall done when there is a lull in the server activit ! The D#((D %Database (nstance (dentifier& is used to correlate the updates in the Transactional 2ogs and in-memor to the respective database! (t is important to note$ however$ that the Transactional 2ogs are not read from during this process since the Transactional 2ogs are mainl a write-onl obSect! The updates are read and flushed from the <#F! The are onl read from the Transactional 2ogs during crash recover ! Transactional logging is more e0pedient because of the fact that there are not a lot of read*writes to it during server production! 8therwise performance would suffer and it would defeat one of the purposes of transactional logging! The Runtime*Restart 'erformance field in the Server document determines how man F# of changes are "ept in memor ! The amount of space used is bound b the "performance" level chosen in the Server document! There are three choices: Standard %default&$ )avor Runtime$ and )avor Restart Recover Time! (f Standard is selected$ the Redo!2imit is N.F#! This means that chec"points during runtime are minimal and N.F# worth of changes are held in the <#F before the are flushed and hardened to databases! The )avor Runtime choice has a Redo!2imit of the smaller of MEEF# or half the defined log si6e! This means that more information is held in the <#F and hardened to the database less fre7uentl ! ?llowing <#F to manage more of the database changes will allow larger machines to better utili6e memor and reduce unnecessar flushing! The )avor Restart Recover Time choice allows for more chec"points during runtime! There is less information held in the <#F and data is hardened to databases more fre7uentl ! The trade-off is that production time is slower but server restart is faster! -rash +eco3ery ?fter a server outage the Transactional 2ogs are pla ed bac"! The Recover

'oint is determined for each NS) re7uiring log updates$ it is the oldest log information that needs to be re-applied to databases! The databases are restored to the e0act moment of the outage$ guaranteed to restore an data from a completed transaction! 'artial transactions will be undone and rolled bac" to the last good state in an effort to avoid corruption in the database! The partial wor" will be removed from the database before restart completes and the database is made available for use! 5ustomers should not move databases awa from a server and cop them over from another server after a server crash! The database ma be missing a significant amount of changes that are onl stored in the transaction log and if the database is not found during restart the changes will not be restored! Recover restart must be performed first and can be trigged$ for e0ample$ b a re7uest to compact a none0istent database! Transactional ,ogging NOT S%&N& Parameters Transactional logging is enabled in the Server document! ?ll the fields in the Server document map to specific N8TAS!(N( parameters! The parameters are as follows: TR?NS28HI?uto)i0upL Tells whether autofi0up is Anabled %,& or Disabled %E& TR?NS28HI<se?llL To use all available space or not! ELDisable$ ,LAnable TR?NS28HISt leL 5ircular %E& vs! ?rchive %,& TR?NS28HI'erformanceL )avor runtime %,&$ Standard %-&$ )avor restart recover %/& TR?NS28HIStatusL Whether transactional logging is Anabled %,& or Disabled %E& TR?NS28HI'athLQQQ Specifies the path to the !TQN files

!uestion What are the 5hec"point )re7uencies and the )lushing Thresholds for Transactional 2ogging?

Answer Setting )avor Restart Standard )avor Runtime -hec.point :re$uency JF# of data in buffer NEF# of data in buffer -MEF# of data in buffer :lushing Threshold -MF# of data in buffer ,-,F# of data in buffer MEEF# of data in buffer

Problem What switches are available for the 58F'?5T server tas"? Solution (n Notes Release M!0 and later$ the default compaction st le is (n-place compaction! Note: When the 5ompact tas" runs it opens the database to find out the amount of T <sed %as opposed to loo"ing in the log!nsf&! When running 58F'?5T from the server console$ the s nta0 is as follows: load compact databasename -switch

-ompact - Style Option 5ompaction st le: (n-place %recommended& -ommand-line Description e$ui3alent -b Notes=Domino +elease

<ses in-place compaction Release M!0$ C!0$ and recovers unused ;!0 space without reducing the file si6e$ unless thereKs a pending structural change to a database$ in which case cop -st le compaction occurs! This is the recommended method of compacting! -b is the onl switch that will not change the D#((D of a database if transactional logging is enabled!

5ompaction st le: (n-place with file si6e reduction

-#

<ses in-place Release M!0$ C!0$ compaction$ recovers ;!0 unused space and reduces file si6e$ unless thereKs a pending structural change in which case cop -st le compacting occurs! (f ou use transaction logging$ do full database bac"ups after compacting completes! <ses cop -st le Release M!0$ C!0$ compaction! <se this ;!0 option$ for e0ample$ to solve database corruption problems Anables users to continue Release M!0$ C!0$ to access databases ;!0 during compacting! (f a user edits a database during compacting$ compacting is cancelled! This is useful onl when cop -st le compacting is done!

5ompaction st le: 5op -st le

-c or -5

5ompaction st le: 5op -st le: ?llow access while compacting

-2 <pper or lower case K2K will wor"!

5ompaction st le: -i Anables compacting to Release N!0$ M!0$ 5op -st le: (gnore <pper and continue even if it C!0$ ;!0 errors and proceed lower case K(K encounters errors such will wor" in RN$ as document corruption! but onl lower 8nl used for cop -st le case KiK will wor" compaction! in RM! Note: the -i option has to be used together with -c or -2 otherwise ou will get the error message UU "(gnore

errors" is onl allowed with cop -st le compaction 44 5hec" for -o or -8 overlapping obects (f using in place compaction chec"s for overlapping obSects and switches to cop st le if an found! Release C!0$ ;!0

-ompact - Options Option 5ompact database onl if unused space is greater than x percent -ommand-line e$ui3alent -S percent Description 5ompacts all databases with a specified percent of unused space! )or e0ample$ if ou specif ,E$ databases with ,ET or more recorded unused space are compacted! Note that the unused space calculation is not alwa s a reliable measure of unused space! Discards built view inde0es! <se this option to compact databases Sust before ou store them on tape$ for e0ample! Does cop -st le compacting! 5ompacts databases without converting to the current release file format of the server that stores the databases or reverts databases in the current release file format to the previous release file format! )or e0ample$ on Domino C servers$ this option compacts Domino M databases without converting them to the Domino C file format and converts Domino C databases to the Domino M file format! This option uses cop -st le compacting!

Discard an built view inde0es

-D

Deep or revert database to previous format

-R

-ompact - Ad3anced Option2 -ommand- Description line e$ui3alent Notes=Domino +elease

No-A0ecute

-e Show effective arguments Release M!0$ C!0$ <pper or without e0ecution since some ;!0 lower case arguments affect others! )or KAK will wor"! e0ample -i onl wor"s with -c$ so b e0ecuting the compact command first with the -e on the end$ is a good wa to chec" s nta0 without actuall compacting a database! -f Disables "Document table bitmap Release M!0$ C!0$ optimi6ation" database propert ! ;!0 Does cop -st le compaction!

Document table bitmap optimi6ation: 8ff Note: 'rior to M!E!/ this 8ption description was incorrect in the online documentation

Document table bitmap optimi6ation: 8n Note: 'rior to M!E!/ this 8ption description was incorrect in the online documentation DonKt support speciali6ed response hierarch : 8ff Note: 'rior to M!E!/ this 8ption description was incorrect in the online documentation DonKt support speciali6ed response hierarch : 8n Note: 'rior to M!E!/ this 8ption description was incorrect in the online documentation Anable transaction logging: 8n Anable transaction logging: 8ff

-)

Anables "Document table bitmap Release M!0$ C!0$ optimi6ation" database propert ! ;!0 Does cop -st le compaction!

-h

Disables "DonKt support speciali6ed response hierarch " database propert ! Does cop st le compaction!

Release M!0$ C!0$ ;!0

->

Anables "DonKt support speciali6ed response hierarch " database propert ! Does cop st le compaction!

Release M!0$ C!0$ ;!0

-T

Anables transaction logging!

Release M!0$ C!0$ ;!0 Release M!0$ C!0$ ;!0

-t

Disables transaction logging!

Faintain -u unread mar"s: 8n Faintain -< unread mar"s: 8ff ?llow for a larger <ND table -D

Disables "DonKt maintain unread Release M!0$ C!0$ mar"s" database propert ! ;!0 Anables "DonKt maintain unread mar"s" database propert ! Release M!0$ C!0$ ;!0

?llow for a larger <ND table in a Release M!0$ C!0$ database past CN D! ;!0 N8TA : not available through the 5ompact tool in the )iles tab of the Domino ?dministrator! Removes large <ND table in Release M!0$ C!0$ database! ;!0 N8TA : not available through the 5ompact tool in the )iles tab of the Domino ?dministrator! 5onverts document attachments Domino C!M!C$ using compression t pe >uffman ;!E!, and later! to 2V,! Note: The database propert "<se 2V, compression for

Disable large -" %4CN D#& <ND table

No e7uivalent option!

-V<

attachments" must be enabled for this switch to be effective! )or Domino C!M!C onl the following Notes!(N( parameter must also be set: DA#<HIAN?#2AI2V,IRA'?(RL, No e7uivalent option! -VD 5onverts document attachments Domino C!M!C$ using compression t pe 2V, to ;!E!, and later! >uffman! )or Domino C!M!C onl the following Notes!(N( parameter must also be set: DA#<HIAN?#2AI2V,IRA'?(RL,

-ompact - Archi3e When ou use the document archiving tool to archive and delete documents in a database$ ou can use the following 5ompact options to archive documents if the database is located on a server and ouKve chosen the advanced archiving option "?utomaticall on server!" Option2 ?rchive onl -ommand-line e$ui3alent -? Description Notes=Domino +elease

?rchives and deletes Release M!0$ C!0$ documents from a ;!0 database without compacting the database! ?rchives and deletes documents from a database and then compacts the database! Release M!0$ C!0$ ;!0

?rchive and then -a compact

Delete and then archive

-S

Deletes documents from New in Release a database and then C!0$ ;!0 compacts the database! N8TA : not available through the 5ompact tool in the )iles tab of the Domino ?dministrator!

Domino C console help %produced b lo compact -?& lists the following options which have no effect : -v Fa"e %v&iews big %do not compress inde0es& -G Fa"e %G&iews small %compress inde0es& This issue was reported to @ualit Angineering$ through S'R + W#2DMQV>2/! The -v and -G flags were never implemented in Domino!

!uestion Fail delivered prior to 5ompact -c running against a database appears as RA?D in the userKs mail file! This mail was delivered after the user closed the session to the server!

Answer This issue was reported to 2otus @ualit Angineering and has been addressed in Domino M!E!.! A0cerpt from the 2otus Notes and Domino Release M!E!. FR fi0 list %available at http:**www!notes!net&: Ser3er--ompact

S'R+ >>??NW<#?S - )i0ed a problem with notes being mar"ed as read incorrectl after the database was compacted!

To avoid this problem in Notes*Domino prior to M!E!.$ use in-place compaction with file-space reclamation %5ompact -#&! The problem occurs because of an issue related to how 'rofile documents are copied into the new database during cop -st le compaction! (t is unrelated to a change in the 8DS of the database$ and it is unrelated to purging deletion stubs! The problem is reall caused b cop -st le compaction$ and will occur an time cop -st le compaction ta"es place! 58F'?5T will perform cop st le compaction regardless of the in-place st le compact parameters if the mail file has undergone a structural change$ such as the mail file design replacement*conversion! ? cop -st le compact will be used$ also$ under the following conditions:

database 8DS is less than the current version the following 5ompact parameters are used: -D*d$ -R*r$ -F*m$ -5*c$ -)*f$ -<*u$ -2*l local encr ption is being enabled

?n of the advanced database properties are being changed$ such as:

Do not support speciali6ed response hierarch Document table bitmap optimi6ation Do not overwrite free space Do not maintain unread mar"s Disable Transaction 2ogging ?llow more fields in database