Per documentation:
  • Port density requirements to support fully redundant configurations and maximum SAN throughput for PS6x00 family: 4x 1GbE ports per controller = 8x 1GbE ports total
  • Disable QoS
  • Enable jumbo frames
  • All network devices should support LACP / LAG
 
 
There is an optional MPIO card that would enable this device to function with MPIO capability to connect to Windows Server. An alternate option is an iSCCI initiator. This is NIC Teaming that aggregate packets via multiple interfaces on the Server, that function has the following features:
  • Switch dependent: this mode only works with a switch that is capable of Etherchannel (also known as LACP, 802.13ad, link aggregation). Windows 2012 supports static teaming or Link Aggregation Control (LACP)
  • Switch independent: Outbound will be transmitted via multiple NICs, inbound via only 1 NIC. This is a good set-up for Web Servers
Here is some instructions on how to configure NIC bonding in Windows:
Configure NIC1 as the production IP address of the server: IP/Mask/Gateway/DNS
Configure NIC2 with IP/Mask of the SAN subnet, only – no Gateway / DNS entry on this interface!
Use “iSCCI initiator” to bind these NICs within Windows to connect to SAN
 
Recovery Time Objective (RTO)
Recovery Point Objective (RPO)
 
Setting up Replication:
Preliminary steps:
Collect group name, IP address, amount of dedicated space, authentication password of replication partner machine
 
Step 1 – Configure groups
– Click on primary group >> click Replication Partners >> Configure partner >> enter Group Name, IP, contact info >> provide password that each group uses to access the other >> leave Delegated field empty >> click Finish
– Click on the secondary group >> repeat previous steps
 
Step 2 – Configure replication on a volume
– click on primary group >> select a volume and click Configure replication >> make any settings change, use default 200% reserve setting >> next >> select to keep a failback snapshot at Advanced Settings >> click Finish >> Yes to create replica immediately >> check progress at Group Monitoring, Replication screen
 
Alternative, using CLI
> vol show  (display current volumes)
> volume select {volume_name} replication enable {partner_name} local-rep-reserve 200% keep-failback
> volume select {volume_name} replication create-replica {partner_name}
> volume select {volume_name} replication show
 
Step 3 – Create Replication Schedule
select primary group >> select volume >> click Create Schedule >> enter name of schedule and choose frequency >> review Summary Screen >> click Finish
 
Step 4 – Monitor Replicas
click Volumes >> {volume_name} >> Replication tab
click Replication partners >> {partner_name} >> Inbound tab
 
Recovery – promoting Replica Set to a become Recovery Volume
click Replication Partners >> {partner_name} >> click Promote to volume >> Yes to pause inbound replication >> choose defaults by clicking Next, Next
click Volumes >> verify {volume_name} with special icon next to it as Recovery volume
 
When primary group and original volume are back online, replicate data back to primary group with these steps:
on Secondary group, select the recovery volume >> click Replicate to partner >> enter credentials >> OK >> observe that primary group demotes original volume to failback replica, and secondary group replicates the recovery volume to the primary group
Categories: