[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[sequence]
	28
	0
	0
	0
	19
	13
	Numbered list
	0
	Bullet
	0
	Indnt bullet
	0
	Indnt caution
	0
	Indnt tip
	0
	Indnt note
	0
	Caution
	0
	Tip
	0
	Note
	0
	Browse
	0
	Keyword
	0
	Context
	0
	Title
	0
	Macros
	0
	Alink
	0
	Window
	0
	Win95 macros
	0
	Win31 macros
	0
	Build tag
[prn]
	PostScript (QMS)
[port]
	LPT2:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	replication
	
	
	
	
	801530489
	7
	799451930
	936
	22
	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]
	1st lev para
	9
	[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]
	Bullet
	11
	[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]
	Indnt bullet
	12
	[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]
	See also prnt
	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
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	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 hlp
	0
	[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 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]
	73
	1572868
	960
	960
	9424
	2813
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	5
	0
	5
	0 290
	[frmlay]
		2720
		8464
		3
		0
		0
		3
		960
		0
		0
		2
		0
		0
		0
		1024
		1
		1200
		9446
		0
	[tbl]
		 7 3 200 86 2731 86 1 43 43
		[h]
			 0 210 10 6 0 3 0
			 1 800 0 6 0 1 0
			 2 800 0 6 0 1 0
			 3 800 0 6 0 1 0
			 4 400 0 6 0 2 0
			 5 600 0 6 0 1 0
			 6 1200 10 6 0 1 0
		[e]
		[w]
			 0 1549 0 6 0
			 1 2999 0 6 0
			 2 3873 0 6 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
@Table col hd@<-#>

>
			 0 1 0 0 0 0 0 1 0 0 0 0
@Table col hd@Replication

>
			 0 2 0 0 0 0 0 1 0 0 0 0
@Table col hd@Mail Routing

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Where required

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Required for all replication between servers; same domain or different.

>
			 1 2 0 0 0 0 0 1 0 0 0 0
Required between servers connected by modems and connections to other domains; not needed for mail routing in the same network and same domain.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Direction of connections

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Connection one</m>way in either direction is sufficient.

>
			 2 2 0 0 0 0 0 1 0 0 0 0
Connection documents must be established both ways (initiated from both servers). (Mail routing also occurs automatically during scheduled replication.)

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Scheduling recommendations

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Don't overlap connection times (if bidirectional), or schedule to call too often because each call requires resources. 

>
			 3 2 0 0 0 0 0 1 0 0 0 0
Because a call is made only if there is outgoing mail to transfer, don't worry about overscheduling.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Schedule recommended 

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Range with Repeat Interval or List of Times.

>
			 4 2 0 0 0 0 0 1 0 0 0 0
Range with Short Repeat Interval.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Normal schedule overridden when:

>
			 5 1 0 0 0 0 0 1 0 0 0 0
REPLICATE or PULL command is entered at the Notes server console.

>
			 5 2 0 0 0 0 0 1 0 0 0 0
"Route at once if" threshold is reached, High Priority mail is pending, or if server console command ROUTE is entered.

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Priorities

>
			 6 1 0 0 0 0 0 1 0 0 0 0
All databases are "medium priority" by default; Notes attempts replication at each call. You can make separate Connection documents for Low, Medium, and High replication priority databases.

>
			 6 2 0 0 0 0 0 1 0 0 0 0
Medium: On schedule or threshold. High: Makes immediate call. Low: Requires Connection between 12:00 midnight and 6:00 A.M. (or as specified in NOTES.INI in the MailLowPriorityTime variable)

>
		[e]
	[tble]
[frm]
	81
	1572868
	720
	960
	9184
	1813
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	6
	1
	0
	59140 4
	[frmlay]
		1620
		8464
		3
		0
		0
		3
		960
		0
		0
		2
		0
		114
		100
		12338
		1
		1200
		9446
		0
	[tbl]
		 3 4 200 86 2026 86 1 43 43
		[h]
			 0 410 10 6 0 1 0
			 1 600 10 6 0 1 0
			 2 200 0 6 0 4 0
		[e]
		[w]
			 0 1384 0 6 0
			 1 1450 0 6 0
			 2 1401 0 6 0
			 3 4186 0 6 0
		[e]
		[data]
			 0 0 0 0 0 0 512 1 0 0 0 0
@Table col hd@Call at times...

>
			 0 1 0 0 0 0 512 1 0 0 0 0
@Table col hd@Repeat interval

>
			 0 2 0 0 0 0 512 1 0 0 0 0
@Table col hd@Retry Period set by Notes

>
			 0 3 0 0 0 0 512 1 0 0 0 0
@Table col hd@Recommended uses

>
			 1 0 0 0 0 0 256 1 0 0 0 0
8:00 A.M. </m> 5:00 P.M.

>
			 1 1 0 0 0 0 256 1 0 0 0 0
120 Minutes

>
			 1 2 0 0 0 0 256 1 0 0 0 0
9 Hours (Entire range)

>
			 1 3 0 0 0 0 256 1 0 0 0 0
High</m>priority replication, high and medium</m>priority mail routing; low</m>priority mail if the range is between midnight and 6:00 A.M.

>
			 2 0 0 0 0 0 256 1 0 0 0 0

>
			 2 1 0 0 0 0 256 1 0 0 0 0

>
			 2 2 0 0 0 0 256 1 0 0 0 0

>
			 2 3 0 0 0 0 256 1 0 0 0 0

>
		[e]
	[tble]
[frm]
	82
	1572868
	720
	7134
	9184
	8407
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	7
	2
	12342
	2573 2313
	[frmlay]
		1620
		8464
		3
		0
		0
		3
		7134
		0
		0
		2
		0
		0
		0
		65280
		1
		1200
		9446
		0
	[tbl]
		 3 4 200 86 2026 86 1 43 43
		[h]
			 0 410 10 6 0 3 0
			 1 600 10 6 0 1 0
			 2 200 0 6 0 4 0
		[e]
		[w]
			 0 989 0 6 0
			 1 758 0 6 0
			 2 1879 0 6 0
			 3 4795 0 6 0
		[e]
		[data]
			 0 0 0 0 0 0 512 1 0 0 0 0
@Table col hd@Call at times...

>
			 0 1 0 0 0 0 512 1 0 0 0 0
@Table col hd@Repeat interval

>
			 0 2 0 0 0 0 512 1 0 0 0 0
@Table col hd@Retry Period set by Notes

>
			 0 3 0 0 0 0 512 1 0 0 0 0
@Table col hd@Recommended uses

>
			 1 0 0 0 0 0 256 1 0 0 0 0
8:00 A.M. </m> 5:00 P.M.

>
			 1 1 0 0 0 0 256 1 0 0 0 0
0 

>
			 1 2 0 0 0 0 256 1 0 0 0 0
9 Hours (Entire range)

>
			 1 3 0 0 0 0 256 1 0 0 0 0
Medium or low</m>priority replication, when daily updates are sufficient, but a long retry period is necessary, as in international calls

>
			 2 0 0 0 0 0 256 1 0 0 0 0

