[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[sequence]
	20
	0
	0
	0
	10
	3
	Numbered list
	0
	Bullet
	0
	Indnt bullet
	0
	Indnt caution
	0
	Indnt tip
	0
	Indnt note
	0
	Caution
	0
	Tip
	0
	Note
	0
	Footnote
[prn]
	PostScript (QMS)
[port]
	LPT3:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	Chapter 4 Controlling How a Database Replicates
	
	
	
	
	801536211
	10
	799105760
	11
	35
	0
	0
	0
	0
	Chapter 04
	
	
	
	
	
	1
[fopts]
	0
	1
	0
	0
	
	
[lnopts]
	2
	Body Text
	1
[docopts]
	5
	2
[GramStyle]
	
[ParaNum]
	1
[tag]
	Body Text
	2
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Body Text
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Ahead
	3
	[fnt]
		Helvetica
		240
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		280
		4
		360
		120
		4
		100
	[brk]
		80
	[line]
		9
		0
		4
		0
		1
		1
		1
		110
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Body Text
	0
	0
[tag]
	Bhead title
	4
	[fnt]
		Helvetica
		220
		0
		16385
	[algn]
		1
		3
		960
		0
		0
	[spc]
		40
		260
		4
		100
		90
		4
		100
	[brk]
		80
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead title
	5
	[fnt]
		Helvetica
		200
		0
		16385
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		80
		0
		4
		100
	[brk]
		80
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Bhead
	6
	[fnt]
		Helvetica
		220
		0
		16385
	[algn]
		1
		3
		960
		0
		0
	[spc]
		40
		260
		4
		100
		90
		4
		100
	[brk]
		80
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead
	7
	[fnt]
		Helvetica
		200
		0
		16385
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		80
		0
		4
		100
	[brk]
		80
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Numbered list
	8
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1704
		336
		336
	[spc]
		40
		240
		4
		0
		80
		4
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		6
		<*:>.
		0
		3
		1
		1
		2
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Numbered list
	0
	0
[tag]
	1st lev para
	9
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		2040
		0
		0
	[spc]
		40
		240
		4
		0
		80
		4
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	1st lev para
	0
	0
[tag]
	Bullet
	11
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1740
		300
		300
	[spc]
		40
		240
		4
		0
		80
		4
		100
	[brk]
		64
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		<*1>
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	bullet
	0
	0
[tag]
	Indnt bullet
	12
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		2064
		216
		216
	[spc]
		40
		240
		4
		0
		80
		4
		100
	[brk]
		64
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		<*1>
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt bullet
	0
	0
[tag]
	2nd lev para
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		2280
		0
		0
	[spc]
		40
		240
		4
		0
		80
		4
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	2nd lev para
	0
	0
[tag]
	See also prnt
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	See also prnt
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Book art
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Book art
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Callout text
	0
	[fnt]
		Helvetica
		160
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		180
		4
		0
		0
		3
		100
	[brk]
		0
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Callout text
	0
	0
[tag]
	Figure title
	0
	[fnt]
		Helvetica
		180
		0
		16385
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		220
		4
		40
		80
		4
		100
	[brk]
		0
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Figure title
	0
	0
[tag]
	Chapter title
	0
	[fnt]
		Helvetica
		320
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		360
		4
		0
		480
		3
		100
	[brk]
		16
	[line]
		9
		0
		3
		0
		1
		3
		1
		644
		10
		1
	[spec]
		0
		1
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Chapter title
	0
	0
[tag]
	1st pg foot
	0
	[fnt]
		Palatino
		180
		0
		49153
	[algn]
		2
		3
		0
		0
		0
	[spc]
		40
		220
		4
		60
		0
		4
		100
	[brk]
		0
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	1st pg foot
	0
	0
[tag]
	Right pg foot
	0
	[fnt]
		Palatino
		180
		0
		49153
	[algn]
		2
		3
		0
		0
		0
	[spc]
		40
		220
		4
		60
		0
		4
		100
	[brk]
		0
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Right pg foot
	0
	0
[tag]
	Left pg foot
	0
	[fnt]
		Palatino
		180
		0
		49153
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		220
		4
		60
		0
		4
		100
	[brk]
		0
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Left pg foot
	0
	0
[tag]
	Table title
	0
	[fnt]
		Helvetica
		180
		0
		16385
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		220
		4
		40
		80
		4
		100
	[brk]
		16
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		8
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Table title
	0
	0
[tag]
	Table col hd
	0
	[fnt]
		Palatino
		180
		0
		49154
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		220
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		7
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		0
		
		
		
	Table col hd
	0
	0
[tag]
	Table Text
	0
	[fnt]
		Palatino
		180
		0
		49152
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		220
		4
		0
		0
		4
		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
		0
		
		
		
	Table Text
	0
	0
[tag]
	See also hlp
	0
	[fnt]
		Helvetica
		200
		0
		16385
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		80
		0
		4
		100
	[brk]
		16
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	See also hlp
	0
	0
[tag]
	See also btn
	0
	[fnt]
		Helvetica
		200
		0
		16384
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		80
		0
		4
		100
	[brk]
		0
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	See also btn
	0
	0
[tag]
	Crossref
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		2040
		0
		0
	[spc]
		40
		240
		4
		0
		40
		4
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Crossref
	0
	0
[tag]
	Indnt caution
	0
	[fnt]
		Helvetica
		200
		0
		16384
	[algn]
		1
		3
		2040
		900
		0
	[spc]
		40
		240
		4
		0
		80
		4
		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]
		272
		1
		2
		.
		,
		$
	Indnt caution
	0
	0
[tag]
	Indnt tip
	0
	[fnt]
		Helvetica
		200
		0
		16384
	[algn]
		1
		3
		2040
		480
		0
	[spc]
		40
		240
		4
		0
		80
		4
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		18944
		3
		1
		1
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Indnt tip
	0
	0
[tag]
	Indnt note
	0
	[fnt]
		Helvetica
		200
		0
		16384
	[algn]
		1
		3
		2040
		600
		0
	[spc]
		40
		240
		4
		0
		80
		4
		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]
		272
		1
		2
		.
		,
		$
	Indnt note
	0
	0
[tag]
	Caution
	0
	[fnt]
		Helvetica
		200
		0
		16384
	[algn]
		1
		3
		1680
		900
		0
	[spc]
		40
		240
		4
		0
		80
		4
		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]
		272
		1
		2
		.
		,
		$
	Caution
	0
	0
[tag]
	Tip
	0
	[fnt]
		Helvetica
		200
		0
		16384
	[algn]
		1
		3
		1680
		480
		0
	[spc]
		40
		240
		4
		0
		80
		4
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		18944
		3
		1
		1
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Tip
	0
	0
[tag]
	Note
	0
	[fnt]
		Helvetica
		200
		0
		16384
	[algn]
		1
		3
		1680
		600
		0
	[spc]
		40
		240
		4
		0
		80
		4
		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]
		272
		1
		2
		.
		,
		$
	Note
	0
	0
[tag]
	Mono
	0
	[fnt]
		Courier
		180
		0
		32769
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		24
		220
		4
		0
		120
		4
		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]
		280
		1
		2
		.
		,
		$
	Mono
	0
	0
[tag]
	Indnt mono
	0
	[fnt]
		Courier
		180
		0
		32769
	[algn]
		1
		3
		2040
		0
		0
	[spc]
		24
		220
		4
		0
		120
		4
		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]
		280
		1
		2
		.
		,
		$
	Indnt mono
	0
	0
[tag]
	Dhead
	0
	[fnt]
		Palatino
		200
		0
		49153
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		24
		240
		4
		0
		0
		4
		100
	[brk]
		16
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		5
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Dhead
	0
	0
[tag]
	Parameter
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		24
		240
		4
		0
		0
		4
		100
	[brk]
		16
	[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
	0
	0
[tag]
	Formula
	0
	[fnt]
		Helvetica
		180
		0
		16384
	[algn]
		1
		3
		2040
		0
		0
	[spc]
		40
		220
		4
		0
		80
		4
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		1
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Formula
	0
	0
[tag]
	Browse
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Browse
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Keyword
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Keyword
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Context
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Context
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Title
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Title
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Macros
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Macros
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Footnote
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		2400
		720
		0
	[spc]
		24
		240
		4
		0
		80
		4
		100
	[brk]
		4
	[line]
		8
		0
		1
		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]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Alink
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Butnbar
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Butnbar
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[tag]
	Window
	0
	[fnt]
		Palatino
		200
		0
		49152
	[algn]
		1
		3
		1680
		0
		0
	[spc]
		40
		240
		4
		0
		120
		4
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		18944
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		.
		,
		
	Window
	4
	1
	2280
	1
	2869
	1
	3480
	1
	4080
	0
[frm]
	5
	1573060
	960
	960
	8486
	2839
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	7
	0
	1
	16384 142
	[frmlay]
		1841
		7526
		1
		0
		0
		1
		960
		0
		0
		2
		0
		0
		0
		0
		1
		1764
		11496
		0
	[tbl]
		 9 8 0 86 1336 86 1 43 43
		[h]
			 0 220 86 2 0 2 0
			 1 663 86 2 0 1 0
			 2 220 86 2 0 7 0
			 3 220 86 2 0 7 0
			 4 220 86 2 0 7 0
			 5 220 86 2 0 7 0
			 6 220 86 2 0 7 0
			 7 220 86 2 0 7 0
			 8 220 86 2 0 7 0
		[e]
		[w]
			 0 1440 86 2 0
			 1 1286 86 2 0
			 2 428 86 3 0
			 3 873 86 3 0
			 4 791 86 3 0
			 5 626 86 3 0
			 6 708 86 3 0
			 7 643 86 3 0
		[e]
		[data]
			 0 1 0 0 0 0 4369 1 0 0 0 0
<+!>

>
			 0 2 408 1 6 0 4369 1 0 0 0 0
<+B><+!>Changes replica can receive from serve<-!>r

>
			 0 3 128 0 1 0 0 0 0 0 0 0
			 0 4 128 0 2 0 0 0 0 0 0 0
			 0 5 128 0 3 0 0 0 0 0 0 0
			 0 6 128 0 4 0 0 0 0 0 0 0
			 0 7 128 0 5 0 4369 0 0 0 0 0
			 1 1 0 0 0 0 4369 1 0 0 0 0
<:S+-1><+!>Server a<-!><+!>ccess l<-!><+!>evel <-!><+!>in<-!><+!> <-!><+!>r<-!><+!>eplica<-!><+!> ACL<-!>

>
			 1 2 24 0 0 0 4369 1 0 0 0 0
<+B><:S+-1>ACL

>
			 1 3 24 0 0 0 4369 1 0 0 0 0
<+B><:s><:S+-1>Replica-

<+B><:S+-1>tion

<+B><:S+-1> Formulas

>
			 1 4 24 0 0 0 4369 1 0 0 0 0
<+B><:s><:S+-1>Design

<+B><:S+-1> Features

>
			 1 5 24 0 0 0 4369 1 0 0 0 0
<+B><:S+-1>Agents

>
			 1 6 24 0 0 0 4369 1 0 0 0 0
<+B><:s><:S+-1>Edited

<+B><:S+-1>Docu-

<+B><:S+-1>ments

>
			 1 7 24 0 0 0 4369 1 0 0 0 0
<+B><:s>New

<+B>Docu-

<+B>ments

>
			 2 1 0 0 0 0 4369 1 0 0 0 0
Manager<:f240,BArial,0,0,0><+&>a<-&><:f>

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

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

>
			 2 4 0 0 0 0 4369 1 0 0 0 0
X

>
			 2 5 0 0 0 0 4369 1 0 0 0 0
X

>
			 2 6 0 0 0 0 4369 1 0 0 0 0
X

>
			 2 7 0 0 0 0 4369 1 0 0 0 0
X

>
			 3 1 0 0 0 0 4369 1 0 0 0 0
Designer<:f240,BArial,0,0,0><+&>a<-&><:f>

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

>
			 3 4 0 0 0 0 4369 1 0 0 0 0
X

>
			 3 5 0 0 0 0 4369 1 0 0 0 0
X

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

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

>
			 4 1 0 0 0 0 4369 1 0 0 0 0
Editor<:f240,BArial,0,0,0><+&>a<-&><:f>

>
			 4 2 0 0 0 0 4369 0 0 0 0 0
			 4 3 0 0 0 0 4369 0 0 0 0 0
			 4 4 0 0 0 0 4369 0 0 0 0 0
			 4 5 0 0 0 0 4369 0 0 0 0 0
			 4 6 0 0 0 0 4369 1 0 0 0 0
