- play_arrow What's New for Administrators
- play_arrow Overview of JSA Administration
- play_arrow User Management
- play_arrow License Management
- play_arrow System Management
- System Management
- System Health Information
- JSA Component Types
- Data Nodes
- Network Interface Management
- JSA System Time
- NAT-Enabled Networks
- Off-site Hosts Management
- Managed Hosts
- Configuration Changes in your JSA Environment
- Deploying Changes
- Restarting the Event Collection Service
- Shutting Down a System
- Restarting a System
- Collecting Log Files
- Changing the Root Password on Your JSA Console
- Resetting SIM
- play_arrow JSA Set Up Tasks
- JSA Set Up Tasks
- Network Hierarchy
- Automatic Updates
- Manual Updates
- Configuring System settings
- IF-MAP Server Certificates
- SSL Certificates
- IPv6 Addressing in JSA Deployments
- Advanced Iptables Rules Examples
- Data Retention
- System Notifications
- Custom Offense Close Reasons
- Configuring a Custom Asset Property
- Index Management
- Restrictions to Prevent Resource-intensive Searches
- App Hosts
- Checking the Integrity Of Event and Flow Logs
- Adding Custom Actions
- Managing Aggregated Data Views
- Accessing a GLOBALVIEW Database
- play_arrow Event Data Processing in JSA
- Event Data Processing in JSA
- DSM Editor Overview
- Properties in the DSM Editor
- Property Configuration in the DSM Editor
- Opening the DSM Editor
- Configuring a Log Source Type
- Configuring Property Autodetection for Log Source Types
- Configuring Log Source Autodetection for Log Source Types
- Configuring DSM Parameters for Log Source Types
- Custom Log Source Types
- Custom Property Definitions in the DSM Editor
- Event Mapping
- Exporting Contents from the DSM Editor
- play_arrow Using Reference Data in JSA
- play_arrow User Information Source Configuration
- play_arrow Juniper Networks X-Force Integration
- play_arrow Managing Authorized Services
- play_arrow Flow Sources Management
- play_arrow Remote Networks and Services Configuration
- play_arrow Server Discovery
- play_arrow Domain Segmentation
- play_arrow Multitenant Management
- Multitenant Management
- User Roles in a Multitenant Environment
- Domains and Log Sources in Multitenant Environments
- Provisioning a New Tenant
- Monitoring License Usage in Multitenant Deployments
- Rules Management in Multitenant Deployments
- Network Hierarchy Updates in a Multitenant Deployment
- Retention Policies for Tenants
- play_arrow Asset Management
- play_arrow Configuring JSA to Forward Data to Other Systems
- Forward Data to Other Systems
- Adding Forwarding Destinations
- Configuring Forwarding Profiles
- Configuring Routing Rules to Forward Data
- Using Custom Rules and Rule Responses to Forward Data
- Configuring Routing Rules to Use the JSA Data Store
- Viewing Forwarding Destinations
- Viewing and Managing Forwarding Destinations
- Viewing and Managing Routing Rules
- play_arrow Event Store and Forward
- play_arrow Security Content
- play_arrow SNMP Trap Configuration
- play_arrow Protect Sensitive Data
- play_arrow Log Files
- play_arrow Event Categories
- play_arrow Common Ports and Servers Used by JSA
- play_arrow RESTful API
Backup JSA Configurations and Data
By default, JSA creates a backup archive of your configuration information daily at midnight. The backup archive includes your configuration information, data, or both from the previous day. You can customize this nightly backup and create an on-demand configuration backup, as required.
Scheduling Nightly Backup
Use the Backup Recovery Configuration window to configure a night scheduled backup process.
By default, the nightly backup process includes only your configuration files. You can customize your nightly backup process to include data from your JSA Console and selected managed hosts. You can also customize your backup retention period, backup archive location, the time limit for a backup to process before timing out, and the backup priority in relation to other JSA processes.
The nightly backup starts running at midnight in the timezone where the JSA Console is installed. If JSA automatic updates are scheduled to run at the same time, the performance of JSA might be impacted.
The Backup Recovery Configuration window provides the following parameters:
Parameter | Description |
|---|---|
General Backup Configuration | |
Backup Repository Path | Type the location where you want to store your backup file. The default location is /store/backup. This path must exist before the backup process is initiated. If this path does not exist, the backup process aborts. If you modify this path, make sure the new path is valid on every system in your deployment.
|
Backup Retention Period (days) | Type or select the length of time, in days, that you want to store backup files. The default is 2 days. This period of time only affects backup files generated as a result of a scheduled process. On-demand backups or imported backup files are not affected by this value. |
Nightly Backup Schedule | Select a backup option. |
Select the managed hosts you would like to run data backups: | This option is only displayed if you select the Configuration and Data Backups option. All hosts in your deployment are listed. The first host in the list is your Console; it is enabled for data backup by default, therefore no check box is displayed. If you have managed hosts in your deployment, the managed hosts are listed below the Console and each managed host includes a check box. Select the check box for the managed hosts you want to run data backups on. For each host (Console or managed hosts), you can optionally clear the data items you want to exclude from the backup archive. |
Configuration Only Backup | |
Backup Time Limit (min) | Type or select the length of time, in minutes, that you want to allow the backup to run. The default is 180 minutes. If the backup process exceeds the configured time limit, the backup process is automatically canceled. |
Backup Priority | From this list box, select the level of importance that you want the system to place on the configuration backup process compared to other processes. A priority of medium or high have a greater impact on system performance. |
Data Backup | |
Backup Time Limit (min) | Type or select the length of time, in minutes, that you want to allow the backup to run. The default is 1020 minutes. If the backup process exceeds the configured time limit, the backup is automatically canceled. |
Backup Priority | From the list, select the level of importance you want the system to place on the data backup process compared to other processes. A priority of medium or high have a greater impact on system performance. |
On the navigation menu (
), click Admin.In the System Configuration section, click Backup and Recovery.
On the toolbar, click Configure.
On the Backup Recovery Configuration window, customize your nightly backup.
Click Save.
Close the Backup Archives window.
On the Admin tab menu, click Deploy Changes.
Creating an On-demand Configuration Backup Archive
If you must back up your configuration files at a time other than your nightly scheduled backup, you can create an on-demand backup archive. On-demand backup archives include only configuration information.
You initiate an on-demand backup archive during a period when JSA has low processing load, such as after normal office hours. During the backup process, system performance is affected.
On the navigation menu (
), click Admin.In the System Configuration section, click Backup and Recovery.
From the toolbar, click On Demand Backup.
Enter values for the following parameters:
Option
Description
Name
Type a unique name that you want to assign to this backup archive. The name can be up to 100 alphanumeric characters in length. The name can contain following characters: underscore (_), dash (-), or period (.).
Description
Type a description for this configuration backup archive. The description can be up to 255 characters in length.
Click Run Backup.
You can start a new backup or restore processes only after the on-demand backup is complete. You can monitor the backup archive process in the Backup Archives window.
Creating an Email Notification for a Failed Backup
To receive a notification by email about a backup failure on the JSA Console or a JSA Event Processor, create a rule that is based on the system notification message.
You must configure an email server to distribute system notifications in JSA. For more information, see Configuring Your Local Firewall.
If a backup fails, you see one of the following backup failure system notifications:
Backup: requires more disk spaceBackup: last Backup exceeded execution thresholdBackup: unable to execute request
Click the Offenses tab.
In the Offenses pane, click Rules.
Click Actions >New Event Rule.
In the Rule Wizard, check the Skip this page when running this rules wizard box and click Next.
In the filter box, type the following search query:
when the event QID is one of the following QIDs
Click the green add (+) icon.
In the Rule pane, click the QIDs link.
In the QID/Name field, type Backup:
Select the following QIDs and click Add +:
Backup requires more disk space
Backup: last backup exceeded execution threshold
Backup unable to execute request
Click Submit.
In the Rule pane, type the following name for your rule test and click Next:
Backup Failure
In the Rule Response section, check the Email box and type the email addresses you want to notify.
