Skip to main content

Commands for managing configuration backup files

Contributors netapp-ahibbard netapp-barbe netapp-aherbin

You use the system configuration backup commands to manage cluster and node configuration backup files.

These commands are available at the advanced privilege level.

If you want to…​ Use this command…​

Create a new node or cluster configuration backup file

system configuration backup create

Copy a configuration backup file from a node to another node in the cluster

system configuration backup copy

Upload a configuration backup file from a node in the cluster to a remote URL (FTP, HTTP, HTTPS, TFTP, or FTPS)

system configuration backup upload

When you use HTTPS in the remote URL, use the -validate-certification option to enable or disable digital certificate validation. Certificate validation is disabled by default.

Note

The web server to which you are uploading the configuration backup file must have PUT operations enabled for HTTP and POST operations enabled for HTTPS. Some web servers might require the installation of an additional module. For more information, see your web server's documentation. Supported URL formats vary by ONTAP release. See the command line help for your ONTAP version.

Download a configuration backup file from a remote URL to a node in the cluster, and, if specified, validate the digital certificate

system configuration backup download

When you use HTTPS in the remote URL, use the -validate-certification option to enable or disable digital certificate validation. Certificate validation is disabled by default.

Rename a configuration backup file on a node in the cluster

system configuration backup rename

View the node and cluster configuration backup files for one or more nodes in the cluster

system configuration backup show

Delete a configuration backup file on a node

system configuration backup delete

Note

This command deletes the configuration backup file on the specified node only. If the configuration backup file also exists on other nodes in the cluster, it remains on those nodes.