Backup Strategies

JSA Data Backups

Data classification is an important consideration for backup strategies for the following reasons:

• Data such as personal identity information (PII) needs to be stored securely, and might need to be kept separate from bulk data backups, and retained for longer periods for compliance reasons.

• Keep JSA system configuration data separate from your security data such as events and flows. It is safer to keep the system configuration separate and easier to restore this data if it stored separately.

• Store data such as PCI data in a separate location so that you can easily access this data when auditors want to see it.

• Think about types of data and retention periods when you develop your backup strategies.

• You can back up some types of data more frequently than others and you can use offsite storage for some data to insure against data loss.

Retention Settings

The default setting for JSA backup retention is 7 days. You can also do an on-demand backup after you make major configuration changes. You can give this on-demand backup a descriptive name to easily find your changes if you need to return to this configuration.

Scheduled backups overwrite older scheduled backups. On-demand backups are kept indefinitely. After the JSA backup volume reaches 75% of its capacity, scheduled backups no longer run.

Backup Location

The backup location is also a significant consideration when you deploy JSA. If your backups remain on a host, and that host fails, then all backup data is lost.

You can either create your backups on an external system, or copy backups to an external system.

Store copies of important data locally and remotely for added data security.