Network Security Manager On-Premises System Administration Guide
- Network Security Manager 2.4.0 On-Premises System
- About Network Security Manager
- Dashboard
- Settings
- Licenses
- Administration
- Time
- Certificates
- Common Access Card (CAC) Authentication
- Diagnostics
- Firmware and Settings
- Backups/Restore Feature
- Configure a Scheduled NSM File System Backup
- Configure a Scheduled NSM File System Backup via SCP
- View NSM File System Backups
- Create a NSM File System Backup
- Create SCP of a NSM File System Backup
- Import a NSM File System Backup
- Export a NSM File System Backup
- Delete a NSM File System Backup
- Restore NSM to a File System Backup
- Backup/Restore NSM using Safemode
- Zero Touch
- Shutdown/Reboot
- Closed Network
- Network
- System Monitor
- High Availability
- NSM Management Console
Configure a Scheduled Backup in High Availability Setup
This section describes how scheduled backup works in a High Availability setup.
Backup can be scheduled only in an Active NSM system. Standby NSM system can't schedule a backup but Standby system triggers a backup run after 30 minutes of the scheduled backup in Active NSM system.
When NSM is configured in a HA pair, it is recommended to create or edit system backup schedules on an Active Primary NSM server.
Scenario: Primary NSM is Active setup and Secondary NSM is Standby setup
In this scenario when a backup is scheduled to run at a time, say t1, in Primary NSM system following the steps in Configure a Scheduled NSM File System Backup, a backup is by default scheduled to be run in the Secondary NSM system at a time which is 30 minutes after the scheduled time in primary system i.e (t1+30).
When the backup is being created at time t1, the Primary NSM system reboots. At this time the Secondary NSM system becomes Active setup and after reboot the Primary NSM system becomes the Standby setup.
After 30 minutes (t1+30) when the backup is being created in Secondary NSM system, it reboots. At this time the Primary NSM system again becomes Active setup and after reboot the Secondary NSM system becomes the Standby setup.
Was This Article Helpful?
Help us to improve our support portal