Seznam vseh posnetkov
Pridobite seznam vseh posnetkov na vaših strežnikih.
Parametri poizvedbe
Parameter
Vrsta
Zahtevano
Opis
server_id
integer
Ne
Filtriranje posnetkov po ID-ju strežnika
Primer zahteve
curl -X GET "https://admin.vps.org/api/v1/snapshots/?server_id=12345" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Kopiraj
import requests
url = "https://admin.vps.org/api/v1/snapshots/"
headers = {
"Authorization": "Bearer YOUR_API_TOKEN",
"Content-Type": "application/json"
}
params = {"server_id": 12345}
response = requests.get(url, headers=headers, params=params)
print(response.json())
Kopiraj
const response = await fetch('https://admin.vps.org/api/v1/snapshots/?server_id=12345', {
method: 'GET',
headers: {
'Authorization': 'Bearer YOUR_API_TOKEN',
'Content-Type': 'application/json'
}
});
const snapshots = await response.json();
console.log(snapshots);
Kopiraj
Primer odgovora
{
"count": 2,
"results": [
{
"id": 801,
"server": {
"id": 12345,
"name": "web-server-01"
},
"name": "pre-migration-snapshot",
"status": "completed",
"size_mb": 5120,
"created_at": "2025-01-15T18:30:00Z",
"description": "Before major migration"
},
{
"id": 798,
"server": {
"id": 12345,
"name": "web-server-01"
},
"name": "weekly-snapshot-2025-01-08",
"status": "completed",
"size_mb": 4856,
"created_at": "2025-01-08T12:00:00Z",
"description": "Weekly snapshot"
}
]
}
Kode stanja odgovora
200
Seznam posnetkov je bil uspešno pridobljen
401
Nepooblaščeno - neveljaven ali manjkajoči žeton za preverjanje pristnosti
Ustvari posnetek
Ustvari posnetek trenutnega stanja strežnika. Posnetki so točne kopije celotnega strežnika.
Zahtevajte parametre telesa
Parameter
Vrsta
Zahtevano
Opis
server_id
integer
Da
ID strežnika za posnetek
name
string
Da
Ime za posnetek (alfanumerično, vezaji, podčrtaji)
description
string
Ne
Neobvezen opis posnetka
Primer zahteve
curl -X POST "https://admin.vps.org/api/v1/snapshots/" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"server_id": 12345,
"name": "before-update-snapshot",
"description": "Snapshot before system update"
}'
Kopiraj
import requests
url = "https://admin.vps.org/api/v1/snapshots/"
headers = {
"Authorization": "Bearer YOUR_API_TOKEN",
"Content-Type": "application/json"
}
data = {
"server_id": 12345,
"name": "before-update-snapshot",
"description": "Snapshot before system update"
}
response = requests.post(url, headers=headers, json=data)
print(response.json())
Kopiraj
const response = await fetch('https://admin.vps.org/api/v1/snapshots/', {
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_API_TOKEN',
'Content-Type': 'application/json'
},
body: JSON.stringify({
server_id: 12345,
name: 'before-update-snapshot',
description: 'Snapshot before system update'
})
});
const snapshot = await response.json();
console.log(snapshot);
Kopiraj
Primer odgovora
{
"id": 802,
"server": {
"id": 12345,
"name": "web-server-01"
},
"name": "before-update-snapshot",
"status": "in_progress",
"size_mb": null,
"created_at": "2025-01-16T16:15:00Z",
"description": "Snapshot before system update",
"message": "Snapshot is being created. This may take 3-10 minutes depending on server size."
}
Kode stanja odgovora
201
Ustvarjanje posnetka se je uspešno začelo
400
Bad Request - Invalid parameters or snapshot limit reached
401
Nepooblaščeno - neveljaven ali manjkajoči žeton za preverjanje pristnosti
404
Not Found - Server does not exist
Opomba: You can have a maximum of 5 snapshots per server. Creating a snapshot while the server is running may result in filesystem inconsistencies. For best results, stop the server before creating a snapshot.
Obnovi iz posnetka
Obnovi strežnik v stanje, ki ga je posnelo v posnetku. To bo prepisalo vse trenutne podatke na strežniku.
Parametri poti
Parameter
Vrsta
Zahtevano
Opis
snapshot_id
integer
Da
Enolični ID posnetka
Primer zahteve
curl -X POST "https://admin.vps.org/api/v1/snapshots/801/restore/" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Kopiraj
import requests
snapshot_id = 801
url = f"https://admin.vps.org/api/v1/snapshots/{snapshot_id}/restore/"
headers = {
"Authorization": "Bearer YOUR_API_TOKEN",
"Content-Type": "application/json"
}
response = requests.post(url, headers=headers)
print(response.json())
Kopiraj
const snapshotId = 801;
const response = await fetch(`https://admin.vps.org/api/v1/snapshots/${snapshotId}/restore/`, {
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_API_TOKEN',
'Content-Type': 'application/json'
}
});
const result = await response.json();
console.log(result);
Kopiraj
Primer odgovora
{
"status": "success",
"message": "Server is being restored from snapshot. This may take 5-15 minutes.",
"snapshot": {
"id": 801,
"name": "pre-migration-snapshot",
"created_at": "2025-01-15T18:30:00Z"
},
"server": {
"id": 12345,
"name": "web-server-01",
"status": "restoring"
}
}
Kode stanja odgovora
200
Obnovitev se je uspešno začela
400
Bad Request - Server is not in a valid state for restoration
401
Nepooblaščeno - neveljaven ali manjkajoči žeton za preverjanje pristnosti
404
Ni najdeno - posnetek ne obstaja
Opozorilo: Restoring from a snapshot will overwrite all current data on the server. This action cannot be undone. The server will be automatically stopped before restoration begins.
Izbriši posnetek
Trajno izbriši posnetek. Tega dejanja ni mogoče razveljaviti.
Parametri poti
Parameter
Vrsta
Zahtevano
Opis
snapshot_id
integer
Da
Enolični ID posnetka
Primer zahteve
curl -X DELETE "https://admin.vps.org/api/v1/snapshots/801/" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Kopiraj
import requests
snapshot_id = 801
url = f"https://admin.vps.org/api/v1/snapshots/{snapshot_id}/"
headers = {
"Authorization": "Bearer YOUR_API_TOKEN",
"Content-Type": "application/json"
}
response = requests.delete(url, headers=headers)
print(response.status_code)
Kopiraj
Kode stanja odgovora
204
Posnetek je bil uspešno izbrisan
401
Nepooblaščeno - neveljaven ali manjkajoči žeton za preverjanje pristnosti
404
Ni najdeno - posnetek ne obstaja
Snapshots vs Backups
Razumevanje, kdaj uporabljati posnetke v primerjavi z varnostnimi kopijami:
API za posnetke
Namen: Quick point-in-time recovery
Hitrost: Faster to create and restore (3-15 min)
Primer uporabe: Before risky operations (updates, config changes)
Shranjevanje: Stored on same infrastructure
Omejitev: 5 snapshots per server
Najboljše za: Short-term rollback capability
API za varnostne kopije
Namen: Long-term data protection
Hitrost: Slower to create and restore (varies)
Primer uporabe: Regular automated data protection
Shranjevanje: Separate backup storage
Omejitev: 10 manual + automatic backups
Najboljše za: Disaster recovery and compliance
Najboljše prakse
Pred posodobitvami: Ustvari posnetek pred večjimi posodobitvami sistema
Preskušanje: Uporabi posnetke pri preizkušanju sprememb nastavitve
Kombinirana strategija: Uporabi posnetke (kratkoročno) in varnostne kopije (dolgoročno)
Očisti: Zbriši stare posnetke po uspešnih posodobitvah
Stanje strežnika: Razmislite o ustavitvi strežnika pred ustvarjanjem kritičnih posnetkov