Pin snapshot data
Connection and CORS help
Use HTTPS for remote clusters or HTTP on loopback. Requests go directly from your browser to the endpoint. Run List collections to populate the collection selector. When copying an authenticated cURL command, set MILVUS_TOKEN in your shell.
For cross-origin requests, configure the endpoint to answer OPTIONS and allow the docs origin, POST, Content-Type, and Authorization if you use a token. Try the copied cURL command to troubleshoot outside the browser.
POST/v2/vectordb/snapshots/pin
{
"dbName": "default",
"collectionName": "books",
"snapshotName": "books_backup",
"ttlSeconds": 3600
}Example response
{
"code": 0,
"data": {
"pinId": 123456789
}
}cURL command
curl --request POST --url 'https://your-cluster.example.com/v2/vectordb/snapshots/pin' \
--header 'Content-Type: application/json' \
--header "Authorization: Bearer ${MILVUS_TOKEN}" \
--data-raw '{
"dbName": "default",
"collectionName": "books",
"snapshotName": "books_backup",
"ttlSeconds": 3600
}'Pin snapshot data against reclamation and obtain a pin ID.
Request fields
dbNamestring- Database name. Operations on collections use default when omitted.
collectionNamestring (required)- Name of the collection.
snapshotNamestring (required)- Name of the collection snapshot.
ttlSecondsinteger- Pin lifetime in seconds.
See HttpClient.pinSnapshotData for the Node.js SDK method.