X

>
			 4 7 0 0 0 0 4369 1 0 0 0 0
X

>
			 5 1 0 0 0 0 4369 1 0 0 0 0
Author<:f240,BArial,0,0,0><+&>a<-&><:f>

>
			 5 2 0 0 0 0 4369 0 0 0 0 0
			 5 3 0 0 0 0 4369 0 0 0 0 0
			 5 4 0 0 0 0 4369 0 0 0 0 0
			 5 5 0 0 0 0 4369 0 0 0 0 0
			 5 6 0 0 0 0 4369 0 0 0 0 0
			 5 7 0 0 0 0 4369 1 0 0 0 0
X

>
			 6 1 0 0 0 0 4369 1 0 0 0 0
Depositor

>
			 6 2 0 0 0 0 4369 0 0 0 0 0
			 6 3 0 0 0 0 4369 0 0 0 0 0
			 6 4 0 0 0 0 4369 0 0 0 0 0
			 6 5 0 0 0 0 4369 0 0 0 0 0
			 6 6 0 0 0 0 4369 0 0 0 0 0
			 6 7 0 0 0 0 4369 0 0 0 0 0
			 7 1 0 0 0 0 4369 1 0 0 0 0
Reader<+&><:f240,BArial,0,0,0>b<-&><:f>

>
			 7 2 0 0 0 0 4369 0 0 0 0 0
			 7 3 0 0 0 0 4369 0 0 0 0 0
			 7 4 0 0 0 0 4369 0 0 0 0 0
			 7 5 0 0 0 0 4369 0 0 0 0 0
			 7 6 0 0 0 0 4369 0 0 0 0 0
			 7 7 0 0 0 0 4369 0 0 0 0 0
			 8 1 0 0 0 0 4369 1 0 0 0 0
No Access

>
			 8 2 0 0 0 0 4369 0 0 0 0 0
			 8 3 0 0 0 0 4369 0 0 0 0 0
			 8 4 0 0 0 0 4369 0 0 0 0 0
			 8 5 0 0 0 0 4369 0 0 0 0 0
			 8 6 0 0 0 0 4369 0 0 0 0 0
			 8 7 0 0 0 0 4369 0 0 0 0 0
		[e]
	[tble]
[frm]
	6
	1573060
	720
	960
	8475
	1969
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	6
	1
	28276
	29807 101
	[frmlay]
		3652
		7755
		1
		0
		0
		1
		960
		0
		0
		2
		0
		0
		0
		0
		1
		1764
		11496
		0
	[tbl]
		 2 4 0 86 1272 86 1 43 43
		[h]
			 0 220 86 2 0 3 0
			 1 880 86 2 0 1 0
		[e]
		[w]
			 0 1440 86 2 0
			 1 2148 86 2 0
			 2 1632 86 2 0
			 3 2148 86 2 0
		[e]
		[data]
			 0 1 0 0 0 0 4369 1 0 0 0 0
<+!>O<-!><+!>n MISSOURCE<-!>

>
			 0 2 0 0 0 0 4369 1 0 0 0 0
<+!>O<-!><+!>n ACCOUNTING<-!>

>
			 0 3 0 0 0 0 4369 1 0 0 0 0
<+!>On <-!><+!>SALES<-!>

>
			 1 1 0 0 0 0 4369 1 0 0 0 0
MISSOURCE, Manager

<:s>ACCOUNTING, Editor

SALES, Editor

>
			 1 2 0 0 0 0 4369 1 0 0 0 0
MISSOURCE, Manager

<:s>ACCOUNTING, --

SALES, Editor

>
			 1 3 0 0 0 0 4369 1 0 0 0 0
MISSOURCE, Manager

<:s>ACCOUNTING, Editor

SALES, --

>
		[e]
	[tble]
[frm]
	6
	1573060
	720
	6846
	9159
	8161
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	5
	2
	256
	0 0
	[frmlay]
		8067
		8439
		1
		0
		0
		1
		6846
		0
		0
		2
		0
		0
		0
		0
		1
		3722
		9538
		0
	[tbl]
		 2 5 0 86 1440 86 1 43 43
		[h]
			 0 220 86 2 0 4 0
			 1 880 86 2 0 1 0
		[e]
		[w]
			 0 1440 86 2 0
			 1 1929 86 2 0
			 2 1516 86 2 0
			 3 1565 86 2 0
			 4 1516 86 2 0
		[e]
		[data]
			 0 1 0 0 0 0 4369 1 0 0 0 0
On PI_HR1

>
			 0 2 0 0 0 0 4369 1 0 0 0 0
On PI_DC2

>
			 0 3 0 0 0 0 4369 1 0 0 0 0
On PI_CHICAGO

>
			 0 4 0 0 0 0 4369 1 0 0 0 0
On PI_TORONTO

>
			 1 1 0 0 0 0 4369 1 0 0 0 0
PI_HR1, Manager<-!><-">

PI_DC2, Editor

PI_CHICAGO, Editor

PI_TORONTO, Editor

>
			 1 2 0 0 0 0 4369 1 0 0 0 0
PI_HR1, Manager


>
			 1 3 0 0 0 0 4369 1 0 0 0 0
PI_HR1, Manager

>
			 1 4 0 0 0 0 4369 1 0 0 0 0
PI_HR1, Manager

>
		[e]
	[tble]
[lay]
	Standard
	3079
	[rght]
		12960
		10166
		1
		960
		1200
		3
		960
		720
		2
		1
		0
		1
		0
		2
		1
		960
		9446
		5
		1
		720
		1
		1440
		1
		2880
		1
		4320
		1
		5760
	[lft]
		12960
		10166
		1
		720
		1200
		3
		960
		960
		2
		1
		0
		1
		0
		2
		1
		720
		9206
		5
		1
		720
		1
		1440
		1
		2880
		1
		4320
		1
		5760
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		1
	[frmlay]
		960
		10166
		1
		720
		180
		3
		0
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		0
	[txt]
>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		2
	[frmlay]
		960
		10166
		1
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		0
	[txt]
>
	[flft]
	[lyfrm]
		1
		5056
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		3
	[frmlay]
		12960
		10166
		1
		720
		480
		3
		11940
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		0
	[txt]
<:P19999,0,4-> Database Manager's Guide                                           Lotus Confidential

>
	[frght]
	[lyfrm]
		1
		13248
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		4
	[frmlay]
		12960
		10166
		1
		960
		480
		3
		11940
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		0
	[txt]
Lotus Confidential                     Controlling How a Database Replicates 
<:P19999,0,4->

>
[elay]
[l1]
	0
[pg]
	35
	16 164 73 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	31 81 82 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	43 410 48 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	59 0 5 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 3 0 0
	73 0 5 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 1 0 0
	87 322 39 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 64 75 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	116 160 71 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	128 286 48 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	145 77 34 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	163 246 83 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	177 83 83 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	195 161 73 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	220 0 9 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	243 0 9 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	259 68 26 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	286 0 0 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	310 199 47 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	331 0 54 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	348 76 78 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	366 157 42 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	378 0 33 0 0 1 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	395 168 83 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	415 81 73 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	432 0 36 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	459 0 5 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	479 0 23 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	504 150 52 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	522 0 5 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	540 0 71 0 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	560 171 42 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	579 0 83 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	596 170 74 32 0 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	615 0 45 0 1 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	625 711 13 1025 0 0 0 240 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><:#1004,8486><:f280,,><+!>Chapter 4 Controlling How a Database Replicates<-!><-!><:f>

<:s><:#480,8486>This chapter provides an overview of replication and then discusses the following topics:

@Bullet@<:s><:#240,8486>Choosing server access levels for proper replication

@Bullet@<:s><:#240,8486>Creating a replica on a server

@Bullet@<:s><:#240,8486>Assigning a replication priority to a database

@Bullet@<:s><:#240,8486>Customizing replication

@Bullet@<:s><:#240,8486>Disabling replication

@Bullet@<:s><:#240,8486>Using the replication history

@Bullet@<:s><:#240,8486>Resolving replication and save conflicts

@Bullet@<:s><:#240,8486>Troubleshooting replication problems

@Ahead@<:s><:#390,8486>About replication

<:s><:#720,8486><:X8,1;Index "Replication" # "overview"><:f><:X8,1;Index "Replica ID" #><:f,,>Notes lets you keep multiple copies of a single database, called replicas, on multiple servers or workstations. This lets users on a variety of networks in a variety of locations 
access the same information.

<:s><:#1440,8486>Replication is the process of exchanging modifications between replicas. Through replication, Notes makes all of the replicas essentially identical over time. For example, users in one office can make changes to a replica on their server at the same time th
at users in another office make changes to a replica of the same database on their server. When the servers replicate, each replica is updated with the information from the replica on the other server.

<:s><:#720,8486>A replica has the same replica ID as the original database. This distinguishes a replica from a copy of a database because the common ID lets you replicate changes between the replica and the original database.

<:s><:#1200,8486>Replication can occur between two servers or between a workstation and a server, for example, between a laptop and a server. Replication can also occur in one or both directions between replicas. That is, you can set up replication so that two replicas rece
ive updates from each other, or so that only one replica receives updates from the other.

<:s><:#1680,8486>Notes lets you choose which databases you want to replicate and when to replicate them. Replication can occur automatically according to a schedule you specify, or manually through server or workstation commands you specify. Replication between servers gene
rally occurs automatically on a schedule specified by a database manager or network administrator, whereas replication between a workstation and a server generally occurs manually when a user needs to replicate updates.

@See also btn@<:s><:#240,8486><:N794794480,D,65535,1,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Ahead@<:s><:#390,8486>About server-to-server replication<-!><-"><-!><-"><-!><-"><-!><-"><-!><-"><:f><-!><-!><-!><-">

<:s><:#960,8486>Replication between Notes servers most often occurs according to schedules set by Notes administrators in Name & Address Book connection records. An administrator can also force server-to-server replication using a server console command. Either server can 
initiate replication. 

<:s><:#960,8486>Replication can be a two-way process in which each participating server receives updates from the other. During two-way replication, each server or workstation plays two roles: a source server that provides information and a destination server that receives
 information.<:X8,2;Index "Source server" # "defined"><:X8,2;Index "Destination server" # "defined">

<:s><:#240,8486><:f180,BArial,0,0,255><+!><+">Figure here<-"><-!><:f>

<:s><:#960,8486>Notes also allows one-way replication to occur. A Notes administrator can schedule replication between servers so that one always acts as a source server and the other as a destination server.<-!><-"><-"> Or an administrator can manually initiate one-way re
plication at the server console.

@See also prnt@<:s><:#240,8486>For more information, see the Administrator's Guide.

@Ahead@<:s><:#390,8486>About features that affect what information replicates between servers

<:s><:#480,8486>These features affect what information one database replica receives from another and can cause two database replicas to contain different information.

@Chead@<:s><:#240,8486>Access Levels

<:s><:#960,8486>Server access in the ACL of a replica determines whether a replica can receive information from another replica and if so what information it can receive. For example, the ACL might indicate that a replica can receive design changes but not changes to the A
CL.<:f,,> 

@Chead@<:s><:#240,8486>Read access lists

<:s><:#960,8486>A database may have access lists associated with views, forms, and Reader fields that allow only a subset of people or servers in the ACL to read them.  A replica must include its own server in these access lists for the server pass along changes to documen
ts associated with the access lists.

@Chead@<:s><:#240,8486>Replication settings 

<:s><:#960,8486>Replication settings control replication characteristics such as whether a replica sends or receives deletions, whether a replica contains only more recently modified documents, whether a replica receives a subset of documents according to a replication for
mulas, and so on.

@Ahead@<:s><:#390,8486>About server access levels and replication 

<:s><:#960,8486>Access levels assigned to source servers in the ACL of a database replica determine what information (if any) the replica can receive from replicas of the database on those servers during replication. Make sure the ACL of each replica database contains the 
names of all source servers that store the replica.

@See also prnt@<:s><:#240,8486><-!><-">For more information about the ACL, see Chapter 3.

@See also prnt@<:s><:#480,8486>Access levels assigned to source servers in the ACL of a replica database, from highest to lowest, and their meaning in terms of replication are:

@Bhead@<:s><:#260,8486><-!><-"><-!><-"><-!><-">Manager access

