How cluster works?

All the servers in a Domino cluster continually communicate with each other to keep updated on the status of each server and to keep database replicas synchronized. Each server in a cluster contains cluster components that are installed with the Lotus Domino server. The components keep replica databases synchronized, and they communicate with each other to ensure that the cluster is running efficiently and smoothly. They also let you set limits for workload balancing, track the availability of servers and databases, and add servers and databases to the cluster. A cluster's ability to redirect requests from one server to another is called failover. When a user tries to access a database on a server that is unavailable or in heavy use, Domino directs the user to a replica of the database on another server in the cluster. An Enterprise server license is needed for clustering and Partitioning. Internet Cluster Manager (ICM) is used for fail-over and load balancing. If Administration Request database got corrupted and u dont have any backup copy then how u will recover. Ans:- Delete the admin4.nsf and restart the server. it will create a new one with all setting & ACL. If i give u 2 Notes.in, one of server and one of Client how can u identify which notes.ini is of server? In Notes.ini for notes, the kit type in the second line is KitType=1 In Notes.ini for domino, the kit type in the second line is KitType=2 1) what is the registration server. Ans: A server which registers new users,server,OU and Organisation and initially stores these document in the Domino directory untill the replicate untill the next replication occures. 2) what is the administration server. Ans: An Administration server controls how the Administration process does its work.It stores the requested work in the administration request database and then process them accordingly to their status.By default first server in the domino domain is the Admin server for the Domino directory which maintains its ACL, performs deletion,name change and replicate to the other server in the DNN. 3) what is the difference between registration & administration server. Ans: 1. Both Def. 2. Registration Server maintains the Names.nsf database while Admin server maintains the Admin4.nsf database. 3. By default there is one primary Admin server w.r.t. Hub-Spoke topology wheres as registration server can be more than one in a domain. 4) what is the administration process. Ans: The Admin process is a program which automates many routine administrative tasks such as Name management task(Rename/delete user and group),Mail file management task(Delete/Move mail file,ACL chages,Enabling agents),Replica management task(Create/Move/Delete replicas).

5) how do work administration process in background. Ans: Adminp works in background with the help of differents components like AdminP server Task(Starts by default on all server starts),Administrator client(Domino/Web)(Different Tools),Domino Directory(It provides set of instructions with AdminP For instance, when a user is renamed, the certificate information is changed. This is stored in a Person document in the Domino Directory. When the renaming process is in progress, this is indicated in the Person document under the Change Request field),Certification Logs Database(Certlog.nsf database created when server installed it works assgining new certificates),Admin4.nsf and administrar 3) what is ODS version of R5,R6,R7. Ans: R5-41, R6-43, R7-43 4) If i am upgrading my Domino from R5 to R7. What should i do on all NSF file? Ans : As ODS version are diffrent on both Release and it will not accept so we need to change the ODS version after upgradation. 1.What is difference between replica & new copy? Replica is a copy of database which having the same replica ID which share during the replication process And new copy is a simpale copy of database which don't have any replica ID and further u cannot replicate from it's original database 2.What is different type of administrator? Full access administrator -- gets all rights and privileges of all administration access levels listed. Administrator -- gets all rights and privileges of database administrator and full-console administrator (but not system administrator). Full console administrator -- gets rights and privileges of view-only console administrator (but not system administrator) System administrator -- gets rights and privileges of restricted system administrator 3.If user forgot his password how will recover the password? If you have recovery information set up for your user ID on your server The recovery password is randomly generated and unique to each recoverable ID file and administrator.When you first log in to Notes and the Password dialog box appears, 2 do not enter your password. Just click OK. 3. Click "Recover Password" in the "Wrong password" dialog box. 4. Select the user ID file to recover in the "Choose ID File to Recover" dialog box. 5. Enter the password(s) given to you by your administrator(s) in the "Enter Passwords" dialog box, and repeat until you have entered all of the passwords, and you are prompted to enter a new password for your user ID. 6. Enter a new password for your ID, and confirm the password when prompted 4.What is ODS version of R5 & R6 & R7? File ext.-----version-------ODS --?-------------V3-------17 .ns4,.nsf-------V4-------20 .nsf------------V5-------41 .nsf------------v6-------43 .nss------------v7-------43 from verson 5 lotus support >4GB size, transaction logging, in-place compaction