>
			 2 1 0 0 0 0 256 1 0 0 0 0

>
			 2 2 0 0 0 0 256 1 0 0 0 0

>
			 2 3 0 0 0 0 256 1 0 0 0 0

>
		[e]
	[tble]
[frm]
	83
	1572868
	960
	960
	9437
	2089
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	8
	3
	11264
	26625 41984
	[frmlay]
		1620
		8477
		3
		0
		0
		3
		960
		0
		0
		2
		0
		1
		0
		960
		1
		1200
		9446
		0
	[tbl]
		 3 4 200 86 2026 86 1 43 43
		[h]
			 0 410 10 6 0 2 0
			 1 800 0 6 0 1 0
			 2 200 86 2 0 4 0
		[e]
		[w]
			 0 1539 0 6 0
			 1 1061 0 6 0
			 2 1698 0 6 0
			 3 4136 0 6 0
			 4 2026 10 4 0
		[e]
		[data]
			 0 0 0 0 0 0 512 1 0 0 0 0
@Table col hd@<:I0,0,0,0><+">Call at times...

>
			 0 1 0 0 0 0 512 1 0 0 0 0
@Table col hd@Repeat interval

>
			 0 2 0 0 0 0 512 1 0 0 0 0
@Table col hd@Retry Period set by Notes

>
			 0 3 0 0 0 0 512 1 0 0 0 0
@Table col hd@Recommended uses

>
			 1 0 0 0 0 0 256 1 0 0 0 0
8:00 A.M.

>
			 1 1 0 0 0 0 256 1 0 0 0 0
0 (N/A)

>
			 1 2 0 0 0 0 256 1 0 0 0 0
60 Minutes (default)

>
			 1 3 0 0 0 0 256 1 0 0 0 0
Low</m>priority replication, when daily updates are sufficient and where calls are successful after just a few retries (as on different networks at the same site)

>
			 2 0 0 0 0 0 256 1 0 0 0 0

>
			 2 1 0 0 0 0 256 1 0 0 0 0

>
			 2 2 0 0 0 0 256 1 0 0 0 0

>
			 2 3 0 0 0 0 256 1 0 0 0 0

>
		[e]
	[tble]
[frm]
	84
	1572868
	960
	4615
	9425
	5888
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	9
	4
	0
	45312 1
	[frmlay]
		1620
		8465
		3
		0
		0
		3
		4615
		0
		0
		2
		0
		1
		0
		720
		1
		1200
		9446
		0
	[tbl]
		 3 4 200 86 2026 86 1 43 43
		[h]
			 0 410 10 6 0 3 0
			 1 600 10 6 0 2 0
			 2 200 0 6 0 4 0
		[e]
		[w]
			 0 1121 0 6 0
			 1 824 0 6 0
			 2 1599 0 6 0
			 3 4878 0 6 0
		[e]
		[data]
			 0 0 0 0 0 0 512 1 0 0 0 0
@Table col hd@<:I0,0,0,0><+">Call at times...

>
			 0 1 0 0 0 0 512 1 0 0 0 0
@Table col hd@Repeat interval

>
			 0 2 0 0 0 0 512 1 0 0 0 0
@Table col hd@Retry Period set by Notes

>
			 0 3 0 0 0 0 512 1 0 0 0 0
@Table col hd@Recommended uses

>
			 1 0 0 0 0 0 256 1 0 0 0 0
8:00 A.M., 1:00 P.M., 4:00 P.M. 

>
			 1 1 0 0 0 0 256 1 0 0 0 0
0 (N/A)

>
			 1 2 0 0 0 0 256 1 0 0 0 0
60 Minutes (default)

>
			 1 3 0 0 0 0 256 1 0 0 0 0
Medium or low</m>priority replication when a few daily updates are sufficient and where calls are successful after just a few retries (as on different networks at the same site)

>
			 2 0 0 0 0 0 256 1 0 0 0 0

>
			 2 1 0 0 0 0 256 1 0 0 0 0

>
			 2 2 0 0 0 0 256 1 0 0 0 0

>
			 2 3 0 0 0 0 256 1 0 0 0 0

>
		[e]
	[tble]
[frm]
	85
	1572868
	960
	8633
	9430
	9896
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	10
	5
	0
	255 0
	[frmlay]
		1620
		8470
		3
		0
		0
		3
		8633
		0
		0
		2
		0
		116
		0
		720
		1
		1200
		9446
		0
	[tbl]
		 3 4 200 86 2026 86 1 43 43
		[h]
			 0 400 10 6 0 1 0
			 1 200 0 6 0 4 0
			 2 600 10 6 0 3 0
		[e]
		[w]
			 0 1539 0 6 0
			 1 840 0 6 0
			 2 2307 0 6 0
			 3 3741 0 6 0
		[e]
		[data]
			 0 0 0 0 0 0 512 1 0 0 0 0
@Table title@<:I0,0,0,0><+">Call at times...

>
			 0 1 0 0 0 0 512 1 0 0 0 0
@Table title@Repeat interval

>
			 0 2 0 0 0 0 512 1 0 0 0 0
@Table title@Retry Period set by Notes

>
			 0 3 0 0 0 0 512 1 0 0 0 0
@Table title@Recommended uses

>
			 1 0 0 0 0 0 256 1 0 0 0 0

>
			 1 1 0 0 0 0 256 1 0 0 0 0

>
			 1 2 0 0 0 0 256 1 0 0 0 0

>
			 1 3 0 0 0 0 256 1 0 0 0 0

>
			 2 0 0 0 0 0 256 1 0 0 0 0
8:00 A.M. </m> 5:00 P.M.; 11:00 P.M., 2:00 A.M. 

>
			 2 1 0 0 0 0 256 1 0 0 0 0
0 (N/A)

>
			 2 2 0 0 0 0 256 1 0 0 0 0
9 Hours (during the range); 60 Minutes (default) after the two set times

>
			 2 3 0 0 0 0 256 1 0 0 0 0
All replication; all mail routing; low</m>priority mail must be routed during a range of time between midnight and 6:00 A.M.