<:s><:#720,8486>The database replica can receive all changes to the ACL from the server as well as all changes allowed by other access levels. The replica only receives deletions if the ACL option "Can delete documents" is selected for the server. 
<:X8,3;Index "Manager access" # "for servers">

<:s><:#480,8486>Although it is not necessary to list a server with Manager access in the ACL of its own replica, doing so lets people know which server has Manager access.<-!><-">

<:s><:#720,8486>You should limit the number of servers that have Manager access to a database. It's common in hub-and-spoke network configurations to assign only the hub server Manager access so that ACL changes are made on only one server.

@Bhead@<:s><:#260,8486>Designer access

<:s><:#1440,8486>The database replica can receive from the server all changes to the database design and to replication formulas but not ACL changes. 
<-!><-"><-">Database design changes include changes to views, forms, agents, the database icon, Using This Database and About This Database documents. The database replica can also receive all changes allowed by lower access levels. The replica can only rec
eive deletions if the ACL option "Can delete documents" is selected. 
<:X8,3;Index "Designer access" # "for servers">

@Bhead@<:s><:#260,8486>Editor access

<:s><:#720,8486>The database replica can receive new documents and document changes from the server. The replica only receives deletions if the ACL option "Can delete documents" is selected.  
<:X8,4;Index "Editor access" # "for servers">

@Bhead@<:s><:#260,8486><+!>Author a<-!><+!>ccess

<:s><:#480,8486>The database replica can receive only new documents from the server. The replica only receives deletions if the ACL option "Can delete documents" is selected. 
<:X8,4;Index "Author access" # "for servers">

@Note@<:s><:#960,8486>Author access prevents all changes from replicating, even changes made by people assigned Author access. To allow a replica to receive changes made by people with Author access, assign the server Editor access or higher in the replica ACL. 
<:f180,BArial,0,0,255><+!><+">CORRECT??<-"><-!><:f>

@Bhead@<:s><:#260,8486>Reader access

<:s><:#240,8486>The server can pull changes from the replica database but not send changes to it.

<:s><:#720,8486>To ensure that your server can act as a source server for another server yet prevent the other server from making changes to the replica on your server, grant the other server Reader access to your replica. 
<-!><-">

@Bhead@<:s><:#260,8486><+!>Depositor a<-!><+!>ccess<-!>

<:s><:#720,8486>The replica cannot receive changes from the server nor can the replica on the other server receives changes from it. This access level applies to users only and is not relevant for servers.

@Bhead@<:s><:#260,8486>No Access

<:s><:#480,8486><-!><-">The server cannot access the replica at all. Use this access prevent a server from receiving changes from and sending changes to the database replica.

<:#720,8486>Simply omitting a server name from an ACL isn't necessarily the same as listing it with No Access since Notes automatically gives names omitted from the ACL the access level assigned to the -Default- group. 

@Bhead@<:s><:#260,8486><-!><-"><-!><-">Summary of server access levels

<:s><:#480,8486>The following table summarizes servers access levels and their affect on replication.

<:s><:t0>

<:s><:#240,8486><+!>Summary of server access levels and replication<-!>

<:s><:#480,8486><:f240,BArial,0,0,0><+&> a <-&><:f>Replica can also receive document deletions from server if the option "Can delete documents" is selected.

<:s><:#240,8486><:f240,BArial,0,0,0><+&>b<-&><:f> Allows server to pull changes from the replica but not to send changes.

<:s><:#240,8486><:f180,BArial,0,0,255><+!><+">

<:s><:#480,8486><+!><+"><:f180,BArial,0,0,255>FIGURE HERE ILLUSTRATING <-!><-"><:f><+!><+"><:f180,BArial,0,0,255>REPLICATION ACCORDING TO SERVER ACL SETTINGS<-"><-!><:f>

@Chead title@<:s><:#240,8486>Examples: Server access levels and replication

@Dhead@<:s><:#240,8486>Example 1: Server access levels in an application tracking database

<+@><:S+-1><:#1295,8486><:f180,BArial,0,0,0>Lu & Ramsey is a small consulting firm that uses Notes for many<:f><:f180,BArial,0,0,0> of its daily business activities. The company's<:f><:f180,BArial,0,0,0> Management Information Services (MIS) group<:f><:f180,BArial,0,0,0> is respon
sible for developing and maintaining company-wide Notes applications as well as applications for use<:f><:f180,BArial,0,0,0> by specific departments. 
<:f><:f180,BArial,0,0,0>MIS uses an<:f><:f180,BArial,0,0,0> Application Tracking database 
<:f><:f180,BArial,0,0,0>to<:f><:f180,BArial,0,0,0> inform all employees of the status of 
<:f><:f180,BArial,0,0,0>applications <:f><:f180,BArial,0,0,0>under development and to provide a list of all applications already in production<:f><:f180,BArial,0,0,0>. 
<:f><:X8,5;Index "ACL" # "servers in, example"> <:X8,5;Index "Examples" # "servers in ACL">

<+@><:S+-1><:#1055,8486><:f180,BArial,0,0,0>The MIS department maintains two servers<:f><:f180,BArial,0,0,0>: MISLAB and MISSOURCE. 
<:f><:f180,BArial,0,0,0>MIS uses MISLAB f<:f><:f180,BArial,0,0,0>or 
<:f><:f180,BArial,0,0,0>application<:f><:f180,BArial,0,0,0> development. O<:f><:f180,BArial,0,0,0>nly MIS developers and their managers have access to this server.<:f><:f180,BArial,0,0,0> MISLAB holds the design template for the Application Tracking databas
e. <:f><:f180,BArial,0,0,0>MIS uses MISSOURCE for<:f><:f180,BArial,0,0,0> 
<:f><:f180,BArial,0,0,0>the department's daily activities and for all communication<:f><:f180,BArial,0,0,0> with other Lu & Ramsey servers.  

<+@><:s><:S+-1><:#422,8486><:f180,BArial,0,0,0>The Accounting and Sales<:f><:f180,BArial,0,0,0> departments maintain their own Notes servers<:f><:f180,BArial,0,0,0>, 
<:f><:f180,BArial,0,0,0>ACCOUNTING and<:f><:f180,BArial,0,0,0> SALES.<:f>

<+@><:S+-1><:#480,8486>MISSOURCE, ACCOUNTING, and SALES replicate though peer-to-peer connections. 

<+@><:S+200><:#400,8486><+!><:f180,BArial,0,0,0>Server access levels in replica ACL<-!><:f><+!>s<-!> 
<:f180,BArial,0,0,0>Replicas of the<:f><:f180,BArial,0,0,0> Application Tracking database reside<:f><:f180,BArial,0,0,0> on MISSOURCE, ACCT, SALES, and R&D.<:f>

<:s><:#480,8486>The following table lists the server access levels assigned to the ACL of each replica.

<:s><:t1>

<:s><:#240,8486> These access levels settings ensure that

@Bullet@<:#240,8486>MISSOURCE controls all ACL and design changes to the database.

@Bullet@<:s><:#480,8486>New documents and changes to existing documents can originate from any server and replicate to all other servers.

@Dhead@<:s><:#240,8486>Example 2: Server access levels in a human resources database

<+@><:S+-1><:#1477,8486><:f180,BArial,0,0,0>Pagano Industries, a company headquartered in San Francisco, has sales and service offices in the U.S. and Canada. The Human Resources department at company headquarters is responsible for defining job descriptions, job grades, and polic
ies and procedures for hiring and performance review. The department developed a database called "Personnel" for this purpose. Field offices hire autonomously, so Human Resources pulls employee information from the field office to keep records up-to-date an
d to administer benefits.  <:X8,6;Index "ACL" # "servers in, example"> 
<:X8,6;Index "Examples" # "servers in ACL"><:f>

<+@><:S+-1><:#960,8486><:f180,BArial,0,0,0><+!>Server access levels in replica ACLs <-!><:f>The company servers holding replicas of the database are PI_HR1, the server used by the Human Resource Department, and PI_DC2, PI_CHICAGO, and  PI_TORONTO, the field office servers. PI_HR1
 is set up as a hub server; the field servers replicate with it but not with each other.

<:s><:S+-1><:#480,8486>The following table lists the server access levels assigned to the ACL of each replica.

<:s><:t2>

<:s><:#240,8486> These access level settings ensure that

@Bullet@<:#240,8486>PI_HR1 controls all design and ACL changes to the database.

@Bullet@<:#480,8486>New documents and changes to existing documents that originate on PI_HR1 replicate to all field office servers.

@Bullet@<:#480,8486>New documents and changes to existing documents that originate on PI_DC2, PI_CHICAGO, or PI_TORONTO replicate to all replicas through PI_HR1.

@Dhead@<:s><:#240,8486>Example 3: Server access levels in a distributed client tracking database

<:s><:S+200><:#1000,8486>Universal Foods has three regional offices, one in Los Angeles, one in Boston, and one in London. Several area offices report to each regional office. The company uses a customized version of the Client Tracking template. Each regional office has an applica
tion design team responsible for maintaining the Client Tracking database for the region. 
<:X8,6;Index "ACL" # "servers in, example"> <:f><:X8,6;Index "Examples" # "servers in ACL">

<:s><:#480,8486>Each regional office includes a server that replicates with the other regional offices and with its area servers. 

<+@><:s><:S+200><:#800,8486><+!><:f180,BArial,0,0,0>Server access levels in replica ACL<-!><:f><+!>s 
<-!>The ACL of the Client Tracking replica on each regional server gives Editor access to its area servers as well as  to all other regional servers. This access ensures that all new documents and changes to existing documents replicate to all servers.

<+@><:s><:S+-1><:#720,8486>The ACL of the replica on each area server gives Designer access to its regional server. This access prevents ACL changes on regional servers from writing over ACLs on area servers.<-!><-">

@Bhead title@<:s><:#260,8486><:f180,BArial,0,0,255><+!><+">Figure here<-"><-!><:f>

@See also prnt@<:s><:#240,8486>For information on creating the ACL, see Chapter 3.

<:s><:#240,8486>

@Ahead@<+@><:s><:#390,8486>About guidelines for selecting server access levels 

<:s><:#720,8486>Server access levels are often the cause of databases failing to replicate as expected. The following points are important for ensuring that database replicate correctly:

@Chead@<:s><:#480,8486>Source server access level in the ACL of a database replica determines what the replica receives

<:s><:#1440,8486>Notes refers to the database replica ACL to determine what each replica can receive from another. For example, suppose there are two replicas of a database, one on server A and another on server B. The ACL on the server A replica gives server B Manager acce
ss and therefore receives all changes from Server B; the ACL on the server B replica gives server A Editor access and receives only new and modified documents from the server A replica.

<:s><:#240,8486><:f180,BArial,0,0,255><+!><+">Figure here????

@Chead@<:s><:#240,8486><-">Servers should have access as high as their users

<:s><:#1200,8486>For a server to pass on all possible changes made within a database replica it stores, the replica ACL must give the server an access level at least as high as the highest user access level.  For example, if someone makes design changes to a database replic
a, the server storing the replica must have Designer or Manager access in the replica ACL in order to pass along the changes.

<:s><:#720,8486>A database replica must also include its server in any read access lists used for views, forms, or Reader fields for the server to be able to pass along changes made to documents associated with these access lists.

@Note@<:s><:#480,8486>A server must have at least Editor access to pass along changes made by users with Author access. 
<:f180,BArial,0,0,255><+!><+">CORRECT??<-"><-!><:f>

@Chead title@<:s><:#240,8486>Intermediate servers must have adequate access

<:s><:#1920,8486>If replication occurs through one or more intermediate servers, the intermediate servers act alternately as source and destination servers and must have the access level necessary for passing along the changes. For example, suppose you want ACL changes on S
erver A to replicate to Server C through an intermediate server, Server B.  To enable Server A to send changes first to Server B, the Server B replica ACL must give Server A Manager access. Then, to enable Server B to pass these changes along to Server C, t
he ACL on Server C must give Server B Manager access.

<:s><:#240,8486><:f180,BArial,0,0,255><+!><+">FIGURE HERE<-"><-!><:f>

@Chead@<:s><:#240,8486>Use Reader access for one-way replication

<:s><:#480,8486>Give a server Reader access in the ACL of a replica to allow the server to receive changes from the replica but not to send changes back. 

<:s><:#240,8486>

@Ahead@<:s><:#390,8486>About using server groups in the ACL 

