Freelance Graphics - id210.PRZ - Lotus Sandbox

lotussandbox.com

Freelance Graphics - id210.PRZ - Lotus Sandbox

ID210: Lotus Notes and Domino 6

Deployment - What You Need To Know

Jeff Mitchell - Lotus Software, IBM Software Group

Jeff_Mitchell@notesdev.ibm.com

Jon Champlin - Lotus Software, IBM Software Group

Jon_Champlin@notesdev.ibm.com


Agenda

Notes/Domino 6 benefits

Planning your upgrade

Server upgrade steps

Client upgrade steps

Deploying new features


Notes/Domino 6 benefits

Client enhancements

Attachment management in mail template

Policies

Instant Message Integration

Multi-threaded operations


Notes/Domino 6 benefits

Client enhancements (cont.)

Smart Update

Many, many more


Notes/Domino 6 benefits

Server enhancements

Single Copy Template (SCT)

LZ1 Compression

View logging

Linear-style transaction logging

Many others...


Planning Your Upgrade

Plan out your upgrade steps

Recommend to do servers, then clients and finally

templates/applications

Look for servers that are used by a specific group of

users (i.e. a certain division or early adopters)

Use latest release of Notes/Domino 6 to avoid

problems that have already been addressed

Get buy-in from upper management

Convince them of the benefits of upgrading

Have them communicate to the user population that

they are behind the upgrade


Server Upgrade Steps

Plan a time to do your upgrades

If possible do server upgrade and database

maintenance with server down

Ensures all databases can be exclusively locked

Prevents maintenance from happening when the

server is restarted for access from clients


Server Upgrade Steps

Make a checklist of server upgrade steps

Clean Domino server shutdown

Backup important files

Install Domino 6 server code

Perform database maintenance

Start your Domino 6 server


Server Upgrade Steps

Do a clean shutdown of the Domino server

If the server does not shutdown cleanly and it has

transaction logging enabled, run '[n]fixup foo' from a

command prompt.

This will force the any data not yet written from the

transaction log extents to the databases to be

written.

Make backups of important files

Server ID file and notes.ini

If space and time allow, all .nsf files on the server


Server Upgrade Steps

Install the Domino 6 server

During the upgrade be aware of the new licensing

types

Domino Utility Server

application services only, no Client Access

License

Domino Messaging Server

messaging services only, no application services

or Domino clusters

Domino Enterprise Server

full support for all messaging and application

services


Server Upgrade Steps


Server Upgrade Steps

Database maintenance

Removing corruption

Converting to new on-disk structure

Rebuilding view/full-text indexes

Administrative setup

Debug_Outfile= or Console_Log_Enabled=1

Notes.ini settings to capture output from

maintenance into a file

Indirect Files (*.ind)

New Notes/Domino 6 feature that can be used with

maintenance tasks


Server Upgrade Steps

Removing corruption

Fixup in Notes/Domino 6 is more stringent than the

R5 version

Running fixup before your upgrade won't hurt, but it

might not catch all the corruptions that Domino 6 will

Run '[n]fixup -f -j -v' from the Domino program

directory

Once fixup has completed, review the console output

file to see if there were any databases that fixup

could not run to completion on


Server Upgrade Steps

New on-disk structure (ODS43)

Some of the new features available in Notes/Domino

6 required changes to internal structures stored

within the .nsf file

view logging

single-copy template

A conversion from the R5 ODS (41) to the R6 ODS

(43) is necessary before these features can be

implemented

Conversion is done by the compact process via

copy-style compaction


Server Upgrade Steps

New on-disk structure (ODS43)

You should ensure there is adequate free disk space

on the drive(s) containing the databases

Must be done with the server down for always in-use

databases (i.e. names.nsf, log.nsf)

Will change the DBIID of the databases so you will

need a new full backup before an incremental backup

can take place

Check output file for errors when complete

Any new databases created on the server after the

upgrade will be in ODS43 format by default


Server Upgrade Steps

Rebuilding view/full-text indexes

The version number used internally within Domino

for view and full-text indexes has changed from R5 to

Notes/Domino 6

This requires a one-time rebuild of all of these

indexes to get them into the new format

This can be CPU intensive so if possible should be

done with the server down immediately after

upgrading to Domino 6

If not done server performance will degrade the first

time the server is started at Domino 6


Server Upgrade Steps

Rebuilding view/full-text indexes

Run '[n]updall -f -r' from the Domino program

directory to rebuild all view/full-text indexes

When complete review the console output file for

errors


Server Upgrade Steps

Start the server as Domino 6

When the server is restarted it will prompt you if

you'd like upgrade the design of the Domino

Directory (names.nsf)

Ok to do if you have not made any customizations to

the design

If you do not want to be prompted (and not have the

upgrade take place), set this notes.ini parameter

Server_Upgrade_No_Directory_Redesign=1

You're running Domino 6!!


Server Upgrade Steps

Remote server installs

Available for UNIX servers

Allows local machine and/or remote machines to

have a new level of Domino installed

Assumes that Domino is not running on target

machines when install is launched

Can be used to upgrade many machines, in multiple

sites if requested, at once


Server Upgrade Steps

Remote server installs (cont.)

Invoked via 'install -script '

Sample script.dat file is shipped with Domino

server

Remote machines are accessed via rsh by default

Can set environment variable NUI_RSH to alternate

remote access method

Can be combined as part of a script to remotely

shutdown servers, upgrade and then restart

