Feature Request - Backup from Storage Snapshots only

[Crashinit]

Afternoon,

I would like to put in a feature request for the following.

Scenario:
Production Nimble at Site A has a Volume Collection that takes an Hourly Snapshot of some volumes and Replicate to it's downstream partner at Site B.
There is no Application Synchronization taking place (i.e. Microsoft VSS, Generic or VMWare snapshots), which means that this is only a crash consistent snapshot and not Application Aware.
The reason behind this is that the VM's that are being replicated offsite is highly sensitive to any latency and the volumes in question is 10TB with a VM around 6-8TB in size.

When Veeam initiates a backup of the specified VM, it causes vmware to take a VMWare snap of the VM, tells nimble to take a snapshot and then VMWare deletes the Snapshot.
Once this is done, Veeam then initiates a storage snapshot transfer of the Volume to Site B where the backup is taken from the Replica Storage Snapshot, which is what we want.

Feature Request:
Due to the size of the VM, the VM is sometimes stunned and causes the workload on the VM to crash which is business impacting.
There is no need for the VM OS to be recoverable, but the content on the Data Disk needs to be (continually growing audio content).

What would be nice is for veeam to be able to use the Nimble snapshot feature only only (which it already does with it's Volume Collection) and then replicate to the downstream nimble and backup the VM this way.
This way, VMware is not called to take a VM snapshot beforehand which is causing the VM stun.
We are only interested in the Data on the disk, not a recoverable Bootable VM.

Thanks.

Craig

[HannesK]

Hello,

What would be nice is for veeam to be able to use the Nimble snapshot feature only only (which it already does with it's Volume Collection) and then replicate to the downstream nimble and backup the VM this way.

If I understood you correctly, then that feature is already available today. https://helpcenter.veeam.com/docs/backu ... ml?ver=100

The information is a little bit hidden in point 9.

The requirement is that no VM in same job has VMDKs on the same storage volume (where the storage snapshot is created). The result is like this screenshot, where you can see, that no VMware snapshot is created



Best regards,
Hannes

[foggy]

But you wouldn't be able to backup from these snapshots, if that is what you're requesting. VSS freeze-only processing is available in snapshot-only jobs and not in backup from storage snapshot jobs.