5.What type of replication? Pull Pull Pull Push (default) Pull Only Push Only 6.When will set the pull type of replication in server? Forces a one-way replication from the specified server to your server. replicate a single database from the specified server to your server we are using pull command by including the database name on the command line 7.What will do if server get hang? Its very difficult to take a single step There are so many reason to get server hang . either ur mail.box is corrupt or there are some hardware issue u can check log file and analyze ur problem and try to resolve it

Server crash
A Domino server crash is a situation where the server program has terminated and it is no longer running. You can often determine the task that the server was performing when it terminated by looking at the crash screen, or from the NSD/RIP log file (depending on which release of Domino you are running). An ABEND is a special form of server crash. The term ABEND is a combination of the words "abnormal end." ABEND crashes do not produce RIP or NSD files.

Server hang
A Domino server hang is a situation where the Domino server is still running, but one or more tasks on the server are not responding to requests. These tasks may still be active, but they are not doing what they are supposed to do. The term "hang" also defines a state that sometimes occurs when computer programs do not run as designed.

8.basic router command? Tell Router Delivery Stats--- it will Shows you Router delivery statistics. Tell Router Compact-------Compacts MAIL.BOX and cleans up open Router queues. You can use this command to compact MAIL.BOX at any time. If more than one MAIL.BOX is configured for the server, each MAIL.BOX database will be compacted in sequence. By default, MAIL.BOX is automatically compacted at 4 AM. Tell Router Show Queues------Shows mail held in transfer queues to specific servers and mail held in the local delivery queue Tell Router Exit or Tell Router Quit-----Stops the Router task on a server. Tell Router Update Config-------Updates the server's routing tables to immediately modify how messages are routed. This removes the 5 minute delay before a Router configuration change takes effect 9.What is parameter of notes.ini? There are a number of parameters in Lotus Domino's notes.ini configuration file that affect ... For example, these are the server task entries in notes.ini: ServerTasks=Update,Replica,Router,AMgr,AdminP,CalConn,Sched ServerTasksAt1=Catalog,Design ServerTasksAt2=UpdAll, Object Collect mailobj.nsf ServerTasksAt3=Object Info -Full ServerTasksAt5=Statlog

10.How internal & external Mail routing work? Give with example? When user send a mail NRPC(Notes protocols) to deposit the message into the MAIL.BOX database on the user's Domino mail server.The Router finds the message in MAIL.BOX and determines where to send the message for each recipient. The Router checks its routing table to calculate the next "hop" for the message on the path to its recipients and determines the appropriate protocol -- either SMTP or Notes routing -- to transfer the message. Using SMTP routing, the Router connects to the destination server -- the recipient's mail server, a relay host, a smart host, or one of the servers in the recipient's Internet domain -- and transfers the message. Using Notes routing, the Router moves the message to the MAIL.BOX database on the server that is the next hop in the path to the recipient's mail server. The Router on that server transfers the message to the next hop, until the message is deposited in the MAIL.BOX database on the recipient's home server.The Router on the recipient's server finds the message (in MAIL.BOX on a Domino server) and delivers it to the recipient's mail file When will set the pull type of replication in serv suppose there are 2 servers A n B pulltype replication mins first let me tell what is initiating srv n target srv Initiating srver mins from wher the changes has been done n trget srver mins from wher the changes will be reflected. a(ini srv) b( trgt srv) now if u made this, the changes will be pulled from b to a i.e any changes done in b will be seen in a bt any changes done in a will not be seen / reflected in b. as a is pull type. 1) what is the registration server. Ans: If I have to create a user and I am sitting on Server A and creating users on Server B, then the Server A is Registration server and Server B is Mailing server, which states the server which is requesting for the registration of user is called registration server. 6) what is ECL and can we implement the ECL from server side. An ECL is used to set up workstation data security.It lets you control which formulas and scripts created by another user can run on your workstation.Yes workstation ECL is updated/Implement from Server Admin's ECL by creating a Security policy document. There are two kinds of ECLs: the Administration ECL, which resides in the Domino Directory (NAMES.NSF), and the workstation ECL, which is stored in the user's Personal Address Book (NAMES.NSF). 7) can we make the HUB server from spoke server. ( Like ADC - DC & Vice Versa ) 8) what is difference between Manager & designer access. The major diff between designer and manager access is manager can edit ACL (execution control List) entry but designer can not modify ACL entry 9) how many types of policy. Ans: 1. Organizational 2. Explicit

