StarWind Software

I have a similar issue to http://www.starwindsoftware.com/forums/ ... f=5&t=3921
I currently have a Starwind v6 cluster and need to set up a Read Only target for use by a Veeam Backup proxy.

The proxy will be connected on separate interfaces from the main SAN to one of the two nodes in the cluster.

Support said this isn't doable-- that is, setting up a "read only" target to an existing device that has a read-write target already assigned to it... with v6 anyway

I've since set up a dev lab with v8 (a single node) and seen that I can set up a target image file as "read only" and seen that it appears possible, at least in a dev environment.

The previous thread re: HyperV said data corruption wasn't an issue for them, but it is obviously a concern for me.

1) Upgrade to V8

2) Do what support says you to do to turn R/O mode on. Technically we don't see why VEEAM should even in theory damage your LUN (that's out of our understanding) but YES you can make LUN Read-Only if it makes you happy

atlhivemind wrote:I have a similar issue to http://www.starwindsoftware.com/forums/ ... f=5&t=3921
I currently have a Starwind v6 cluster and need to set up a Read Only target for use by a Veeam Backup proxy.

The proxy will be connected on separate interfaces from the main SAN to one of the two nodes in the cluster.

Support said this isn't doable-- that is, setting up a "read only" target to an existing device that has a read-write target already assigned to it... with v6 anyway

I've since set up a dev lab with v8 (a single node) and seen that I can set up a target image file as "read only" and seen that it appears possible, at least in a dev environment.

The previous thread re: HyperV said data corruption wasn't an issue for them, but it is obviously a concern for me.