Hi forum!
What happens when a vzdump is scheduled (let's say, snapshot, live) on a VM that has, in turn, an iSCSI (but would be same question for cifs, NFS, or whatever) target mounted on its own on its filesystem?
To avoid confussion, I mean PVE being completelly unaware of the guest VM doing that usage of network storage mounted on its own.
When backup triggers ... what happens with the mount point folder of the VM?, is the remote data (potentially huge) added to the backup lzo file? (my guess is that vzdump just backs the VM virtual disk at block device level) ... so my answer would be NO, no remote data, just data on virtual disk ... but I'm not sure!
... I was thinkinng to make a lab and just try, but I guess this is the place to ask for this and avoid rediscovering fire.
Thank you very much in advance.
Best regards
What happens when a vzdump is scheduled (let's say, snapshot, live) on a VM that has, in turn, an iSCSI (but would be same question for cifs, NFS, or whatever) target mounted on its own on its filesystem?
To avoid confussion, I mean PVE being completelly unaware of the guest VM doing that usage of network storage mounted on its own.
When backup triggers ... what happens with the mount point folder of the VM?, is the remote data (potentially huge) added to the backup lzo file? (my guess is that vzdump just backs the VM virtual disk at block device level) ... so my answer would be NO, no remote data, just data on virtual disk ... but I'm not sure!
... I was thinkinng to make a lab and just try, but I guess this is the place to ask for this and avoid rediscovering fire.
Thank you very much in advance.
Best regards
