Popis svih snimaka
Dohvatite popis svih snimaka na vašim poslužiteljima.
Parametri upita
Parametar
Tip
Potreban
Opis
server_id
integer
Ne
Filtriranje snimaka prema ID-u poslužitelja
Primjer zahtjeva
curl -X GET "https://admin.vps.org/api/v1/snapshots/?server_id=12345" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Copy
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())
Copy
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);
Copy
Primjer 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"
}
]
}
Kodovi statusa odgovora
200
Popis snimaka uspješno dohvaćen
401
Neovlašteno - Nevažeći ili nedostajući token za autentifikaciju
Izradi snimku
Create a snapshot of a server's current state. Snapshots are point-in-time copies of the entire server.
Zahtjev za parametre tijela
Parametar
Tip
Potreban
Opis
server_id
integer
Da
ID poslužitelja za snimanje
name
string
Da
Naziv snimke (alfanumerički, crtice, podcrte)
description
string
Ne
Neobavezni opis za snimku
Primjer zahtjeva
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"
}'
Copy
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())
Copy
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);
Copy
Primjer 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."
}
Kodovi statusa odgovora
201
Izrada snimke uspješno je pokrenuta
400
Bad Request - Invalid parameters or snapshot limit reached
401
Neovlašteno - Nevažeći ili nedostajući token za autentifikaciju
404
Not Found - Server does not exist
Bilješka: 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.
Vrati iz snimke
Restore a server to the state captured in a snapshot. This will overwrite all current data on the server.
Parametri puta
Parametar
Tip
Potreban
Opis
snapshot_id
integer
Da
Jedinstveni ID snimke
Primjer zahtjeva
curl -X POST "https://admin.vps.org/api/v1/snapshots/801/restore/" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Copy
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())
Copy
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);
Copy
Primjer 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"
}
}
Kodovi statusa odgovora
200
Vraćanje je uspješno pokrenuto
400
Bad Request - Server is not in a valid state for restoration
401
Neovlašteno - Nevažeći ili nedostajući token za autentifikaciju
404
Nije pronađeno - Snimka ne postoji
Upozorenje: 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 snimku
Trajno izbriši snimku. Ovu radnju nije moguće poništiti.
Parametri puta
Parametar
Tip
Potreban
Opis
snapshot_id
integer
Da
Jedinstveni ID snimke
Primjer zahtjeva
curl -X DELETE "https://admin.vps.org/api/v1/snapshots/801/" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Copy
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)
Copy
Kodovi statusa odgovora
204
Snimka uspješno izbrisana
401
Neovlašteno - Nevažeći ili nedostajući token za autentifikaciju
404
Nije pronađeno - Snimka ne postoji
Snapshots vs Backups
Understanding when to use snapshots versus backups:
API za snimke
Svrha: Quick point-in-time recovery
Ubrzati: Faster to create and restore (3-15 min)
Primjer upotrebe: Before risky operations (updates, config changes)
Pohrana: Stored on same infrastructure
Ograničiti: 5 snapshots per server
Najbolje za: Short-term rollback capability
API za sigurnosne kopije
Svrha: Long-term data protection
Ubrzati: Slower to create and restore (varies)
Primjer upotrebe: Regular automated data protection
Pohrana: Separate backup storage
Ograničiti: 10 manual + automatic backups
Najbolje za: Disaster recovery and compliance
Best Practices
Before Updates: Create a snapshot before major system updates
Testing: Use snapshots when testing configuration changes
Combined Strategy: Use both snapshots (short-term) and backups (long-term)
Clean Up: Delete old snapshots after successful updates
Server State: Consider stopping the server before creating critical snapshots