How does 2012R2 CSV 2.0 handle backups?
hello,
just wondering how backups should work failover cluster running on 2012r2. have read direct i/o should used in 2012r2 when running virtual machine backups instead of redirected access in 2008. expecting when backup taken vm backed access data local iscsi connection no matter node csv owned by.
what seeing if vm , csv on different nodes disk access run on management network connection csv iscsi owner vm owner , sent backup server. causes reduced backup speed. csv stays in online mode , running get-clustersharedvolumestate shows volumes in direct access still. have no 3<sup>rd</sup> party hardware vss providers , happening on 2 separate clusters.
what trying figure out how supposed work or not? able me this? have spoken symantec microsoft issue have not confirm expected or not.
yes, correct, direct i/o has been enabled since 2012.
image scenario: when add data vm, csv i/o synchronization direct, that’s say, vm access storage directly.
however, regarding running vm backups, contain metadata update, synchronization done on 1 node (the coordinator node), , metadata changes nodes routed through coordinator node. below screenshot , document reference.
introduction cluster shared volumes , csv architecture:
what’s more, if consider cluster backup speed slow , needs optimized, tuning regarding cluster network might useful you, please refer below website.
configuring windows failover cluster networks
other csv related knowledge reference.
cluster shared volume (csv) inside out
http://blogs.msdn.com/b/clustering/archive/2013/12/02/10473247.aspx
best regards,
please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com
Windows Server > Hyper-V
Comments
Post a Comment