To reduce the days of statistical data stored in trending data: Note: This method only works if the repository has trending data enabled. In the top navigation, click Repositories , then click Repositories. Click the repository that may be causing the issue. Reduce Days Trending to a desirable date. SSH into the Tenable. Stop the Tenable. Run the following command to list out the contents of the directory: ls -l Files older than 1 month are usually safe to delete.
Start the Tenable. Delete the unneeded reports from oldest to newest. Additional Resources. Not finding your answer? Ask our community of users and experts. Ask a question. Related Articles Nessus disk space usage Number of Views Number of Views 2. Number of Views 1. Number of Views You must be a registered user to add a comment.
If you've already registered, sign in. Otherwise, register and sign in. Just delete them when you don't need them. Most of us keep a couple just in case we do need to roll back, but generally you don't need more than a couple. Yes, that's how I'd do it on windows.
But you might have a "log rotate" function you could use as well that's what I reach for on Unix-like systems. Welcome to another Taco Tuesday! First of all, congratulations goes out to to last week's winner Definitely a unique use case! You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events. Atlassian Community logo Products Interests Groups.
Create Ask the community. Make sure the replacement device has access to the backup file. The restore process can retrieve the backup with SCP, so we recommend you put the backup somewhere accessible.
You can use the console or you can SSH to the newly configured management interface IP address or hostname. Keep in mind that the restore process will change this IP address. With SCP: restore remote-manager-backup location scp-hostname username filepath backup tar-file.
From the local device: restore remote-manager-backup backup tar-file. The role is noted in the backup file name. If you are restoring both devices in the HA pair, do this sequentially. Do not run the restore command on the second device until the restore process completes for the first device, including the reboot.
At this time, the device should appear out of date. Before you deploy, perform any post-restore tasks and resolve any post-restore issues:. Resolve licensing conflicts or orphan entitlements. Contact Cisco TAC. Resume HA synchronization.
See Suspend and Resume High Availability. The restore process removes VPN certificates from FTD devices, including certificates added after the backup was taken. If a restored device is not marked out of date, force deploy from the Device Management page: Redeploy Existing Configurations to a Device. Verify that the restore succeeded and the replacement device is passing traffic as expected. It assumes you have access to a successful backups of:. Maintaining registration ensures replacement devices can automatically reconnect after restore.
Locate a successful backup of your FXOS configurations. Make sure FXOS is running a compatible version. You must be running a compatible FXOS version before you re-add logical devices. Use Firepower Chassis Manager to add logical devices and perform initial configurations. Do not set the same management IP addresses as the logical device or devices on the faulty chassis. This can cause problems if you need to register a logical device in order to patch it.
If you need to patch a logical device, register to the FMC as described in the getting started guide. This feature allows you to return to a known good configuration or to recover from a system failure. To import from a local configuration file:. Click Choose File to navigate to and select the configuration file that you want to import. Click Import. Click Yes to confirm that you want to import the specified configuration file.
To import from a configuration file on a remote server:. Enter the hostname or IP address of the location where the backup file is stored. In the File Path field, enter the full path to the configuration file including the file name. Shut down, power off, and delete the virtual machine. For procedures, see the documentation for your virtual environment. Restoring overwrites all configurations, with very few exceptions.
The Backup Management page lists all locally stored backup files. Make sure Replace Configuration Data is enabled, then click Restore again to begin. Backups are stored as unencrypted archive. The file name includes identifying information that can include:. We recommend you back up appliances to a secure remote location and verify transfer success.
Backups left on an appliance may be deleted, either manually or by the upgrade process; upgrades purge locally stored backups. For more information on your options, see Backup Storage Locations. The Backup Management page lists available backups.
Enable or disable remote storage for backups without having to edit the FMC system configuration. This option appears only after you configure remote storage. You can move a file back and forth as many times as you want. This will delete—not copy—the file from the current location. When you move a backup file from remote storage to the FMC, where it is stored on the FMC depends on the kind of backup:.
Click Upload Backup , choose a backup file, and click Upload Backup again. Unlike moving a backup file, this does not delete the backup from the FMC.
The following table describes backup storage options for FMCs and managed devices. After you do this, all subsequent FMC backups and FMC-initiated device backups are copied to that volume, but you can still use the FMC to manage them restore, download, upload, delete, move. You cannot provide CLI options or set a disk space threshold, and it does not affect remote storage of reports. You also cannot manage backup files after they are copied out.
This option is useful if you want to store backups locally and SCP them to a remote location. If you do not configure remote storage by mounting a network volume, you can save backup files on the FMC:. Do not configure remote storage by mounting a network volume.
Do not enable Retrieve to Management Center. You can now use the FMC to perform on-demand remote backups of certain managed devices.
Previously, only and series devices supported backups, and you had to use the device's local GUI. For supported platforms, see Requirements for Backup and Restore. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book Updated: October 6, Chapter: Backup and Restore.
Storing Backup Files You can store backups locally. What Is Backed Up? FMC backups can include: Configurations. What Is Restored? Make sure you understand and plan for the following: You cannot restore what is not backed up. Restoring fails VPN certificates. Requirements for Backup and Restore Backup and restore has the following requirements.
Model Requirements: Restore A replacement appliance must be the same model as the one you are replacing.
Version Requirements As the first step in any backup, note the patch level. License Requirements Address licensing or orphan entitlements concerns as described in the best practices and procedures.
Back up a device from the FMC: Global only. Restore a device: None. Restore devices locally. Guidelines and Limitations for Backup and Restore Backup and restore has the following guidelines and limitations. Guidelines and Restrictions Do not modify the contents of the configuration file. Best Practices for Backup and Restore Backup and restore has the following best practices. When to Back Up We recommend backing up during a maintenance window or other time of low use.
You should back up in the following situations: Regular scheduled backups. After SLR changes. Before upgrade or reimage. After upgrade. Maintaining Backup File Security Backups are stored as unencrypted archive.
Caution We recommend you back up FMCs and devices to a secure remote location and verify transfer success. Do not suspend or break HA before you restore. Check Disk Space. Before Restore Before restore, you should: Revert licensing changes. Revert any licensing changes made since you took the backup.
Disconnect faulty appliances. Disconnect the management interface, and for devices, the data interfaces. Do not unregister managed devices. After Restore After restore, you should: Reconfigure anything that was not restored. Before you begin You must read and understand the requirements, guidelines, limitations, and best practices. Step 2 Choose whether to use an existing backup profile or start fresh.
FMC backups require that you use or create a backup profile. Enter a Name for the backup profile. Provide a hostname or IP address, the path to the remote directory, and a username and password. Note This option is useful if you want to store backups locally and also SCP them to a remote location. Step 6 Optional Enable Email and enter an email address to be notified when the backup completes.
Step 7 Click Start Backup to start the on-demand backup. Step 8 Monitor progress in the Message Center. The manifest appears, listing the name of each file, its owner and permissions, and its file size and date. Step 4: Select the backup file that you want to restore and click Restore. The Restore Backup page appears. Note that if the VDB version in the backup does not match the VDB version currently installed on your appliance, the Restore button is grayed out.
Step 9: Reapply any access control, intrusion, network discovery, health, and system policies to the restored system. If you add licenses after a backup has completed, these licenses will not be removed or overwritten if this backup is restored. To prevent a conflict on restore, remove those licenses before restoring the backup, noting where the licenses were used, and add and reconfigure them after restoring the backup.
It is recommended that you save the backup task in the Backup Profiles and schedule a reoccurring job to run the backup automatically and in certain intervals you feel comfortable with. It can be daily backup, weekly or monthly.
It depends on how frequently you change the system configuration and whether you want to back up the events or just the configuration.
You can download the configuration template for free. Step 2: Click on Defense Center Backup.
0コメント