McAfee EPOCDE-AA-BA Product Guide - Page 193

Replication tasks, Repository selection

Page 193 highlights

Using tasks to manage products and systems Server tasks and what they do 16 Replication tasks Use replication tasks to copy the contents of the master repository to distributed repositories. Unless you have replicated master repository contents to all your distributed repositories, some systems do not receive them. Ensure that all your distributed repositories are up-to-date. If you are using global updating for all of your updates, replication tasks might not be necessary for your environment, although they are recommended for redundancy. However, if you are not using global updating for any of your updates, you must schedule a Repository Replication server task or run a Replicate Now task. Scheduling regular Repository Replication server tasks is the best way to ensure that your distributed repositories are up-to-date. Scheduling daily replication tasks ensures that managed systems stay up-to-date. Using Repository Replication tasks automates replication to your distributed repositories. Occasionally, you might check in files to your master repository that you want to replicate to distributed repositories immediately, rather than wait for the next scheduled replication. Run a Replicate Now task to update your distributed repositories manually. Full vs. incremental replication When creating a replication task, select Incremental replication or Full replication. Incremental replication uses less bandwidth and copies only the new updates in the master repository that are not yet in the distributed repository. Full replication copies the entire contents of the master repository. McAfee recommends scheduling a daily incremental replication task. Schedule a weekly full replication task if it is possible for files to be deleted from the distributed repository outside of the replication functionality of the ePolicy Orchestrator software. Repository selection New distributed repositories are added to the repository list file containing all available distributed repositories. The agent of a managed system updates this file each time it communicates with the McAfee ePO server. The agent performs repository selection each time the agent (McAfee Framework Service) service starts, and when the repository list changes. Selective replication provides more control over the updating of individual repositories. When scheduling replication tasks, you can choose: • Specific distributed repositories to which the task applies. Replicating to different distributed repositories at different times lessens the impact on bandwidth resources. These repositories can be specified when you create or edit the replication task. • Specific files and signatures that are replicated to the distributed repositories. Selecting only those types of files that are necessary to each system that checks in to the distributed repository lessens the impact on bandwidth resources. When you define or edit your distributed repositories, you can choose which packages you want to replicate to the distributed repository. This functionality is intended for updating only products that are installed on several systems in your environment, like Virus Scan Enterprise. The functionality allows you to distribute these updates only to the distributed repositories these systems use. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 193

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

Replication tasks
Use replication tasks to copy the contents of the master repository to distributed repositories. Unless
you have replicated master repository contents to all your distributed repositories, some systems do
not receive them. Ensure that all your distributed repositories are up-to-date.
If you are using global updating for all of your updates, replication tasks
might not be necessary for your environment, although they are
recommended for redundancy. However, if you are not using global
updating for any of your updates, you must schedule a Repository
Replication server task or run a Replicate Now task.
Scheduling regular Repository Replication server tasks is the best way to ensure that your distributed
repositories are up-to-date. Scheduling daily replication tasks ensures that managed systems stay
up-to-date. Using Repository Replication tasks automates replication to your distributed repositories.
Occasionally, you might check in files to your master repository that you want to replicate to
distributed repositories immediately, rather than wait for the next scheduled replication. Run a
Replicate Now task to update your distributed repositories manually.
Full vs. incremental replication
When creating a replication task, select
Incremental replication
or
Full replication
. Incremental replication uses
less bandwidth and copies only the new updates in the master repository that are not yet in the
distributed repository. Full replication copies the entire contents of the master repository.
McAfee recommends scheduling a daily incremental replication task.
Schedule a weekly full replication task if it is possible for files to be
deleted from the distributed repository outside of the replication
functionality of the ePolicy Orchestrator software.
Repository selection
New distributed repositories are added to the repository list file containing all available distributed
repositories. The agent of a managed system updates this file each time it communicates with the
McAfee ePO server. The agent performs repository selection each time the agent (
McAfee Framework
Service
) service starts, and when the repository list changes.
Selective replication provides more control over the updating of individual repositories. When
scheduling replication tasks, you can choose:
Specific distributed repositories to which the task applies. Replicating to different distributed
repositories at different times lessens the impact on bandwidth resources. These repositories can
be specified when you create or edit the replication task.
Specific files and signatures that are replicated to the distributed repositories. Selecting only those
types of files that are necessary to each system that checks in to the distributed repository lessens
the impact on bandwidth resources. When you define or edit your distributed repositories, you can
choose which packages you want to replicate to the distributed repository.
This functionality is intended for updating only products that are installed
on several systems in your environment, like Virus Scan Enterprise. The
functionality allows you to distribute these updates only to the
distributed repositories these systems use.
Using tasks to manage products and systems
Server tasks and what they do
16
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
193