Back Up 9.1.00 and 9.1.1 Databases and Restart the Services

Finishing the Upgrade Preparations › Back Up the Databases › Back Up 9.1.00 and 9.1.1 Databases and Restart the Services

Back Up 9.1.00 and 9.1.1 Databases and Restart the Services

Before you upgrade a CA Network Flow Analysis 9.1.00 or 9.1.1 deployment, back up the databases and files in the following table, then restart the services.

Important:

Make the backups run concurrently. If you restore data from backups that have different timestamps, problems can result. Ensure that your backed-up data files are timestamped with the same hour.
Store backups to a remote location to guard against the possibility of a hardware or OS failure on the main server. For example, back up the databases to an administrative share or mapped network drive.

Database	Description	Standalone Server	Harvester Servers (Distributed)	NFA Console Server (Distributed)
reporter	Enterprise Overview data and NFA console configuration data	Important		Important
harvester	Harvester configuration data	Important	Important
poller	Poller configuration data	Important	Important
ReaperArchive15	Historical (15-minute) data	Recommended	Recommended
Customized Files	Configuration or other files that have been customized	Important	Important	Important
Customized data_retention	Settings to regulate data retention	Important if customized	Important if customized
ReaperArchive	Realtime (1-minute) data	Optional, rarely backed up	Optional, rarely backed up
Windows Registry	Settings for the Windows Harvesters		Important (Windows Harvesters)

The following list describes the databases and their locations:

reporter database: Back up the previous 24 hours of Enterprise Overview data, NFA console configuration settings, and synchronization information.
Path: <NFA_Install_Path>\MySql51\data\reporter directory
harvester database: Back up the Harvester configuration data.
Path: <NFA_Install_Path>\MySql51\data\harvester directory
poller database: Back up the Poller configuration data. The poller and harvester configuration data are essential to perform the relational mapping that provides access to 15-minute data. The poller configuration data provides information about devices and interfaces to enable polling, such as persistent IDs for interfaces.
Path: <NFA_Install_Path>\MySql51\data\poller directory
ReaperArchive15 database: Optionally, back up the historical (15-minute) data that is stored for the reporting routers and interfaces. This backup is optional, but many administrators do back up the 15-minute data.
Path: <NFA_Install_Path>\Netflow\datafiles\ReaperArchive15 directory
Customized configuration files: Back up any customized configuration files--files that you customized or that were customized by CA Support. In addition, back up any customizations that you made to the website or reports.
The CA Network Flow Analysis configuration files typically have a .config, conf., or .ini extension and are located in the product installation path. Other customizations may include .css files and report logos.
ReaperArchive database: (Recommended) Back up the historical (15-minute) data.
Path: <NFA_Install_Path>\Netflow\datafiles\ReaperArchive directory
Customized data_retention database: If you customized any data retention settings, back up the data retention configuration data. It is unusual to customize data retention settings except with the assistance of CA Support. Changes to data retention settings can cause problems from rising demands on drive space.
Path: <NFA_Install_Path>\MySql51\data\data_retention directory
Windows Registry: Back up the Windows Registry on Windows Harvester servers. Harvester Registry settings are converted to MySQL database settings during the upgrade.
Back up the Registry as a .reg file by selecting File, Export in the Registry Editor window. For more information about the new location of Harvester settings, see the Release Notes topic "Relocation of Harvester Settings."

Follow these steps:

Connect to the server:
1. Open a remote desktop session.
2. Initiate a Terminal Services or VNC session to the installation server.
Copy each of the target directories or files to a remote location.
Restart the services.

Next: Verify that the servers meet the installation prerequisites.