<:s><:#960,8486>Whenever possible, use server groups in an ACL rather than individual server names. Using groups enables you to add or delete a server name from a central location and have the change automatically reflected in any ACLs that include the group. 
<:X8,8;Index "ACL" # "groups in">Groups listed in an ACL must exist in a public Name & Address Book. 

<:s><:#480,8486>Notes provides the following two groups in every Name & Address Book. A Notes administrator is responsible for adding servers to each group.

@Chead@<:#240,8486><+!>LocalDomainServers<-!> 

<:#960,8486>Servers in the same domain as the server on which the database is stored. This server group typically is given higher access than the OtherDomainServers group. 
<:f,,> LocalDomainServers is often given Designer access to allow replication of design changes ac<:f><:f,,>ross the domain. 
<:f><:X8,8;Index "LocalDomainServers" #><:f><:f,,> <:X8,8;Index "Groups" # "LocalDomainServers">

@Chead@<:#240,8486><+!>OtherDomainServers

<:#960,8486>Servers outside the domain of the server on which the database is stored. This group is typically assigned a lower access such as Reader access so that control of the database remains within the local domain. To prevent a database from replicating outside t
he local domain, assign OtherDomainServers No Access.

<:#720,8486>An exception to this rule is if each server contains Name & Address Books for all domains; in this case give OtherDomainServers and LocalDomainServers the same access to ensure that changes can replicate to all domains. 
<:X8,8;Index "OtherDomainServers" #> <:X8,8;Index "Groups" # "OtherDomainServers">

@Bhead@<:s><:#260,8486>External companies in groups

<:#960,8486>The Notes Administrator should not include servers of outside companies in the LocalDomainServers or OtherDomainServers groups, since these groups are often assigned high access to databases.  Instead, the Notes administrator should create a separate group 
for external servers. <:X8,9;Index "Groups" # "external servers in"> 
<:X8,9;Index "Servers" # "external">

@Ahead@<:s><:#390,8486>About replication of design templates

<:s><:#960,8486>The database designer can create a design template for a database, making design changes to the template rather than to the working copy of the database. A designer can manually update working replicas of the database with the template. Or the designer can 
rely on the server DESIGN task to do this.

<:s><:#1440,8486>If the DESIGN task is used to update a database design, you must create a replica of the design template in the Notes data directory or subdirectory on each server that stores a replica of the database. Create a replica of a design template in the same way 
that you create a replica of a database. Servers must have Manager or Designer access to replicate design changes. Replication of the templates should occur at least once a day so that the replica designs stay in sync.

<:s><:#480,8486>The server Design task updates all databases to conform to their templates. The DESIGN task runs by default every morning at 1:00 A.M. local time.<-">

@See also prnt@<:s><:#240,8486>For information on design templates, see the Application Developer's Guide.

@See also prnt@<:s><:#240,8486>For information on the Design task, see the Administrator's Guide.

@Ahead@<+@><:#390,8486>About replication and workflow applications

@Bhead@<+@><:s><:#260,8486>Mail routing and replication schedules

<+@><:#1680,8486>Because workflow applications often use mail to route documents and Notes servers are often scheduled to route mail more frequently than they replicate databases, it's possible for an e-mail notification with a link to arrive before the new or updated docum
ent to which it links is replicated. Work with your Notes administrator to set the optimal routing and replication schedules for mail files and workflow applications. Also consider building a delay into agents that send e-mail notifications, such as waiting
 24 hours.

@Note@<+@><:s><:#1200,8486>Replication delays are typically related to the number of intermediate servers through which replication occurs for the updates to reach their destinations. It may take as long for a database to replicate from San Jose to Los Angeles as it does from San Jos
e to Tokyo, depending on the replication architecture within an organization.

@Bhead@<+@><:#260,8486>Multiple-database workflow applications

<+@><:#960,8486>If your workflow applications uses multiple databases and you are creating replicas on one or more additional servers, be sure to add the full set of databases to each server. This is essential if the application uses links and lookups for connects between 
databases.

<+@><:s><:I0,0,0,0><:#240,8486>

@Ahead@<:s><:#390,8486>About deciding if a replica on a server is needed

<:s><:#240,8486>You may need to create a database replica because:

@Bullet@<:s><:#480,8486>The database is heavily used and you want to improve its performance by distributing it across servers.

@Bullet@<:s><:#240,8486>Remote offices require their own replicas.

@Bullet@<:s><:#480,8486>A group of people are only interested in a subset of documents within the database.

@Bullet@<:s><:#480,8486>You want to use a replica as a backup from which to restore information if the original gets corrupted.

<:s><:#1200,8486>One strategy for determining if database replicas are needed is to initially put a database on one server only and monitor its use. If you find that the database is heavily used by a particular group of people, for example, people at a regional office conne
cted over a wide area network, then you might add a replica of the database for use by this subset of people.

<:s><:#1200,8486>Create replicas of a database only as necessary. Unnecessary proliferation of replicas can waste server and network resources. Multiple replicas can also require more database maintenance. Keep in mind that since two replicas are likely to be out of sync a 
certain amount of time between replications, creating a replica is not useful if people will need real-time access to the database.

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486><-!><-"><-!><-"><-!><-"><-!><-"><-!><-"><:f><-!><-!>Creating a replica on a server

<:s><:#720,8486>Try to create a replica at a time of day when use of the database is light, to minimize user interruptions--this is especially important when creating replicas of large databases. 

@Numbered list@<:s><:#480,8486>Ask the Notes administrator to grant you "Create replica databases" access in the server document.

@Numbered list@<:s><:#240,8486>Select the original database icon and choose File - Replication - New Replica.

@Numbered list@<:s><:#480,8486>Next to Server, click the drop-down arrow and select the server on which you want to place the new replica.<-!><-">

@Numbered list@<:s><:#240,8486>Specify the file name and title for the replica you are creating.

@Numbered list@<:s><:#480,8486>(Optional) Click Replication Settings to determine replication characteristics for the new replica.

@Numbered list@<:s><:#480,8486>(Optional) Click Local Security, select "Secure this database for," and click OK to encrypt the database with the server ID file. 

@Numbered list@<:s><:#480,8486>(Optional) Click Size Limit, specify a size limit for the new replica in MB, then click OK.

@Numbered list@<:s><:#720,8486>Select "Create: Immediately" to immediately populate the new replica with documents. Select "Create: Next scheduled replication" to populate the new replica the next time replication occurs.

@Numbered list@<:s><:#480,8486>Select "Copy Access Control List" to copy the ACL from the original to the new replica.

@Numbered list@<:s><:#240,8486>Click OK.

@Note@<:s><:#720,8486>Do not choose File - Database - New Copy to create a replica. If you use this command, the replica ID of the copy is different from that of the original and the two databases can't replicate.

@Chead title@<:s><:#240,8486>Details: Creating a replica on a server

<:#240,8486><+!>Server<-!>

<:s><:#480,8486>Creating a replica on one server does not automatically propagate the replica to other servers; you must manually create replicas on each additional server.

@Dhead@<:s><:#240,8486>File name

<:s><:#480,8486>Any file name you choose must be unique to the workstation or server on which you place the replica.

<:s><:#720,8486>A replica's file name has no bearing on replication; if the file names of two databases are different, they still replicate if the Replica IDs are identical. File names don't replicate.

<:#720,8486>To put the replica in a subdirectory, next to File name,  type the subdirectory, a backslash, and then the file name; for example, SALES\LEADS. If the specified directory does not exist, Notes creates it for you.

@Dhead@<:s><:#240,8486>Replication Settings

<:s><:#960,8486>Replication settings let you control a variety of replication characteristics, such as the documents and features a replica receives, whether older, unmodified documents are automatically removed from a replica, the replication priority, and so on. 

<:s><:#1680,8486>If you set replication settings as you create a replica, the specified settings are automatically set on the new replica. For example, if you define a replication formula as you create the replica, the new replica automatically contains only the documents a
nd features indicated by the formula.  If you do not select replication settings as you create a replica, the new replica inherits the replica settings of the original.

@See also prnt@<:s><:#240,8486>For more information, see "About customizing replication" later in the chapter.

@Dhead@<:s><:#240,8486><+!><:ZDDE_BOOKMARK1>Local Security<-!>

<:#1440,8486>This option helps prevent unauthorized local access to a database. Notes encrypts the database using  the ID of the server that stores the database; only somebody using the server ID can access the replica database. The contents of the database are illegibl
e to people who have physical access to the server using a different ID. This encryption also carries over to copies of the database made at the operating system level.

<:s><:#240,8486>You must have Manager access to encrypt a database.<:Z~DDE_BOOKMARK1>

<:s><:#240,8486><+!>Size Limit<-!>

<:s><:#960,8486>To control growth of the database, specify a size limit in MB. Users see a message if they attempt to add documents to a database that has reached its maximum size. Users can sometimes add documents to a database that has reached its size limit if there is 
unused space within the database. 

<:s><:#480,8486>If a database reaches its size limit, you can reduce the database size by archiving it or by using replication settings.

@See also prnt@<:s><:#480,8486>For more information on controlling the size of databases, see "Ways to control the size of a database" in Chapter 5

@Dhead@<:s><:#240,8486><+!>Create immediately or at next scheduled replication

<:s><:#1680,8486>If you select "Create: Immediately," you must wait while Notes replicates all documents in the original to the new replica database. 
<:f180,BArial,0,0,255><+!><+">(True or does this happen in the background?)<-"><-!><:f> If you select "Create: Next scheduled replication" Notes creates a replica stub, a replica shell that Notes populates with documents at the next replication. Consider se
lecting "Create: Next scheduled replication" if the database is large or you're creating a series of replica databases and you don't want to wait while the initial replication of documents occurs.

<:#1200,8486>If you select "Create: Immediately" and replication is disabled on the original, Notes displays a message stating that replication is disabled and asking you if you want to reenable. If you select Yes to reenable replication, the new replica is populated wi
th documents. If you select No, Notes creates a replica stub just as if the option "Create: Next scheduled replication" is selected

@See also prnt@<:s><:#480,8486><-!><-">For more information, see "Disabling replication for a database" later in the chapter.

<:s><:#240,8486><+!>Copy Access Control List<-!>

<:s><:#1200,8486>If you select this option, make sure you are listed with Manager access in the ACL of the original database so that you have Manager access to the new replica on the server. If the new replica does not list you with Manager access, you can't modify the ACL 
or replication settings or delete the replica database. 

<:s><:#480,8486>If you don't copy the ACL to the new replica, the new replica automatically gives you Manager access. 

<:s><:#240,8486><:f180,BArial,0,0,255><+!><+">In what situations would you copy? What situations wouldn't you?<-"><-!><:f>

@Ahead@<:s><:#390,8486>About replication priorities for public databases

<:s><:#1200,8486>A Notes administrator can schedule replication so that databases assigned different priorities replicate at different times. For example, Notes administrators can schedule databases assigned high-priority such as Name & Address Books to replicate frequently
 and schedule databases assigned low-priority to replicates during off-hours. Database managers assign a replication priority for databases.

<:s><:#240,8486>Your Notes administrator can tell you how priority scheduling is set up on a server.

@Bhead title@<:s><:#260,8486>Assigning a replication priority for a public database

<:s><:#480,8486>If you assign two replica copies different priorities, Notes uses the priority assigned to the replica on the server that initiates the replication.

@Numbered list@<:s><:S+200><:#400,8486>For an existing replica, select the database icon and choose File - Replication - Replication Settings. 

@Numbered list@<:s><:S+200><:#400,8486>If you are creating a new replica database, click Replication Settings in the New Replica dialog box.

@Numbered list@<:s><:#240,8486>Click the Other icon.

@Numbered list@<:s><:#240,8486>Below "Scheduled replication priority" select Low, Medium, or High.

@Numbered list@<:s><:#240,8486>Click OK.

@Ahead@<:s><:#390,8486>About customizing replication

<:s><:#480,8486><:X8,13;Index "Replication" # "customizing"><:X8,13;Index "Selective replication" #>Notes lets you replicate a subset of documents to a replica so you can limit the size of replicas. With selective replication, you can:

@Bullet@<:s><:#240,8486>Save disk space.

@Bullet@<:s><:#240,8486>Reduce the time and expense of remote replication.

@Bullet@<:s><:#240,8486>Display only the parts of databases you're interested in.

<:s><:#720,8486>For example, you could create a local replica of your mail database on a laptop and replicate only those documents created in the last two months. This way, the replica takes up less space on your laptop and takes less time to create.