10) one group which are allready exist, if we want to deploy the explicit policy on them what is the step. Ans: Select group->select groups from Tool panes->click assign policy.(An Explicit policy always override the Organisational policy...see by Policy synopsis) 11) how we take the lotus server backup. Ans: Backup files: All ID files(Servers/Users),All Database(Data folder->NSF+NTF) what is ACL & type? 1. Access Control list(Acl) type -->1.No Access 2.Depositor 3.reader 4.Author, 5.Editor 6.designer 7.manager 5.What are type of replication? ans: three type 1.pull type 2.push type, 3.pulpush type, 1.when the changes in the target srver get reflected in the initiating srv. 2.when the changes in the ini srver get reflected in the target srver. 3.when both happens mins first pull, then push.

Replication Type
Push-Pull: a workload server both pulls in and pushs out: Pull-Pull: Servers pull from each other Depositor users can not pull, only push replications from a server. Reader users can not push, only pull replication of changes from a server By default, replication is performed to all files identified with the same Replica ID displayed in Database Properties Information tab. Replication occurs in this order: 1. 2. 3. ACL changes Design changes Document changes

14.what will be do when replication stop between the two server? ans: Stop showing the effect, i.e if you make any change in a srver 1 it will not be reflected in srver 2 and vice versa.

File Size Limitations

o o o

Database file names can be up to 8 characters. Domino Database names can have no more than 32 characters. Domino databases can hold up to 16GB.

Transaction log: Transaction logging captures all the changes that are made to databases and writes them to a transaction log. A transaction log is a record of changes made to Notes databases. The transaction log consists of log extents and the log control file (NLOGCTRL.LFH). There are three logging styles to choose from -- circular, linear, and archived The Database Transaction log file is 192 MB by default, in \LOGDIR, with a maximum limit of 4096 MB. With circular logging, Domino reuses a fixed amount of disk space (up to 4GB) for transaction logs. After the disk space is used up, Domino starts overwriting old transactions, starting with the oldest. When the space fills up, perform a backup on the databases. Archived logging creates log files as needed. It simplifies backup and restoration, and provides online and partial backups. The log files are not overwritten until you archive them. Policy Settings Creating a policy is a two-step process. If you create an organizational policy, it automatically applies when you register users. If you create an explicit policy, you assign it manually during user registration, in the Person document or by using the Policy Assignment tool. Using a policy, you control how users work with Notes. A policy is a document that identifies a collection of individual policy settings documents. Each of these policy settings documents defines a set of defaults that apply to the users and groups to which the policy is assigned.

(1)

Create an Archive settings document to create and modify a set of rules that defines how mail database documents are selected and archived. Create a Desktop settings document to dynamically update desktop settings and configurations for users. Create a Registration settings document to register a number of users with the same settings. Create a Security settings document to define and maintain Admin ECL settings and to setup Internet and password security. Creating a Setup policy settings document to define first-time user setup configurations.

(2)

(3)

(4)

(5)

Types of IDs you can recertify

You can recertify any of the following types of IDs: Organizational unit Server User Organization certifier (when it is used to certify itself)

Certifier IDs and certificates

Certifier IDs and certificates form the basis of Domino security. To place servers and users correctly within your organization's hierarchical name scheme, you create a certifier ID for each branch on the name tree. You use the certifiers during server and user registration to "stamp" each server ID and user ID with a certificate that defines where each belongs in the organization. Servers and users who belong to the same name tree can communicate with each other; servers and users who belong to different name trees need a cross-certificate to communicate with each other.

here are two types of certifier IDs: organization and organizational unit.

Organization certifier ID
The organization certifier appears at the top of the name tree and is usually the name of the company -- for example, Acme. During first server setup, the Server Setup program creates the organization certifier and stores the organization certifier ID file in the Domino data directory, giving it the name CERT.ID. During first server setup, this organization certifier ID automatically certifies the first Domino server ID and the administrator's user ID. If your company is large and decentralized, you might want to use the Domino Administrator after server setup to create a second organization certifier ID to allow for further name differentiation -- for example, to differentiate between company subsidiaries.

