• Home
• Brands
• Juniper Manuals
• Juniper STRM 2008.2 - RESTORING YOUR DATA 6-2008
• Juniper STRM 2008.2 - RESTORING YOUR DATA 6-2008 Troubleshooting Tips

Juniper STRM 2008.2 - RESTORING YOUR DATA 6-2008 Troubleshooting Tips

Download Troubleshooting tips of Juniper STRM 2008.2 - RESTORING YOUR DATA 6-2008 Processor for Free or View it Online on All-Guides.com.

1

2

3

4

5

6

Release 2008.2

JUNIPER NETWORKS STRM

T

ECHNICAL NOTE

RESTORING YOUR DATA

JUNE 2008

If you are using STRM 2008.1 and above, you can schedule the backup of your

configuration information and data using the STRM Administration Console. The

data portion of the backup includes all offenses (including targets and attacker

information), asset data, event category information, vulnerability data, event data,

and flow data located on STRM.

You can restore your configuration information using the STRM interface, however,

you must use the procedures in this document to restore your flow, event, or

reporting data. This document includes:

• Before You Begin

• Restoring Your Data

• Troubleshooting Tips

Caution: If the current configuration of your STRM system differs from the

configuration that existed at the time the data was backed up, your system may

experience some gaps in information once the data is restored. For example, if the

recovered data includes device information from a device that no longer exists, the

interface will not display information regarding this removed device.

Before You Begin Each managed host in your deployment, including the STRM Console, Flow

Processors, and Event Processors create backup files in the

/store/backup/

directory.

Note: Your system may also include a mount /store/backup from an external SAN

or NAS service, which allows for long term off-line retention of data, as often

required for compliancy regulations, such as, HIPPA and PKI.

Before you restore the data, consider the following:

• Locate the managed host on which the data is backed up (Console, Flow

Processor, or Event Processor).

• Backup files are saved using the following format:

backup.<name>.<hostname>_<host ID>.<target date>.<backup

type>.<timestamp>.tgz