<:s><:#960,8486>Or, suppose you work for a community theater group and use a database that provides information on federal and state arts grants. If the database classifies documents according to art form, you could create a local replica of the database and replicate only
 those documents related to theater grants.

@See also btn@<:s><:#240,8486><:N794794544,D,65535,15,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

@Ahead@<:s><:#390,8486>

@Ahead@<:s><:#390,8486>Ways to customize replication

<:s><:#240,8486><:X8,14;Index "Replication" # "customizing"><:X8,14;Index "Selective replication" #>You can do the following to limit the size of replicas:

@Bullet@<:s><:#240,8486>Shorten large incoming documents 

@Bullet@<:s><:#240,8486>Shorten or remove older documents 

@Bullet@<:s><:#240,8486>Receive only newer documents 

@Bullet@<:s><:#240,8486><-!><-"><-">Receive only certain documents <-!><-"><-!><-"><-!><-"><-!><-"><-!><-">

@Bullet@<:s><:#240,8486>Receive only certain database features 

<:s><:#240,8486>You can also do the following:

@Bullet@<:s><:#240,8486>Limit what a replica sends 

@Bullet@<:s><:#240,8486>Disable replication for a database

<:s><:#240,8486>

<:s><:#240,8486>If you are a database manager, you can also customize server to server replication.

@See also btn@<:s><:#240,8486><:N794794553,D,65535,17,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>Shortening large incoming documents

<:#480,8486><:X8,14;Index "Truncating documents" #><:X8,14;Index "Document" # "truncating">You can remove bitmaps, attachments, other large objects, and all but the first 45K of rich text from documents that a replica receives.<+!><+">??Is this right?<-"><-!>

@Numbered list@<:s><:#240,8486>Click the replica.

@Numbered list@<:s><:#240,8486>Choose File - Database - Replication Settings.

@Numbered list@<:s><:#240,8486>Select "Truncate incoming large documents".

@Numbered list@<:s><:#240,8486>Click OK.

@See also btn@<:#240,8486><-#>{bmc 1details.bmp}See details 

@See also btn@<:s><:#240,8486><:N794794560,D,65535,19,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486><-#><-#><-#><-#><-#>

<:s><:#240,8486>

@Chead title@<:#240,8486>Details: Shortening large incoming documents

<:s><:#240,8486><:X8,15;Index "Truncating documents" #><:X8,15;Index "Document" # "truncating"><:X8,15;Index "Agents" # "and truncated documents"><:X8,15;Index "Restoring" # "truncated documents"><:f>When you receive truncated documents, keep the following in mind:

@Bullet@<:s><:#480,8486>When you open a truncated document, Notes displays "(TRUNCATED)" in the document window title.

@Bullet@<:#480,8486>You cannot categorize or edit truncated documents. Also, agents do not work on truncated documents.<+!><+">??Is this true?<-"><-!>

@Bullet@<:s><:#480,8486>Notes does not replicate truncated documents to another replica, unless the replica also has the "Truncate incoming large documents" option selected.

@Bullet@<:s><:#720,8486>To get the rest of a truncated document, open the document and choose View - Refresh Truncated Document. If Notes can refresh the document from more than one server database, it prompts you to choose the server.

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>

@Bhead title@<:s><:#260,8486>Shortening or removing older documents

<:#960,8486><:X8,15;Index "Truncating documents" #><:X8,15;Index "Document" # "truncating"><:X8,15;Index "Headline" #><:X8,15;Index "Removing" # "older documents"><:X8,15;Index "Deleting" # "older documents">When you replicate, you can shorten or remove documents from 
a replica that have not been modified in a specified number of days.<+!><+">??Does Notes shorten/remove documents only upon replication? Or, is Notes always looking for older documents to shorten/remove? Can you select this for an unreplicated database?<-">
<-!>

@Numbered list@<:s><:#240,8486>Click the replica.

@Numbered list@<:s><:#240,8486>Choose File - Database - Replication Settings.

@Numbered list@<:s><:#240,8486>Select "Save space by".

@Numbered list@<:s><:#240,8486>Do one of the following:

@Indnt bullet@<:s><:#240,8486>Select "removing" to remove older documents.

@Indnt bullet@<:#480,8486>Select "keeping only headlines of" to shorten older documents by.<+!><+">??What exactly is a headline?<-"><-!>

@Indnt bullet@<:#720,8486>Select "truncating the contents of" to shorten older documents by removing bitmaps, attachments, other large objects, and all but the first 45K of rich text.<+!><+">??Is this right?<-"><-!>

@Numbered list@<:s><:#240,8486>Enter the number of days you want to use to check for unmodified documents.

@Numbered list@<:s><:#240,8486>Click OK.

@Caution@<:s><:#480,8486>When you remove a document from a replica, Notes permanently deletes it from the replica.

@See also btn@<:#240,8486><-#>{bmc 1details.bmp}See details 

@See also btn@<:s><:#240,8486><:N794794574,D,65535,21,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Chead title@<:#240,8486>Details: Shortening or removing older documents

@Chead@<:s><:#240,8486>What Notes does

<:s><:#960,8486><:X8,16;Index "Purge interval" #><:X8,16;Index "Deleting" # "documents"><:X8,16;Index "Removing" # "documents">When Notes finds unmodified documents in a local database you're replicating, it prompts you before shortening or removing them. Notes displays th
e prompt each time you open the database until you choose Yes, change the number of days specified, or deselect "Save space by".

<:#720,8486>When Notes finds unmodified documents in a server database you're replicating (If you're a database manager), Notes shortens or removes documents automatically without prompting you.<+!><+">??Is this true?<-"><-!>

@Chead@<:s><:#240,8486>Purge interval

<:s><:#960,8486>In addition to using the number of days you specify to check for unmodified documents, Notes uses the number to determine the database's purge interval. The purge interval is one-third the number of days you specify (for example, if you specify 60 days, the
 purge interval is 20 days).

<:s><:#1680,8486>Notes uses the purge interval to delete document identifies called deletion stubs from a database. When you delete a document from a database, Notes keeps a deletion stub that identifies the document. This way, the deletion can be replicated to other replic
as (unless you select "Do not send deletions made in this replica to other replicas" in the Replication Settings dialog box). When a deletion stub is older than the purge interval, Notes deletes it, freeing up the space the document occupied.

<:s><:#960,8486>The default purge interval is 30 days. To make sure deletions you make in a replica are sent to other replicas, replicate at least once every 30 days or, if you select the "Save space by" option, at least as often as one-third the number of days you specify
.

@Note@<:s><:#720,8486>When Notes removes documents that are older than the purge interval from a replica, Notes deletes the documents from the replica and does not create deletion stubs for the documents.

@Chead@<:s><:#240,8486>Truncated documents

@Bullet@<:s><:#480,8486>When you open a truncated document, Notes displays "(TRUNCATED)" in the document window title.

@Bullet@<:#480,8486>You cannot categorize or edit truncated documents. Also, agents do not work on truncated documents.<+!><+">??Is this true?<-"><-!>

@Bullet@<:s><:#480,8486>Notes does not replicate truncated documents to another replica, unless the replica also has the "Truncate incoming large documents" option selected.

@Bullet@<:s><:#720,8486>To get the rest of a truncated document, open the document and choose View - Refresh Truncated Document. If Notes can refresh the document from more than one server database, it prompts you to choose the server.

<:s><:#240,8486>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>Receiving only newer documents

<:s><:#480,8486><:X8,17;Index "Cutoff date" #>You can specify that a replica receive only those documents that have been created or modified since a certain date. This is called the cutoff date.

@Numbered list@<:s><:#240,8486>Click the replica.

@Numbered list@<:s><:#240,8486>Choose File - Database - Replication Settings.

@Numbered list@<:s><:#240,8486>Select "Only replicate documents saved or modified after" and enter a date.

@Numbered list@<:s><:#240,8486>Click OK.

@See also btn@<:s><:#240,8486><:N794794584,D,65535,23,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>Receiving only certain documents

<:s><:#240,8486><:X8,17;Index "Deletions" # "replicating">You can select the documents a replica receives.

@Numbered list@<:s><:#240,8486>Click the replica.

@Numbered list@<:s><:#240,8486>Choose File - Database - Replication Settings.

@Numbered list@<:s><:#240,8486>Click Receive.

@Numbered list@<:s><:#240,8486>Select "Selected documents".

@Numbered list@<:s><:#240,8486>Do one of the following:

@Indnt bullet@<:#480,8486>To select the documents in one or more folders, select the folder(s).<+!><+">??How will this work?<-"><-!>

@Indnt bullet@<:s><:#240,8486>To select the documents using a formula, enter the formula.

@Numbered list@<:s><:#480,8486>(Optional) To keep documents in the replica that have been deleted from the database you're replicating with, select "Do not receive deletions".

@Numbered list@<:s><:#240,8486>Click OK.

@See also btn@<:s><:#240,8486><:N794794591,D,65535,25,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>Receiving only certain database features

<:s><:#240,8486><:X8,18;Index "Forms" # "replicating"><:X8,18;Index "Views" # "replicating"><:X8,18;Index "Replication formula" #><:X8,18;Index "Access control list" # "replicating"><:X8,18;Index "Agents" # "replicating">You can select the database features a replica recei
ves.

@Numbered list@<:s><:#240,8486>Click the replica.

@Numbered list@<:s><:#240,8486>Choose File - Database - Replication Settings.

@Numbered list@<:s><:#240,8486>Click Advanced.

@Numbered list@<:s><:#240,8486>Do any of the following:

@Indnt bullet@<:s><:#240,8486>Select "Forms, views, etc."  to receive a database's basic design.

@Indnt bullet@<:s><:#240,8486>Select "Agents" to receive a database's agents.

@Indnt bullet@<:s><:#480,8486>Select "Replication formula" to receive the formula a database uses to select the documents it replicates.

@Indnt bullet@<:s><:#240,8486>Select "Access control list" to receive a database's access control list.

@Numbered list@<:s><:#240,8486>Click OK.

@Note@<:#1440,8486>If you create a local replica and deselect "Access control list", Notes assigns you Manager access to the replica. But, if you do not have equivalent rights in the ACL of the original database on the server (for example, you have only Reader access), you ca
nnot replicate changes you make in the replica back to the server.<+!><+">??Still true for V4?  Or will the replicas keep their ACLs via the local access feature?<-"><-!>

@See also btn@<:s><:#240,8486><:N794794599,D,65535,27,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>Limiting what a replica sends

<:s><:#480,8486><:X8,18;Index "Deletions" # "replicating"><:X8,18;Index "Access control list" # "replicating">You can prevent certain changes you make in a replica from being sent to other replicas of a database.

@Numbered list@<:s><:#240,8486>Click the replica.

@Numbered list@<:s><:#240,8486>Choose File - Database - Replication Settings.

@Numbered list@<:s><:#240,8486>Click Send.

@Numbered list@<:s><:#240,8486>Select any of the following:

@Indnt bullet@<:s><:#480,8486>Select "Do not send deletions made in this replica to other replicas" to prevent deletions from replicating.

@Indnt bullet@<:#960,8486>Select "Do not send changes in database title & catalog info to other replicas" to prevent changes you make to a database's title or changes you make to a database's Database Catalog categories from replicating.<+!><+">??What's catalog info mean?<-"><-!>

@Numbered list@<:s><:#240,8486>Click OK.

@Note@<:#960,8486>If you are a database manager, you can also select "Do not send changes in local access control property to other replicas" to prevent changes you make to a database's access control list from replicating to other replicas.<+!><+">??<-"><+">Is this right?<-">
<-!>

@See also btn@<:s><:#240,8486><:N794794609,D,65535,29,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Ahead@<:s><:#390,8486>About central administration of replication settings

<:s><:#1200,8486>If there are replicas of a database on more than one server, you can customize replication for each replica from one central source replica and then replicate these custom settings to the appropriate replicas. This approach to customizing replication is use
ful for centralized database management and assumes that a database manager knows the replication requirements for each replica. 

<:s><:#720,8486>Central administration of replication settings requires cooperation between the central manager and local database managers since it's possible for local database managers to override centrally-created replication settings.

<:s><:#960,8486>You can only use this centralized approach when using a replication formula to limit the documents replicas receive or when specifying specific features for replicas to receive. You cannot centrally administer the following replication settings--these must 
be set directly at each replica database: 

@Bullet@<:s><:#240,8486>"Truncate incoming large documents"