Organizational unit certifier IDs

The organizational unit certifiers are at all the branches of the tree and usually represent geographical or departmental names -- for example, East/Acme or Sales/East/Acme. If you choose to, you can create a first-level organizational unit certifier ID during server setup, with the result that the server ID and administrator's user ID are stamped with the organizational unit certifier rather than with the organization certifier. If you choose not to create this organizational unit certifier during server setup, you can always use the Domino Administrator to do it later -- just remember to recertify the server ID and administrator's user ID. A certificate is a digitally signed message added by a certifier to a Notes ID file. Recovery information is stored in the certifier ID. The recovery password is stored in the User ID. Mail encryption. Station, Form, View Access and Workstation ECL Field Access: Authors, Encryption, Readers, Signing

The nstats.exe agent process collects statistics and events to file statrep.nsf based on the list of thresholds, messages, and servers to monitor specified in file events4.nsf.
AdminP The Administration Process automates many administration tasks. tell adminp process all tell adminp show databases AMgr The Agent Manager runs scheduled and triggered agents in Domino databases.

tell amgr resume tell amgr status

Catalog

Maintains the Domain Catalog, which helps users to find and locate Domino databases and files of interest to them within the Domino domain
Compact (Database Compaction)

Reorganizes the disk usage by each database in order to free up unused space. The Compact task can be invoked with the following commands (the various options can be combined as needed): load compact [database] Compacts the database or specified subdirectory. load compact [database] -S X Compacts databases with greater than X % free space.

[database] -D Compacts databases and deletes any built view indexes. load compact [database] -R Compacts databases and changes the ODS version to R4 from R5. Used when backing out of an upgrade from R4 to R5. load compact [database] -M For R4 databases, sets a maximum size of 4GB and compacts the database. load compact [database] -b Compacts databases in place. Can be used only if the database internal format is not being changed due to a change in one if the advanced database properties. It recovers unused space within the database, but does not reduce the file size of the database. load compact [database] -B Compacts databases in place. It recovers unused space within the database, and does reduce the file size of the database. load compact [database] -c Uses copy-style compaction of the database, rather than in-place compaction. load compact [database] -L When using copy-style compaction, allows access to the database while the compaction is in process. Compaction ends for the database if a user accesses the database. load compact [database] -i When using copy-style compaction, ignores any errors that occur during compaction. load compact [database] -f Compacts the database and changes the format of the database to disable support for document table bitmap optimization. load compact [database] -F Compacts the database and changes the format of the database to enable support for document table bitmap optimization. load compact [database] -H Compacts the database and changes the format of the database to enable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae. load compact [database] -h Compacts the database and changes the format of the database to disable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae. load compact [database] -T Compacts the database and changes the format of the database to enable transactional logging. load compact [database] -t Compacts the database and changes the format of the database to disable transactional logging. load compact [database] -U
load compact

Compacts the database and changes the format of the database to maintain unread marks. load compact [database] -u Compacts the database and changes the format of the database to disable maintaining unread marks. load compact [database] -A Doesn't compact the database; archives documents to another database, and then deletes those documents from this database if archiving is set up for the database. load compact [database] -a If archiving is set up for the database, archives documents to another database and then deletes these documents from this database and compacts the database.
Convert

Used to update the mail databases to a new mail template design, typically used when upgrading the server to from R4 to R5. The Convert task can be invoked with the following commands: load convert [-r] mailfilepath currenttemplatename newtemplatename Converts the mail databases in the given mailfilepath from the currenttemplatename (* can be used to match all existing templates) to the newtemplatename. The new mail template for R5 is called MAIL50.NTF. The -r option is used to recursively process subdirectories below the given mailfilepath. load convert -l mailfilelist Produces a list of primary mail databases (but not replicas) on the server and writes the list to the file specified in mailfilelist. This option is used to produce a list of mail database files, which would be used with the -f option as shown in the next entry. load convert -f mailfilelist currenttemplatename newtemplatename Updates the mail databases listed in the mailfilelist from the currenttemplatename (* can be used to match all previous templates) to the newtemplatename. The new template in R5 is called MAIL50.NTF. load convert -m mailfilepath Changes the mail databases specified within the mailfilepath to able be used for IMAP mail access.
Fixup

