Even though I have configured Starwind 5.7's log rotation to keep last 30, log files continue to accumulate and can't be deleted manually. When attempted, I receive an error that file is currently open in Starwind. This is occuring on 2 separate Starwind servers, builds 5.7.1721 and 5.7.1733

Any new ETA on a public release that includes a fix for this? We experienced a 2 hour interruption in service today when a single cluster node failure caused an unsuccessful failover of a cluster shared volume. Is support for cluster shared volumes in a Microsoft WIndows 2008 R2 cluster a supported ...

When will this upgrade be available? This problem with persistent reservations seems to dramatically impact StarWind's usefulness in a Microsoft 2008 Cluster.

Thanks...

Lowell

When will a public release containing this fix be available? Would this wait until 5.5? I'm a bit reluctant to install a beta on my production SAN supporting 40 virtual servers and 1500 users.

I have subscribed to the beta program and received no response.

After an upgrade to 5.3, my Hyper-V cluster is having problems moving cluster shared volumes between nodes.

The Starwind log has entries like:

160 PR: * PR-RESERVE Conflict. Reservation key xxxxx. Failed key xxxxx from iqn...

Help?

Lowell