@Bullet@<:s><:#240,8486>"Documents not modified in the last <[> ] days will be removed"

@Bullet@<:s><:#240,8486>"Do not send deletions made in this replica to other replicas"

@Bullet@<:#240,8486>"Do not send changes in database title & catalog info to other replicas"

@Bullet@<:s><:#240,8486>"Do not send changes in local access control property to other replicas"

@Bullet@<:s><:#240,8486>"Only replicate documents saved or modified after:"

@Bullet@<:s><:#240,8486>"CD-ROM publishing date:"

@Bhead title@<:s><:#260,8486>Centrally-administering replication settings

<:s><:#480,8486>To customize replication for multiple replicas from one source replica, you complete the following tasks:

<:s><:#240,8486>Task 1: Select a destination/source server combination.

<:s><:#240,8486>Task 2: Specify the documents replicas receive.

<:s><:#240,8486>Task 3: Select the database features replicas receive.

<:s><:#240,8486>Repeat Tasks 1 - 3 for each combination of destination/source server.

@Bhead title@<:s><:#260,8486>Selecting a destination/source server combination

<:s><:#240,8486>This is task 1 of 3 for centrally-administering replication settings.

@Numbered list@<:s><:#480,8486>Select the database icon from which you want to centrally-administer replication settings and choose File - Replication - Replication Settings.

@Numbered list@<:s><:#240,8486>Click the Advanced icon.

@Numbered list@<:s><:#720,8486>To the right of "When computer," click the computer icon, select or type the name of the destination server, select Add Server then click OK. You can also accept the default entry.

@Numbered list@<:s><:#720,8486>To the right of "Receives from," click the computer icon, select or type the name of a source server, select Add Server, then click OK. You can also accept the default entry.

@Numbered list@<:s><:#480,8486>To delete a server, click either computer icon, select a server, select Delete Server, then click OK. 

@Chead title@<:s><:#240,8486>Details: Selecting a destination/source server combination

@Bullet@<:s><:#1200,8486>The server you specify for "When computer:" is the destination server which receives the subset of information. The server you specify for "Receives from:" is the source server which stores the entire contents of a database. Make sure to specify the destina
tion and source servers correctly to avoid removing documents from the wrong replica.

@Bullet@<:s><:#720,8486>If you type a server name rather than selecting a name from the list of servers, make sure to use the correct case or else replication settings don't take effect.  
<:f180,BArial,0,0,255><+!><+">???STILL TRUE FOR R4?  <-"><-!><:f>

@Bullet@<:s><:#1680,8486>These steps also let you define replication between a local replica and a replica on a specific source server.  (Usually locally administered replication defines replication between the local replica and all source servers.)  For example, a replica on Serve
r A has two source servers, Server B and Server C. Server A receives all information from Server C and all information except new designs from Server B. You can define replication between Servers A and B without doing so between Servers A and C.

@Bhead title@<:s><:#260,8486><-!><-">Specifying the documents a replica receives

<:s><:#240,8486>This is task 2 of 3 for centrally-administering replication settings.

@Numbered list@<:s><:#240,8486>Select "Only replicate selected documents."

@Numbered list@<:s><:#480,8486>If you want a replica to receive only documents in specific folders or views, select the folders or views.

@Numbered list@<:#1200,8486>If you want to use a formula to determine the documents a replica receives, click @ and type the formula. To paste a database field or @function into the formula, click Fields & Functions, select a field or function, and paste it into the formula. 

@Chead title@<:s><:#240,8486>Details: Specifying the documents a replica receives

@Bullet@<:s><:#480,8486>The view or formula you specify applies only to the destination/source server combination currently selected in the Replication Settings dialog box.

@Bullet@<:s><:#480,8486><-!>Replication formulas are similar to view selection formulas, which determine the documents that appear in a view.

@Bullet@<:s><:#480,8486>To create or edit a formula in a larger window, click the magnifying glass icon.

@Bullet@<:#480,8486><:f180,BArial,0,0,0>You cannot use<:f180,BArial,0,0,0> <:f180,BArial,0,0,0>@D<:f><:f180,BArial,0,0,0>bL<:f><:f180,BArial,0,0,0>ookup, @U<:f><:f180,BArial,0,0,0>serN<:f><:f180,BArial,0,0,0>ame,<:f><:f180,BArial,0,0,0> @Environment, or @Now in a replication<:f>
<:f180,BArial,0,0,0> formula.<:f180,BArial,0,0,255><-!><-"><+!><+"> ???Still true in R4?<-!><-"><:f>

@Bullet@<:#960,8486>Using @IsResponseDoc in a replication formula causes all response documents in a database to replicate, not just those that meet the selection criteria. To avoid replication this, use @AllChildren or @AllDescendants instead.<:f180,BArial,0,0,255><+!><+"> Do
es @IsResponseDoc still behave as as it did in R3?<-"><-!><:f>

@Bhead title@<:s><:#260,8486>Choosing the database features a replica receives

<:s><:#240,8486>This is task 3 of 3 for centrally-administering replication settings. 
<-">

@Numbered list@<:s><:#480,8486>Deselect "Forms, views, etc." to prevent a replica from  receiving database design changes.

@Numbered list@<:s><:#720,8486>Deselect Agents to prevent a replica from receiving agents. <+!><+"><:f180,BArial,0,0,255>What if the option is selected for a while, and then deselected--how are previously replicated agents affected?<-!><-"><:f>

@Numbered list@<:s><:#480,8486>Select Replication formula to let a replica receive the selected replication settings.

@Numbered list@<:s><:#480,8486>Deselect "Access control list" to prevent a replica from receiving ACL changes.

@Numbered list@<:#480,8486>Select "Do not receive deletions" to prevent the replica from receiving document deletions from the source server(s).

@Numbered list@<:s><:#240,8486>Click OK.

@Chead title@<:s><:#240,8486>Details: Choosing the database features a replica receives

@Bullet@<:s><:#480,8486>By default, a replica inherits all database features except the replication formula from a source server replica.

@Bullet@<:s><:#480,8486>The features you select apply only to the destination/source server combination currently selected in the Replication Settings dialog box.

@Bullet@<:s><:#720,8486>A replica can only receive changes if it grants the source server appropriate access. For example, a replica can receive design changes if its ACL gives the source server Designer or Manager access. 

@Bullet@<:#960,8486>Forms, views, etc.--Deselecting this option prevents a replica from receiving design changes.<+!><+"><:f180,BArial,0,0,255> 
<-"><-!><:f>This is necessary only if a source server has Designer or Manager access; Editor access or less automatically prevents replication of design changes. 
<+!><+"><:f180,BArial,0,0,255>CORRECT INFO IN THIS PARAGRAPH?<-!><-"><:f>

@Bullet@<:#1680,8486>Agents--Deselecting this option prevents a replica from receiving agents, although changes caused by agents can still replicate. If there are multiple replicas of a database, any agents should run on one server only and this option should be deselected on a
ny other replicas.<+!><+"><:f180,BArial,0,0,255> <-"><-!><:f>Deselecting this option to prevent replication of agents is necessary only if a source server has Designer or Manager access; Editor access or less automatically prevents replication of agents. 
<+!><+"><:f180,BArial,0,0,255>CORRECT INFO IN THIS PARAGRAPH?

@Bullet@<:s><:#960,8486>Replication formula--Selecting this option ensures that the replication settings made on a source server replica replicate to the appropriate destination replicas.  Replicas must first give the source server Designer or Manager access.

@Bullet@<:s><:#1440,8486>Access control list--Deselecting this option prevents a replica from receiving changes to the ACL. Server access in replica ACLs affect replication, so it's important to choose server ACL settings carefully. Deselecting this option to prevent replication of
 the ACL is necessary only if a source server has Manager access; Designer access or less automatically prevents replication of ACL changes. 

@Bullet@<:#1440,8486>Select "Do not receive deletions," to prevent the destination replica(s) from receiving deletions from the source server. 
<-">You can achieve the same effect by deselecting the ACL option "Can delete documents" for all servers listed in the replica ACL. However, by using the "Do not receive deletions" option, you avoid having to deselect the "Can delete documents" for individu
al server names.

@See also prnt@<:s><:#480,8486>For more information on server names in the ACL and their affect on database replication, see "About server access levels and replication" later in this chapter.

@Chead title@<:s><:#240,8486>Examples: Centrally-administering replication settings

@Dhead@<:s><:#240,8486><+!>Example 1: u<-!><+!>sing the same replication settings for <-!><+!>all destination servers<-!><+!> 
<-!>

<:#960,8486>A server at LMI Industries headquarters has a technical support database on the server HEADQUARTERS1 used to post information about customer problems and their resolutions. The database displays customer suggestions made in the course of support calls in a 
view called Customer Suggestions. 

<:#960,8486>Each LMI sales office wants to store a replica of this database that contains only customer suggestions and not other details of support calls. The manager of the customer support database at company headquarters sets up replication settings as follows: 

<:s><:#240,8486>Screen shot to come; will show: 

<:s><:#240,8486>	Replication Settings for SUPPORT

<:s><:#240,8486>	When computer: -Any Server-

<:#240,8486>	Receives from: HEADQUARTERS_1

<:s><:#240,8486>	View Customer Suggestions selected.

<:#960,8486>The destination server is Any Server since the sales office servers are the only other servers that store the replica. The source server is HEADQUARTERS1. "Replication formula" is selected to ensure that the replication settings can replicate to the sales o
ffice servers<-!><-">

@Dhead@<:s><:#240,8486><+!>Example 1: Using separate replication settings<-!><+!> for each destination server<-!> 

<:#1680,8486>Acme Corporation headquarters has a database for sales leads that it stores on the server HQSALES. Acme has three remote regional sales offices, each with its own Notes server named according to its region: EASTSALES, WESTSALES, and INTLSALES. To help reduc
e replication time associated with asynchronous replication to these regional servers, the database manage at company headquarters wants the sales leads replica on each regional server to contain only sales leads for its region.  

<:#960,8486>Selection of one of the keywords East, West, or International in the required field, Region, signifies which region the sales lead applies to. The database manager sets up the following replication settings for EASTSALES in the replica on HQSALES as follows
:

<:s><:#240,8486>Screen shot to come; will show: 

<:s><:#240,8486>	Replication Settings for SALES

<:#240,8486>	When computer: EASTSALES

<:#240,8486>	Receives from: HQSALES

<:s><:#240,8486>	Replication formula:

<:#240,8486>		SELECT Region = "East" | @AllDescendants<-!><-">

<:#480,8486>The option "Replication formula" is selected, so that the HQSALES can replicate the formula to EASTSALES.

<:#960,8486>The manager creates similar replication formulas between HQSALES and the replicas on WESTSALES and INTLSALES. After all the replication formulas are in place, the manager replicates the formula to the replicas at the three regional sales offices.

@Ahead@<:s><:#390,8486>About changes to centrally-administered replication settings

<:s><:#1680,8486>Changing centrally-administered replication settings requires two replications for the changes to take effect: the first replication to replicate the new settings from the source server to the destination servers and a second replication to replicate based 
upon the new settings. The second replication doesn't occur until the source database is updated in some other way; to force the new selective replication settings to take effect if the source database isn't updated, clear the Replication History.

@See also prnt@<:s><:#240,8486>For more information, "Clearing a database's replication history."

@Bhead title@<:s><:#260,8486>Disabling replication for a database

<:s><:#720,8486><:X8,24;Index "Replication" # "disabling"><:X8,24;Index "Disabling" # "replication">You can temporarily disable replication for a database. This is useful if you want to prevent a database from being updated, or if you want to check to see if a database is 
corrupted before replicating with a server.

@Numbered list@<:s><:#240,8486>Click the database.

@Numbered list@<:s><:#240,8486>Choose File - Database - Replication Settings.

@Numbered list@<:s><:#240,8486>Select "Temporarily disable replication".

@Numbered list@<:s><:#240,8486>Click OK.

@See also btn@<:s><:#240,8486><:N794794617,D,65535,31,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

@Ahead@<:s><:#390,8486>

@Bhead title@<:s><:#260,8486>Displaying a database's replica ID

@Numbered list@<:s><:#240,8486><:X8,24;Index "Replica ID" # "displaying"><:X8,24;Index "Displaying" # "replica ID">Click the database.

@Numbered list@<:s><:#240,8486>Choose File - Database - Properties.

@Numbered list@<:s><:#240,8486>Click the Information tab.

@1st lev para@<:#240,8486>{bmc 0m_info.bmp}