Fixes suspected corrupt Domino databases. These options can be combined as needed: load fixup [database] -F When fixup runs against multiple databases, by default it checks only documents with the last modified date since its last run. This parameter then forces the fixup task to check all documents in all databases being checked. load fixup [database] -i Checks only new documents in the database since the last run of fixup.

load fixup [database] -J Runs fixup against databases that have transaction logging enabled. parameter isn't used, fixup doesn't check these databases. load fixup -L

If this

When used without specifying the database to check, logs every database suspected of being corrupted. The default is to log only when a database problem is found and needs to be corrected. load fixup [database] -N Changes the way that fixup operates when a corrupted document within a database is encountered. When this parameter is specified, any corrupted documents found are not deleted. A typical use of this is to allow documents to be copied to another database before fixup deletes them in an effort to retrieve documents from a corrupted database. load fixup [database] -Q Instructs fixup to be less thorough in its checking for corrupted documents in the database. load fixup [database] -U Changes unread document lists to the older R4 format. (Lotus recommends that you do this only when requested by Lotus Support.) load fixup [database] -V Specifies to not check views for corruption.
MTC (Message Tracking Collector)

Monitors the work of the Router process (which delivers mail in Domino) and keeps records as required as to what mail was sent to whom. This allows users and administrators to query mail status. This task does not need to be explicitly started; if mail tracking is enabled on the server by a Configuration document, then Domino will start this task automatically as the Router task is started.
tell mtc process

Collects information now for message tracking, rather than waiting for the message tracking interval. tell mtc interval value Changes the collection interval used for message tracking information by the MTC task.
tell mtc compact

Compacts the message tracking store database now.

tell mtc reindex

Reindexes the message tracking store database now. tell mtc purge value Purges collected message tracking information older than value days from the message tracking database now.
Router

Delivers mail to databases on this server and forwards it to other servers as required. This task has the following commands available to modify its behavior while it is running:
tell router delivery stats

Shows the current mail routing delivery statistics.

tell router compact

Shuts down the mail routing process on the server, and compacts the MAIL.BOX database. If more than one MAIL.BOX is on the server (for example, MAIL1.BOX and MAIL2.BOX if the server is configured to have two), each of these databases is compacted in turn. When the compaction activity is complete, the router process is resumed.
tell router show queues

Shows the current number of waiting mail items in the queues for each destination mail server. tell router use databasename Enables the use of shared mail on this server. It also changes the value of SHARED_MAIL to 2 in NOTES.INI. databasename is the name of the database used for the shared mail database, and a new database link called MAILOBJ.NSF is created in the server data directory, which points to databasename.
Updall (Indexer)

Maintains changed views and full text indices as the data changes within the Domino database. load updall [database] -A Performs an incremental update of an R4 site search database. load updall [database] -B Performs a full update of an R4 site search database. load updall database -C Rebuilds the full text indexes and any unused views in the database. load updall [database] -F Updates full text indexes but not views. load updall [database] -H Updates full text indexes that are configured to be updated immediately. load updall [database] -L Updates full text indexes that are configured to be updated immediately, hourly, or daily. load updall [database] -M Updates full text indexes that are configured to be updated immediately or hourly. load updall [database] -R Rebuilds all full text indexes and all views in the database. load updall database -T view Rebuilds the out-of-date view in the database. load updall database -T view -R Rebuilds the view in the database whether or not it is out of date. load updall [database] -V Updates view but not full text indexes. load updall [database] -X Displays the number of user appointments and resource reservations in the free time database.

Access level privileges in the ACL

After you assign an access level to each user, group, and server, you can select or deselect privileges within an access level. Access level Default privileges Optional privileges Manager Create documents Create private agents Create personal folders/views Create shared folders/views Create LotusScript/Java agents Read public documents Write public documents Create documents Create private agents Create personal folders/views Create shared folders/views Read public documents Write public documents Create documents Read public documents Write public documents Author Read public documents Delete documents Replicate or copy documents

Designer

