1) No, anything we do is file system agnostic as we sit @ block level (below file system) and basically don't care much about what's on top of us.
Could you please explicitly point where "NTFS only" was referenced?
2) See 1)
3) With synchronous mirror two (or more) nodes act as a single entity so if one node fails - users don't express any downtime or service interruption. With
asynchronous mode remote node acts as a "final resort", disaster recovery location. No automatic and transparent failover happens BUT you still have last
copy of your data to be used as a backup (or back seeding to main site). Sync mode is for high-perormance LANs and async mode is intended to be used with WANs.
4) and 5) See 3) Everything is pretty much the same.
BPVMT wrote:I had thought I read in some Starwind documentation that Asynchronous Mode was intended only for NTFS, as of a few starwind versions ago.
- Is that still the case?
- What versions of NTFS are supported?
- What are the benefits/drawbacks of using this mode?
- What is the benefit or drawback of using Aysnchromous mode with VMFS (VMWare's Proprietary File System) and it's various versions?
- What is the benefit or drawback of using Aysnchromous mode with REFS (The new MS File system based off NTFS) ?