@See also btn@<:s><:#240,8486><:N794794726,D,65535,57,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Ahead@<:s><:#390,8486><-&>About replicating databases between servers

<:s><:#480,8486>There are two ways to replicate databases between servers both of which are done by Notes administrators: replicating by schedule or replicating manually.

@Bhead@<:s><:#260,8486>Scheduled replication

<:s><:#720,8486>Notes administrators create Connection documents in the server Name & Address Book to schedule replication between servers. They can schedule one-way or two-way replication and indicate which databases to replicate.

@Bhead@<:s><:#260,8486>Manual replication

<:s><:#720,8486>Notes administrators can force replication between servers using server console commands. You can't use Notes workspace commands to force replication between two server databases. 
<:f180,BArial,0,0,255><+!><+">LAST SENTENCE TRUE??<-"><-!><:f>

@See also prnt@<:s><:#480,8486>For more information on server-to-server replication, see the Administrator's Guide.

@Ahead@<:s><:#390,8486>About Replication History

<:s><:#1440,8486><:X8,25;Index "Replication history" #>Notes maintains a Replication History for any Notes database that has successfully replicated at least once. Notes uses this history to determine the date of documents to include in the database's next replication with 
a particular server. For example, if a database successfully replicated with the SUPPORT server 24 hours ago, Notes will only replicate documents added, modified, or deleted in the replica on SUPPORT in the last 24 hours.

@Note@<:s><:#720,8486>Before replication starts between two databases, Notes checks the replication history stored with each database to make sure they agree. If they do not, Notes performs a full replication.

<:s><:#1200,8486>The first time a database replicates successfully with another server, an entry appears in the Replication History. If the database replicates with additional servers, an entry for each server is added to the history. On subsequent replications with a serve
r, no new entries appear in the list; instead, Notes updates the date and time to the most recent replication with that server.

<:s><:#480,8486>If a database does not replicate successfully, Notes does not update the Replication History and attempts to replicate the same changes during the next replication.

@See also btn@<:s><:#240,8486><:N794794748,D,65535,59,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>

@Bhead title@<:s><:#260,8486>Displaying a database's replication history

<:s><:#240,8486><:X8,25;Index "Replication history" #><:X8,25;Index "Displaying" # "Replication history">You can display when and with which server a database has replicated.

@Numbered list@<:s><:#240,8486>Click the database.

@Numbered list@<:s><:#240,8486>Choose File - Database - Properties.

@Numbered list@<:s><:#240,8486>Click the Information tab.

@1st lev para@<:#240,8486>{bmc 0m_info.bmp}

@Numbered list@<:s><:#240,8486>Click Replication History.

@Numbered list@<:s><:#240,8486>Do either of the following:

@Indnt bullet@<:s><:#240,8486>Select Date to view the information by date.

@Indnt bullet@<:s><:#240,8486>Select Server name  to view the information by server.

@Numbered list@<:s><:#240,8486>Click Done to close the dialog box.

@Tip@<:s><:#480,8486>To display more information about an entry, select it and click Zoom. To copy the entire replication history to the clipboard, click Copy.

@See also btn@<:s><:#240,8486><:N794794756,D,65535,61,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>

@Bhead title@<:s><:#260,8486>Clearing a database's replication history

<:s><:#240,8486><:X8,26;Index "Replication history" #><:X8,26;Index "Clearing" # "Replication history">You can clear a database's entire replication history or individual entries in it.

@Numbered list@<:s><:#240,8486>Click the database.

@Numbered list@<:s><:#240,8486>Choose File - Database - Properties.

@Numbered list@<:s><:#240,8486>Click the Information tab.

@1st lev para@<:#240,8486>{bmc 0m_info.bmp}

@Numbered list@<:s><:#240,8486>Click Replication History.

@Numbered list@<:#240,8486>Do one of the following:<+!><+">??Is this right?<-"><-!>

@Indnt bullet@<:s><:#240,8486>To clear individual entries, select them.

@Indnt bullet@<:s><:#240,8486>To clear the entire replication history, select all of the entries.

@Numbered list@<:s><:#240,8486>Click Clear.

@Numbered list@<:#240,8486>Click Yes to delete the selected entries.<+!><+">??Does this prompt appear as spec'd?<-"><-!>

@Numbered list@<:s><:#240,8486>Click Done to close the dialog box.

@Tip@<:s><:#720,8486>It's useful to clear a database's replication history if you think your database doesn't contain all the documents it should or if your database's replication history is out of sync with other replicas.

@Note@<:s><:#1200,8486>If you clear the history, Notes no longer has a record of when replication occurred last, so Notes will replicate each document fully at the next replication (rather than replicating only what has changed since the last replication). Because this creates ne
twork traffic and takes more time, clear the history only if you're sure you need to.

@See also btn@<:s><:#240,8486><:N794794765,D,65535,63,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>

@Ahead@<:s><:#390,8486>About replication and save conflicts

<:s><:#720,8486><:X8,27;Index "Replication conflicts" #><:X8,27;Index "Save conflicts" #>A replication conflict occurs when two or more users edit the same document in different replicas between replications. A save conflict occurs when two or more users edit the same docu
ment in a database on a server at the same time.

@Chead@<:s><:#240,8486>How Notes treats replication conflicts

<:#960,8486>At the next replication after two users modify the same document, Notes designates the update with the most changes as the main document. Notes display the other(s) as responses to the main document labeled "<[>Replication or Save Conflict]" with a diamond 
symbol in the left margin.

@Note@<:s><:#480,8486>If a document is edited in one replica and deleted in another, the deletion takes precedence.

@Chead@<:s><:#240,8486>How Notes treats save conflicts

<:s><:#1440,8486>When more than one user opens the same document to edit at the same time, Notes designates the first update (the document that gets saved first) as the main document. When another user tries to save the same document, Notes prompts the user to save it as a 
Save Conflict document. If the user does, Notes displays it as a response to the main document labeled "<[>Replication or Save Conflict]" with a diamond symbol in the left margin.

@See also btn@<:s><:#240,8486><:N794794787,D,65535,69,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486>Resolving replication and save conflicts

<:#720,8486><:X8,27;Index "Replication conflicts" #><:X8,27;Index "Save conflicts" #><:X8,27;Index "Deleting" # "conflict documents"><:X8,27;Index "Removing" # "conflict documents">After a replication or save conflict, Notes saves one document as the main document and 
the other(s) as responses. You can save information from a response in the main document, or make one of the responses the main document.

@Chead@<:s><:#240,8486>Deleting a response but saving its information in the main document

@Numbered list@<:s><:#240,8486>Open the response document containing information you want to save.

@Numbered list@<:s><:#240,8486>Select the information you want to copy and choose Edit - Copy.

@Numbered list@<:s><:#240,8486>Put the main document in edit mode.

@Numbered list@<:s><:#240,8486>Move to where you want the information and choose Edit - Paste.

@Numbered list@<:s><:#240,8486>Save the main document.

@Numbered list@<:s><:#240,8486>Move the highlight to the response document .

@Numbered list@<:s><:#240,8486>Choose Edit - Clear or press DEL.

@Numbered list@<:s><:#240,8486>Press F9 to update the view and delete the response document.

@Chead@<:s><:#480,8486>Deleting the main document and making a response the main document

@Numbered list@<:s><:#240,8486>Put the response document you want to make the main document in edit mode.

@Numbered list@<:s><:#240,8486>Save the response document.

@Numbered list@<:s><:#240,8486>If there are other response documents, do the following:

@Indnt bullet@<:s><:#240,8486>Select the other response documents and choose Edit - Cut.

@Indnt bullet@<:s><:#240,8486>Move the highlight to the document you saved in step 2.

@Indnt bullet@<:s><:#240,8486>Choose Edit - Paste.

@Numbered list@<:s><:#240,8486>Move the highlight to the old main document.

@Numbered list@<:s><:#240,8486>Choose Edit - Clear or press DEL.

@Numbered list@<:s><:#240,8486>Press F9 to update the view and delete the old main document.

@See also btn@<:s><:#240,8486><:N794794795,D,65535,71,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

<:s><:#240,8486>

@Ahead@<:s><:#390,8486>

<:s><:#240,8486>

<:s><:#240,8486>

<:s><:#240,8486>

<:s><:#240,8486>

@Bhead title@<+@><:s><:#520,8486>Reducing the number of replication or save conflicts on public databases

<+@><:s><:#480,8486>By using one of the following techniques you can reduce or eliminate replication or save conflicts: 

@Bullet@<+@><:s><:#480,8486>Assign most users Author access or lower rather than Editor access to prevent people from editing others' documents.

@Bullet@<+@><:#720,8486>Use a $Conflict field in a form to resolve conflicts in one of several ways. For example, use $ConflictMerge to merge conflict documents if no fields conflict.

@Bullet@<+@><:#720,8486>Use one of the versioning options on forms (new versions become responses, prior versions become responses, or new versions becomes siblings) so that edited documents automatically become new documents.

@Ahead@<+@><:s><:#390,8486>About concurrent ACL or design changes

<+@><:s><:#1440,8486>If ACL or design changes are made on separate database replicas between replications, then when replication occurs the most recent change prevails, assuming that both servers have the necessary access to replicate the changes. For example, if someone change
s the ACL on server A and then someone else changes the ACL on server B and both servers have Manager access, during the next replication session, the more recent ACL on server B prevails. 

<+@><:s><:#240,8486>You should give only one or two servers Manager or Designer access to a database.

@Ahead@<:s><:#390,8486>About size differences among replicas of a database

<:s><:#480,8486>It's not unusual for replicas of a database to vary in size, sometimes substantially. The most common reasons for size differences among replicas of a database are:

<:s><:#240,8486><+!>Selective replication<-!> 

<:s><:#480,8486>Selective replication causes one replica to receive only a subset of documents and features from another replica.

<:s><:#240,8486><+!>Access Control List

<:s><:#480,8486>The ACL prevents a replica from receiving all documents or design elements from a source replica.

<:s><:#240,8486><+!>Read ACLs or Reader Names fields<-!>  

<:s><:#480,8486>A destination server isn't included in a Read ACL or Reader Names field and therefore doesn't receive all documents from a source server replica.

<:s><:#240,8486><+!>View Indexes

<:s><:#480,8486> A view is used in one replica but not in another; the replica containing the unused view is smaller because no index is built for the unused view. 

<:s><:#240,8486><+!>Deletions not replicated<-!> 

<:s><:#480,8486>The replication setting "Do not receive deletions" or "Do not send deletions made in this replica to other replicas" is selected causing a discrepancy in replica sizes.

<:s><:#240,8486><+!>Unused<-!><+!> space<-!> 

<:s><:#240,8486>One replica has been compacted while another hasn't.

@See also btn@<:s><:#240,8486><:N798503577,KB,65535,1,1
@@Section("See related topics",9, SWISS, 0, 2313, 64, 1, 360, "")

>

@Ahead@<+@><:s><:#390,8486>About troubleshooting replication problems

<+@><:s><:#240,8486>The following topics suggest solutions to common database replication problems.

@Bhead title@<+@><:s><:#260,8486><+!>Why aren't two databases replicating?<-!>

<+@><:s><:#240,8486>The most common reasons two databases fail to replicate are:

<+@><:s><:#240,8486><+!>The replica IDs are not the same<-!>

<+@><:#720,8486>Databases with different replica IDs cannot replicate. Examine the Replica ID<:f,,> for each database and make sure they are the same.<+!> 
<-!>To determine the replica ID of a database, <:f><:f,,>choose File - Database - Properties and then click the Info tab<:f><:f,,>.

<+@><:s><:#960,8486>If the replica IDs don't match, create a new replica of the database by choosing File - Replication - New Replica--do not choose File - Database - New Copy. Clear the Replication History on any other replicas to ensure that the next replication is a full re
plication.

@Dhead@<+@><:s><:#240,8486><+!>Servers don't have sufficient access in the database ACL<-!>

<+@><:s><:#720,8486>Check that the ACL in each database gives sufficient access to servers. The following message in the server Notes Log (LOG.NSF) indicates insufficient server access: "Access control is set to not allow replication."

@See also prnt@<:s><:#480,8486>For more information, see "About server access levels and replication and "About guidelines for selecting server access levels" earlier in this chapter. 

@See also prnt@<+@><:s><:#240,8486>For information on the Notes Log, see Chapter 7 of the Administrator's Guide.

<:s><:#240,8486><+!>Replication is disabled