Delete documents Create LotusScript/Java agents Replicate or copy documents Delete documents Create private agents Create personal folders/views Create shared folders/views Create LotusScript/Java agents Replicate or copy documents Create documents Delete documents Create private agents Create personal folders/views Create LotusScript/Java agents Write public documents Replicate or copy documents Create private agents Create personal folders/views Create LotusScript/Java agents Write public documents Replicate or copy documents Read public documents Write public documents Read public documents Write public documents

Editor

Reader

Read public documents

Depositor No Access

Create documents None

DNN (DOMINO NAMED NETWORK) A Domino named network is a group of servers in a given Domino domain that share a common protocol and are connected by a LAN or modem connections.

NNN (NOTES NAMED NETWORK) The Domino Server Setup program automatically places all servers that are in a Domino domain and that run the same network protocol in the same Notes named network (NNN). In the Server document, the setup program assigns each NNN a default name in the format portname network.

LOG FILE Every Domino server has a log file (LOG.NSF) that reports all server activity and provides detailed information about databases and users on the server. The log file is created automatically when you start a server for the first time CONNECTION DOCUMENT The Server Connection document establishes a connection between servers and establishes how and when servers connect to replicate and to exchange mail. Create a Server Connection document whenever you need to establish any new or additional server connections SERVER DOCUMENT The Server document is set up when you register a server. It contains many of the settings that define how your server operates. You also use the Server document to enable mail routing, transaction logging, and fault recovery, as well as other services and features. The administrator who creates the Server document is listed as the administrator responsible for the server, unless you specify otherwise during server registration CROSS DOMAIN CONFIGURATION The Cross-domain Configuration document specifies how a domain exchanges and processes administration requests. Use this document to specify which requests a domain can send to another domain or which requests a domain can receive for processing from another domain. The Cross-domain Configuration document is stored in the Administration Requests database (ADMIN4.NSF). DOMINO DIRECTORY The Domino directory contains documents that control directory services, manage server tasks, and define server-to-server communication, as well as many other types of documents. Lotus Domino automatically creates some documents when you perform certain administrative tasks Your address book or Domino Directory People Groups (3) Mail-In Databases (4) Policies (5) Settings (6) Certificates
(1) (2)

DOMAIN DOCUMENT Domain documents define the domains used in mail routing. Use the Domain document form to create the following types of domain documents:

(1)

Foreign Domain document Non-adjacent Domain document Adjacent Domain document Foreign X.400 Domain document Foreign SMTP Domain document Foreign cc:Mail Domain document Global Domain document

(2)

(3)

(4)

(5)

(6)

(7)

MAIL-IN DATABASE

The Mail-In Database document defines the properties and location of a database that can receive mail. Whenever you define a database as being able to receive mail, you must create a corresponding Mail-In Database document. SSL To set up SSL on your server, you need a key ring containing a server certificate from an Internet certificate authority. You can request and obtain a server certificate from either a Domino or third-party certificate authority (CA) and then install it in a key ring. MAIL ENCRYPTION Mail encryption protects messages from unauthorized access. Only the body of a mail message is encrypted; the header information -- for example, the To, From, and Subject fields -- is not. Notes users can encrypt mail sent to other Notes users or to users of mail applications that support S/MIME -- for example, Microsoft Outlook Express and Netscape Communicator. Users can use Notes mail encryption to encrypt mail sent to other Notes users, encrypt mail received from other Notes users, or encrypt all documents saved in a mail database. Notes uses the recipient's public key, which is stored in the sender's Personal Address Book or in the Domino Directory, to encrypt outgoing and saved mail. In general, mail sent to users in a foreign domain cannot be encrypted

How outgoing Notes mail encryption works

1. 2. 3. The sender sends an outgoing message and selects the Encrypt option. Notes generates a random encryption key and encrypts the message with it. Notes encrypts the random encryption key with the recipient's public key and appends the new key to the message. The recipient's public key must be stored in either a Domino Directory or LDAP directory that a user can access or in the sender's Personal Address Book. If the encrypted message is addressed to multiple recipients, the message is encrypted only once with one random key, and the random key is encrypted using the public key of each recipient. When the recipient attempts to open the encrypted message, the user's mail application attempts to decrypt the random key, using the recipient's private key. If this is successful, the random key decrypts the message. If decryption is successful, the recipient can read the message. If decryption is unsuccessful, the user receives a message indicating that the decryption failed and the mail application does not allow the user to access the message.

4.

5.

6.