Backup schedule using POST with https

[ConnorH]

I am trying to resolve the ActiveIQ Suggestion “The node is not configured to save configuration backups to a remote location.” We don’t really understand why POST is the defaulted method for HTTPS and how we cannot change it to PUT as is explained by the KB article the ActiveIQ Suggestion links us to:

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. For more information, see your web server's documentation.

The problem we are facing is that Artifactory does not support POST for HTTPS and this is where we are attempting to have our backups land. Artifactory returns a 405 when we attempt to use POST. 

::*> system configuration backup upload -node storage-cold-01 -backup storage-cold.8hour.2025-03-20.02_15_00.7z -destination <artifactory link> -rest-method POST

Enter the username: <username>
Enter the password:

Uploading the configuration backup file.

Error: command failed: Upload operation of configuration backup file exited with error: Failed to upload configuration backup file "/mroot/etc/backups/config/storage-cold.8hour.2025-03-20.02_15_00.7z" to

<artifactory link>. Error: HTTP response code said error : The requested URL returned error: 405.

::*>

We are able to use ‘system configuration backup upload’ with ‘-rest-method PUT’. We notice there is no way to adjust the REST method that the scheduled backup uses though. 

I opened a technical support case regarding this and have been told that I must ask about this in here. 

[the_br0cken]

I am facing the same issue. I configured Apache with WebDav as suggested. Manual upload via HTTPS with RESTMethod PUT works.

Shouldn't be to hard to implement a switch for the automated upload.

Using unencrypted Protocols in 2025 isn't a valid option.

[ConnorH]

The technical case was updated with the following information on March 28th, 2025:

NetApp Support Site - JiraNgage - CONTAP-196995

Here is the minimum recommended release with this enhancement:

9.16.1RC1 - 9.16.1P2
9.15.1RC1 - 9.15.1P8
9.14.1P4 - 9.14.1P11

Other options would be to use the HTTP protocol to send these config backups to Artifactory or switch to a web server that allows POST requests for HTTPS.

Please refer to these docs:

How to setup cluster configuration backups using a web server with HTTPS enabled - NetApp Knowledge Base

Commands for managing configuration backup schedules

Updated to "NetApp Release 9.16.1P4: Tue May 27 23:22:56 UTC 2025" though we still are seeing the backup attempt to use POST for HTTPS which results in a 405 return status. 

ONTAP is reporting the following:

Description
This message occurs when the configuration backup cannot be uploaded to the destination URL.
Event
configbr.uploadFailed: Configuration backup file /mroot/etc/backups/config/<hostname>.8hour.2025-07-07.18_15_01.7z cannot be uploaded to the destination URL https://<URL>.com/artifactory/<>/NetApp/backups/<hostname>/<hostname>.8hour.2025-07-07.18_15_01.7z. Error: 'HTTP response code said error : The requested URL returned error: 405'.
Action
Ensure that the destination URL is reachable, the protocol in the URL is supported, and the user credentials are valid.

Either we misunderstood the feature request implementation or said implementation isn't in this version?