>
		[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
		780
		480
		3
		11940
		900
		0
		1
		0
		1
		1
		0
		1
		780
		9266
		1
		3
		9900
	[txt]
<:R1,1,3,7961,><:P19999,0,3->  Administrator's Guide	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
		900
		480
		3
		11940
		780
		0
		1
		0
		1
		1
		0
		1
		900
		9386
		1
		3
		9900
	[txt]
@Right pg foot@<:R1,1,3,8486,>Lotus Confidential 	Administrator's Guide <:P19999,0,3->

>
[elay]
[l1]
	0
[pg]
	22
	22 0 5 516 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
	38 415 39 36 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
	66 99 14 4 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
	86 93 88 36 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
	114 0 0 36 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
	147 320 24 4 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
	178 0 48 4 0 0 0 40 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	201 97 53 4 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
	238 101 48 4 0 0 0 40 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	275 0 0 36 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
	310 0 36 4 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
	342 0 0 36 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
	376 0 0 4 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
	400 0 0 4 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
	435 0 0 4 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
	460 0 5 4 1 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 5 0 0
	474 201 54 4 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
	495 93 24 4 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
	518 0 5 4 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
	537 0 5 4 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
	556 0 0 4 0 0 0 40 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	563 0 27 1029 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@Chapter 3 Setting Up and Managing Replication

This chapter discusses how to replicate databases between servers, how to set up and schedule replication, as well as connecting Notes servers in different environments. 


@Ahead@About replication

Notes lets you distribute copies of a source database onto multiple servers or workstations. This allows users on different networks in different locations to access the same information. Through the process of replication, Notes keeps all of these copies, 
known as replica databases, essentially identical over time.

For example, a user in one office can change a document in a replica database on a server at the same time that a user in another office makes a change to the same document in another replica database on their server. When the two servers connect to each ot
her at scheduled intervals, the databases can replicate changes to documents, access control lists, and database design elements, such as forms and views. 
<:X8,-32768;Index "replication" # "settings"><:X8,-32768;Index "replication settings" #>

@Bhead@What can and cannot be replicated

Notes can replicate the following:

@Bullet@Access control list (ACL) settings

@Bullet@Access control lists

@Bullet@Database design elements, such as forms, views, macros, selective replication formulas, as well as the icon that represents the database

@Bullet@Entire documents

@Bullet@Selected portions of documents

Notes cannot replicate the following:

@Bullet@Database settings

@Bullet@Replication settings

@Bullet@The contents of full-text indexes

@Bullet@View indexes

<+!><[>I suspect that this topic could use a bit more information.]<-!>

@See also hlp@
See also <+!><[><-!><+!> About types of replication, <-!><+!>About factors that control replication,<-!><+!> About setting up 
<-!><+!>replication]<-!>

<:p<* >>About types of replication

There are two types of replication. Both types have similar results.

@Bullet@Workstation-to-server replication allows you to replicate all databases that your workstation has in common with the server or to replicate only databases that you specify. For more information, see 
<+!><[>jump to About workstation-to-server replication]<-!> .

@Bullet@Server-to-server replication replicates all databases that the two servers have in common. For more information, see 
<+!><[>jump to About server-to-server replication]<-!>.

@See also hlp@
<+!><[>About <-!><+!>replication, About types of server-to-server replication, About setting up replication]<-!>

@Bhead title@About server-to-server replication<:X8,-32768;Index "server-to-server replication" #><:X8,-32768;Index "replication" # "types of">

Server-to-server replication is the process which changes to a replica database on one server are passed to the replica database on another server. Notes minimizes the amount of time that replication takes by passing only those changes that have occurred si
nce the previous replication between the two servers.

@Chead@Prerequisites for administrators 

The key to successful replication is establishing one or more connection documents. For server-to-server replication, you need at least one connection document in the Public Name & Address Book (PNAB) to enable one server to call the other server.

In the connection document are fields that you use to schedule replication. You identify the specific times or ranges of times, as well as the days of the week, when you want replication to occur. You also indicate the priority level of the databases that y
ou want to replicate. The database manager identifies the priority of a database in the 
<+!><[>hat?] <-!>document.

Although one connection document is sufficient to establish replication between two servers, you can create multiple connection documents to manage replication of databases of different priorities or to establish a different replication schedule for weekend
s, for example.

@Chead@What happens during server-to-server replication

Replication begins when it is scheduled in the connection document in the PNAB or when you type a server command at the console that forces immediate replication. Before replication, the two servers authenticate their identities to ensure that they are both
 certified with a mutually trusted Certifier ID.

First, the servers check the Replica ID on every database and build a list of the databases that they have in common--that is, databases whose Replica IDs are identical. The Replica ID is a unique number generates by Notes for a database and all of its repl
ica databases. A database is a true replica if it has the same Replica ID as the original database. The Replica ID, not the database file name, determines if two databases are replica copies of each other. 

Second, the "destination server"--that is, the server that will receive the changes-- compares its list of databases, including all subdirectories in the Notes data directory and any linked subdirectories to which the destination server has access, with the
 list that the "source server" has. The source server is the server that will provide the changes. The destination server then builds a list of databases that the servers have in common. For each database, the destination server builds a list of document, d
esign, and access control list (ACL) modifications since the previous replication with the source server.

Third, the destination server's Replicator processes each database in the list. For each, the Replicator requests that the source server send field-level modifications to each document. Notes does not replicate entire documents; it replicates only the field
s in a document that have changed since the previous replication. During replication, users can still work with databases that are being replicated, although access time might be slightly affected.

Fourth, when database replication is completely successful, the destination server's Replicator uses the time stamp of the source server to record the time at which the replication was completed. This information is recorded in the replication history of ea
ch database. <+!><[>where is that history? should I also talk about document info and the "modified" date here? are there now field-level IDs, since there's field-level replication?]<-!>

If errors occur during replication--for example, if the Replicator determines that documents are corrupted ---the replication history for those documents is not updated. If the Replicator encounters two identical errors in a database, it terminates the repl
ication for the database and proceeds to the next database. The next replication will again attempt to copy the modified documents. 

<+!>Karen: Do we need a topic on the Replicator? I've found a lot of info about how it works...and it seems a little too detailed to go in here<-!>

@See also hlp@
See also <+!><[>About connection documents<-!><+!>, About types of server-to-server replication, 
<-!><+!>About types of workstation-to-server replication; <-!><+!>About replication schedules, Viewing a Replica ID

<+!>.<-!>

@Bhead title@About types of server-to-server replication

Here's where we'll talk about pull pull, etc.

why do you use one type over another? pros, cons, etc.?

@Chead@Pull-Pull


@Chead@Push-Pull


@Chead@Push only


@Chead@Pull only


@See also hlp@See also 


@Bhead title@About workstation-to-server replication<:X8,-32768;Index "workstation-to-server replication" #>

Workstation-to-server replication allows users to replicate local database replicas, which are on their desktop, with database replicas on the server. To do this, the user initiates replication; the server never initiates replication with a workstation.<:X8,-32768;Index "replication types" #>
<:X8,-32768;Index "replication" # "types of">

Users who work away from the office often use workstation-to-server replication to obtain updated copies of their mail file and other critical databases.

@Chead@Prerequisites for workstation-to-server replication

For workstation-to-server replication to work, the user must do the following:

@Bullet@Make sure that the workstation has a modem.

@Bullet@Configure a COM port for the modem.

@Bullet@Create a remote connection document in the personal Name & Address book to connect the workstation with the server.

@Bullet@Obtain the domain and server name, as well as the phone number of a dial-in server from the system administrator.

@Bullet@<+!><[>The above stuff I made up. It needs a good looking over and a check against any mobile stuff I can find.]<-!>

@See also hlp@<+!>

<+!><[>Setting up server-to-server replication]<-!>

<+!>

<+!>.

@Ahead@About scheduling server-to-server replication

Scheduling replication between Notes servers is an important part of setting up your Notes system. To set up replication, you edit the connection documents in the Public Name & Address Book (PNAB).<:X8,-32768;Index "replication" # "scheduling"><:X8,-32768;Index "replication" # "server-to-server">

@Bhead@Calling schedules

In the connection document, you schedule replication by entering replication as a task and listing specific times and/or ranges of times when the server should attempt to contact the other server. 

@Chead@Calling at specific times

When you set up a calling schedule that includes a single time, such as 8:00AM or a series of single times, such as 8:00AM and 4:00PM, the server retries the call for an hour. For example, if the calling schedule is for 8:00AM and 4:00PM, the server retries
 the call from 8:00AM until 9:00AM and from 4:00PM until 5:00PM, or until replication succeeds. Because Notes automatically retries the call for one hour, it pays no attention to the Repeat at interval field in the connection document.

@Chead@Calling during ranges of times

When you set up a calling schedule that includes a range, you also indicate a repeat interval that specifies how often the call is made during the specified range. Be sure to set a range of time and a matching repeat interval, so each call can complete prio
r to the specified interval; otherwise, the next call cannot begin.

For example, suppose you create a connection document instructing server A to call server B from 8:00AM until 5:00PM with a repeat interval of 120 minutes. If server A calls and replicates successfully with server B at 8:30AM., server A will not place the n
ext call until 10AM.

@Bhead@When calls are incomplete

Notes computes a retry period based on the calling times and the repeat interval to determine how often the server tries to call again after a failed or incomplete attempt. Failure can occur because the remote phone is busy or does not answer or if replicat
ion terminates abruptly.

If the calling schedule is a range, the server retries the call for the length of the range until replication succeeds. When calling during a range with not repeat interval set, the time between call attempts increases with each unsuccessful attempt. This p
revents the server from wasting resources trying to make a call that cannot be completed. 
<+!><[>If the user lists mix of range and specific times, does notes pay attention to the repeat interval for the ranges?]

If the calling schedule is a single time or a series of single times, the server retries the call for an hour or until replication succeeds. 
<+!><[>Does this mean that it will try beyond the period if it's unsuccessful?]<-!>

To replicate databases from one server to another (one-way), create a single connection document on the server where the databases are located. To replicate databases between servers (two-way), you create connection documents on both servers.

When you set up two-way replication, create a schedule so one server always calls the other. Scheduling both servers on a network to call each other is a waste of network resources.

<+!>KAREN: The last two paragraphs on this topic are misplaced. I haven't figured out how to work in info on the various types of replication scheduling. There's a lot more to say on this topic.<-!>

@See also hlp@See also <+!><[>About mail routing, About scheduling mail routing, About using multiple connection documents for replication; Scheduling immediate ; scheduling ...<-!>


@Bhead title@Setting up server-to-server replication


@See also hlp@See also About scheduling server-to-server replication


@Chead title@Details: Setting up server-to-server replication




@Bhead title@Scheduling server-to-server replication<:X8,-32768;Index "scheduling" # "replication"><:X8,-32768;Index "replication" # "scheduling"><:X8,-32768;Index "replication" # "server-to-server">

To schedule replication between two servers, you edit the server's Connection document. 

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of the calling server from the Servers list. 

@Numbered list@Choose Name & Address Book.

@Numbered list@Choose View Connections.

@Numbered list@Select and open the calling server's Connection document.

@Numbered list@Choose Actions - Edit Document.

@Numbered list@Be sure this switch is set to Schedule Enabled in the Enabled/Disabled field. 

@Numbered list@Enter the time you want this server to contact the other server in the "Call at times" field. You can enter specific times, ranges (such as 8:00 AM - 10:00 PM), or both. Use a comma to separate times. 

@Numbered list@Enter the interval you want in the "Repeat interval of" field. The default is 360 minutes. 

@Numbered list@When you use a range of time in the "Call at times" field, enter the number of minutes between one call and the next. The server tries to replicate and route mail at the specified interval. If it can't complete its tasks, it keeps trying until it succeeds. 
After successful replication or mail routing, the server calls again at the repeat interval that you set. 

@Numbered list@Specifies the days of the week that you want the server to call in the "Days of week" field. By default, the server calls every day of the week. To use a different schedule for the weekend, create two Connection documents: one that specifies a schedule for 
calling Monday to Friday and another for calling on Saturday and Sunday.

@Numbered list@<+@>Specify Replication in the Tasks field. Both Mail Routing and Replication are enabled initially (separated by a comma). To set up different schedules and priorities for replication and routing, you create separate Connection documents.

@Numbered list@Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@See also hlp@See also scheduling server-to-server replication, ... routing, setting up immediate server-to-server routing,... replication


@Chead title@<-!><-">Details: Scheduling server-to-server replication


@Bhead title@
@Bhead title@Forcing immediate server-to-server replication

When you want to replicate changes to databases to and from servers, use the REPLICATE command. 
<:X8,-32768;Index "Server commands" # "REPLICATE"><:X8,-32768;Index "replication" # "forcing immediate"><:X8,-32768;Index "replication" # "server-to-server">

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of the server from the Servers list. 

@Numbered list@Choose Remote Console.

@Numbered list@Enter REPLICATE "server name"

@Numbered list@Close the Remote Console.


@See also hlp@See also Scheduling 


@Chead title@<-!><-">Details: Forcing immediate server-to-server replication



@Bhead title@Setting up one-way immediate server-to-server replication 

When you want to replicate changes to Notes databases in one direction, use the PULL command. 
<:X8,-32768;Index "Server commands" # "PULL"><:X8,-32768;Index "replication" # "server-to-server"><:X8,-32768;Index "replication" # "immediate one-way">

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of a server from the Servers list. 

@Numbered list@Choose Name & Address Book.

@Numbered list@Choose Remote Console.

@Numbered list@Enter PULL "server name"

@Numbered list@Close the Remote Console.

@See also hlp@See also scheduling server-to-server replication, ... routing, setting up immediate server-to-server routing


@Chead title@Details: Setting up one-way immediate server-to-server replication 


g

@Ahead@About database replicas<:X8,-32768;Index "database replicas" #>

A database replica is an exact copy of a database. When you create a database replica, the replica and the original database share the same Replica ID. This is a unique number that Notes assigns to each database. For two databases to replicate, they must ea
ch have this unique Replica ID, which Notes stores in the Database Properties. The file names of the databases can be completely different, but if their Replica IDs are identical, the databases will replicate.

@Bhead@Database replicas on servers<:X8,-32768;Index "database replicas" # "servers">

Creating a database replica on a server allows additional users in different sites or on different networks to access information. To enable users to create database replicas on a server, you must list their names in the Create replica databases field of th
e server document. Without this privilege, users cannot create replicas on the server. 

It's wise to limit the number of users who have this privilege--in fact, it's a good idea to create a group document in the Public Name & Address Book (PNAB) to list the users who have create replica access. That way, you can add and delete user names from 
that list to control who has this privilege. 

Create database replicas only as necessary. Unnecessary proliferation of replicas wastes server and network resources, as well as results in increased replication, access control list, and database management problems. To determine if a database replica is 
necessary, put the database on only one server and monitor the <+!><[>what?]<-!> to see how heavily used the database is. If you find that the database is heavily used by a particular group of people--for example, people at a regional office that is connect
ed over a wide area network--create a database replica on a local server for that group.

@Bhead@Database replicas on workstations<:X8,-32768;Index "database replicas" # "workstations">

Creating a database replica on a workstation allows an individual user to 
<+!><[>what? I need some more info for here.]<-!>

@See also hlp@See also <+!><[>Ways to create database replicas, ]<-!>


@Ahead@Ways to create replica databases

There are two ways to create replica databases. Which method you choose depends on whether you want to create a copy on the server or a copy on your workstation.

@Bullet@Creating a database replica on a server <+!><[>this text should be a jump]<-!>

@Bullet@Creating a database replica on a workstation <+!><[>this text should be a jump]<-!>

@See also hlp@See also <+!><[>About database replicas]<-!>


@Bhead title@About replica databases on workstations


@See also hlp@See also Creating a replica database on a workstation

@Chead title@Creating a replica database on a workstation


@See also hlp@See also About replica databases on workstations

@Chead title@Details: Creating a replica database on a workstation


@See also hlp@See also Creating a replica database on a workstation

@Bhead title@About replica databases on servers


@See also hlp@See also Creating a replica database on a server

@Chead title@Creating a replica database on a server


@See also hlp@See also About replica databases on servers


@Chead title@Details: Creating a replica database on a server


@See also hlp@See also Creating a replica database on a server



@Ahead@About factors that control what replicates<:X8,-32768;Index "replication" # "factors that control">

When designing a database, a database designer can use a number of features that control what documents actually replicate between versions of the database. The designer can tailor these to meet security, time, or resource constraints. Unexpected replicatio
n results--for example, replication not being allowed, wrong documents replicating, or too few documents replicating--can often be traced to the way in which replication controls are set for the database.

If the database designer uses no replication control features, replica databases receives the entire contents of the original database during replication.

The following are the controls that the database designer can set:

@Bullet@The ACL for the database is where the database designer lists the users and servers that can access and change the database. The database ACL controls whether database elements, such as views, forms, documents, and the ACL itself, are replicated. For more i
nformation, see <+!><[>jump here to a topic called About database access control lists<-!><+!> -- this topic doesn't yet exist]<-!>

@Bullet@Read access lists determine whether certain documents can be "read" by the destination server. A destination server can receive documents only if the database designer has given the server read access to them. For more information, see 
<+!><[>jump to a topic called About database read-access lists--topic doesn't yet exist]<-!>

@Bullet@The replication settings, which appear on the <+!><[>what? dialog or property sheet?]<-!>, control whether documents meeting special criteria, such as age, are replicated. For more information, see 
<+!><[>jump here to a topic called About database replication settings--this topic doesn't yet exist]<-!>

@Bullet@Replication formulas, which the database designer creates, establish criteria for which documents are replicatedt--for example, they can instruct the server to replicate only documents written by a certain person or about a certain topic. For more informati
on, see <+!><[>jump to About database replication formulas-- this topic doesn't yet exist]<-!>

As a system administrator, you can control access to the server by listing users and servers in the access control list (ACL) for the server. By doing so, you 
<+!><[>what?]

@See also hlp@See also <+!><[>List of access levels<-!><+!>]<-!>


@Bhead title@About database access control lists 


@See also hlp@See also Editing the database-specific access control list


@Chead title@Editing the database-specific access control list<:X8,-32768;Index "access control list" # "database-specific">

To change the access control list for a database, add or remove people, servers, or groups in the Access Control infobox.

@Numbered list@At your workstation, choose File - Database - Access Control.

@Numbered list@Click Show All in the dropdown box to view all of the people, servers, and groups that can access this database. 

@Numbered list@To delete access to the database, select a name of a person, group, or a server in the list box and then click Remove.

@Numbered list@To provide access to the database, click Add and enter the name of the person, group, or server. Specify the level you want in the Access Level box.  

@Numbered list@To rename a person, server, or group, select a name of a person, group, or a server in the list box and then click Rename. Specify the level of access if needed.

@Numbered list@ Click OK to exit the infobox.

@See also hlp@See also About database access control lists


@Chead title@Details: Editing the database-specific access control list


@Bhead title@About database read-access lists 


@See also hlp@See also Editing the database-specific read-access list


@Chead title@Editing the database-specific read-access list


@See also hlp@See also About database read-access lists


@Chead title@Details: Editing the database-specific read-access list


@Bhead title@About database replication settings 


@See also hlp@See also Specifying database-specific replication settings; Displaying database-specific replication information; Viewing a Replica ID


@Chead title@Specifying database-specific replication settings


@See also hlp@See also About database replication settings; Displaying database-specific replication information; Viewing a Replica ID


@Chead title@Details: Specifying database-specific replication settings



@Chead title@Displaying database-specific replication information


@See also hlp@See also Specifying database-specific replication settings; About database replication settings; Viewing a Replica ID


@Chead title@Details: Displaying database-specific replication information



@Chead title@Viewing a Replica ID 


@See also hlp@See also Specifying database-specific replication settings; Displaying database-specific replication information; About database replication settings


@Chead title@Details: Viewing a Replica ID



@Bhead title@About database replication formulas 


@See also hlp@See also Specifying database-specific replication formulas



@Chead title@Specifying database-specific replication formulas


@See also hlp@See also About database replication formulas


@Chead title@Details: Specifying database-specific replication formulas



@Bhead title@About selective replication 


@See also hlp@See also Writing a formula for selective replication; 


@Chead title@Writing a formula for selective replication


@Chead title@Details: Writing a formula for selective replication



@Bhead title@About replication priority 


@See also hlp@See also Specifying the priority of a specific database


@Chead title@Specifying the priority of a specific database


@See also hlp@See also About replication priority; About factors that control what replicates


@Chead title@Details: Specifying the priority of a specific database




@Bhead title@List of access level<:X8,-32768;Index "access level" # "list of">s

Notes supports seven access levels. A database designer uses these access levels to define a database's access control list (ACL). 

@Chead@No Access

Users and servers have absolutely no access to the database. Users cannot even add the database icon to their workspace.

@Chead@Depositor

Users can compose documents, but they cannot read any documents, not even the ones that they compose. 
<+!><[>what about servers? does this a apply<-!><+!> to servers too?]<-!>

@Chead@Reader

Users can read documents, but they cannot compose any documents.

Servers with this access cannot replicate any changes to or from another server. 

@Chead@Author

Users with this access can:

@Bullet@Compose documents, read documents, and edit the documents that they compose.

Servers with this access can:

@Bullet@Replicate new documents. 

@Bullet@If the database designer checks Can delete documents on the ACL, the servers can also delete documents.

@Chead@Editor

Users with this access can:

@Bullet@Compose documents, read documents, and edit any documents, regardless of who composed them.

Servers with this access can:

@Bullet@Replicate new documents and changes to existing documents.

@Bullet@If the database designer checks Can delete documents on the ACL, the servers can delete documents.

@Chead@Designer

Users with this access can:

@Bullet@Have all of the privileges of Editor access

@Bullet@Modify the database icon, the About Database document, the Using Database document

@Bullet@Modify all design elements--for example, fields, forms, and views

Servers with this access can:

@Bullet@Have all of the privileges of Editor access

@Bullet@Replicate design elements--that is, fields, forms, views, and macros

@Bullet@Replicate the database icon, Using Database, and About Database documents

@Bullet@Replicate replication formulas

@Chead@Manager

Users with this access can:

@Bullet@Have all of the privileges of Designer access

@Bullet@Define database replication settings

@Bullet@Modify the database ACL

@Bullet@Delete the database

Servers with this access can:

@Bullet@Have all of the privileges of Designer access

@Bullet@Replicate the database ACL

@See also hlp@See also <+!><[>Creating a database access control list (ACL) -- topic not yet written]<-!>


@Bhead title@About server factors that control what replicates


@See also hlp@See also About factors that control what replicates; Preventing replication of specific databases


@Chead title@Preventing replication of specific databases<:X8,-32768;Index "Replication" # "preventing"><:X8,-32768;Index "database replication" # "preventing">

To prevent replication in specific databases, you edit the calling server's Connection document. 

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of the server from the Servers list. 

@Numbered list@Choose Name & Address Book.

@Numbered list@Choose View Connections.

@Numbered list@Select and open the calling server's Connection document.

@Numbered list@Choose Actions - Edit Document.

@Numbered list@Sets the limit on how long a single replication session can last in the "Replication Time Limit" field. The time is specified in minutes. When the replicator reaches the limit, replication ends whether it is completed or not. Clear the field to disable the 
limit. ??What is MINIMUM, MAXIMUM or RECOMMENDED??

@Numbered list@Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@See also hlp@See also About server factors that control what replicates


@Ahead@Ways to change server-to-server replication 

After setting up basic replication for servers, you can now make changes to the server's Connection documents to schedule immediate, daily, or weekly replication. You can determine the priority of a database or mail message by giving it a High, Medium , or 
Low values. Sample schedules are provided in this section. <:X8,-32768;Index "replication" # "server-to-server"><:X8,-32768;Index "replication" # "changing">

@Bullet@<-!><-">Specifying how servers exchange data during replication

@Bullet@<++>S<-+><+,>pecifying which database<-,><+,>s replicate<-,>

@Bullet@Specifying <+,>replication priority for databases<-,>

@Bullet@Specifying a time limit for replication 

@See also hlp@See also WS rep



@Bhead title@Specifying how servers exchange data during replication

To specify the type of replication you want or how servers exchange data, you edit the calling server's Connection document. 
<:X8,-32768;Index "replication" # "type of">

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of a server from the Servers list. 

@Numbered list@Choose Name & Address Book.

@Numbered list@Choose View Connections.

@Numbered list@Select and open the calling server's Connection document.

@Numbered list@Choose Actions - Edit Document.

@Numbered list@Specify the type of replication in the Replication Type field. 

@Bullet@Pull Pull indicates that each server sends and receives data

@Bullet@Push Pull indicates that the calling server sends changes to the destination server and the destination server sends all updated data to the calling server

@Bullet@Pull only indicates that the destination server sends all updated data to the calling server

@Bullet@Push only indicates that the calling server sends all the changes to the destination server

@Numbered list@Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@See also hlp@See also 


@Chead title@Details: Specifying how servers exchange data during replication



@Bhead title@Specifying<+,> which database<-,><+,>s to replicate<-,>

To specify which databases you want to replicate, you edit the calling server's Connection document. 
<:X8,-32768;Index "replication" # "changing"><:X8,-32768;Index "replication" # "database"><:X8,-32768;Index "database replication" # "specifying">

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of the calling server from the Servers list. 

@Numbered list@Choose Name & Address Book.

@Numbered list@Choose View Connections.

@Numbered list@Select and open the calling server's Connection document.

@Numbered list@Choose Actions - Edit Document.

@Numbered list@Specify the databases you want to replicate in the "Files to Replicate" field. The default is a blank field, which indicates that all the databases in common are replicated. You can also list specific database file names. ??ANY WAY TO GROUP - according to D
IRECTORY??

@Numbered list@Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@See also hlp@See also 


@Chead title@Details: Specifying <+,>which database<-,><+,>s to replicate<-,>



@Bhead title@Specifying<+,> replication priority for databases<-,> 

To specify the priority of the databases you want to replicate, you edit the calling server's Connection document. 
<:X8,-32768;Index "replication" # "priority"><:X8,-32768;Index "replication" # "database"><:X8,-32768;Index "database replication" # "priority">

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of the server from the Servers list. 

@Numbered list@Choose Name & Address Book.

@Numbered list@Choose View Connections.

@Numbered list@Select and open the calling server's Connection document.

@Numbered list@Choose Actions - Edit Document.

@Numbered list@<:S+194>Specify the priority of the databases you want to replicate in the "Replicate databases of priority" field. The default is blank, which means that all databases replicate. Press SPACE to show the other choices, which are High, Medium, Low, and Medium and Hi
gh. You can choose to replicate only Medium and High priority databases, or only High priority databases. Connections that replicate higher priority databases must occur more often. You can also set a replication priority for each database. 

@Numbered list@Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@See also hlp@
@Chead title@Details: Specifying <+,>replication priority for databases<-,>

To take advantage of replication priorities, you must set up two or three Connection documents per server</m>to</m>server connection. Each Connection document triggers replication of different priority databases. You can set this by creating one or two more
 Connection documents to connect to the same server. Choose one or both other choices in the "Replicate databases of priority:" field. Also, specify Calling times, Repeat interval, and Days of week.

@Note@Connection documents for different priority databases to the same remote computer must not specify overlapping times. If the times overlap by even as little as a minute, the Connection document chosen is arbitrary. This causes erratic replication; one Conne
ction document is chosen at random each time replication takes place. For example: Replication is OK when you set Medium and High to 1:00 A.M. - 9:59 PM and Low is set to 10:00 P.M. - 12:59 A.M. Replication problems occur when you set Medium and High to 1:0
0 A.M. - 10:00 P.M. and Low is set to 10:00 P.M. - 1:00 A.M.

Database managers often set this priority when they set up a database. If your database is not replicating often, increase the priority level. 


@Chead title@<:S+194>Example: Specifying replication priority for databases 

<:S+194>Suppose there are 15 databases on your server. The database managers have assigned High priority to five databases, Medium priority to five databases, and Low priority to five databases.

<:S+194>To replicate these databases to a remote server, you might set up three Remote Connection documents. Each document specifies one of the following replications:

@Bullet@<:S+194>Once every hour: High priority databases only

@Bullet@<:S+194>Once every six hours: High and Medium priority databases only

@Bullet@<:S+194>Once every 24 hours: High, Medium, and Low priority databases

The databases then replicate according to the schedule you created. (You may want to schedule a call between midnight and 6:00 A.M., both to replicate low</m>priority databases and, if it's a Remote connection, to route low</m>priority mail.)


@Bhead title@<+!>Specifying a time limit for each replication <-!>

To specify a time limit for replication, you edit the calling server's Connection document. 

@Numbered list@At your workstation, select File - Tools - Administration.

@Numbered list@Choose the name of the server from the Servers list. 

@Numbered list@Choose Name & Address Book.

@Numbered list@Choose View Connections.

@Numbered list@Select and open the calling server's Connection document.

@Numbered list@Choose Actions - Edit Document.

@Numbered list@Sets the limit on how long a single replication session can last in the "Replication Time Limit" field. The time is specified in minutes. When the replicator reaches the limit, replication ends whether it is completed or not. Clear the field to disable the 
limit. ??What is MINIMUM, MAXIMUM or RECOMMENDED??

@Numbered list@Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@See also hlp@See also 

@Chead title@<+!>Details: Specifying a time limit for each replication<-!>



@Ahead@About multiple replicators



@See also hlp@See also Specifying multiple replicators 


@Bhead title@Specifying multiple replicators 


@See also hlp@See also About multiple replicators 


@Chead title@Details: Specifying multiple replicators 

@Bhead title@

@See also hlp@See also About multiple replicators


@Ahead@About replication history


@See also hlp@See also Checking the server log for replication history, Clearing the replication history


@Chead title@Details: Preventing replication of specific databases




@Ahead@Checking the server log for replication history


@See also hlp@See also About replication history


@Bhead title@Clearing the replication history


@See also hlp@See also About replication history


@Ahead@About replication and security 


@See also hlp@See also 


@Ahead@Table of server commands for replication

PULL

REPLICATE 

SHOW TASKS 

HELP

SHOW PORT


@See also hlp@See also <+!><[>Issuing a server command?<-!><+!>]<-!>

@Ahead@Table of differences between routing and replication in Connection documents

The following table summarizes the differences between Connection documents set up specifically for replication, and Connection documents set up for mail routing. 

@Table title@Connection document differences between replication and mail routing

@Table title@<:t0>

@Bhead title@About replication and routing schedules

<:X8,-32768;Index "Scheduling" # "replication and mail routing"><:X8,-32768;Index "Replication" # "scheduling"><:X8,-32768;Index "Mail routing" # "scheduling"><:X8,-32768;Index "Name & Address Book" # "Connection document"><:X8,-32768;Index "Connection document" #>
Scheduling replication and mail routing between Notes servers is an important part of setting up Notes servers. Some sites have replication designers to plan, create, and maintain schedules and handle replication requests. Improperly scheduled replication a
nd mail routing can result in replication and mail routing problems. You can check the sample replication and remote mail routing calling schedules for an example of schedules that cover a range of hours, a single time, a list of times, or a combination. 

@Chead@<+!>Determining calling schedules 

The Connection document contains two fields that determine the calling schedule, "Call at times" and "Repeat at interval". "Call at times" indicates the range of time or specific times when calls are attempted. "Repeat interval of" determines how soon the s
erver calls after a successful exchange of information if the schedule is set to a range of time.

When you set a specific range in the "Call at times" field, the "Repeat at interval" field is used to determine how often the call is made during the specified range. Be sure to set a range of time and a matching "Repeat at interval" so each call can comple
te prior to the specified interval, otherwise the next call cannot begin.

When you set a specific time in the "Call at times" field, the "Repeat at interval" field is not used. Be sure to set specific times so the calls can complete prior to the specified time, otherwise the next call cannot begin. 

@Chead@How the Retry Period is Determined

Notes computes the <+">Retry Period<:X8,-32768;Index "Retry Period" # "defined"><-"> based on the calling times and the repeat interval to determine how often the server tries to call again, after a failed or incomplete attempt (for example, if the remote p
hone is busy or does not answer, or if replication or mail routing terminates abruptly), as follows:

@Bullet@If the calling schedule is a <+">range<-">, such as 8:00 A.M. to 5:00 P.M., the server retries the call for the length of the range (from 8:00 A.M. until 5:00 P.M.), until replication or mail routing succeeds. When calling during a range with no repeat inte
rval set, the time between call attempts increases with each unsuccessful attempt. This prevents the server from wasting resources trying to make a call that can't be completed.

@Bullet@If the calling schedule is not a range, but a <+">single time<-"> such as 8:00 A.M., or a series of single times such as 8:00 A.M. and 4:00 P.M., the server retries the call for an hour. For example, in the latter case, the server retries from 8:00 A.M. unt
il 9:00 A.M., and from 4:00 P.M. until 5:00 P.M. (or until replication or mail routing succeeds). 

@Chead@Schedule Guidelines

@Bullet@When scheduling mail routing, keep in mind the existing replication schedule, because mail routing normally accompanies replication. In other words, do not overschedule traffic between servers.

@Bullet@You can schedule two calls a day for both replication and mail routing: one in the morning, one in the afternoon. 

@Bullet@When scheduling mail routing between two servers, you may want to schedule one of the servers to do most of the calling, for billing purposes. (But each server must have at least one Remote Connection document scheduling mail routing to the other server.)

@Bullet@Schedule calls for times when there is less activity on the network. For example, have the servers call before or after work hours, or at lunchtime.

@Bullet@For peer</m>to</m>peer connections, limit the number of servers that one server calls to 10 to avoid overloading the server with too many tasks. This isn't necessary with a hub</m>and</m>spoke configuration (see "Hub</m>and</m>Spoke Connections" later in th
is chapter for more information).

@Bullet@Server performance degrades if the server makes too many calls. When the server becomes overloaded, calls start backing up, mail does not get through, and users may receive poor service from the server.

@Bullet@With multiple servers' schedules, staggered schedules work well. For example, you could schedule the first server to replicate and/or route mail from 8:00 A.M. to 10:00 A.M., the second server from 8:05 A.M. to 10:05 A.M., and so on. 

@Bullet@For greater efficiency and economy, schedule replications of different priority databases. See "Using Replication Priorities in Schedules" later in this chapter. You can schedule a call between midnight and 6:00 A.M., for example, to replicate low</m>priori
ty databases and (if a Remote connection) to route low</m>priority mail.

@Bullet@Connection documents should not have overlapping schedules for the same task, in the same direction, at the same time. Overlapping task schedules give the server conflicting instructions.<:X8,-32768;Index "Conflict" # "in Connection document schedules">

@Chead title@Example: Setting specific replication time

When you set a specific time in the "Call at times" field, the "Repeat at interval" field is not used. Be sure to set specific times so the calls can complete prior to the specified time, otherwise the next call cannot begin. 

For example, if you specify 8:00 AM and 9:00 AM in the "Call at times" field, then the two servers (A and B) begin to replicate data or route mail at 8:00 AM and complete the call at 9:03AM. The server cannot begin the second call at 9:00 AM since the first
 task is not completed prior to 9:00 AM. 

@See also hlp@
About replication and routing schedules


@Chead title@Example: Overlapping replication times 

For example, when you create a Connection document that specifies replication from server East to server North between 9:00 A.M. and 6:00 P.M., be sure there is not another Connection document specifying replication from server East to server North between 
4:00 P.M. and 10:00 P.M.

Edit one of the documents to eliminate the two</m>hour overlap between 4:00 P.M. and 6:00 P.M. For example, you can edit the second document to specify routing from 6:01 P.M. to 10:00 P.M.

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Scheduled replication on different ports 

Do not create two Connection documents for replication that specify calling the same server on different ports. For example, a server should not have a Connection document that specifies calling a server for replication on LAN0, and another Connection docum
ent that specifies calling the same server for replication on COM1. Make sure when you set up two-way replication that the servers are not calling each other on different ports at the same time. 

@Bullet@To communicate with servers outside of your domain, be sure your domain's Name & Address Book contains Connection documents that initiate communication from your domain's server. 

@Bullet@Be sure that your domain's Name & Address Book contains Server documents that define servers within your domain.<+"> 
<-">

@Bullet@Be sure to keep track of the servers' ports you are using as well as the scheduled time and task. Especially, since Notes Release 3 and 4 allows the Mail Router to make calls on multiple ports at the same time. 

@Indnt bullet@For remote connections, include all ports in the Connection document.

@Indnt bullet@For network connections, the Mail Router uses any available enabled network ports. 

@Indnt bullet@On OS/2 Servers, you can adjust the NOTES.INI variable MailMaxThreads to increase the maximum number of threads the Mail Router can create to perform its mail transfers efficiently. The default is one thread per server port.

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Scheduling international connections

<:X8,-32768;Index "International" # "scheduling connections">When planning your schedules to connect servers internationally, you must be aware of the time differences between countries. You want to replicate the documents created during each time zone's pe
ak business or work hours as well as make sure that you are replicating at an off-peak time.

For example, if you're in the Eastern United States and you replicate with a Notes server in Germany, you want to schedule replication and mail routing between 3:00 A.M. and 12:00 P.M. Eastern Standard Time (EST) to correspond to Germany's business hours, w
hich are six hours ahead of EST. 

Also, the Notes administrator in Germany can schedule replication and mail routing between 3:00 P.M. to 11:00 P.M. (??NEED TIME ZONE NAME) to correspond to United States' EST business hours, which are six hours behind.

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Setting specific replication range 

When you set a specific range in the "Call at times" field, the "Repeat at interval" field is used to determine how often the call is made during the specified range. Be sure to set a range of time and a matching "Repeat at interval" so each call can comple
te prior to the specified interval, otherwise the next call cannot begin. 

For example, when you set Server A to call Server B from 8:00 until 5:00, with a Repeat Interval of 120 minutes, Server A calls and replicates successfully with server B at 8:30 AM. If server B then calls server A at 9:00 AM to replicate, server A suppresse
s a replication with server B since server A has already replicated with server B within the past 120 minutes. 

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Scheduling a range with a repeat interval

This example uses a call range of 8:00 A.M. to 5:00 P.M. and the Repeat Interval is 120 minutes. The server makes the first call at 8:00 A.M.

If unsuccessful, the server retries periodically until it establishes a connection and successfully replicates or routes mail. If the server cannot connect and replicate, it keeps trying until 5:00 P.M., the end of the calling period.

After the server successfully replicates or routes mail, it calls again 120 minutes after the previous call ended.

@Table title@ Range with repeat interval example

@AmiTable@<:t1>

A call range with a repeat interval of 2-3 hours is a frequently used schedule. A range simplifies the administration of multiple servers because the range and repeat interval ensure that each server connects regularly throughout the day. 

Staggered schedules, as illustrated in Figure 4</m>3, are best when scheduling multiple servers - especially when they're connecting to a Hub server (described in the next section).

@Tip@Grouping same</m>function servers to start at the same time helps with troubleshooting. For example, if you start Database servers replicating at the same time and users report a problem, you know it's a replication problem and not a mail routing problem. 


When you are connecting multiple servers, you can stagger the connection schedules to allow faster and more efficient replication and routing. (CHECK old FIGURES)

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Scheduling a range without a repeat interval

This example uses a call range from 8:00 A.M. to 5:00 P.M. and no Repeat Interval. The server retries periodically after a failed call, for the entire call range, but won't call again after a successful exchange of information.

In a calling range with no repeat interval, the time between call attempts increases with each unsuccessful attempt. In this example, the server attempts the first call at 8:00 A.M. If unsuccessful, the server tries again at 8:05 A.M., and again at 8:15 A.M
., until it succeeds at, say, 8:35 A.M. The server won't try to call again until 8:00 the next morning.

@Table title@ Range without a repeat interval

@AmiTable@<:t2>

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Scheduling a single time 

The schedule in this example is set for one call only. There is no need for a Repeat Interval, since the server is set up for just one calling time per day. (You set a Repeat Interval only if you have a call range.) The Retry Period defaults to 60 minutes.

The server calls at 8:00 A.M. If unsuccessful, it retries for an hour. Whether or not the call succeeds, the next call is not until 8:00 the next morning. 

@Table title@ A single time

@AmiTable@<:t3>

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Scheduling a list of times

In this example, the schedule is set for a list of times. Again there is no need for a Repeat Interval, and the Retry Period defaults to 60 minutes. 

The server calls at 8:00 A.M. If unsuccessful, it retries for up to an hour, until 9:00 A.M. Whether or not the call succeeds, the next call attempt is at 1:00 P.M. If unsuccessful, it retries for up to an hour, until 2:00 P.M. Whether or not the call succe
eds, the next call is at 4:00 P.M. If unsuccessful, it retries for up to an hour, until 5:00 P.M.

@Table title@ A list of times

@AmiTable@<:t4>

@See also hlp@See also About replication and routing schedules


@Chead title@Example: Scheduling a range and a list of times

The last example uses a combination: first, a range from 8:00 A.M. to 5:00 P.M., and then single times of 11:00 P.M. and 2:00 A.M. You don't set a Repeat Interval, since this schedule uses single times. Between 8:00 A.M. and 5:00 P.M., the server calls as i
n the second example. At 11:00 P.M. and 2:00 A.M., the server calls as in the fourth example. 

@Note@If you are setting up a dial</m>up (remote) connection, be sure to schedule mail routing during a 
<+">range<-"> of time between midnight and 6:00 A.M. By default, this is the only time Low Priority mail is routed (but it can be changed by changing the NOTES.INI variable MailLowPriorityTime= as described in Appendix A).<:X8,-32768;Index "Low priority mail" #>
<:X8,-32768;Index "Mail" # "low priority">

@Table title@ A range and a list of times

@AmiTable@<:t5>

@See also hlp@<:S+194>Replication and routing schedules

<:S+194>

@Ahead@<:S+194>Testing replication


@See also hlp@
Troubleshooting replication


@Ahead@Troubleshooting replication

When you cannot replicate between two servers, you can check specific fields to be sure that replication is enabled and the servers are connected. The following table ?? information provides the troubleshootig basics. If you need additional information, che
ck the Troubleshooting section (Chapter 12). 

 

@See also hlp@
Troubleshooting replication

>

[Embedded]
00085054
