[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[prn]
	Apple LaserWriter II NTX
[port]
	LPT2:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	
	
	
	
	
	801520852
	42
	794094184
	4645
	11
	0
	0
	0
	0
	
	
	
	
	
	
	1
[fopts]
	0
	1
	0
	0
	
	
[lnopts]
	2
	Body Text
	1
[docopts]
	5
	2
[GramStyle]
	
[ParaNum]
	1
[tag]
	Body Text
	2
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Ahead
	3
	[fnt]
		Arial
		220
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		240
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		2160
		3
		0
		1
		1
		1
		65
		10
		1
	[spec]
		0
		1
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead title
	4
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		79
		0
		3
		100
	[brk]
		80
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Chead title
	5
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead
	6
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		180
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead
	7
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Numbered list
	8
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		300
		300
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		5
		<*:>.
		0
		3
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Numbered list
	0
	0
[tag]
	Bullet
	9
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		120
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Bullet
	2
	1
	160
	1
	400
	0
[tag]
	See also hlp
	11
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		40
		4
		180
		0
		3
		100
	[brk]
		96
	[line]
		9
		0
		3
		0
		1
		1
		1
		70
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	0
	120
[tag]
	See also prnt
	12
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	1st lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	1st lev para
	0
	0
[tag]
	Indnt bullet
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		420
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		16
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Indnt bullet
	0
	0
[tag]
	2nd lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		600
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	2nd lev para
	0
	0
[tag]
	Book art
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Book art
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Callout text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Callout text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Figure title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		40
		60
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Figure title
	0
	0
[tag]
	Chapter title
	0
	[fnt]
		Arial
		280
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		300
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Chapter title
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	1st pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	1st pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Right pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Right pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Left pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Left pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Table title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		60
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		7
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Table title
	0
	0
[tag]
	Table col hd
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		4
	[line]
		10
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		6
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table col hd
	0
	0
[tag]
	Table Text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table Text
	0
	0
[tag]
	See also btn
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		240
	[spc]
		24
		200
		4
		0
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Crossref
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		513
		3
		0
		300
		600
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Crossref
	0
	0
[tag]
	Indnt caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt caution
	0
	0
[tag]
	Indnt tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		324
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt tip
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Indnt note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt note
	0
	0
[tag]
	Caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Caution
	0
	0
[tag]
	Tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		324
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Tip
	0
	0
[tag]
	Note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Note
	0
	0
[tag]
	Mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Indnt mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		300
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Dhead
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Parameter
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Parameter
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Formula
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Formula
	0
	0
[tag]
	Browse
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		+
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Browse
	0
	0
[tag]
	Keyword
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		K
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Keyword
	0
	0
[tag]
	Context
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		#
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Context
	0
	0
[tag]
	Title
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		$
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Title
	0
	0
[tag]
	Macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		!
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Macros
	0
	0
[tag]
	Footnote
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		244
		0
	[spc]
		40
		2400
		3
		0
		0
		1
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		256
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Footnote
	0
	0
[tag]
	Alink
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		A
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Alink
	0
	0
[tag]
	Butnbar
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		0
		0
		3
		100
	[brk]
		48
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Butnbar
	0
	0
[tag]
	Window
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		>
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Window
	0
	0
[tag]
	Win95 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		W
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win95 macros
	0
	0
[tag]
	Win31 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		X
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win31 macros
	0
	0
[tag]
	Build tag
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		*
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Build tag
	0
	0
[frm]
	1
	1573060
	960
	5267
	6256
	9342
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	6
	0
	0
	0 0
	[frmlay]
		5148
		5296
		1
		0
		0
		1
		5267
		0
		0
		2
		0
		12
		0
		0
		1
		1104
		6920
		0
	[tbl]
		 12 4 200 86 1440 86 1 43 43
		[h]
			 0 200 86 2 0 4 0
			 1 200 86 2 0 2 0
			 2 200 86 2 0 2 0
			 3 400 86 2 0 1 0
			 4 200 86 2 0 2 0
			 5 400 86 2 0 1 0
			 6 200 86 2 0 2 0
			 7 400 86 2 0 1 0
			 8 200 86 2 0 4 0
			 9 200 86 2 0 2 0
			 10 200 86 2 0 2 0
			 11 200 86 2 0 4 0
		[e]
		[w]
			 0 2257 86 2 0
			 1 840 86 2 0
			 2 1005 86 2 0
			 3 807 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 8704 1 0 0 0 0
Task

>
			 0 1 0 0 0 0 8704 1 0 0 0 0
Daily

>
			 0 2 0 0 0 0 8704 1 0 0 0 0
Weekly 

>
			 0 3 0 0 0 0 8704 1 0 0 0 0
Monthly

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Monitor mail routing

>
			 1 1 0 0 0 0 0 1 0 0 0 0
X

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Fix corrupted databases

>
			 2 1 0 0 0 0 0 1 0 0 0 0
X

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Monitor databases that need maintenance

>
			 3 2 0 0 0 0 0 1 0 0 0 0
X

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Monitor replication

>
			 4 1 0 0 0 0 0 1 0 0 0 0
X

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Monitor remote communications

>
			 5 1 0 0 0 0 0 1 0 0 0 0
X

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Check memory

>
			 6 3 0 0 0 0 0 1 0 0 0 0
X

>
			 7 0 0 0 0 0 0 1 0 0 0 0
Check swap file or swap space

>
			 7 3 0 0 0 0 0 1 0 0 0 0
X

>
			 8 0 0 0 0 0 0 1 0 0 0 0
Check disk space

>
			 8 1 0 0 0 0 0 1 0 0 0 0
X

>
			 8 2 0 0 0 0 0 1 0 0 0 0
X

>
			 8 3 0 0 0 0 0 1 0 0 0 0
X

>
			 9 0 0 0 0 0 0 1 0 0 0 0
Monitor server load

>
			 9 3 0 0 0 0 0 1 0 0 0 0
X

>
			 10 0 0 0 0 0 0 1 0 0 0 0
Monitor server performance

>
			 10 3 0 0 0 0 0 1 0 0 0 0
X

>
			 11 0 0 0 0 0 8192 1 0 0 0 0
Back up the server

>
			 11 1 0 0 0 0 8192 1 0 0 0 0
X

>
			 11 2 0 0 0 0 8192 1 0 0 0 0
X

>
			 11 3 0 0 0 0 8192 1 0 0 0 0
X

>
		[e]
	[tble]
[frm]
	9
	1573060
	960
	9650
	8249
	10179
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	7
	1
	0
	0 0
	[frmlay]
		2659
		7289
		1
		0
		0
		1
		9650
		0
		0
		2
		0
		12
		0
		0
		1
		1284
		9482
		0
	[tbl]
		 4 3 200 86 2726 86 1 43 43
		[h]
			 0 400 86 2 0 1 0
			 1 1800 86 2 0 1 0
			 2 1200 86 2 0 1 0
			 3 600 86 2 0 1 0
		[e]
		[w]
			 0 2505 129 6 0
			 1 1714 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 4352 1 0 0 0 0
Statistic

>
			 0 1 0 0 0 0 4352 1 0 0 0 0
Statistics Report that contains it

>
			 0 2 0 0 0 0 4352 1 0 0 0 0
Meaning

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Transmissions.Retried

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Communications

>
			 1 2 0 0 0 0 0 1 0 0 0 0
Use to monitor network transmissions; a high number can slow performance. Retransmissions are caused by CRC errors, alignment errors, collisions, and aborted transmissions. Could indicate a problem with a network cable or network interface card.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Server.Sessions.Dropped

>
			 2 1 0 0 0 0 0 1 0 0 0 0
System

>
			 2 2 0 0 0 0 0 1 0 0 0 0
Use to monitor server response time; a high number of dropped sessions regularly could signal the need for a bigger hard disk, database cleanups or moves, or more memory.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Errors.RetransmittedPackets


>
			 3 1 0 0 0 0 0 1 0 0 0 0
Communications

>
			 3 2 0 0 0 0 0 1 0 0 0 0
A high number of retransmissions can slow down performance.

>
		[e]
	[tble]
[frm]
	9
	1573060
	960
	2335
	8396
	8294
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	5
	2
	0
	0 0
	[frmlay]
		2479
		7436
		1
		0
		0
		1
		2335
		0
		0
		2
		0
		12
		0
		0
		1
		1104
		9302
		0
	[tbl]
		 6 3 200 86 2726 86 1 43 43
		[h]
			 0 400 86 2 0 1 0
			 1 1200 86 2 0 1 0
			 2 600 86 2 0 1 0
			 3 1200 86 2 0 1 0
			 4 1200 86 2 0 1 0
			 5 800 86 2 0 1 0
		[e]
		[w]
			 0 2521 129 6 0
			 1 1845 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 4352 1 0 0 0 0
Statistic

>
			 0 1 0 0 0 0 4352 1 0 0 0 0
Statistics Report that contains it

>
			 0 2 0 0 0 0 4352 1 0 0 0 0
Meaning

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Mem.Allocated

>
			 1 1 0 0 0 0 0 1 0 0 0 0
System 

>
			 1 2 0 0 0 0 0 1 0 0 0 0
OS/2 and NLM only; a high number indicates many users are accessing the server. Consistently high numbers may indicate need for another server or more memory.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
CommandBlocks.Available

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Communications

>
			 2 2 0 0 0 0 0 1 0 0 0 0
If this drops to a low number, server may be unable to support additional users

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Sessions.InUse


>
			 3 1 0 0 0 0 0 1 0 0 0 0
Communications

>
			 3 2 0 0 0 0 0 1 0 0 0 0
If the number of sessions in use is equal to the maximum number of sessions, you may want to increase the maximum number of session in the network configuration file.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Server.Trans.PerMinute

Server.Trans.PerMinute.Peak

Server.Trans.Total

Server.Users

>
			 4 1 0 0 0 0 0 1 0 0 0 0
System

>
			 4 2 0 0 0 0 0 1 0 0 0 0
Use to monitor server use; if any of these numbers are consistently higher than other servers and performance is a problem, you may want to distribute the server's load or add a server.

>
			 5 0 0 0 0 0 8192 1 0 0 0 0
Server.Users.Peak

>
			 5 1 0 0 0 0 8192 1 0 0 0 0
System

>
			 5 2 0 0 0 0 8192 1 0 0 0 0
Use to monitor server use, if the peak is high on a regular basis, shift some of the server's load to another server.

>
		[e]
	[tble]
[lay]
	Standard
	3079
	[rght]
		12960
		10166
		1
		960
		1200
		3
		960
		720
		0
		1
		0
		1
		0
		2
		1
		960
		9446
		1
		1
		3120
	[lft]
		12960
		10166
		1
		720
		1200
		3
		960
		960
		0
		1
		0
		1
		0
		2
		1
		720
		9206
		1
		1
		3120
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		3
	[frmlay]
		960
		10166
		1
		720
		180
		3
		0
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		2
		4674
	[txt]
>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		1
	[frmlay]
		960
		10166
		1
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		2
		4674
	[txt]
>
	[flft]
	[lyfrm]
		1
		5056
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		4
	[frmlay]
		12960
		10166
		1
		720
		480
		3
		11940
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		3
		9900
	[txt]
Administrator's Guide <:P10,0,10->                                                                                        Lotus Confidential

>
	[frght]
	[lyfrm]
		1
		13248
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		2
	[frmlay]
		12960
		10166
		1
		960
		480
		3
		11940
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		3
		9900
	[txt]
Lotus Confidential                                                                              Maintaining the Notes Server 
<:P10,0,10->

>
[elay]
[l1]
	0
[pg]
	11
	20 98 14 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	48 0 27 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	75 200 78 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	102 196 103 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	133 0 9 0 1 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	161 0 56 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	185 189 77 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	211 192 75 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	220 0 5 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 1 0 0
	237 0 27 32 1 0 0 220 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	241 97 100 1025 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
[edoc]
@Chapter title@<:s><:#300,8486>Chapter 10  Maintaining the Notes Server

<:s><:#200,8486>This chapter describes server maintenance task that you should perform routinely.

@Ahead@<:s><:#240,8486><-!><-">About maintaining a Notes server

@hd:opener@<:s><:#200,8486>As a server administrator, you make sure that:

@Bullet@<:s><:#200,8486>Users can access the server quickly and consistently

@Bullet@<:s><:#200,8486>Mail is routed properly

@Bullet@<:s><:#200,8486>Databases are replicating as scheduled

@Bullet@<:s><:#200,8486>Server hardware is functioning

@Bullet@<:s><:#200,8486>Databases are active and maintained (a task you share with each database's manager)

@Bullet@<:s><:#200,8486>The server is backed up regularly<-!><-">

@Bhead@<:s><:#220,8486>Using a maintenance checklist

<:s><:#400,8486>The following table describes the server maintenance tasks that you should complete daily, weekly, or monthly to ensure a server runs smoothly and efficiently. 

@See also prnt@<:s><:#400,8486>This chapter describes all of these tasks except for monitoring databases that need maintenance. For this information, see Chapter 11.

<:s><:t0>

@Ahead@<:s><:#240,8486>About dead mail

<:#600,8486>After attempting delivery of mail for 24 hours, if a server cannot deliver mail because of a mail routing problem, the server places the mail item in the Dead Mail view of the server's Mailbox (MAIL.BOX). The following mail routing problems are common cause
s of dead mail:

@Bullet@<:s><:#200,8486>A destination server is unavailable for longer than 24 hours.

@Bullet@<:s><:#200,8486>A destination server doesn't have a protocol in common with the initiating server.

@Bullet@<:s><:#200,8486>There are problems with modem communications.

@Bullet@<:s><:#400,8486>An alarm is mistakenly set up to be mailed to a server rather than an individual and is therefore undeliverable.

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">Any other reasons? <-"><-!><:f>

<:s><:#400,8486>To determine the cause of a dead mail message, open its dead mail document in the Mailbox.. After you resolve any problems, release the dead mail for delivery.

<:s><:#400,8486>A mail item that results in a delivery failure report caused by an addressing problem, such as specifying a name not listed in the Name & Address Book, is not a dead mail item.

<:s><:#200,8486>Since mail routing is a high priority for users, check a server every day for dead mail.

<:s><:#200,8486><+!>SHOW TASKS<-!>

<:s><:#400,8486>Use the server console command SHOW TASKS as a quick way to see the number of dead mail messages in the Mailbox.

<:#200,8486><+!>Mailbox (MAIL.BOX)<-!>

<:#600,8486>The Mailbox, located in the server data directory, displays any dead mail documents in the view Dead Mail. Each dead mail document describes the cause of the dead mail message. After you've corrected the problem, you can resend the dead mail.

<:s><:#200,8486><+!>Statistics database<-!>

<:#800,8486>If you've set up a server to report statistics, the Statistics Reports - Mail & Database view of Stats & Events Report (STATREP.NSF) displays the number of dead mail items for each statistics report. You can also set up an alarm for the statistic MAIL.DEAD 
to report when the MAIL.BOX contains more than a specified number of dead mail items.

@See also prnt@<:s><:#200,8486>For more information on alarms, see "About reporting statistic alarms" in Chapter 9.

@Bhead title@<:s><:#220,8486>Checking for dead mail

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Using SHOW TASKS

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>You can check the performance of the mail router quickly by entering the SHOW TASKS command at the server console or at a remote server console. The server responds with a list of current server tasks and status. Check the following line:<:X8,-32768;Index "Server commands" # "show tasks">

@disp:sys@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Pending mail:  <+">number	<-">Dead mail:<+"> number

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>If the Dead mail number is greater than 0, examine the dead mail document(s) in the server Mailbox to determine the cause of failure.<:X8,-32768;Index "Dead mail" #><:X8,-32768;Index "Mail" # "dead">

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>(It is normal for the Pending mail number to vary, as mail is queued for sending and then sent.<:X8,-32768;Index "Pending mail" #><:X8,-32768;Index "Mail" # "pending">)

@Chead@<:R><:#200,8486>Using Stats & Events Report (STATREP.NSF)

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>If you've set up the server to report statistics, you can check the Stats & Events Report database to see the number of dead mail messages. 

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Double-click the STATISTICS database icon (STATREP.NSF) for the server that collects statistics.

@Numbered list@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Choose View - Statistics Reports - Mail & Database.<-!><-">

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>The dead mail column of the view shows the number of dead mail messages.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>You can also set up an alarm for the statistic MAIL.DEAD to report when the number of dead mail messages exceeds a specified threshold.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For more information, see Chapter 9.

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Opening the Mailbox

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>You must be an administrator of the server or have at least Editor access in the Mailbox access control list to open the Mailbox. 
<+!><+"><:f180,BArial,0,0,255>(True?) <-!><-"><:f>The Mailbox is located in the server's data directory.<-!><-">

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Open the Mailbox (MAIL.BOX) on the server. The database is located in the Notes data directory.

@Numbered list@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Choose View - Dead Letters.

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Determining the cause of a dead mail message

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>A Dead Mail document in the Mailbox explains the cause of a dead mail message. You must be an administrator of the server or have at least Editor access in the mailbox access control list to open the mailbox. 
<:f180,BArial,0,0,255><+!><+">(True?) 

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Open the Mailbox (MAIL.BOX) on the server. The database is located in the Notes data directory.

@Numbered list@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Choose View - Dead Letters.

@Numbered list@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Double-click a dead mail document to open it.<-!><-">

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>See Chapter 12 for information about troubleshooting mail routing problems.

@Bhead title@<:R><:#220,8486>Resending dead mail

<:#200,8486>After you correct any problems, remail dead letters.

@Numbered list@<:#200,8486>Open the mailbox (MAIL.BOX) on the server.

@Numbered list@<:s><:#200,8486>Choose Actions - Release Dead Messages.<-!><-">

@Ahead@<:s><:#240,8486>About monitoring mail routing

<:s><:#200,8486>Use the following methods to monitor mail routing:

<:s><:#200,8486><+!>Event reporting<-!>

<:s><:#600,8486>If you run the Event task on a server, you can configure an Event Monitor document to reports mail events that potentially indicate a mail routing problem. For example, you can create an Event Monitor document for mail that reports only mail messages classi
fied as Fatal, Failure, and Warning (high). 

@See also prnt@<:s><:#200,8486>For more information, see "Creating an Event Monitor document" in Chapter 9.

<:s><:#200,8486><+!>Statistics reporting<-!>

<:#600,8486>Running the Report task on a server automatically generates a variety of mail statistics in the Stats & Events Report database (STATREP.NSF), including the number of undeliverable mail messages in MAIL.BOX and the number of pending mail messages.

<:#600,8486>You can also configure Statistic Monitor documents to generate alarms for these mail statistics when they exceed specified thresholds. For example, you can create an alarm that notifies you when the router has been unable to transfer more than 10 messages.

@See also prnt@<:s><:#400,8486>For more information, see "Reading a statistics report" and "Setting up a statistics monitor document" in Chapter 9.

@See also prnt@<:s><:#200,8486><+!>Notes Log<-!>

<:#600,8486>If you don't run the Event task to report mail messages from the Notes Log (LOG.NSF), you should check daily the Mail Routing Events view of the Log (LOG.NSF) for significant mail routing problems. The Mail Routing Events displays all mail routing events, e
ven routine ones that don't indicate a problem. 

<:s><:#200,8486>For more information, see Chapter 9.

@Ahead@<:s><:#240,8486>About detecting corrupted databases

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486><:X8,-32768;Index "Database" # "checking"><:X8,-32768;Index "Checking databases" # "automatically"><:X8,-32768;Index "Database" # "fixup"><:X8,-32768;Index "Fixup" #><:X8,-32768;Index "Corrupted" # "data"><:X8,-32768;Index "Server crash" # "preventing with database fixup">
Corrupted databases or documents are the most common cause of server crashes. Database corruption is most frequently caused by:

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>Improper shutdown of the operating system due to system reboot, system crash, power failure, or use of improper shutdown procedures 

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Improper database access by an API program<-!><-">

<:R1,4,1,0,1,720,1,1440,1,2160,>The Fixup server program checks for and fixes corrupted databases when possible. Although Notes also checks for and fixes a corrupted database if necessary each time someone opens a database, running Fixup helps reduce the number of corrupted databases that
 users encounter.<-!><-">

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>When checking for database corruption, Notes searches for improperly closed databases. Notes does the following if it detects an improperly closed database:

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Validates and verifies every field in every document

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Purges any corrupted documents without propagating the deletions to replicas of the database

<:R1,4,1,0,1,720,1,1440,1,2160,>In addition, manually loading Fixup rebuilds any corrupted views. (Corrupted views are not fixed when Fixup runs automatically at server startup or when users open corrupted databases)

<:R1,4,1,0,1,720,1,1440,1,2160,>Fixup doesn't run on open databases but reports any opened databases encountered, for example, LOG.NSF, MAIL.BOX or NAMES.NSF. 

@Bhead@<:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Ways to run FIXUP

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>You can run FIXUP in the following ways:

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><+!>At server startup<-!>

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>The Fixup program always runs when you start a server. FIXUP at server startup checks and fixes the Notes Log (LOG.NSF) so that the Log can receive reports of subsequent databases repairs. When Fixup runs at server startup, it does not detect and rebuild co
rrupted views.

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><+!>Manually as needed

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>You can run Fixup manually to fix a specific database you suspect is corrupted. You can also run it manually to check for and fix corrupted views. Since Fixup uses significant CPU resources, run it manually only when necessary.

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><+!>As a scheduled server<-!><+!> program<-!> <+!>(not recommended)<-!>

<:R1,4,1,0,1,720,1,1440,1,2160,><:#800,8486>You can also schedule Fixup to run as an automatic server task, although this is not recommended since Fixup consumes significant CPU resources. Fixup run as an automatic server task detects and fix corrupted views as well as documents. If you schedule Fixu
p to run, be sure to run it only once a week during non-peak hours. 

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Fixing corrupted databases

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>To run FIXUP manually, type the following server command

@Mono@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>LOAD FIXUP <<FILENAME<;> <<SWITCHES<;>

@Dhead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><-!><-"><<FILENAME<;>

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>(Optional) Type the file name of a specific database that you want to check. 

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>If you do not specify a database, FIXUP checks all databases on the server in the following order:

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>First checks the Notes Log (if closed) and if necessary fixes it so all subsequent repairs are logged

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Checks and repairs any other Notes databases that were improperly closed

@Dhead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><<SWITCHES<;>

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>(Optional) You can type the following switches:

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>-L	Reports to the Notes Log every database FIXUP suspects is corrupted (every database FIXUP opens). Without this switch, FIXUP only logs actual problems encountered. Useful only when running FIXUP on all databases.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>-V	Avoids running FIXUP on views. Choosing this switch reduces the time FIXUP takes to run. 

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>-I	Does an incremental fixup that only checks documents modified since FIXUP was last run.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>-N	Does not purge corrupted documents so that the next time FIXUP runs or the next time a user opens the database, FIXUP must check the database again. This switch for use primarily when FIXUP is run against specific database.  
<:f180,BArial,0,0,255><+!><+">What's the point in using this switch? 
<-!><-"><:f>

@Note@<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>Although it's not recommended, you can run Fixup as a scheduled server task by creating a Program document in the Name & Address Book. If you do this, make sure to run Fixup during off-peak hours and at most once a week. 

@Chead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Examples: Fixing corrupted databases

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>To run FIXUP on all databases, check for both corrupted documents and views, and log the name of each database checked to the Notes Log,  type

@Mono@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>LOAD FIXUP -L 

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>To run FIXUP on SALES.NSF and check for both corrupted documents and views,  type:

@Mono@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>LOAD FIXUP SALES.NSF

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>To run FIXUP on all databases and check only for corrupted documents (not views), type:

@Mono@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>LOAD FIXUP -V<-!><-">

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Finding database corruption messages in the Notes Log

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>Corrupted documents and views<-"> are often the cause of server crashes, so Fixup automatically deletes corrupted documents (and rebuilds corrupted views when not run at server startup) to help keep the server in operation. To locate messages in the Notes L
og relating to database corruption:

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Open LOG.NSF on the server.

@Numbered list@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Choose View - Miscellaneous Events.<-!><-">

@Numbered list@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Select recent documents and find documents containing the word "damage."

@See also prnt@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>See Chapter 9 for information about restoring documents purged by FIXUP.

@Chead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><+!>Details: <-!> Finding database corruption messages in the Notes Log

<:R><:#200,8486>"Document NT<<Document Number<;> in database <<Database Name<;> is damaged:"

<:s><:#200,8486>A line describing the cause for the corruption follows, for example:

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#400,8486>"Document is damaged or obsolete (unrecognized data type)" or "Document is damaged or obsolete (unrecognized field)"

<:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>If Fixup has purged a document, the Log displays a message similar to this:

<:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>"Document NT000021NC in database SALES.NSF has been deleted"

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#400,8486>(The document number is the equivalent to the last 10 digits of the document ID displayed when you choose File - Document - Properties)

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>The following messages indicate view corruption: 

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486><-">"Page format is incorrect"

<:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>"Invalid CNO vector - position == 0"

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>"Container integrity has been lost - rebuild"

@Ahead@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#240,8486>About checking replication

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486><:f180,BArial,0,0,255><+!><+">TO COME<-"><-!><:f>

@Ahead@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#240,8486>About monitoring remote communications

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#800,8486>If your server relies on modems to communicate with other servers or remote users, it's important that communications remain trouble-free. Although you can't necessarily prevent a remote communications problem, promptly correcting problems ensures that info
rmation continues to circulate efficiently to all sites.

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Use the following tools to monitor remote communications on a daily basis:

@Dhead@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Notes Log

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#600,8486>If Log Modem I/O or Log Script I/O is selected in the Additional Setup dialog for the remote port, the Miscellaneous Events view shows details about modem or script responses. Without these options selected, Miscellaneous Events indicates when calls are com
pleted but no further details.

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#400,8486>Check the Phone Calls view of the Notes Log to see details about calls a server has made and received. This view includes totals for each day as well as total for all the days displayed.

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486><:f180,BArial,0,0,255><+!><+">Can Event task report these same messages? 
<-"><-!><:f>

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486><+!>Event reporting<-!>

<:s><:R><:#600,8486>If you run the Event task on a server, you can configure an Event Monitor document to reports communications events that potentially indicate a remote communications problem, for example a modem not responding or the inability to establish a connection with
 a remote system. 

@See also prnt@<:s><:#200,8486>For more information, see "Creating an Event Monitor document" in Chapter 9.

@Dhead@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Statistics Reporting

<:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#600,8486>Running the Report task on a server automatically generates a variety of communications statistics in the Stats & Events Report database (STATREP.NSF), for example, the number of retransmissions on a port. 

<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#400,8486>You can also configure Statistic Monitor documents to generate alarms when communications statistics exceed specified thresholds. 
<:f180,BArial,0,0,255><+!><+">What alarms useful for remote communications monitoring? 
<-"><-!><:f> 

@Bhead title@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#220,8486>Logging modem responses

<:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#800,8486>If you suspect there's a modem problem, log modem responses to the server Notes Log (LOG.NSF). Since logging modem responses can significantly increase the size of the Notes Log, use these options only while you troubleshoot a problem. After you correct the
 problem, deselect the options to save disk space.

@Numbered list@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Choose File - Tools - Notes Preferences and click the Ports icon.

@Numbered list@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Select the remote port.

@Numbered list@<:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Click XPC Options.

@Numbered list@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Select "Log Modem I/O" or "Log Script I/O."

@Numbered list@<:s><:R1,8,1,0,1,720,1,720,1,1440,1,2160,1,2880,1,3600,1,4320,><:#200,8486>Click OK.

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Ways to check memory

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>At least once a month use one of the following methods to check the amount of memory on your server:

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Entering a command to check memory

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Using a diagnostic disk to check memory

@Bullet@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Using statistics reporting to check memory

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For information on server memory requirements, see the Installation Guide.

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Entering a command to check memory

@Chead title@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><+!>NLM<-!>

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>To display the amount of configured memory on a Notes Server for NetWare, type the following command at the NetWare system console:

@Mono@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>memory

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><-!><-">To assess memory usage, use the NetWare Monitor program and select Resource Utilization.

<:R1,4,1,0,1,720,1,1440,1,2160,>Refer to your NetWare documentation for more information

@Chead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>OS/2

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>To display the amount of memory (RAM) and swapping memory available on the boot drive of the Notes server, type the following command at the Notes server console: 
<-!><-">

@Mono@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>SHOW MEMORY

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>If there is little difference between the amount of memory<-!><-"><-"> and the amount of disk space, the server may need more RAM. 
<-!><-">To display the amount of disk space, type the following command at the Notes server console:

@Mono@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>SHOW DISKSPACE

@Chead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>UNIX 

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>To display the amount of memory available on a UNIX server, use an operating system command. Refer to your UNIX documentation for instructions.<-!><-">

@Chead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Windows (NT)

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486><-!><-">To display the amount of memory available on an NT server, use the Microsoft windows NT Diagnostics program or the Windows Control Panel.

@Chead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Windows 16

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486><-!><-">To display the amount of memory available on a Windows 16 server, use the Windows Control Panel. 
<:f180,BArial,0,0,255><+!><+">Correct??<-"><-!><:f>

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Using a diagnostic disk to check memory

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>Once a month, run your operating system's diagnostic disk to test system memory if applicable. 
<-!><-">Refer to your operating system documentation for details.<-!><-"><-!><-">

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Using statistics reporting to check memory

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>If you run the Report task on a server, you can check the Memory Statistics section of a System Statistics Report to see memory usage statistics.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>You might also set up an alarm to report if allocated memory (Mem.Allocated) exceeds a certain value. A high allocated memory value indicates that many users are accessing the server. Consistently high values for allocated memory may indicate the need for m
ore memory or another server. 

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For more information, see Chapter 9.

@Bhead title@<:s><:R><:#220,8486>Checking the swap file size

<:s><:#400,8486><-!><-"><-">A large swap file can point to an impending server crash or the need for more RAM. Check the size of the server swap file at least once a month.

@Chead@<:s><:#200,8486>OS/2

<:#800,8486>On a Notes Server for OS/2, you should keep the size of the swap file below 20MB and swap file size should not regularly exceed 20% of RAM. The swap file on a Notes Server for OS/2 is SWAPPER.DAT and is typically found in the directory C:\OS2\SYSTEM. Use an
 operating system command<-"> to check the size of this file.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#800,8486>If you run the Report task on the server, you can check the Memory Statistics section of a System Statistics Report to see the size of the swap file. The statistic Mem.SwapFile.Size shows the swap file size. 
<-!><-">You can also generate an alarm that notifies you when the Mem.SwapFile.Size statistic exceeds the recommended 20MB limit.<-!><-">

@Chead@<:s><:R><:#200,8486>UNIX

<:#600,8486>For optimum performance, we recommend that swap space be three times the amount of physical memory. Physical memory plus swap space should be at least 100MB. Refer to your operating system documentation for information about checking swap space on a UNIX se
rver.<-!><-">

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Correcting swap file problems<-!><-">

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>OS/2

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>When a swap file becomes too big--usually due to low memory conditions--server performance deteriorates and the server may crash. If the swap file becomes too big (exceeds 20MB) 
<-!><-">restart the server to flush out the swap file then reset the file to the default value of 512K.<-!><-">

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>If the swap file consistently exceeds 20% or more of RAM, you should increase your system memory, up to the maximum size allowed by OS/2. For example, with 6MB RAM and a swap file of 1.5MB the swap file is 25% of RAM; add 2MB of RAM for a total of 8MB to im
prove performance.

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>UNIX?

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Checking disk space

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>To ensure that there is enough space for new mail and new documents in non-mail databases, monitor server disk space at least once a week; if space is critical, monitor disk space daily.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>You can use the SHOW DISKSPACE command on the Notes server (or installation directory on a UNIX system) to check available server disk space.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#800,8486>If you run the Report task on the server, you can also check the Disk Statistics section of a System Statistics Report to see the free disk space available on each drive (or file system in UNIX). Look for the statistic Disk.<+">n<-">.free.<-!><-"> You can a
lso create a Statistics Monitor document that generates an alarm when Disk.<+">n<-">.free falls below a specific size, for example, 10MB.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For information on server disk space requirements, see the Installation Guide.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For information on the Report task, see Chapter 9.

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>About freeing disk space

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>Use any of the following methods to free up disk space on a server. If these methods are not helpful and low disk space remains a chronic problem, consider adding disk space or adding another Notes server.

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><:f180,BArial,0,0,255><+!><+">Any other ways to free disk space??<-"><-!><:f>

@Dhead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Compact databases

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Remove unused space in databases by running the server program Compact.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For more information, see Chapter 10.

@Dhead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Move or delete databases

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Move databases to another server or delete databases that are no longer used.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For more information, see Chapter 10.

@Dhead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Reduce the size of server administration databases

@Bullet@<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>Notes Log (LOG.NSF). Specify 7 days for the replication settings option "Documents not modified in the last 
<+">x<-"> days will be removed." Also, since modem or script I/O logging can significantly increase the size of the Log, disable these options when you are finished troubleshooting a problem.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>For information about replication settings, see the Database Manager's Guide or Help. For information about modem logging, see "Logging modem responses" earlier in the chapter.

@Bullet@<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>Stats & Events Report (STATREP.NSF). Specify 7 days for the replication settings option "Documents not modified in the last 
<+">x<-"> days will be removed." <:f180,BArial,0,0,255><+!><+">OK recommendation for STATREP??<-"><-!><:f> You can also reduce its size by limiting the number of servers that report statistics to the database.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For information about statistics reporting, see Chapter 9.

@Bullet@<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>Database Catalog (CATALOG.NSF). Don't replicate the Catalog to other servers; store information about databases on one server only. To temporarily free disk space, delete the Database Catalog (CATALOG.NSF) and then recreate it later by using the LOAD CATALO
G command.

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For information about the Database Catalog, see Chapter 10.

@Ahead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#240,8486>About monitoring server load

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>The following table describes statistics generated by the Report task that are useful for monitoring server load. If you run the Report task, monitor these statistics once a month.

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486><:f180,BArial,0,0,255><+!><+">How else to monitor server load other than using statistics reporting??<-"><-!><:f>

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:t2>

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For more information on statistics reporting, see Chapter 9.

@Ahead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#240,8486>About monitoring server performance

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>The following table describes statistics generated by the Report task that are useful for monitoring server performance. If you run the Report task, monitor these statistics once a week. 
<:f180,BArial,0,0,255><+!><+">Any other ways to monitor server performance other than statistics reporting? 
<-"><-!><:f>

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:t1>

@See also prnt@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>For more information on statistics reporting, see Chapter 9.

@Ahead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#240,8486>About backing up the server

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>It's critical that you do daily backups of all Notes server data files including databases, template files, NOTES.INI, and ID files. These backups can be done directly to tape or to a file server and then to tape. At least one recent set of backup files sho
uld be stored off-site in the event of fire, flood, or theft. 

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>You should also copy the server ID file to diskette and store it in a secure area.

<:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>Notes requires that the following files be open when it runs: LOG.NSF, NAMES.NSF, MAIL.BOX and the server ID file. If your backup utility cannot back up open files, you must shut down the server before doing a backup. 

@Bhead title@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Backing up directly to tape

@Chead@<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>NLM

<:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Include the Notes server files in your regular NetWare backup.

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>NT

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>???

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>OS/2

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>The most direct way to back up is to attach a tape drive to the server and run a backup program to copy its files to tape. This method can be costly as it requires a tape drive for each Notes server.

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>UNIX

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>Use tar or cpio commands to back up files to a local or remote tape drive. If these utilities are not available on your system, refer to your system documentation for comparable alternatives.

@Chead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#200,8486>Windows 16

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>The most direct way is to attach a tape drive to the server and run a backup program to copy its files to tape. This method can be costly as it requires a tape drive for each Notes server.

@Bhead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Backing up to a file server

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#600,8486>This method involves backing up to a file server and from there to tape and is useful if there is already a backup schedule in place for a network file server. This method allows the Notes server to be up and running faster than it would be if it were shut 
down to back up directly to tape.

@Bhead@<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#220,8486>Using replication for backing up

<:s><:R1,4,1,0,1,720,1,1440,1,2160,><:#800,8486>Each production database on a server should have a replica copy on another server if possible. When you create a replica for this purpose, copy the entire database to the new replica (access control list, views, forms, and documents). If problems occur in a
 database, it is sometimes possible to restore the database from a replica copy. 

<:R1,4,1,0,1,720,1,1440,1,2160,><:#400,8486>Replication should never be your sole method of database backup--damaged or accidentally changed databases often do replicate in which case your only recourse is recovery from a server backup tape.

>

[Embedded]
00062971
