How to backup running .img (iSCSI target) file?

[scerazy]

I have a target file which has pretty static data (Vault), accessed very rarely.
But it is connected to live system (in case user wants something from Vault)

How can I backup this .img file?

There was some discussion here http://www.starwindsoftware.com/forums/starwind-f5/clarification-backup-img-files-t1826.html, but it stopped long ago

Seb

[Max (staff)]

Hi Seb,
The're is no way to back up a running img file using any 3rd party tool.
However, in the upcoming release we're adding this feature to our engine. You will be able to set an offsite backup destination and replicate your data on a scheduled basis.
Currently V5.8 is available on our beta testing forum.

[chop]

Hello,

is there any news on this? we are running thin prov disks are still looking for a backup solution for running drives?

Chris

[anton (staff)]

Yes, there are a lot of news. You can use StarWind built-in VM backup to backup / restore individual machines and you can also use built-in synchronous replication (async one coming soon) to put second copy on location you want.

[chop]

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

[anton (staff)]

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.

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