clientapi-pve 2026.5.24

Generated from apidoc.js. NOT an official Proxmox specification. See https://pve.proxmox.com/pve-docs/api-viewer/ for the upstream documentation.
Documentation
/*
 * Proxmox Virtual Environment API
 *
 * Generated from apidoc.js. NOT an official Proxmox specification. See https://pve.proxmox.com/pve-docs/api-viewer/ for the upstream documentation.
 *
 * The version of the OpenAPI document: 9.x
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

/// ClusterBackupGetBackupResponseDataInnerFleecing : Options for backup fleecing (VM only).
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct ClusterBackupGetBackupResponseDataInnerFleecing {

    /// Enable backup fleecing. Cache backup data from blocks where new guest writes happen on specified storage instead of copying them directly to the backup target. This can help guest IO performance and even prevent hangs, at the cost of requiring more storage space.
    #[serde(rename = "enabled", skip_serializing_if = "Option::is_none")]
    pub enabled: Option<models::PveBoolean>,

    /// Use this storage to storage fleecing images. For efficient space usage, it's best to use a local storage that supports discard and either thin provisioning or sparse files.
    #[serde(rename = "storage", skip_serializing_if = "Option::is_none")]
    pub storage: Option<String>,


}

impl ClusterBackupGetBackupResponseDataInnerFleecing {
    /// Options for backup fleecing (VM only).
    pub fn new() -> ClusterBackupGetBackupResponseDataInnerFleecing {
        ClusterBackupGetBackupResponseDataInnerFleecing {
            
            enabled: None,
            
            storage: None,
            
        }
    }
}