ANy general recommendations for usage of Server 2012 Teaming vs. stand alone multiple nics for data, hearbeat or replication channels? originally teaming was recommended (several years ago) more recently non teamed - any change or recommended best practices for server 2012 and pending new starwind r...

restarting (restart computer) a single node with auto-syncing enabled
it takes less than a day to get everything up (other node images remain online)
I will send server log outside forum

back to earlier question -
What is the auto sychronization method for targets with write-back cache enabled?

It appears to be going thru full sync -
amount of data across replication link and time required to get second node online

these are on the replication link btw the primary and sceondary HA nodes - initiated by the starwind setup - they don't appear in favorites

After Upgrade and restart on secondary is it usual behaviour for iscsi connections to see two on secondary target primary iqn.2008-08.com.starwindsoftware:haip001.itu.xx.xx-hahvT1Partner secondary iqn.2008-08.com.starwindsoftware:hagw001.itu.xx.xx-hahvT1 iqn.2008-08.com.starwindsoftware:hagw001.itu....

Also noticed on restart if auto-synchronization enabled with 10+ targets (replication nic saturated - I still need to do some nic optimization with this) sync much slower than manually doing in groups of 2 It might be a useful feature to permit synchronization priorities (or delay for targets) to mi...

figured that out - extra work if you have 10+ targets ..

It would be a useful feature if this could be toggled from the Starwind management Console for a future revision !

i have ha iscsi target connected to two nodes of cluster as cluster shared volume after performing steps (deleting and recreating targets) the csv comes up with redirected access on the cluster - to get the redirected access off the after disconnecting iscsi targets the favorites for primary and sec...

ok - found updated document for most current version
I also noticed updated TCP / NIC optimazation etc for 2008 r2 (thanks)

after upgrading both nodes how do you enable options for caching and autosync after failures for existing targets?

Is there an upgrade document available for HA deployment?
Peter

are the chap permissons assigned per HAIMAGE not cleared - there appeared to be some persistence of permisions when recreating "HAIMAGE*"

Do you keep a updated public list of issues "bugs" to provide required technical details for implementation, planning / deployment
work arounds ..
P

IF I set chap permissions on HA Targets after creation - is there any documentation .. tech notes? It appears i have two iscsi connection to both target/partner but the replication iscsi link between the two is broken after restarting 1 server .. Can you set chap on HA targets? or to just the server...

the objective for HA to be always ON is noted - the point was if you do need to do "controlled" shutdown there should be some method that won't require full sync on restart - disconnect all connections from HA (shutdown all resources with iscsi connections) both flagged in sync (no changes...

extended power outage required both nodes to be shutdown - not common but does occur.