You cannot backup .img files safely. Neither from StarWind nor from any other target on Earth. Reason is quite simple - we @ target side have no clue about writer application performing I/O on initiator side.
We cannot signal it "flush and hold writes". So .img is not going to be consistent unless image is dismounted @ initiator side.
Yes, there's a lot of development. We do have built-in backup for Hyper-V and VMware backup is coming soon. Also V6 will support +1 async replication so you'll be able to keep extra copy of your content at DR location.
But you'll NEVER be able to produce target backups with third-party software. It's physically not possible.
chop wrote:The virtual thing is all great, but what about backing up .img files and more importantly thin disk allocations? is there any development on backing up snapshots to a unc path? or replicating *.ibv and *.ibvd data to unc or alternative paths?
Cheers
Chris