IBM has Domino upgrades automated via cron

during offshift hours


Client Upgrade Steps

Know your workstations

Supported OS versions

Minimum hardware requirements

Backup critical files?

Recommended, but not required

notes.ini, id file, *.dsk, *.nsf, *.dic

Know your environment and your needs

Home grown roaming users

Local user privileges

Multi-user vs. Single user installs, features

Designer/Admin/Notes vs. Notes only


Client Upgrade Steps

Doing the deed

Customized installs - transforms

InstallShield Tuner for Lotus Notes

Silent installs

Installing without local privileges

Client feature options

Group policy editor

Administrator account

Multi-user / Roaming user options

Upgrade by Mail


Client Upgrade Steps

Client setup

Automatic on upgrades

Scriptable setup

Mail design upgrade

Individual or in groups

convert

Manual vs automatic

Seamless mail upgrade


Client Upgrade Steps

The end result


Deploying New Features

First determine if the client machines need to be

upgraded to take advantage of the new feature you are

implementing

Prioritize the new features that are applicable to your

company so you can deploy the biggest wins first

Look for deployment overlap that might cause features

to be deployed in tandem

Example: If all server documents have to be modified

for two features doing them together might make

sense


Deploying New Features

Selected new features

Attachment management

Policies

Single Copy Template (SCT)

LZ1 compression

View logging

Linear style transaction logging


Deploying New Features

Attachment management

Provide the ability to reply to or forward a message

without the attachments

Attachments are replaced with "Attachment ''

deleted by "

Huge space savings on mail servers

No ODS requirement

Once servers and clients have been upgraded to

Notes/Domino 6, the mail file designs can be

upgraded to mail6.ntf


Deploying New Features

Policies

Control over user's desktops, security, archiving

Extends down to the document and field level

Inheritance

No ODS requirement


Deploying New Features

Single Copy Template (SCT)

New functionality introduced in Domino 6.01

Requires databases and template to be at ODS43

Single version of the template used by multiple

databases

Template and databases must be on same server

Database references common design elements in the

template

Common design elements are removed from each

database that references the template

Unique design elements remain in the databases


Deploying New Features

Single Copy Template (cont.)

Immediate update of all database designs when the

template is modified

No need to run the design task

Transparent to all APIs (Lotuscript, C/C++, Java)

Disk space savings for a database based off mail6.ntf

are 10 MB (11.5 MB -> 1.5 MB)

When new copy/replica of the database is made to

another server or a client, common design elements

are stored in destination database


Deploying New Features

Single Copy Template (cont.)


Deploying New Features

Single Copy Template (cont.)

To enable:

Mark the template as a 'Single Copy Template'

Run the design task on all databases that use the

template

This will replace the common design elements

with the reference pointers

Run compact -B on the databases

This will remove the common design elements

from the database and reclaim the space they had

occupied


Deploying New Features

LZ1 Compression

Alternative to Huffman compression algorithm

Requires database be at ODS43

Have seen 10% - 50% reduction in size from Huffman

algorithm

Compression is done by the client when attaching

No additional work done at the server

Existing attachments are left in Huffman format

Need to be reattached to be converted to LZ1


Deploying New Features

LZ1 Compression (cont.)

LZ1 attachments are converted on-the-fly to Huffman

for pre-Notes/Domino 6 clients and servers

Conversion is done by the server

Translation time can be extensive, so only

recommended in full Notes/Domino 6 environment

Enabled on the advanced tab of the Database

Properties popup


Deploying New Features

LZ1 Compression (cont.)


Deploying New Features

View Logging

Requires that database be at ODS43 level

Server must be running transaction logging

Should only be enabled for views that need to be up

to date immediately when restarting from a crash or

after media recovery

do not enable on ALL views!!

Only incremental view updates are logged, not full

rebuilds

Updates stored as a new record format in existing log

extents (transparent to administrators)


Deploying New Features

View Logging (cont.)

Reduces server restart time after an outage

IBMUS Domino Directory (180,000+ docs / ~2 GB)

View logging enabled on $Users and

$ServerAccess

Rebuild of $Users

Without view logging - ~4 hours

With view logging - ~5 minutes

Enabled via Advanced tab of View Properties box in

the Domino Designer client


Deploying New Features

View Logging (cont.)


Deploying New Features

View Logging (cont.)

LZ1 compression results from IBM

MS Word attachment -- 257,024 bytes

Huffman --> 232,313 bytes (9.7% reduction)

LZ1 --> 205,055 bytes (23.3% reduction)

NSF attachment -- 7,077,888 bytes

Huffman --> 4,144,863 bytes (41.5% reduction)

LZ1 --> 1,161,497 bytes (83.6% reduction)


Deploying New Features

Linear-style Transaction Logging

Allows larger disks to be utilized for transaction

logging drives

Creates a sliding 4 GB window of active log extents

Reduces how often backups need to be taken on

busy servers

No ODS requirement

Enabled by choosing 'Linear' option for Logging

Style


Recap

Review the new features available in Notes/Domino 6

Convince management that upgrading is the right thing

to do

Plan your upgrade steps

Follow the recommended client and server upgrade

steps for a successful deployment

Deploy new features on a prioritized basis once the

servers (and clients if necessary) have been upgraded


FYI...

Upgrading to Lotus Notes and Domino 6 Redbook

Notes/Domino 6 Forum on LDD

other sessions here


Your Turn.... Q & A

More magazines by this user
Similar magazines