ASA 5550 High Availability Situation

We have a couple of 5550's setup as an active/passive HA pair.  Recently one of the firewalls (standby) had a hardware issue and needed to be replaced.  Would it be easier/better to just restore the backup config from the defective appliance or should we just use the HA wizard in ASDM or cli to configure the new standby firewall?
Thanks,
PTH

Just replace the firewall and put in the failover commands then plug in the failover interface on each ASA and you will be good to go. The standby will download the active configuration.

Similar Messages

  • ASA 5520 High Availability

    I have two ASA 5520s.  One has an IDS card and one doesn't. This makes the high availability wizard fail.  Can I manually setup the high availability.  I don't really need two ASA-SSM-20s.  I just want to have one ASA in Standby mode.  Is this possible.  Anybody have a configuration similar to this?
    Thanks,
    Alex Pfeil                  

    Hi,
    Let me first say that I have not configure a Failover pair where the units dont have matching hardware. So I kind of wonder even if the ASA accepts the configurations, will the failover act normally.
    Usually if I configure basic configurations for some ASA Failover pair I first configure all the basic configurations on the ASA and make sure that each interface on the ASA has the "ip address x.x.x.1 255.255.255.0 standby x.x.x.2" configuration under the interfaces
    I then configure the existing ASA with a basic Failover configuration such as
    failover
    failover replication http
    failover lan unit primary
    failover lan interface failover Management0/0
    failover key
    failover link failover Management0/0
    failover interface ip failover 255.255.255.0 standby
    I then prepare a blank ASA and finally configure its Failover too
    failover
    failover replication http
    failover lan unit secondary
    failover lan interface failover Management0/0
    failover key
    failover link failover Management0/0
    failover interface ip failover 255.255.255.0 standby
    I will then attach the Secondary unit to the network and finally attach the Failover link between the ASAs and let the Primary unit replicate all the configurations to the Secondary unit.
    Naturally this is something that would probably be best done during a separate scheduled maintanance break along with configuration backups etc just to be on the safe side.
    - Jouni

  • ASA 5520: Configuring Active/Standby High Availability

    Hi,
    I am new to Cisco firewalls. We are moving from a different vendor to Cisco ASA 5520s.
    I have two ASA 5520s running ASA 8.2(5). I am managing them with ASDM 6.4(5).
    I am trying to setup Active/Standby using the High Availability Wizard. I have interfaces on each device setup with just an IP address and subnet mask. Primary is 10.1.70.1/24 and secondary is 10.1.70.2/24. The interfaces are connected to a switch and these interfaces are the only nodes on this switch. When I run the Wizard on the primary, configure for Active/Standby, enter the peer IP of 10.1.70.2 and I get an error message saying that the peer test failed, followed by an error saying ASDM is temporarily unable to connect to the firewall.
    I tried this using a crossover cable to connect the interfaces directly with the same result.
    Any ideas?
    Thanks.
    Dan

    The command Varun is right.
    Since you want to know a little bit more about this stuff, here goes a bit. Every interface will have a secondary IP and a Primary IP where the Active/Standby pair will exchange hello packes. If the hellos are not heard from mate, the the unit is delcare failed.
    In case the primary is the one that gets an interface down, it will failover to the other unit, if it is the standby that has the problem, the active unit will declare the other Unit "standby failed). You will know that everything is alright when you do a show failover and the standby pair shows "Standby Ready".
    For configuring it, just put a secondary IP on every interface to be monitored (If by any chance you dont have an available secondary IP for one of the interfaces you can avoid monitoring the given interface using the command no "monitor-interface nameif" where the nameif is the name of the interface without the secondary IP.
    Then put the commands for failover and stateful link, the stateful link will copy the connections table (among other things) to avoid downtime while passing from One unit to another, This link should have at least the same speed as the regular data interfaces.
    You can configure the failover link and the stateful link in just one interface, by just using the same name for the link, remember that this link will have a totally sepparate subnet from the ones already used in firewall.
    This is the configuration
    failover lan unit primary
    failover lan interface failover gig0/3
    failover link failover gig0/3
    failover interface ip failover 10.1.0.1 255.255.255.0 standby 10.1.0.2
    failover lan unit secondary
    failover lan interface failover gig0/3
    failover link failover gig0/3
    failover interface ip failover 10.1.0.1 255.255.255.0 standby 10.1.0.2
    Make sure that you can ping each other secondary/primary IP and then put the command
    failover first on the primary and then on the secondary.
    That would fine.
    Let me know if you have further doubts.
    Link for reference
    http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008080dfa7.shtml
    Mike

  • Best practice for High availability design, HSRP

    Hi,
    I am planning to create High Availability for LAN to WAN connectivity.
    But I want to know your opinion about the best way how to do this. I googled for a solution/best way how to do this, but I didn't found in my opinion right answer.
    The situation:
    I have 2 3945E Routers and 2 3560 switches. The design that I am planning to implement is below.
    The main goal is to have redundant connection, whatever one of the devices will fail. For example, if the R1 will fail, R2 should become active, if the SW1 will fail, the SW2 will take care about reachability and vice versa. The router 1 should be preferred always, if the link to ISP isn't down, because of greater bandwidth. So why am I drown 2 connections to 2 separate switches. If the SW1 will fail, I will still have a connection to WAN using R1 router.
    The Router interface should be configured with sub interfaces (preferred over secondary IP address of interface), because more than 10 subnets will be assigned to the LAN segment. The routers have 4 Gi ports.
    HSRP must be enabled on LAN side, because PC's on LAN must have redundant def. getaway.
    So, the question is - what is the best and preferred way to do this?
    In my opinion, I should use BVI and combine R1 routers 2 interfaces in to logical one and do the same for the R2.
    Next, turn the router in to L3 switch using IRB and then configure HSRP.
    What would be your preferred way to do this?

    Hi Audrius,
    I would suggest you to go with HSRP. GLBP you will use where you want load balance.
    I think the connectivity between your Routers (3945) and switches (3560) is gigabit connection which is high speed. So keep one physical link from your switches to each router and do HSRP on those router physical interfaces.
    In this way you will have high availability like if R1 fails then R2 will take over.
    Regarding the config see the below which I have for one of my Customer DC.
    ACTIVE:
    track 1 interface GigabitEthernet0/0 line-protocol
    track 2 interface GigabitEthernet0/0 line-protocol
    interface GigabitEthernet0/1
    ip address 10.10.10.12 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    duplex full
    speed 100
    standby use-bia scope interface
    standby 0 ip 10.10.10.10
    standby 0 priority 110
    standby 0 preempt
    standby 0 authentication peter2mo
    standby 0 track 1 decrement 30
    standby 0 track 2 decrement 30
    STANDBY:
    track 1 interface GigabitEthernet0/0 line-protocol
    interface GigabitEthernet0/1
    ip address 10.10.10.11 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    duplex full
    speed 100
    standby use-bia scope interface
    standby 0 ip 10.10.10.10
    standby 0 priority 90
    standby 0 authentication peter2mo
    standby 0 track 1 decrement 30
    Please rate the helpfull posts.
    Regards,
    Naidu.

  • High Availability Test Cases for ECC6.0, PI 7.0, BI 7.0???

    Dear All
    I am in a pretty difficult situation here. I have to write test cases for the components in the High Availability environment. We are running AIX 5L with HACMP/XD clusters ACTIVE/PASSIVE setting. The following components are in the landscape, ECC6.0, PI 7.0 BI 7.0 cFolders 4.0 Portal 7.0 SLD 2004s and Solman 4.0. I have to write test cases for the above components especially ECC, PI BI and cFolders in the HA environment as to
       1.<b>WHAT WILL BE THE EFFECT ON OTHER COMPONENTS IF ECC</b> <b>FAILOVER  and so on for PI and BI</b>,
       2. How do I check the consistency of the system after a failover, since the time for a failover will be anywhere between 3 - 4 mins.
    Can anyone pls give me a 5 or 6  checks like
    Checking RFC connections
    ABAP dumps
    Consistency check (txn: SICK)   and so on
    In the test cases I have to make sure that after a failover the system is up and ready to perform the activities that it was able to before the Failover......
    Will appreciate any suggestions and will definitely reward points for any helpful answers....Thanks in advance.

    Hi Shailesh,
    If you want you can activate SCM_SNC_GEN_1 depending upon business needs or configuration.
    As per my understanding there is no need to activate any business function but if you need additional feature of SNC to be used then refer below help link for more details:
    http://help.sap.com/saphelp_SNC700_ehp01/helpdata/en/a2/6d67d9b60149cb887acf72ae0b90ac/frameset.htm
    In ECC you are going for EPh5 which means no need to activate any additional business function(Normally SNC needs EPh4 only for some the latest feature to be use like in workorder collaboration ManufacturingWorkOrderInformation and ManufacturingWorkOrderProductionProgressNotification XML are used if ECC is with EPh4)
    Regards,
    Nikhil

  • Transaction Log Truncate not working on Sql Server 2012 High Availability Groups

    Hi Everyone
    Firstly I have tried to search the forum for similar issues but can't seem to find any that match our situation.
    We have a SQL Server 2012 High Availability Group with 2 Nodes
    Node 1 = Primary
    Node 2 = Secondary
    Backup Schedule as follows
    Full Database Backup @ 00:00
    Transaction Log Backup every 30 minutes from 00:30:00 till 23:59:59.
    These backups are run by Maintenance Jobs, but we have also tried doing direct backups in SSMS using Backup Database and Backup Log commands.
    Before we configured the High Availability group the transaction log backups worked fine.
    After we configured the High Availability group we performed a Full Backup and the T-Log schedule did the T-Log backup. The 1st T-log backup truncated the log (Used space Decreased) as expected.
    However subsequent T-Log backups do not truncate the T-Log.
    This happens both in our acceptance and Live environments. This also happens when running the backups as a Backup operator and sysadmin, this does not seem to be a permissions issue at all.
    We have tried running the Backup on the Primary and Secondary Replica.
    What about High Availability groups could stop Transaction Log Backups from not truncating the log?
    Thanks
    James

    Hi Sean
    Thank you for your reply, please see the output of the sys.databases query below, and some others which you may find usefull.
    Query: select database_id,recovery_model_desc, log_reuse_wait, log_reuse_wait_desc from sys.databases
    where database_id = 5
    Result: database_id    recovery_model_desc    log_reuse_wait    log_reuse_wait_desc
                     5                               
    FULL                             0                           
    NOTHING
    I also ran the following
    select database_id, truncation_lsn, last_received_lsn, last_commit_lsn, last_hardened_lsn, last_redone_lsn,*
    from sys.dm_hadr_database_replica_states
    go
    database_id
    truncation_lsn
    last_received_lsn
    last_commit_lsn
    last_hardened_lsn
    last_redone_lsn
    database_id
    group_id
    replica_id
    group_database_id
    is_local
    synchronization_state
    synchronization_state_desc
    is_commit_participant
    synchronization_health
    synchronization_health_desc
    database_state
    database_state_desc
    is_suspended
    suspend_reason
    suspend_reason_desc
    recovery_lsn
    truncation_lsn
    last_sent_lsn
    last_sent_time
    last_received_lsn
    last_received_time
    last_hardened_lsn
    last_hardened_time
    last_redone_lsn
    last_redone_time
    log_send_queue_size
    log_send_rate
    redo_queue_size
    redo_rate
    filestream_send_rate
    end_of_log_lsn
    last_commit_lsn
    last_commit_time
    low_water_mark_for_ghosts
    5
    1231833000417170000000
    1231833000418880000000
    1231833000418880000000
    1231833000418890000000
    1231833000418880000000
    5
    1391A499-3F9A-47D5-BCE0-70BC204E2A5B
    7E8BFC2E-363F-4C48-86F0-C276D3E0C8D9
    0581E17A-6B7B-4B8F-9288-BF765BFBCE77
    0
    2
    SYNCHRONIZED
    1
    2
    HEALTHY
    NULL
    NULL
    0
    NULL
    NULL
    4294967295429490000000000
    1231833000417170000000
    1
    41863
    1231833000418880000000
    41863
    1231833000418890000000
    41863
    1231833000418880000000
    41863
    0
    25541
    0
    84404
    75304
    1231833000418880000000
    1231833000418880000000
    41863
    441019861
    5
    1231833000417170000000
    NULL
    1231833000418880000000
    1231833000418890000000
    NULL
    5
    1391A499-3F9A-47D5-BCE0-70BC204E2A5B
    83B9F00E-D63F-4AC0-98FC-35E48FFA2C6F
    0581E17A-6B7B-4B8F-9288-BF765BFBCE77
    1
    2
    SYNCHRONIZED
    1
    2
    HEALTHY
    0
    ONLINE
    0
    NULL
    NULL
    4294967295429490000000000
    1231833000417170000000
    NULL
    NULL
    NULL
    NULL
    1231833000418890000000
    NULL
    NULL
    NULL
    NULL
    NULL
    NULL
    NULL
    NULL
    1231833000418880000000
    1231833000418880000000
    41863
    441019861
    And
    dbcc loginfo
    go
    RecoveryUnitId
    FileId
    FileSize
    StartOffset
    FSeqNo
    Status
    Parity
    CreateLSN
    0
    2
    458752
    8192
    1231828
    0
    128
    0
    0
    2
    458752
    466944
    1231829
    0
    128
    0
    0
    2
    458752
    925696
    1231830
    0
    128
    0
    0
    2
    712704
    1384448
    1231831
    0
    128
    0
    0
    2
    19398656
    2097152
    1231832
    0
    128
    1229654000000040000000
    0
    2
    10199171072
    21495808
    1231833
    2
    128
    1229656000000010000000
    0
    2
    10199171072
    10220666880
    0
    0
    64
    1229656000000010000000
    0
    2
    10199171072
    20419837952
    1231827
    0
    64
    1229656000000010000000
    0
    2
    10199171072
    30619009024
    0
    0
    128
    1229656000000010000000
    0
    2
    10199171072
    40818180096
    0
    0
    128
    1229656000000010000000
    0
    2
    10199171072
    51017351168
    0
    0
    128
    1229656000000010000000
    0
    2
    10199171072
    61216522240
    0
    0
    128
    1229656000000010000000
    0
    2
    10199171072
    71415693312
    0
    0
    128
    1229656000000010000000
    0
    2
    10199171072
    81614864384
    0
    0
    128
    1229656000000010000000
    0
    2
    536870912
    91814035456
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    92350906368
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    92887777280
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    93424648192
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    93961519104
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    94498390016
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    95035260928
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    95572131840
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    96109002752
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    96645873664
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    97182744576
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    97719615488
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    98256486400
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    98793357312
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    99330228224
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    99867099136
    0
    0
    64
    1229989001661260000000
    0
    2
    536870912
    100403970048
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    100940840960
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    101477711872
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    102014582784
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    102551453696
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    103088324608
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    103625195520
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    104162066432
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    104698937344
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    105235808256
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    105772679168
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    106309550080
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    106846420992
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    107383291904
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    107920162816
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    108457033728
    0
    0
    64
    1229995000058520000000
    0
    2
    536870912
    108993904640
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    109530775552
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    110067646464
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    110604517376
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    111141388288
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    111678259200
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    112215130112
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    112752001024
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    113288871936
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    113825742848
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    114362613760
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    114899484672
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    115436355584
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    115973226496
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    116510097408
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    117046968320
    0
    0
    64
    1230004000028400000000
    0
    2
    536870912
    117583839232
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    118120710144
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    118657581056
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    119194451968
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    119731322880
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    120268193792
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    120805064704
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    121341935616
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    121878806528
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    122415677440
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    122952548352
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    123489419264
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    124026290176
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    124563161088
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    125100032000
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    125636902912
    0
    0
    64
    1230012000103140000000
    0
    2
    536870912
    126173773824
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    126710644736
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    127247515648
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    127784386560
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    128321257472
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    128858128384
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    129394999296
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    129931870208
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    130468741120
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    131005612032
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    131542482944
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    132079353856
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    132616224768
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    133153095680
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    133689966592
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    134226837504
    0
    0
    128
    1230338000973820000000
    0
    2
    536870912
    134763708416
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    135300579328
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    135837450240
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    136374321152
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    136911192064
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    137448062976
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    137984933888
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    138521804800
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    139058675712
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    139595546624
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    140132417536
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    140669288448
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    141206159360
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    141743030272
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    142279901184
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    142816772096
    0
    0
    128
    1230338001901440000000
    0
    2
    536870912
    143353643008
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    143890513920
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    144427384832
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    144964255744
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    145501126656
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    146037997568
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    146574868480
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    147111739392
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    147648610304
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    148185481216
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    148722352128
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    149259223040
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    149796093952
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    150332964864
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    150869835776
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    151406706688
    0
    0
    128
    1230346000103040000000
    0
    2
    536870912
    151943577600
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    152480448512
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    153017319424
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    153554190336
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    154091061248
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    154627932160
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    155164803072
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    155701673984
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    156238544896
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    156775415808
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    157312286720
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    157849157632
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    158386028544
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    158922899456
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    159459770368
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    159996641280
    0
    0
    128
    1230355000086930000000
    0
    2
    536870912
    160533512192
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    161070383104
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    161607254016
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    162144124928
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    162680995840
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    163217866752
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    163754737664
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    164291608576
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    164828479488
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    165365350400
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    165902221312
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    166439092224
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    166975963136
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    167512834048
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    168049704960
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    168586575872
    0
    0
    128
    1230364000070870000000
    0
    2
    536870912
    169123446784
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    169660317696
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    170197188608
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    170734059520
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    171270930432
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    171807801344
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    172344672256
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    172881543168
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    173418414080
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    173955284992
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    174492155904
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    175029026816
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    175565897728
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    176102768640
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    176639639552
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    177176510464
    0
    0
    128
    1230373000054750000000
    0
    2
    536870912
    177713381376
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    178250252288
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    178787123200
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    179323994112
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    179860865024
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    180397735936
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    180934606848
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    181471477760
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    182008348672
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    182545219584
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    183082090496
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    183618961408
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    184155832320
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    184692703232
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    185229574144
    0
    0
    128
    1230382000038660000000
    0
    2
    536870912
    185766445056
    0
    0
    128
    1230382000038660000000
    The create LSN column seems to have been truncated so here is is again, sorry for the bulky reply.
    CreateLSN
    0
    0
    0
    0
    1229654000000041600001
    1229656000000012000001
    1229656000000012000001
    1229656000000012000001
    1229656000000012000001
    1229656000000012000001
    1229656000000012000001
    1229656000000012000001
    1229656000000012000001
    1229656000000012000001
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229989001661260800316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1229995000058525600316
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230004000028405600295
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230012000103148800147
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338000973824800555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230338001901449600555
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230346000103044000554
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230355000086934400510
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230364000070872800554
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230373000054757600431
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    1230382000038664800234
    Thanks
    James

  • WebLogic Server clusters not high available!!

              I'm working with WebLogic Server 6.0.
              I try to connect to cluster using explicit IP addresses.
              For this case,first ,I cluster server A,B and C ,then client try to look up home
              interface at server A.
              After server A return home reference ,client creates EJB object and calls method
              using that reference .
              If server A fail, it still working with others server ,B and C.
              But if new client try to find home reference at server A ,he can't.
              This situation means that WebLogic Server cluster is not high availability or
              I did something wrong with configuration?
              And if I missed something ,how can I fix it?
              Thanks for your attention.
              

    Hi King,
              If you look up at a non-existent IP/port, then it will not respond. That is
              expected behavior.
              You should not be using an explicit IP like that. At least use DNS round
              robin.
              Peace,
              Cameron Purdy
              Tangosol Inc.
              Tangosol Coherence: Clustered Coherent Cache for J2EE
              Information at http://www.tangosol.com/
              "KING TEAM" <[email protected]> wrote in message
              news:3c449200$[email protected]..
              >
              > I'm working with WebLogic Server 6.0.
              > I try to connect to cluster using explicit IP addresses.
              >
              > For this case,first ,I cluster server A,B and C ,then client try to look
              up home
              > interface at server A.
              >
              > After server A return home reference ,client creates EJB object and calls
              method
              > using that reference .
              >
              > If server A fail, it still working with others server ,B and C.
              >
              > But if new client try to find home reference at server A ,he can't.
              >
              > This situation means that WebLogic Server cluster is not high availability
              or
              > I did something wrong with configuration?
              >
              > And if I missed something ,how can I fix it?
              >
              > Thanks for your attention.
              >
              >
              

  • Multi Site SQL High Availability group

    Hi,
    We have our primary Data Centre where we have 2 MS SQL 2012 Enterprise Servers and 2 SharePoint 2013 Enterprise servers.
    We have SQL High Availability group implemented on our primary Site (Site A)
    Site A has subnet of 192.168.0.0.
    We recently added a new DR Site (Site B). Site B we have MS SQL 2012 Enterprise Servers.  Site B have a subnet of
    172.1.1.0
    Both sites are connected via a VPN Tunnel. MS SQL 2012 Enterprise Server on Site B has been added in have SQL High Availability
    group of Site A.
    SQL High Availability group have 2 IPs 192.168.0.32 and 172.1.1.32. SQL Listener have 2 IPs 192.168.0.33 and 172.1.1.33
    We want to make sure that if Site A completely down then Site B work as an active Site. But when Site A down we are unable
    to ping High Availability group and Site B is unable to work as active site. SQL and SharePoint services are completely down.
    Site A has AD(Primary Domain  Controller) and Site B has ADC(Additional Domain Controller).
     Site A has witness server.
    We are using Server 2012 Data Centre
    Please suggest.
    Farooq

    SharePoint is not the same as any other applications. The DR site has to be a completely different farm from your production. This means that the SharePoint_AdminContent and config databases on both farms are different and should not be included in the Availability
    Group (they do not support asynchronous Availability Group.) Only content databases and other SharePoint databases supported in an Availability Group should be included as per this
    TechNet article. Have a look at this
    blog post for your networking configuration.
    The reason your Windows cluster service goes down in the DR data center when the when your primary data center goes down is because the cluster has no majority votes. You have 4 available votes in your cluster - 3 in the primary data center in the form of
    the 2 Availability Group replicas and the witness server and 1 in the DR data center. If the Windows cluster does not have majority of votes, it automatically shuts down the cluster. This is by design. That is why when this situation happens, you need to force
    the cluster to start without a quorum as described in
    this article (Windows Server 2012 R2 introduced the concept of dynamic witness and dynamic quorum to address this concern.) By default, the IP address of the Availability Group listener name will be registered on all of the DNS servers if the cluster is
    running Windows Server 2012 and higher (this is the RegisterAllProvidersIP property that Samir mentioned.) However, you need to flush the DNS cache on the SharePoint web and application servers and point them to the correct IP address on the DR server after
    failover. This is because the default TTL value of the Availability Group listener name is 20 minutes. 
    It is important to define your DR strategies and objectives when designing the architecture to make sure that the solution will meet your goals. This will also help you automate some of the processes in the DR data center when failover or a disaster occurs.
    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog |
    Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course

  • SAP BWA 2 node high availability

    Hi All
    My Customer uses 2 node(48GB each) active SAP BWA for their production system.
    As this customer want High Availability for this BWA. He want to change it to 1 node active + 1 node stand by
    It uses OCFS2 for cluster file system.
    Is it possible for this Customer to change from 2 active to 1 active + 1 stand by ?
    My best regards,
    Nam Hee Jae

    Hi Kamal,
    Thanks and appreciate your reply, but I still wonder how the fail-over happen with 1 active + 1 stand by. Does the watchdog or fail-over mechanism working even in 1 active + 1 stand by ?
    Normally, 3 system is required in distributed system to prevent split brain situation.
    I want to know if their is any limitation using 1 active + 1 stand by except the memory utilization of each Blade.
    My best regards,
    Nam Hee

  • High Availibility

    Hello Everyone,
    We are implementing the entire Identity and Access Management Suite in High Availability.
    We have 2 boxes for OID & OVD AND 2 for OAM.
    We have Apache webserver on which we have a webgate, which would be configured for reverse proxy.
    My question here is, for HA in regards to Apache WebServer:
    Should I only have one Apache webserver in the HA or should I have two of those for those 2 boxes of OAM ?
    I am fairly new to this technology, so please bear with me.
    Thanks.

    Hey,
    Take a look at this picture(Figure 5-1 Oracle Access Manager in Active-Active Topology) of OAM High Availability documentation, it should be answer your main question:
    This link: http://download.oracle.com/docs/cd/B28196_01/core.1014/b28186/coreid_topo.htm.
    If you need more, I have some topologies examples and we can discuss about your particular situation. Example: Zone1(2 servers with WebCache[reverse proxy]) ; Zone2(2 servers with OAM) ; Zone3(2 servers with OID).
    regards,

  • BPEL High Availability for various adapter configurations

    Hello,
    I have created a BPEL process that uses DBAdapter to poll for inserts into a table using a sequence file on the file system. This is one of the options for the DBAdapter. This adapter is called from an "receive" activity.
    My understanding is that a bpel internal process schedules the adapter to check the sequence file at intervals. When the sequence value is read a query is executed to determine if there are inserts/updates. If so, a new process instance is created.
    Now, how would this work in a HA situation? (Assume a LB in front of two bpel instances with oracle http server (ohs))
    Are there two processes polling the sequence file, one in each bpel instance ?
    Are the requests funnelled through the Load Balancer address ? (In effect being made from the application server tier back out to the load balancer at the "front").
    This is probably a specific example of a general question about event-driven processes and high availability.
    Thanks in advance, this important for a customer who has a large volume of transactions that require multiple nodes to manage the load and will be using FileAdapter and DBAdapter to receive the events.

    No answer

  • Oracle Linux High Availability (HA)

    We would like to employ High Availability (HA) on Oracle Linux in order to provide solid service. How can we achieve this? What software do we need to install and where to start? We want HA not only for middle tier but all kind of software running on the server.

    If you cannot make a decision based on technical aspects, perhaps it will help to make a decision considering other aspects:
    - what product or service are you trying to provide?
    - what is your technical background?
    - what is your budget?
    - what are you planning for the future?
    I have not seen any useful general review or comparison of cluster products and there are several major players on the market. The situation is obviously complex and the right product depends on the product or service you are planning to provide. If you are ever thinking about using an Oracle database product, it would be foolish not to go for Oracle Clusterware.
    I think you should also very much consider virtualization and HA. Again, if you are planning to provide Oracle services, Oracle VM Server for x86 might be your best option, which is also a free product and designed for a production environment.
    In my humble opinion, Oracle products are generally complex and not necessarily the most admin or user-friendly solutions, but you will find a lot of support and as far as I'm aware, no other product will provide you a better cost of ownership than Oracle Linux and Oracle VM Server, which is zero.

  • ASA 5550 failover configuration

    I have two identical ASA 5550 firewalls that I need to set up for Active/Standby failover so I can then upgrade them with zero downtime.  I am running them in single, routed mode so I would have to configure failover for Active/Standby.  Can I do a cable-based configuration? The documentation states that is only available on the PIX 500 Security Appliance.  Going through the Support Community forums it appears I can.  Who is right?  If I can do cable-based configuration do I have to turn off the secondary ASA to do the inital configuration?  Thanks much.

    Hello James,
    Yes, you can do cable-based (if you mean connect the devices via a cable without a switch.. That will not be a problem)
    Cisco recommends use a switch between the units for troubleshooting purposes but it's not a MUST.
    Configuration wise, same procesure nothing different so just follow the regular process.
    For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
    Any question contact me at [email protected]
    Cheers,
    Julio Carvajal Segura

  • AGPM High Availability / Fault Tolerance

    I’m looking for any informations about Advanced Group Policy Management (AGPM) High Availability / Fault Tolerance.
    The most interesting is that, in introduction for AGPM Planning Guide is described section about
    Planning for AGPM high-availability and improved fault tolerance, but content not exists.
    Microsoft MVP: Virtual Machine | http://blog.porowski.pro |
    http://VirtualizationGeek.PL

    Hi,
    You may type the key words into the bing of TechNet website to search for the information you need. According to my search,
    the following two links inlcude the detailed information regarding AGPM. But less information regarding AGPM High Availability / Fault Tolerance can be found from TechNet website.
    Advanced Group Policy Management 4.0 Documents
     http://www.microsoft.com/downloads/en/details.aspx?FamilyID=58FD6CDA-0210-4DA0-91D2-8C3CC2817DF8&displaylang=en 
    Advanced Group Policy Management
     http://technet.microsoft.com/en-us/library/dd420466.aspx 
    Based on the current situation, I will also submit a feedback to Microsoft through our internal channel and requst more contents regarding
    AGPM High Availability / Fault Tolerance to be published. While we cannot guarantee that these contents will be added, we would like to ensure you that we will make every effort to see that they do.
    Arthur Li
     TechNet Subscriber Support 
    in forum
    If you have any feedback on our support, please contact
     [email protected] . 
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Advice Requested - High Availability WITHOUT Failover Clustering

    We're creating an entirely new Hyper-V virtualized environment on Server 2012 R2.  My question is:  Can we accomplish high availability WITHOUT using failover clustering?
    So, I don't really have anything AGAINST failover clustering, and we will happily use it if it's the right solution for us, but to be honest, we really don't want ANYTHING to happen automatically when it comes to failover.  Here's what I mean:
    In this new environment, we have architected 2 identical, very capable Hyper-V physical hosts, each of which will run several VMs comprising the equivalent of a scaled-back version of our entire environment.  In other words, there is at least a domain
    controller, multiple web servers, and a (mirrored/HA/AlwaysOn) SQL Server 2012 VM running on each host, along with a few other miscellaneous one-off worker-bee VMs doing things like system monitoring.  The SQL Server VM on each host has about 75% of the
    physical memory resources dedicated to it (for performance reasons).  We need pretty much the full horsepower of both machines up and going at all times under normal conditions.
    So now, to high availability.  The standard approach is to use failover clustering, but I am concerned that if these hosts are clustered, we'll have the equivalent of just 50% hardware capacity going at all times, with full failover in place of course
    (we are using an iSCSI SAN for storage).
    BUT, if these hosts are NOT clustered, and one of them is suddenly switched off, experiences some kind of catastrophic failure, or simply needs to be rebooted while applying WSUS patches, the SQL Server HA will fail over (so all databases will remain up
    and going on the surviving VM), and the environment would continue functioning at somewhat reduced capacity until the failed host is restarted.  With this approach, it seems to me that we would be running at 100% for the most part, and running at 50%
    or so only in the event of a major failure, rather than running at 50% ALL the time.
    Of course, in the event of a catastrophic failure, I'm also thinking that the one-off worker-bee VMs could be replicated to the alternate host so they could be started on the surviving host if needed during a long-term outage.
    So basically, I am very interested in the thoughts of others with experience regarding taking this approach to Hyper-V architecture, as it seems as if failover clustering is almost a given when it comes to best practices and high availability.  I guess
    I'm looking for validation on my thinking.
    So what do you think?  What am I missing or forgetting?  What will we LOSE if we go with a NON-clustered high-availability environment as I've described it?
    Thanks in advance for your thoughts!

    Udo -
    Yes your responses are very helpful.
    Can we use the built-in Server 2012 iSCSI Target Server role to convert the local RAID disks into an iSCSI LUN that the VMs could access?  Or can that not run on the same physical box as the Hyper-V host?  I guess if the physical box goes down
    the LUN would go down anyway, huh?  Or can I cluster that role (iSCSI target) as well?  If not, do you have any other specific product suggestions I can research, or do I just end up wasting this 12TB of local disk storage?
    - Morgan
    That's a bad idea. First of all Microsoft iSCSI target is slow (it's non-cached @ server side). So if you really decided to use dedicated hardware for storage (maybe you do have a reason I don't know...) and if you're fine with your storage being a single
    point of failure (OK, maybe your RTOs and RPOs are fair enough) then at least use SMB share. SMB at least does cache I/O on both client and server sides and also you can use Storage Spaces as a back end of it (non-clustered) so read "write back flash cache
    for cheap". See:
    What's new in iSCSI target with Windows Server 2012 R2
    http://technet.microsoft.com/en-us/library/dn305893.aspx
    Improved optimization to allow disk-level caching
    Updated
    iSCSI Target Server now sets the disk cache bypass flag on a hosting disk I/O, through Force Unit Access (FUA), only when the issuing initiator explicitly requests it. This change can potentially improve performance.
    Previously, iSCSI Target Server would always set the disk cache bypass flag on all I/O’s. System cache bypass functionality remains unchanged in iSCSI Target Server; for instance, the file system cache on the target server is always bypassed.
    Yes you can cluster iSCSI target from Microsoft but a) it would be SLOW as there would be only active-passive I/O model (no real use from MPIO between multiple hosts) and b) that would require a shared storage for Windows Cluster. What for? Scenario was
    usable with a) there was no virtual FC so guest VM cluster could not use FC LUs and b) there was no shared VHDX so SAS could not be used for guest VM cluster as well. Now both are present so scenario is useless: just export your existing shared storage without
    any Microsoft iSCSI target and you'll be happy. For references see:
    MSFT iSCSI Target in HA mode
    http://technet.microsoft.com/en-us/library/gg232621(v=ws.10).aspx
    Cluster MSFT iSCSI Target with SAS back end
    http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
    Guest
    VM Cluster Storage Options
    http://technet.microsoft.com/en-us/library/dn440540.aspx
    Storage options
    The following tables lists the storage types that you can use to provide shared storage for a guest cluster.
    Storage Type
    Description
    Shared virtual hard disk
    New in Windows Server 2012 R2, you can configure multiple virtual machines to connect to and use a single virtual hard disk (.vhdx) file. Each virtual machine can access the virtual hard disk just like servers
    would connect to the same LUN in a storage area network (SAN). For more information, see Deploy a Guest Cluster Using a Shared Virtual Hard Disk.
    Virtual Fibre Channel
    Introduced in Windows Server 2012, virtual Fibre Channel enables you to connect virtual machines to LUNs on a Fibre Channel SAN. For more information, see Hyper-V
    Virtual Fibre Channel Overview.
    iSCSI
    The iSCSI initiator inside a virtual machine enables you to connect over the network to an iSCSI target. For more information, see iSCSI
    Target Block Storage Overviewand the blog post Introduction of iSCSI Target in Windows
    Server 2012.
    Storage requirements depend on the clustered roles that run on the cluster. Most clustered roles use clustered storage, where the storage is available on any cluster node that runs a clustered
    role. Examples of clustered storage include Physical Disk resources and Cluster Shared Volumes (CSV). Some roles do not require storage that is managed by the cluster. For example, you can configure Microsoft SQL Server to use availability groups that replicate
    the data between nodes. Other clustered roles may use Server Message Block (SMB) shares or Network File System (NFS) shares as data stores that any cluster node can access.
    Sure you can use third-party software to replicate 12TB of your storage between just a pair of nodes to create a fully fault-tolerant cluster. See (there's also a free offering):
    StarWind VSAN [Virtual SAN] for Hyper-V
    http://www.starwindsoftware.com/native-san-for-hyper-v-free-edition
    Product is similar to what VMware had just released for ESXi except it's selling for ~2 years so is mature :)
    There are other guys doing this say DataCore (more playing for Windows-based FC) and SteelEye (more about geo-cluster & replication). But you may want to give them a try.
    Hope this helped a bit :) 
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Maybe you are looking for