McAfee M-1250 Upgrade Guide - Page 25

Backing up Network Security Platform data, Performing a database backup

Page 25 highlights

Upgrading the Central Manager Preparing for the upgrade 3 Backing up Network Security Platform data Before you upgrade, back up your tables and save any McAfee Custom Attacks (formerly UDS) that you have created. If you have a very large number of alerts and packet logs to upgrade, first consider archiving and deleting any alert and packet log data that you do not need prior to creating your database backup files. Save your entire backup in a different location than the current Central Manager or Manager to prevent data loss. Performing a database backup Back up your database BEFORE you upgrade. McAfee strongly recommends backing up All Tables and archiving the alerts and packet logs. Performing an All-Tables backup The All Tables backup process is time consuming (based upon the size of your database); however, it ensures the integrity of your existing data should you encounter any difficulties at any point during the upgrade, or should you wish to return to your current version of the Central Manager/Manager. Note that an All-Tables backup includes all Custom Attacks as well. To perform an All-Tables backup: Task 1 Navigate to \bin. 2 Execute the dbadmin.bat file. The standalone tool opens. 3 Select All Tables as the Backup Type: 4 Type a Backup Filename. You can use alphanumeric characters including hyphens and underscores (for example, backup_01-10-10). 5 Optionally type the Backup Directory where you want the backup to be stored. You can specify the full-path to the Backup Directory or just the directory name. If you do not specify a backup directory, then the backup is stored in the default backup directory at \App\Backups. 6 Optionally type a description of your backup in Comments. 7 Click Backup. After a few moments, the following message appears: "Database backup successful." You can see the backup information by clicking the DB Restore tab. In the backup directory, you will find an XML file (JAR format) with the backup file name that you specified. Reviewing the Upgrade Considerations Review this section carefully before you commence the upgrade process: • Central Manager upgrade downtime window: How long the upgrade takes depends on the size of your deployment and the size of your database. The Central Manager upgrade process alone can take an hour to complete. • OS upgrade downtime: Central Manager 6.0 is supported on Windows Server 2008 R2 (Standard Edition) 64-bit English and Japanese. If you plan to upgrade the OS, then factor this in when you estimate the Central Manager downtime. McAfee® Network Security Platform 6.1 Upgrade Guide 25

  • 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

Backing up Network Security Platform data
Before you upgrade, back up your tables and save any McAfee Custom Attacks (formerly UDS) that
you have created. If you have a very large number of alerts and packet logs to upgrade, first consider
archiving and deleting any alert and packet log data that you do not need prior to creating your
database backup files.
Save your entire backup in a different location than the current Central Manager or Manager to prevent
data loss.
Performing a database backup
Back up your database BEFORE you upgrade. McAfee strongly recommends backing up All Tables and
archiving the alerts and packet logs.
Performing an All-Tables backup
The All Tables backup process is time consuming (based upon the size of your database); however, it
ensures the integrity of your existing data should you encounter any difficulties at any point during the
upgrade, or should you wish to return to your current version of the Central Manager/Manager. Note
that an All-Tables backup includes all Custom Attacks as well.
To perform an All-Tables backup:
Task
1
Navigate to <Central Manager/Manager install directory>\bin.
2
Execute the dbadmin.bat file.
The standalone tool opens.
3
Select
All Tables
as the Backup Type:
4
Type a
Backup Filename
. You can use alphanumeric characters including hyphens and underscores (for
example, backup_01-10-10).
5
Optionally type the Backup Directory where you want the backup to be stored. You can specify the
full-path to the Backup Directory or just the directory name.
If you do not specify a backup directory, then the backup is stored in the default backup directory
at <Central Manager/Manager install directory>\App\Backups.
6
Optionally type a description of your backup in
Comments
.
7
Click
Backup
. After a few moments, the following message appears: "Database backup successful."
You can see the backup information by clicking the
DB Restore
tab. In the backup directory, you will
find an XML file (JAR format) with the backup file name that you specified.
Reviewing the Upgrade Considerations
Review this section carefully before you commence the upgrade process:
Central Manager upgrade downtime
window: How long the upgrade takes depends on the size of your
deployment and the size of your database. The Central Manager upgrade process alone can take an
hour to complete.
OS upgrade downtime:
Central Manager 6.0 is supported on Windows Server 2008 R2 (Standard
Edition) 64-bit English and Japanese. If you plan to upgrade the OS, then factor this in when
you estimate the Central Manager downtime.
Upgrading the Central Manager
Preparing for the upgrade
3
McAfee
®
Network Security Platform 6.1 Upgrade Guide
25