Add a snapshot schedule to a snapshot rule
Adds a snapshot schedule to a snapshot rule.
HTTP request syntax (URI)
POST <base_URI>/v8/storage/snapshot-rules/{snapshotRuleObjectId}/schedules
Parameters
Name | Type | Required | Values | Description |
snapshotRuleObjectId | URI_PARAM | Y | string | ID of the snapshot rule object. |
emails | BODY | Y | string | List of emails separated by ';'. |
time | BODY | Y | string | UNIX cron job time specification format. |
Return codes
Code | Data | Description |
201 | filesystemSnapshotSchedule | filesystemSnapshotSchedule object is returned. |
400 | Error Message | Missing or invalid request contents. |
403 | Error Message | Operation forbidden by access level. |
404 | Error Message | Requested resource not found. |
500 | Error message | Error associated with the storage system. |
Any HTTP status code other than 201 indicates that the API did not complete successfully.
Request example
curl -vk -H "X-Api-Key: zrxvSDAv9x.RIP4gkmKarG3beF.or.4Tc2im7oeqYN88C9XPGHxbXC" https://172.17.239.120:8444/v8/storage/snapshot-rules/343a3a3a38363539453444453845324646344541303030303030303030303030303030303a3a3a7269636b535352756c65/schedules -d '{"time":"30 16 * * *", "emails":"user1@example.com;user2@example.com"}' -X POST
Response example
HTTP/1.1 201 Created { "filesystemSnapshotSchedule": { "emails": "user1@example.com;user2@example.com", "handle": 1, "objectId": "3330203136202a202a202a7377616d6d79406864732e636f6d3b687472696e68406864732e636f6d3a3a3a343a3a3a31", "isValid": true, "time": "30 16 * * *", "virtualServerId": 4 }, "uri": "https://172.17.239.120:8444/v8/storage/snapshot-rules/343a3a3a38363539453444453845324646344541303030303030303030303030303030303a3a3a7269636b535352756c65/schedules/3330203136202a202a202a7377616d6d79406864732e636f6d3b687472696e68406864732e636f6d3a3a3a343a3a3a31" }