Export a Repository

Required User Role: Administrator

You can export a repository from one Tenable Security Center and import it as an offline repository on another Tenable Security Center. You can export repositories via the Tenable Security Center user interface or the CLI. For more information, see Offline Repositories.

Note: Depending on the size of the repository database, this file can be quite large. It is important to save the file to a location with sufficient free disk space.

Tip: If the repository you want to export has trend data enabled and you want to include trend data in your repository export, export the repository via the CLI. Repositories that you export via the user interface do not include trend data. For more information about trend data, see IPv4/IPv6 Repositories, Agent Repositories, and Universal Repositories.

To export a repository via the user interface:

Log in to Tenable Security Center via the user interface.
Click Repositories > Repositories.

The Repositories page appears.
Right-click the row for the repository you want to export.

The actions menu appears.

-or-

Select the check box for the repository you want to export.

The available actions appear at the top of the table.
Click Export.

Tenable Security Center exports the repository.

To export a repository via the CLI:

Prepare the command you want to run.

/opt/sc/customer-tools/exportRepository.sh [repID] [trendingDays] [trendWithRaw]

Variable	Description
repID	The repository ID of the repository you want to export. To locate the repository ID, view the details for the repository, as described in View Repository Details.
trendingDays	(IP, Agent, and Universal repositories only) The number of days of vulnerability trending data to include. To use the preconfigured repository setting, type default. Note: The number of days of trending data included in the export cannot exceed the Days Trending setting for the repository or the number of days of trending data available for the repository. For example, if you request 30 days of trending data, but trending data has been enabled for only 15 days, then the export includes only 15 days of trending data. For more information about repository settings, see IPv4/IPv6 Repositories, Agent Repositories, and Universal Repositories.
trendWithRaw	(IP, Agent, and Universal repositories only) Specify whether you want the export to include plugin output data: yes or no. To use the preconfigured repository setting, type default.

Variable

Description

repID

The repository ID of the repository you want to export. To locate the repository ID, view the details for the repository, as described in View Repository Details.

trendingDays

(IP, Agent, and Universal repositories only) The number of days of vulnerability trending data to include. To use the preconfigured repository setting, type default.

Note: The number of days of trending data included in the export cannot exceed the Days Trending setting for the repository or the number of days of trending data available for the repository. For example, if you request 30 days of trending data, but trending data has been enabled for only 15 days, then the export includes only 15 days of trending data. For more information about repository settings, see IPv4/IPv6 Repositories, Agent Repositories, and Universal Repositories.

trendWithRaw

(IP, Agent, and Universal repositories only) Specify whether you want the export to include plugin output data: yes or no. To use the preconfigured repository setting, type default.

(Optional) To automatically overwrite an existing repository file with the same name, include the optional argument -f.

In the CLI in Tenable Security Center, run the export command.

For example:

/opt/sc/customer-tools/exportRepository.sh -f 1 default default

Tenable Security Center exports the repository.

What to do next:

To import the repository to another Tenable Security Center, add an offline repository to that Tenable Security Center, as described in Add a Repository.