| Label | Action | Expanded Description / Example |
|---|---|---|
| Profile Name* | Enter a value | A unique identifier for the external backup profile. This name is displayed in the profile list and is used to distinguish this export job from others. Choose a meaningful name that reflects the device’s scope or destination. Example: Cisco FTP Backup. |
| Status | Toggle on/off | Controls whether the profile is active. Enabled: The profile can be executed manually or automatically based on its schedule. Disabled: No exports will run, even if a schedule exists. |
| Visibility | Select Public or Private | Determines who can view and manage this profile. Public profiles are visible across users within the selected scope, while Private profiles are restricted to the creator and authorized users. |
| Asset Tag | Select from the dropdown | Narrows the device scope by asset tag. Only devices associated with the selected asset tag are included in the export. Useful when devices are categorized logically across environments or vendors. |
| Device Group | Select from the dropdown | Defines the device group whose configurations will be exported. NCCM uses this selection to identify which devices stored configurations are included in the export job. |
| Label | Action | Expanded Description / Example |
|---|---|---|
| Protocol | Select FTP or SFTP | Specifies the file transfer protocol used to export configurations. FTP uses standard file transfer, while SFTP provides encrypted communication and is recommended for secure environments. |
| Backup Directory* | Enter a value | The absolute directory path on the external server where exported files and folders are created. NCCM creates subfolders under this path based on the selected folder format. Example: /backup/cisco/. |
| Backup Host* | Enter a value | The IP address or hostname of the external FTP/SFTP server that receives the configuration backups. Example: 10.0.4.201 or backup-server.company.com. |
| Select Backup Server Credential* | Select from the dropdown | Use an existing credential profile stored in Infraon for authenticating to the external server. This avoids manual credential entry and ensures centralized credential management. |
| Username* | Enter a value | The username used to authenticate to the external server when credentials are provided manually, rather than selecting a saved credential profile. |
| Password* | Enter a value | The password associated with the specified username. This is used only when manual credential entry is selected. |
| Port* | Enter a value | The port number used for the FTP or SFTP connection. Common examples include 21 for FTP and 22 for SFTP. |
| Label | Action | Expanded Description / Example |
|---|---|---|
| Backup File Name Format | Select IP Address or Hostname | Determines how exported configuration files are named. Choosing an IP Address creates files named after the device's IP address, whereas choosing a Hostname uses the device's hostname. Example: 10.0.4.201.cfg or router-core-1.cfg. |
| Backup Folder Format* | Select date format | Defines how folders are created under the backup directory. Formats use Python-supported date patterns.
|
| Include Inventory Data | Toggle on/off | When enabled, NCCM exports device inventory details along with configuration files. This helps retain hardware and software context alongside backups. |
| Configuration Type* | Add one or more options | Specifies which configuration types are exported. Running exports the active configuration, Startup exports the saved configuration, and selecting both exports both types if available. |
| Label | Action | Expanded Description / Example |
|---|---|---|
| Execute Now | Select option | Executes the export job immediately after the profile is submitted. This option ignores scheduling rules and runs the export once. |
| Schedule | Select option | Enables the scheduled execution of the export job based on the defined timing configuration. |
| Schedule Mode | Select Once / Every / Daily / Weekly / Monthly | Defines how often the export job runs. For example, Daily runs once per day, while Weekly runs on selected days of the week. |
| Time | Set time | Specifies the exact time at which the scheduled export runs. Example: 11:30 AM. |
| Add Schedule | Click to add | Allows adding multiple schedules to the same profile, enabling exports at different times or frequencies. |
| Start (Optional) | Select date and time | Defines when the schedule becomes active. Until this date, the job has not been executed. |
| Until (Optional) | Select date and time | Defines when the schedule expires. After this date, no further exports occur. |
| Schedule Summary | View-only | Displays a human-readable summary of the configured schedule, such as Scheduled for every day at 11:30. |