<:#1440,8486>Check that replication is enabled on both replicas of the database. To do this, select the database icon and choose File - Replication - Replication Settings and click the Other icon; see if "Temporarily disable replication" is selected.  If it is, deselect
 it. The following message in the server Notes Log (LOG.NSF) may indicate that replication is disabled: "Unable to Replicate with Server 
<+">Servername<-">: None of the Selected Databases has a Replica on the Server."

@Dhead@<+@><:s><:#240,8486><+!>You haven't used a <-!><+!>hierarchical<-!><+!> server name<-!><+!> in the ACL

<+@><:s><:#1200,8486>If the Name & Address Book uses a hierarchical name for a server, you must use that exact hierarchical name in the ACL of a replica, either individually or within a group. If an ACL uses the common name for a server but the Name & Address Book uses the hier
archical name, the server won't have access to the replica and replication won't occur.  
<:f180,BArial,0,0,255><+!><+"> CORRECT? <-"><-!><:f><:X8,30;Index "Distinguished names" # "and replication"> 
<:X8,30;Index "Troubleshooting replication" # "distinguished names and">

@See also prnt@<+@><:s><:#480,8486>For more information, see "About server access levels and replication" earlier in this chapter.

<+@><:s><:#240,8486><+!>There is a<-!><+!> server or network problem

<+@><:s><:#240,8486>The following server or network problems may be preventing replication:

@Bullet@<+@><:s><:#240,8486>There is no connection record between the two servers that store the database.

@Bullet@<+@><:s><:#240,8486>The servers do not have common certificates.

@Bullet@<+@><:s><:#240,8486>There is a problem with the network hardware or software.

@Bullet@<+@><:s><:#240,8486>There is a modem failure.

<+@><:s><:#240,8486>For more information, see your Notes administrator.

@Dhead@<+@><:s><:#240,8486><+!>A server doesn't have access to a directory link

<+@><:s><:#480,8486>If a source server uses a directory link to point to a replica, the destination server must be given access to the directory link in order to receive changes.

@See also prnt@<+@><:s><:#240,8486>For more information, see your Notes administrator.

@Bhead title@<:s><:#260,8486>Why doesn't a replica database contain all the documents it should?

<:s><:#480,8486>If none of the following explanations apply, try clearing the replication history by choosing File - Database - Properties, clicking Replication History, and then Clear. 

@See also prnt@<+@><:s><:#240,8486>For more information, see "About Replication History" earlier in this chapter.

@Dhead@<+@><:s><:#240,8486>The source server has insufficient access

<+@><:s><:#1200,8486>The source server access in a destination replica ACL determines what the destination replica can receive from the source server. Give the source server higher access in the destination replica ACL if necessary. The following message in the server Notes Log
 (LOG.NSF) indicates insufficient server access: "Access control is set to not allow replication."

@See also prnt@<:s><:#720,8486>For more information, see "About server access levels and replication, "About features that affect what information replicates between servers," and "About guidelines for selecting server access levels" earlier in this chapter. 

@See also prnt@<+@><:s><:#240,8486>For information on the Notes Log, see Chapter 7 of the Administrator's Guide.

@Dhead@<:s><:#240,8486><+!>You haven't included <-!><+!>a destination server in an access list<-!>

<:s><:#960,8486>Access lists allow only a subset of people and servers in the ACL to access documents. If such access lists exist, add the destination server to them in the source server replica. If the access list uses a role to define access, add the destination server t
o the role on the source server replica.

@See also prnt@<:s><:#720,8486>For more information, see "About server access levels and replication, "About features that affect what information replicates between servers," and "About guidelines for selecting server access levels" earlier in this chapter. 

@Dhead@<:s><:#240,8486><+!>The source server has insufficient access to its replica<-!>

<:s><:#720,8486>The ACL on a source server replica must list the source server with access at least as high as its users in order to pass along changes. Increase the source server access on the source server replica if necessary.

@See also prnt@<:s><:#720,8486>For more information, see "About server access levels and replication, "About features that affect what information replicates between servers," and "About guidelines for selecting server access levels" earlier in this chapter. 

@Dhead@<+@><:s><:#240,8486><+!>An intermediate server has insufficient access

<+@><:s><:#720,8486>If replication between a source and destination server occurs through an intermediate server, make sure the source and destination server replica ACLs give the intermediate server high enough access to replicate all changes.

@See also prnt@<+@><:s><:#240,8486>For more information, see "About guidelines for selecting server access levels."

@Dhead@<+@><:s><:#240,8486><+!>Replication settings are filtering documents<-!>

<+@><:s><:#480,8486>Some replication settings acts as filters that screen out documents and features. Check the replication settings.

@See also prnt@<+@><:s><:#240,8486>For more information, see "About customizing replication" earlier in this chapter.

@Dhead@<+@><:s><:#240,8486><+!>The server is out of disk space

<+@><:s><:#480,8486>Ask your Notes administrator if the server is out of disk space and if so, investigate moving a replica to another server or deleting databases on the server.

<+@><:s><:#240,8486><+!>System dates are causing the problem<-!><:f180,BArial,0,0,255><+!><+"> 

<+@><:s><:#240,8486><+!><+"><:f180,BArial,0,0,255>Need to investigate this<-"><-!><:f>

@Bhead title@<:s><:#260,8486>Why isn't a replica database receiving ACL or design changes?

<:s><:#720,8486>To receive ACL changes from a source server, the replica database on the destination server must give the source server Manager access and the source server must give the destination server at least Reader access.

<:s><:#720,8486>To receive design changes from a source server, the replica database on the destination server must give the source server at least Designer access and the source server replica must give the destination server at least Reader access.

@See also prnt@<:s><:#480,8486>For more information, see "About server access levels and replication" earlier in this chapter.

<+@><:s><:#240,8486>

@Bhead title@<+@><:s><:#260,8486>Why don't changes to the database title replicate?

<+@><:#720,8486>If the replication setting "Do not send changes in database title & catalog info to other replicas" is set on the source server replica, the title won't replicate. Deselect this setting to replicate a database title.

@See also prnt@<+@><:s><:#240,8486>For more information, see "About customizing replication" earlier in this chapter."

@Bhead title@<+@><:s><:#260,8486><+!>Why are replicas different sizes?<-!>

<:s><:#720,8486>Replication settings, ACLs, Read ACLs, Reader Names fields, view indexes, and unused space are some of the reasons replicas of a database may not be the same size.

@See also prnt@<:s><:#480,8486>For more information, see "About size differences among replicas of a database" in Chapter 5.

@Bhead title@<+@><:s><:#260,8486><+!>Why do I see the message "Database is not fully initialized yet"<-!>

<+@><:s><:#480,8486>This message indicates that the replica is a replica stub that hasn't yet been populated with documents.

@See also prnt@<+@><:s><:#480,8486>For more information on replica stubs, see "Creating replicas on servers" earlier in this chapter and "Creating a replica stub" in Help.

<+@><:s><:#480,8486>The most common reasons users see this message when they try to open a database are:

@Dhead@<+@><:s><:#240,8486>A replica stub on a workstation hasn't been manually replicated

<+@><:s><:#720,8486>If users create replica stubs on their workstations and don't  populate them with documents according to a schedule, they must manually replicate to populate the replica with documents.

@See also prnt@<+@><:s><:#480,8486>For more information, see "Creating a replica stub" and "Ways to replicate local databases" in Help.

<:s><:#480,8486><+!>The server storing the replica stub doesn't have<-!><+!> adequate access to pull information<-!><+!> 
<-!>

<:s><:#720,8486>If you rely on scheduled replication to populate a replica stub, the server storing the replica stub must have at least Reader access in the source server replica ACL to pull the documents from the source server.

@See also prnt@<+@><:s><:#480,8486>For more information, see "About server access levels and replication" earlier in this chapter.

@Dhead@<+@><:s><:#240,8486><+!>An<-!><+!> appropriate connection record between two servers isn't in place

<+@><:s><:#1200,8486>If you rely on scheduled replication to populate a replica stub on a server with documents from a replica on another server, a correctly-configured connection record must exist between the two servers storing the replica and the replica stub. Confirm with y
our Notes administrator that an appropriate connection record exists.

@Dhead@<+@><:s><:#240,8486>Replication is disabled

<:s><:#720,8486>Notes cannot populate a replica stub if replication is disabled on the source or destination server replica. To see if replication is disabled, select the database icon, choose File - Replication - Replication Settings and click the Other icon.

@Dhead@<:s><:#240,8486><+!>The file name shown on <-!><+!> the replica stub is incorrect

<:s><:#1680,8486>Press and hold SHIFT and choose View - Server Names to show the server and file names of icons on the workspace. A replica stub icon should show the source server and file name of the original replica; if the source server replica is in a subdirectory, the 
file name shown on the replica stub should include the path to the subdirectory. To correct the source server or file name shown on the replica stub, choose File - Database - Properties; on a replica stub, the source server and file name appear in the Title
 field. 

<:s><:#240,8486><:f180,BArial,0,0,255><+!><+">Correct for R4?--I don't think so.<-"><-!><:f>

@Bhead title@<:s><:#520,8486><+!>Why does a new replica contain the ACL of the source server when I didn't copy the ACL?<-!>

<:s><:#240,8486><+!>

@Dhead@<:s><:#480,8486><+!>Somebody modified the ACL on the source server before initial replication occurred

<:s><:#1200,8486>If you create a replica stub and somebody modifies the ACL on the source server before initial replication occurs, the ACL on the source server becomes the most recent one and replicates to the replica stub. Simply opening the Access Control List dialog box
 on the source server replica and then closing it can causes this problem.

@Dhead@<:s><:#240,8486><+!>The server times are out of sync

<:s><:#720,8486>If you create a complete replica immediately (rather than creating a replica stub) and the time on the source server is later than the time on the destination server, the new replica contains the ACL from the source server.

@Bhead title@<:s><:#260,8486><+!>Why aren't<-!><+!> deletions replicating<-!><+!>?<-!>

<:s><:#240,8486><+!>

<:s><:#240,8486><+!>Servers don't have adequate access to the database

<:s><:#480,8486>To receive document deletions, the ACL on a destination server replica must give the source server Editor access or higher and have "Delete documents" selected.

<:s><:#240,8486><+!>A replication setting is preventing deletions from replicating<-!>

<:s><:#480,8486>A source server doesn't send deletions to another replica if the replication setting "Do not send deletions made in this replica to other replicas" is selected.

<:s><:#240,8486>

@Bhead title@<:s><:#260,8486><+!>Why are unexpected deletions occurring<-!><+!> in a replica?<-!>

<:s><:#480,8486>You can prevent a database from receiving deletions made in other replicas by selecting the replication setting "Do not receive deletions."

<:s><:#240,8486><+!>There is a new replication formula in place

<:s><:#480,8486>A replication formula eliminates certain documents from a replica. A new replication formula may change the contents of a database.

<:s><:#240,8486><+!>A replication setting is automatically removing older, unmodified documents

<:s><:#720,8486>The replication setting "Documents not modified in the last <[> ] days will be removed" removes older, unmodified documents. If the specified number of days is low, consider increasing the value.

@Bhead title@<:s><:#260,8486><+!>Why are deleted documents reappearing?<-!><-!><-!><-">

<:s><:#240,8486><+!>

<:s><:#240,8486><+!>A purge interval prevents replication of deletions<-!>

<:s><:#1200,8486>To save disk space, Notes purges deletion stubs that remain from document deletions according to the replication setting  "Save space by removing documents that have not been modified within the last <[> ] days." 
<:f180,BArial,0,0,255><+!><+">???CORRECT?<-"><-!><:f> If Notes purges the deletion stubs before they have a chance to replicate, deleted documents can reappear after the next replication.

@See also prnt@<:s><:#480,8486>For more information, see "Details: Shortening or removing older documents" in Help.

<:s><:#240,8486><+!>A document edit writes over<-!><+!> a <-!><+!>document deletion

<:#2400,8486>When the same document is modified on different servers between replication sessions, the "winning" document is the one modified most frequently, or if both are modified only once, the winner is the one modified most recently. If a document is edited multip
le times on one server and deleted on another server between replication sessions, the edited document "wins" because it underwent the greatest number of changes, even if the deletion was the most recent change. If somebody deletes a document on one server 
and then someone else updates the document on another server once between replication sessions, the edit overrides the deletion because both documents were updated once and the edit occurred after the deletion.

>

[Embedded]
00117740
