McAfee EPOCDE-AA-BA Product Guide - Page 312

Backup and restore ePolicy Orchestrator databases, Changing SQL Server information

Page 312 highlights

A Appendix: Maintaining ePolicy Orchestrator Databases Backup and restore ePolicy Orchestrator databases For most enterprise customers, using simple recovery mode is an acceptable solution as the most typical data lost in the event of a disaster is event information. Using full recovery mode adds the administrative overhead of periodically backing up the transaction log, as well as the ePolicy Orchestrator database. Primarily for this reason, McAfee recommends using simple recovery mode for the ePolicy Orchestrator database. If you use full recovery mode, ensure you have a good backup plan for both your ePolicy Orchestrator database and transaction log. A discussion of SQL Server database backup plans is beyond the scope of this guide. For more details, please refer to the Microsoft SQL Server documentation. Backup and restore ePolicy Orchestrator databases McAfee recommends that you back up ePolicy Orchestrator databases regularly to protect your data and guard against hardware and software failure. If you ever need to reinstall the server, you might need to restore from a backup. How often you back up depends on how much of your data you are willing to risk. Some possible approaches include: • Back up your database at least once a week. • If you have made many changes to your deployment, you might want to back up daily. • To mitigate bandwidth demands during regular business hours, you might schedule automated nightly backups. • To further balance the load, you might perform incremental daily or nightly backups, and a full weekly backup each week. Save the backup copy to a different server than the one hosting your live database. If your database server crashes, you don't want to lose your backup too. Performing regular backups provides the ability to restore your database if that should ever become necessary because of software or hardware failure, or because of an upgrade to server or database server hardware. For information on backing up and restoring your SQL database, see: • Microsoft documentation for the management tool appropriate for the database you are using. • McAfee KnowledgeBase article KB52126. Changing SQL Server information Use this task to edit the SQL Server connection configuration details. This is useful to make changes to the user account information in ePolicy Orchestrator when you make changes to the SQL Server authentication modes in SQL Server Enterprise Manager or SQL Server Management Studio. Do this if you need to use a privileged SQL user account for added network security. Changing the database settings to point this McAfee ePO server to an McAfee ePO database that is not an exact match can cause the removal of product extensions and the loss of all associated data. McAfee recommends performing this task only to change the configuration of your existing database. 312 McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide

  • 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

For most enterprise customers, using simple recovery mode is an acceptable solution as the most
typical data lost in the event of a disaster is event information. Using full recovery mode adds the
administrative overhead of periodically backing up the transaction log, as well as the ePolicy
Orchestrator database.
Primarily for this reason, McAfee recommends using simple recovery mode for the ePolicy Orchestrator
database.
If you use full recovery mode, ensure you have a good backup plan for both your ePolicy Orchestrator
database and transaction log. A discussion of SQL Server database backup plans is beyond the scope
of this guide. For more details, please refer to the Microsoft SQL Server documentation.
Backup and restore ePolicy Orchestrator databases
McAfee recommends that you back up ePolicy Orchestrator databases regularly to protect your data
and guard against hardware and software failure. If you ever need to reinstall the server, you might
need to restore from a backup.
How often you back up depends on how much of your data you are willing to risk. Some possible
approaches include:
Back up your database at least once a week.
If you have made many changes to your deployment, you might want to back up daily.
To mitigate bandwidth demands during regular business hours, you might schedule automated
nightly backups.
To further balance the load, you might perform incremental daily or nightly backups, and a full
weekly backup each week.
Save the backup copy to a different server than the one hosting your live database. If your database
server crashes, you don’t want to lose your backup too.
Performing regular backups provides the ability to restore your database if that should ever become
necessary because of software or hardware failure, or because of an upgrade to server or database
server hardware.
For information on backing up and restoring your SQL database, see:
Microsoft documentation for the management tool appropriate for the database you are using.
McAfee KnowledgeBase article KB52126.
Changing SQL Server information
Use this task to edit the SQL Server connection configuration details.
This is useful to make changes to the user account information in ePolicy Orchestrator when you make
changes to the SQL Server authentication modes in SQL Server Enterprise Manager or SQL Server
Management Studio. Do this if you need to use a privileged SQL user account for added network security.
Changing the database settings to point this McAfee ePO server to an
McAfee ePO database that is not an exact match can cause the removal
of product extensions and the loss of all associated data. McAfee
recommends performing this task only to change the configuration of
your existing database.
A
Appendix: Maintaining ePolicy Orchestrator Databases
Backup and restore ePolicy Orchestrator databases
312
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide